diff --git a/ai-data/generative-apis/api-cli/understanding-errors.mdx b/ai-data/generative-apis/api-cli/understanding-errors.mdx index 2f8d964613..09ef5b8381 100644 --- a/ai-data/generative-apis/api-cli/understanding-errors.mdx +++ b/ai-data/generative-apis/api-cli/understanding-errors.mdx @@ -27,13 +27,13 @@ If the response code is not within the 2xx range, the response will contain an e Below are usual HTTP error codes: - 400 - **Bad Request**: The format or content of your payload is incorrect. The body may be too large, or fail to parse, or the content-type is mismatched. -- 401 - **Unauthorized**: The `authorization` header is missing. Find required headers in [this page](/ai-data/generative-apis/api-cli/using-generative-apis/) -- 403 - **Forbidden**: Your API key does not exist or does not have the necessary permissions to access the requested resource. Find required permission sets in [this page](/ai-data/generative-apis/api-cli/using-generative-apis/) +- 401 - **Unauthorized**: The `authorization` header is missing. Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/) +- 403 - **Forbidden**: Your API key does not exist or does not have the necessary permissions to access the requested resource. Find required permission sets in [this page](/generative-apis/api-cli/using-generative-apis/) - 404 - **Route Not Found**: The requested resource could not be found. Check your request is being made to the correct endpoint. - 422 - **Model Not Found**: The `model` key is present in the request payload, but the corresponding model is not found. - 422 - **Missing Model**: The `model` key is missing from the request payload. -- 429 - **Too Many Requests**: You are exceeding your current quota for the requested model, calculated in requests per minute. Find rate limits on [this page](/ai-data/generative-apis/reference-content/rate-limits/) -- 429 - **Too Many Tokens**: You are exceeding your current quota for the requested model, calculated in tokens per minute. Find rate limits on [this page](/ai-data/generative-apis/reference-content/rate-limits/) +- 429 - **Too Many Requests**: You are exceeding your current quota for the requested model, calculated in requests per minute. Find rate limits on [this page](/generative-apis/reference-content/rate-limits/) +- 429 - **Too Many Tokens**: You are exceeding your current quota for the requested model, calculated in tokens per minute. Find rate limits on [this page](/generative-apis/reference-content/rate-limits/) - 500 - **API error**: An unexpected internal error has occurred within Scaleway's systems. If the issue persists, please [open a support ticket](https://console.scaleway.com/support/tickets/create). For streaming responses via SSE, 5xx errors may occur after a 200 response has been returned. \ No newline at end of file diff --git a/ai-data/generative-apis/api-cli/using-chat-api.mdx b/ai-data/generative-apis/api-cli/using-chat-api.mdx index 2d3bdb30c7..2fe2f11cc5 100644 --- a/ai-data/generative-apis/api-cli/using-chat-api.mdx +++ b/ai-data/generative-apis/api-cli/using-chat-api.mdx @@ -48,7 +48,7 @@ curl --request POST \ ## Headers -Find required headers in [this page](/ai-data/generative-apis/api-cli/using-generative-apis/). +Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/). ## Body @@ -69,12 +69,12 @@ Our chat API is OpenAI compatible. Use OpenAI’s [API reference](https://platfo - stream - stream_options - presence_penalty -- [response_format](/ai-data/generative-apis/how-to/use-structured-outputs) +- [response_format](/generative-apis/how-to/use-structured-outputs) - logprobs - stop - seed -- [tools](/ai-data/generative-apis/how-to/use-function-calling) -- [tool_choice](/ai-data/generative-apis/how-to/use-function-calling) +- [tools](/generative-apis/how-to/use-function-calling) +- [tool_choice](/generative-apis/how-to/use-function-calling) ### Unsupported parameters @@ -88,6 +88,6 @@ If you have a use case requiring one of these unsupported parameters, please [co ## Going further -1. [Python code examples](/ai-data/generative-apis/how-to/query-language-models/#querying-language-models-via-api) to query text models using Scaleway's Chat API -2. [How to use structured outputs](/ai-data/generative-apis/how-to/use-structured-outputs) with the `response_format` parameter -3. [How to use function calling](/ai-data/generative-apis/how-to/use-function-calling) with `tools` and `tool_choice` \ No newline at end of file +1. [Python code examples](/generative-apis/how-to/query-language-models/#querying-language-models-via-api) to query text models using Scaleway's Chat API +2. [How to use structured outputs](/generative-apis/how-to/use-structured-outputs) with the `response_format` parameter +3. [How to use function calling](/generative-apis/how-to/use-function-calling) with `tools` and `tool_choice` \ No newline at end of file diff --git a/ai-data/generative-apis/api-cli/using-embeddings-api.mdx b/ai-data/generative-apis/api-cli/using-embeddings-api.mdx index 0c36e50244..e81b4e0875 100644 --- a/ai-data/generative-apis/api-cli/using-embeddings-api.mdx +++ b/ai-data/generative-apis/api-cli/using-embeddings-api.mdx @@ -32,7 +32,7 @@ curl --request POST \ ## Headers -Find required headers in [this page](/ai-data/generative-apis/api-cli/using-generative-apis/). +Find required headers in [this page](/generative-apis/api-cli/using-generative-apis/). ## Body @@ -53,5 +53,5 @@ Our embeddings API is OpenAI compatible. Use OpenAI’s [API reference](https:// If you have a use case requiring one of these unsupported parameters, please [contact us via Slack](https://slack.scaleway.com/) on #ai channel. - Check our [Python code examples](/ai-data/generative-apis/how-to/query-embedding-models/#querying-embedding-models-via-api) to query embedding models using Scaleway's Embeddings API. + Check our [Python code examples](/generative-apis/how-to/query-embedding-models/#querying-embedding-models-via-api) to query embedding models using Scaleway's Embeddings API. \ No newline at end of file diff --git a/ai-data/generative-apis/api-cli/using-generative-apis.mdx b/ai-data/generative-apis/api-cli/using-generative-apis.mdx index 7b67c72e18..1181ad3608 100644 --- a/ai-data/generative-apis/api-cli/using-generative-apis.mdx +++ b/ai-data/generative-apis/api-cli/using-generative-apis.mdx @@ -13,7 +13,7 @@ dates: ## Access -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) is needed. +- A valid [API key](/iam/how-to/create-api-keys/) is needed. ## Authentication @@ -51,11 +51,11 @@ curl --request POST \ ## Permissions -Permissions define the actions a user or an application can perform on Scaleway Generative APIs. They are managed using Scaleway’s [Identity and Access Management](/identity-and-access-management/iam/quickstart/) interface. +Permissions define the actions a user or an application can perform on Scaleway Generative APIs. They are managed using Scaleway’s [Identity and Access Management](/iam/quickstart/) interface. -[Owner](/identity-and-access-management/iam/concepts/#owner) status or certain [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allow you to perform actions in the intended Organization. +[Owner](/iam/concepts/#owner) status or certain [IAM permissions](/iam/concepts/#permission) allow you to perform actions in the intended Organization. -Querying AI models hosted by Scaleway Generative APIs will require any of the following [permission sets](/identity-and-access-management/iam/concepts/#permission-set): +Querying AI models hosted by Scaleway Generative APIs will require any of the following [permission sets](/iam/concepts/#permission-set): - **GenerativeApisModelAccess** - **GenerativeApisFullAccess** diff --git a/ai-data/generative-apis/how-to/query-code-models.mdx b/ai-data/generative-apis/how-to/query-code-models.mdx index b9eb9b492f..b81e329d51 100644 --- a/ai-data/generative-apis/how-to/query-code-models.mdx +++ b/ai-data/generative-apis/how-to/query-code-models.mdx @@ -13,21 +13,21 @@ dates: Scaleway's Generative APIs service allows users to interact with powerful code models hosted on the platform. -Code models are inherently [language models](/ai-data/generative-apis/how-to/query-language-models/) specialized in **understanding code**, **generating code** and **fixing code**. +Code models are inherently [language models](/generative-apis/how-to/query-language-models/) specialized in **understanding code**, **generating code** and **fixing code**. As such, they will be available through the same interfaces as language models: -- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/ai-data/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. -- Via the [Chat API](/ai-data/generative-apis/how-to/query-language-models/#querying-language-models-via-api) +- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. +- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api) -For more information on how to query language models, read [our dedicated documentation](/ai-data/generative-apis/how-to/query-language-models/). +For more information on how to query language models, read [our dedicated documentation](/generative-apis/how-to/query-language-models/). Code models are also ideal AI assistants when **added to IDEs** (integrated development environments). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - An IDE such as Visual Studio Code or JetBrains ## Install Continue in your IDE diff --git a/ai-data/generative-apis/how-to/query-embedding-models.mdx b/ai-data/generative-apis/how-to/query-embedding-models.mdx index 7a5dd8e6f1..fd2e4345b6 100644 --- a/ai-data/generative-apis/how-to/query-embedding-models.mdx +++ b/ai-data/generative-apis/how-to/query-embedding-models.mdx @@ -19,8 +19,8 @@ The embedding service is OpenAI compatible. Refer to OpenAI's [embedding documen - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - Python 3.7+ installed on your system ## Querying embedding models via API @@ -72,8 +72,8 @@ This code sends input text to the `bge-multilingual-gemma2` embedding model and The following parameters can be adjusted to influence the output of the embedding model: - **`input`** (string or array of strings): The text or data you want to convert into vectors. -- **`model`** (string): The specific embedding model to use, find all our [supported models](/ai-data/generative-apis/reference-content/supported-models). +- **`model`** (string): The specific embedding model to use, find all our [supported models](/generative-apis/reference-content/supported-models). - If you encounter an error such as "Forbidden 403" refer to the [API documentation](/ai-data/generative-apis/api-cli/understanding-errors) for troubleshooting tips. + If you encounter an error such as "Forbidden 403" refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips. diff --git a/ai-data/generative-apis/how-to/query-language-models.mdx b/ai-data/generative-apis/how-to/query-language-models.mdx index ab40d37398..237c0a9f93 100644 --- a/ai-data/generative-apis/how-to/query-language-models.mdx +++ b/ai-data/generative-apis/how-to/query-language-models.mdx @@ -14,14 +14,14 @@ dates: Scaleway's Generative APIs service allows users to interact with powerful language models hosted on the platform. There are several ways to interact with language models: -- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/ai-data/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. -- Via the [Chat API](/ai-data/generative-apis/how-to/query-language-models/#querying-language-models-via-api) +- The Scaleway [console](https://console.scaleway.com) provides complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. +- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - Python 3.7+ installed on your system ## Accessing the Playground @@ -41,7 +41,7 @@ The web playground displays. ## Querying language models via API -The [Chat API](/ai-data/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations. +The [Chat API](/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations. You can query the models programmatically using your favorite tools or languages. In the following example, we will use the OpenAI Python client. @@ -114,7 +114,7 @@ The following parameters will influence the output of the model: - **`stop`**: A string or list of strings where the model will stop generating further tokens. This is useful for controlling the end of the output. - If you encounter an error such as "Forbidden 403" refer to the [API documentation](/ai-data/generative-apis/api-cli/understanding-errors) for troubleshooting tips. + If you encounter an error such as "Forbidden 403" refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips. ## Streaming diff --git a/ai-data/generative-apis/how-to/query-vision-models.mdx b/ai-data/generative-apis/how-to/query-vision-models.mdx index deea91960f..be6d5321d3 100644 --- a/ai-data/generative-apis/how-to/query-vision-models.mdx +++ b/ai-data/generative-apis/how-to/query-vision-models.mdx @@ -18,14 +18,14 @@ Scaleway's Generative APIs service allows users to interact with powerful vision There are several ways to interact with vision models: -- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/ai-data/generative-apis/how-to/query-vision-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. -- Via the [Chat API](/ai-data/generative-apis/how-to/query-vision-models/#querying-vision-models-via-the-api) +- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/generative-apis/how-to/query-vision-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. +- Via the [Chat API](/generative-apis/how-to/query-vision-models/#querying-vision-models-via-the-api) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - Python 3.7+ installed on your system ## Accessing the playground @@ -45,7 +45,7 @@ The web playground displays. ## Querying vision models via the API -The [Chat API](/ai-data/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations. +The [Chat API](/generative-apis/api-cli/using-chat-api/) is an OpenAI-compatible REST API for generating and manipulating conversations. You can query the vision models programmatically using your favorite tools or languages. Vision models take both text and images as inputs. @@ -173,7 +173,7 @@ The following parameters will influence the output of the model: - **`stop`**: A string or list of strings where the model will stop generating further tokens. This is useful for controlling the end of the output. - If you encounter an error such as "Forbidden 403", refer to the [API documentation](/ai-data/generative-apis/api-cli/understanding-errors) for troubleshooting tips. + If you encounter an error such as "Forbidden 403", refer to the [API documentation](/generative-apis/api-cli/understanding-errors) for troubleshooting tips. ## Streaming diff --git a/ai-data/generative-apis/how-to/use-function-calling.mdx b/ai-data/generative-apis/how-to/use-function-calling.mdx index 054f0c0046..a9729433a0 100644 --- a/ai-data/generative-apis/how-to/use-function-calling.mdx +++ b/ai-data/generative-apis/how-to/use-function-calling.mdx @@ -19,13 +19,13 @@ Function calling allows a large language model (LLM) to interact with external t -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - Python 3.7+ installed on your system ## Supported models -All the [chat models](/ai-data/generative-apis/reference-content/supported-models/#chat-models) hosted by Scaleway support function calling. +All the [chat models](/generative-apis/reference-content/supported-models/#chat-models) hosted by Scaleway support function calling. ## Understanding function calling @@ -323,7 +323,7 @@ For more information about function calling and advanced implementations, refer - [OpenAI Function Calling Guide](https://platform.openai.com/docs/guides/function-calling) - [JSON Schema Specification](https://json-schema.org/specification) -- [Chat Completions API Reference](/ai-data/generative-apis/api-cli/using-chat-api/) +- [Chat Completions API Reference](/generative-apis/api-cli/using-chat-api/) Function calling significantly extends the capabilities of language models by allowing them to interact with external tools and APIs. diff --git a/ai-data/generative-apis/how-to/use-structured-outputs.mdx b/ai-data/generative-apis/how-to/use-structured-outputs.mdx index 143a47a225..e3d7bd6dba 100644 --- a/ai-data/generative-apis/how-to/use-structured-outputs.mdx +++ b/ai-data/generative-apis/how-to/use-structured-outputs.mdx @@ -15,18 +15,18 @@ dates: Structured outputs allow users to get consistent, machine-readable JSON format responses from language models. JSON, as a widely-used format, enables seamless integration with a variety of platforms and applications. Its interoperability is crucial for developers aiming to incorporate AI functionality into their current systems with minimal adjustments. -By specifying a response format when using the [Chat Completions API](/ai-data/generative-apis/api-cli/using-chat-api/), you can ensure that responses are returned in a JSON structure. +By specifying a response format when using the [Chat Completions API](/generative-apis/api-cli/using-chat-api/), you can ensure that responses are returned in a JSON structure. There are two main modes for generating JSON: **Object Mode** (schemaless) and **Schema Mode** (deterministic, structured output). There are several ways to interact with language models: -- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/ai-data/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. -- Via the [Chat API](/ai-data/generative-apis/how-to/query-language-models/#querying-language-models-via-api) +- The Scaleway [console](https://console.scaleway.com) provides a complete [playground](/generative-apis/how-to/query-language-models/#accessing-the-playground), aiming to test models, adapt parameters, and observe how these changes affect the output in real-time. +- Via the [Chat API](/generative-apis/how-to/query-language-models/#querying-language-models-via-api) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) for API authentication +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) for API authentication - Python 3.7+ installed on your system ## Types of structured outputs diff --git a/ai-data/generative-apis/index.mdx b/ai-data/generative-apis/index.mdx index af86e56846..bbd6030701 100644 --- a/ai-data/generative-apis/index.mdx +++ b/ai-data/generative-apis/index.mdx @@ -8,7 +8,7 @@ meta: productName="Generative APIs" productLogo="inference" description="Generative APIs provide access to pre-configured serverless endpoints of the most popular AI models, hosted in European data centers and priced per 1M tokens used." - url="/ai-data/generative-apis/quickstart" + url="/generative-apis/quickstart" label="Generative APIs Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to access, configure and use a Generative APIs endpoint in a few steps." label="View Quickstart" - url="/ai-data/generative-apis/quickstart/" + url="/generative-apis/quickstart/" /> diff --git a/ai-data/generative-apis/quickstart.mdx b/ai-data/generative-apis/quickstart.mdx index 83c320237e..b0248294b4 100644 --- a/ai-data/generative-apis/quickstart.mdx +++ b/ai-data/generative-apis/quickstart.mdx @@ -25,8 +25,8 @@ Hosted in European data centers and priced competitively per million tokens used - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A valid [API key](/iam/how-to/create-api-keys/) - Python 3.7+ installed on your system ## Start with the Generative APIs Playground @@ -59,7 +59,7 @@ pip install openai ## Configure and set your API key and service URL -1. Have your [API key](/identity-and-access-management/iam/how-to/create-api-keys/) ready or generate a new one from the Scaleway console. +1. Have your [API key](/iam/how-to/create-api-keys/) ready or generate a new one from the Scaleway console. 2. Use the following code in your Python script: ```py @@ -74,7 +74,7 @@ client = OpenAI( Make sure that you replace `` with the API key obtained from your Scaleway account. - It is recommended to store your API keys securely using environment variables or [secret management tools](/identity-and-access-management/secret-manager/) to prevent unauthorized access. + It is recommended to store your API keys securely using environment variables or [secret management tools](/secret-manager/) to prevent unauthorized access. ## Send your first API request @@ -106,4 +106,4 @@ This very simple example demonstrates how the Chat API can be used to generate c ## Going further -Now that you are familiar with the basics, explore the full potential of Generative APIs by customizing your API requests. Refer to our [How-to guides](/ai-data/generative-apis/how-to/) for more advanced features and usage. +Now that you are familiar with the basics, explore the full potential of Generative APIs by customizing your API requests. Refer to our [How-to guides](/generative-apis/how-to/) for more advanced features and usage. diff --git a/ai-data/generative-apis/reference-content/model-lifecycle.mdx b/ai-data/generative-apis/reference-content/model-lifecycle.mdx index d89c512141..1a0e6cff49 100644 --- a/ai-data/generative-apis/reference-content/model-lifecycle.mdx +++ b/ai-data/generative-apis/reference-content/model-lifecycle.mdx @@ -28,5 +28,5 @@ A model provided through Scaleway Generative APIs may be classified into one of We guarantee support for new models for at least 8 months starting from their regional launch. Customers will receive a 3-month notice before any model is marked as End-of-Life (EOL). - Following the EOL date, information regarding the model version remains exclusively available on our [dedicated documentation page](/ai-data/generative-apis/reference-content/supported-models/#deprecated-models). + Following the EOL date, information regarding the model version remains exclusively available on our [dedicated documentation page](/generative-apis/reference-content/supported-models/#deprecated-models). diff --git a/ai-data/generative-apis/reference-content/supported-models.mdx b/ai-data/generative-apis/reference-content/supported-models.mdx index 641dd14465..cc31b9a562 100644 --- a/ai-data/generative-apis/reference-content/supported-models.mdx +++ b/ai-data/generative-apis/reference-content/supported-models.mdx @@ -15,7 +15,7 @@ dates: This service is free while in beta. [Specific terms and conditions](https://www.scaleway.com/en/contracts/) apply. -Our [Chat API](/ai-data/generative-apis/how-to/query-language-models) has built-in support for the most popular instruct models. +Our [Chat API](/generative-apis/how-to/query-language-models) has built-in support for the most popular instruct models. ## Chat models @@ -39,7 +39,7 @@ Our [Chat API](/ai-data/generative-apis/how-to/query-language-models) has built- ## Embedding models -Our [Embeddings API](/ai-data/generative-apis/how-to/query-embedding-models) provides built-in support for the following models, hosted in Scaleway data centers, available via serverless endpoints. +Our [Embeddings API](/generative-apis/how-to/query-embedding-models) provides built-in support for the following models, hosted in Scaleway data centers, available via serverless endpoints. | Provider | Model string | Model size | Embedding dimension | Context window | License | Model card | |-----------------|-----------------|-----------------|-----------------|-----------------|-----------------|-----------------| @@ -51,7 +51,7 @@ Our [Embeddings API](/ai-data/generative-apis/how-to/query-embedding-models) pro ## Deprecated models -Scaleway's model lifecyle is introduced on our [dedicated documentation page](/ai-data/generative-apis/reference-content/model-lifecycle/). +Scaleway's model lifecyle is introduced on our [dedicated documentation page](/generative-apis/reference-content/model-lifecycle/). | Provider | Model string | EOL date |-----------------|-----------------|-----------------| diff --git a/ai-data/generative-apis/troubleshooting/fixing-common-issues.mdx b/ai-data/generative-apis/troubleshooting/fixing-common-issues.mdx index 9db31bacb9..3a9ecd1b5a 100644 --- a/ai-data/generative-apis/troubleshooting/fixing-common-issues.mdx +++ b/ai-data/generative-apis/troubleshooting/fixing-common-issues.mdx @@ -23,19 +23,19 @@ Below are common issues that you may encounter when using Generative APIs, their - [Ask our support](https://console.scaleway.com/support/tickets/create) to raise your quota - Smooth out your API requests rate by limiting the number of API requests you perform in parallel - Reduce the size of the input or output tokens processed by your API requests -- Use [Managed Inference](/ai-data/managed-inference/), where these quota do not apply (your throughput will be only limited by the amount of Inference Deployment your provision) +- Use [Managed Inference](/managed-inference/), where these quota do not apply (your throughput will be only limited by the amount of Inference Deployment your provision) ## 504: Gateway Timeout ### Cause -- The query is too long to process (even if context-length stays [between supported context window and maximum tokens](https://www.scaleway.com/en/docs/ai-data/generative-apis/reference-content/supported-models/)) +- The query is too long to process (even if context-length stays [between supported context window and maximum tokens](https://www.scaleway.com/en/docs/generative-apis/reference-content/supported-models/)) - The model goes into an infinite loop while processing the input (which is a known structural issue with several AI models) ### Solution - Set a stricter **maximum token limit** to prevent overly long responses. - Reduce the size of the input tokens, or split the input into multiple API requests. -- Use [Managed Inference](/ai-data/managed-inference/), where no query timeout is enforced. +- Use [Managed Inference](/managed-inference/), where no query timeout is enforced. ## Structured output (e.g., JSON) is not working correctly @@ -46,7 +46,7 @@ Below are common issues that you may encounter when using Generative APIs, their ### Solution - Ensure the proper field `"response_format"` is used in the query. - Provide a JSON schema in the request to guide the model's structured output. -- Refer to the [documentation on structured outputs](/ai-data/generative-apis/how-to/use-structured-outputs/) for examples and additional guidance. +- Refer to the [documentation on structured outputs](/generative-apis/how-to/use-structured-outputs/) for examples and additional guidance. ## Multiple "role": "user" successive messages diff --git a/ai-data/managed-inference/concepts.mdx b/ai-data/managed-inference/concepts.mdx index 48ae79f096..8053abf1a9 100644 --- a/ai-data/managed-inference/concepts.mdx +++ b/ai-data/managed-inference/concepts.mdx @@ -13,7 +13,7 @@ categories: --- ## Allowed IPs -Allowed IPs are single IPs or IP blocks that have the [required permissions to remotely access a deployment](/ai-data/managed-inference/how-to/manage-allowed-ips/). They allow you to define which host and networks can connect to your Managed Inference endpoints. You can add, edit, or delete allowed IPs. In the absence of allowed IPs, all IP addresses are allowed by default. +Allowed IPs are single IPs or IP blocks that have the [required permissions to remotely access a deployment](/managed-inference/how-to/manage-allowed-ips/). They allow you to define which host and networks can connect to your Managed Inference endpoints. You can add, edit, or delete allowed IPs. In the absence of allowed IPs, all IP addresses are allowed by default. Access control is handled directly at the network level by Load Balancers, making the filtering more efficient and universal and relieving the Managed Inference server from this task. diff --git a/ai-data/managed-inference/how-to/create-deployment.mdx b/ai-data/managed-inference/how-to/create-deployment.mdx index f6e3fe4695..d44fea3e22 100644 --- a/ai-data/managed-inference/how-to/create-deployment.mdx +++ b/ai-data/managed-inference/how-to/create-deployment.mdx @@ -14,12 +14,12 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click the **AI & Data** section of the [Scaleway console](https://console.scaleway.com/), and select **Managed Inference** from the side menu to access the Managed Inference dashboard. 2. Click **Deploy a model** to launch the model deployment wizard. 3. Provide the necessary information: - - Select the desired model and quantization to use for your deployment [from the available options](/ai-data/managed-inference/reference-content/) + - Select the desired model and quantization to use for your deployment [from the available options](/managed-inference/reference-content/) Some models may require acceptance of an end-user license agreement. If prompted, review the terms and conditions and accept the license accordingly. diff --git a/ai-data/managed-inference/how-to/delete-deployment.mdx b/ai-data/managed-inference/how-to/delete-deployment.mdx index 225064d5ad..524852df7b 100644 --- a/ai-data/managed-inference/how-to/delete-deployment.mdx +++ b/ai-data/managed-inference/how-to/delete-deployment.mdx @@ -18,8 +18,8 @@ Once you have finished your inference tasks you can delete your deployment. This - A Scaleway account logged into the [console](https://console.scaleway.com) - - A [Managed Inference deployment](/ai-data/managed-inference/quickstart/) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A [Managed Inference deployment](/managed-inference/quickstart/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Managed Inference** in the **AI & Data** section of the [Scaleway console](https://console.scaleway.com) side menu. A list of your deployments displays. 2. Choose a deployment either by clicking its name or selecting **More info** from the drop-down menu represented by the icon to access the deployment dashboard. diff --git a/ai-data/managed-inference/how-to/manage-allowed-ips.mdx b/ai-data/managed-inference/how-to/manage-allowed-ips.mdx index b455c05683..e3b991ab33 100644 --- a/ai-data/managed-inference/how-to/manage-allowed-ips.mdx +++ b/ai-data/managed-inference/how-to/manage-allowed-ips.mdx @@ -18,8 +18,8 @@ Allowed IPs restrict the IPs allowed to access your Managed Inference endpoints. - A Scaleway account logged into the [console](https://console.scaleway.com) - - A [Managed Inference deployment](/ai-data/managed-inference/quickstart/) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A [Managed Inference deployment](/managed-inference/quickstart/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization Allowed IP configuration is only available for public endpoints. diff --git a/ai-data/managed-inference/how-to/managed-inference-with-private-network.mdx b/ai-data/managed-inference/how-to/managed-inference-with-private-network.mdx index a686ed3149..c95c27cddf 100644 --- a/ai-data/managed-inference/how-to/managed-inference-with-private-network.mdx +++ b/ai-data/managed-inference/how-to/managed-inference-with-private-network.mdx @@ -20,8 +20,8 @@ Using a Private Network for communications between your Instances hosting your a - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - A [Managed Inference deployment](/ai-data/managed-inference/quickstart/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A [Managed Inference deployment](/managed-inference/quickstart/) ## How to attach a Private Network to a Managed Inference deployment @@ -30,7 +30,7 @@ Using a Private Network for communications between your Instances hosting your a 1. Click **Managed Inference** in the **AI & Data** section of the [Scaleway console](https://console.scaleway.com) side menu. A list of your deployments displays. 2. Navigate to the **Deployments** section and click **Create New Deployment**. The setup wizard displays. -3. During the [setup process](/ai-data/managed-inference/how-to/create-deployment/), you access the **Networking** section. +3. During the [setup process](/managed-inference/how-to/create-deployment/), you access the **Networking** section. 4. You will be asked to **attach a Private Network**. Two options are available: - **Attach an existing Private Network**: Select from the list of available networks. - **Add a new Private Network**: Choose this option if you need to create a new network. @@ -57,9 +57,9 @@ Using a Private Network for communications between your Instances hosting your a ## How to send inference requests in a Private Network -1. [Create an Instance](/compute/instances/how-to/create-an-instance/) which will host the inference application. +1. [Create an Instance](/instances/how-to/create-an-instance/) which will host the inference application. - Ensure the Instance [is attached to the same Private Network](/compute/instances/how-to/use-private-networks/) as your Managed Inference deployment. + Ensure the Instance [is attached to the same Private Network](/instances/how-to/use-private-networks/) as your Managed Inference deployment. 2. Download the TLS certificate from your Managed Inference deployment, available from the **Overview** tab in the **Endpoints** section. @@ -77,14 +77,14 @@ Using a Private Network for communications between your Instances hosting your a Ensure the destination directory exists and you have write permissions. Create the directory if necessary. -4. Connect to your Instance [using SSH](/compute/instances/how-to/connect-to-instance/). +4. Connect to your Instance [using SSH](/instances/how-to/connect-to-instance/). 5. Open a text editor and create a file named `inference.py` using the following command: ```bash nano inference.py ``` 6. Paste the following Python code sample into your `inference.py` file: - This script takes an example of a conversational task with a request sent to an [LLM through the Chat Completions API](/ai-data/managed-inference/reference-content/openai-compatibility/#chat-completions-api). + This script takes an example of a conversational task with a request sent to an [LLM through the Chat Completions API](/managed-inference/reference-content/openai-compatibility/#chat-completions-api). ```py import requests diff --git a/ai-data/managed-inference/how-to/monitor-deployment.mdx b/ai-data/managed-inference/how-to/monitor-deployment.mdx index 947d57b845..5ee59a2b22 100644 --- a/ai-data/managed-inference/how-to/monitor-deployment.mdx +++ b/ai-data/managed-inference/how-to/monitor-deployment.mdx @@ -13,13 +13,13 @@ categories: - ai-data --- -This documentation page shows you how to monitor your Managed Inference deployment with [Cockpit](/observability/cockpit/quickstart/). +This documentation page shows you how to monitor your Managed Inference deployment with [Cockpit](/cockpit/quickstart/). - A Scaleway account logged into the [console](https://console.scaleway.com) - - A [Managed Inference deployment](/ai-data/managed-inference/quickstart/) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - A [Managed Inference deployment](/managed-inference/quickstart/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to monitor your LLM dashboard @@ -27,5 +27,5 @@ This documentation page shows you how to monitor your Managed Inference deployme 2. Click a deployment name or > **More info** to access the deployment dashboard. 3. Click the **Monitoring** tab of your deployment. The Cockpit overview displays. 4. Click **Open Grafana metrics dashboard** to open your Cockpit's Grafana interface. -5. Authenticate with your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). The Grafana dashboard displays. -6. Select your Managed Inference dashboard from the [list of your managed dashboards](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) to visualize your metrics. \ No newline at end of file +5. Authenticate with your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). The Grafana dashboard displays. +6. Select your Managed Inference dashboard from the [list of your managed dashboards](/cockpit/how-to/access-grafana-and-managed-dashboards/) to visualize your metrics. \ No newline at end of file diff --git a/ai-data/managed-inference/index.mdx b/ai-data/managed-inference/index.mdx index f4b0b3f280..93bded41ae 100644 --- a/ai-data/managed-inference/index.mdx +++ b/ai-data/managed-inference/index.mdx @@ -8,7 +8,7 @@ meta: productName="Managed Inference" productLogo="inference" description="Effortlessly deploy AI models on a sovereign infrastructure, manage and scale inference with full data privacy. Start now with a simple interface for creating dedicated endpoints." - url="/ai-data/managed-inference/quickstart" + url="/managed-inference/quickstart" label="Managed Inference Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and delete a Managed Inference endpoint in a few steps." label="View Quickstart" - url="/ai-data/managed-inference/quickstart/" + url="/managed-inference/quickstart/" /> diff --git a/ai-data/managed-inference/quickstart.mdx b/ai-data/managed-inference/quickstart.mdx index 3b3f42038b..8e69a098b5 100644 --- a/ai-data/managed-inference/quickstart.mdx +++ b/ai-data/managed-inference/quickstart.mdx @@ -20,9 +20,9 @@ With Scaleway Managed Inference, you can easily deploy, manage, and scale LLMs w Here are some of the key features of Scaleway Managed Inference: * **Easy deployment**: Deploy state-of-the-art open weights LLMs with just a few clicks. Scaleway Managed Inference provides a simple and intuitive interface for generating dedicated endpoints. -* **Security**: Scaleway provides [a secure environment](/ai-data/managed-inference/reference-content/data-privacy-security-scaleway-ai-services/) to run your models. Our platform is built on top of a secure architecture, and we use state-of-the-art cloud security. -* **Complete data privacy**: [No storage](/ai-data/managed-inference/reference-content/data-privacy-security-scaleway-ai-services/#data-storage-policies) or third-party access to your data (prompt or responses), to ensure it remains exclusively yours. -* **Interoperability**: Scaleway Managed Inference was designed as a drop-in [replacement for the OpenAI APIs](/ai-data/managed-inference/reference-content/openai-compatibility/), for a seamless transition on your applications already using its libraries. +* **Security**: Scaleway provides [a secure environment](/managed-inference/reference-content/data-privacy-security-scaleway-ai-services/) to run your models. Our platform is built on top of a secure architecture, and we use state-of-the-art cloud security. +* **Complete data privacy**: [No storage](/managed-inference/reference-content/data-privacy-security-scaleway-ai-services/#data-storage-policies) or third-party access to your data (prompt or responses), to ensure it remains exclusively yours. +* **Interoperability**: Scaleway Managed Inference was designed as a drop-in [replacement for the OpenAI APIs](/managed-inference/reference-content/openai-compatibility/), for a seamless transition on your applications already using its libraries. This service is in beta. [Specific terms and conditions](https://www.scaleway.com/en/contracts/) apply. @@ -31,14 +31,14 @@ Here are some of the key features of Scaleway Managed Inference: - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Managed Inference deployment 1. Navigate to the **AI & Data** section of the [Scaleway console](https://console.scaleway.com/), and select **Managed Inference** from the side menu to access the Managed Inference dashboard. 2. Click **Create deployment** to launch the deployment creation wizard. 3. Provide the necessary information: - - Select the desired model and the quantization to use for your deployment [from the available options](/ai-data/managed-inference/reference-content/) + - Select the desired model and the quantization to use for your deployment [from the available options](/managed-inference/reference-content/) Some models may require acceptance of an end-user license agreement. If prompted, review the terms and conditions and accept the license accordingly. @@ -61,7 +61,7 @@ Managed Inference deployments have authentication enabled by default. As such, y 1. Click **Managed Inference** in the **AI & Data** section of the side menu. The Managed Inference dashboard displays. 2. Click next to the deployment you want to edit. The deployment dashboard displays. 3. Click **Generate key** in the **Deployment connection** section of the dashboard. The token creation wizard displays. -4. Fill in the [required information for API key creation](/identity-and-access-management/iam/how-to/create-api-keys/) and click **Generate API key**. +4. Fill in the [required information for API key creation](/iam/how-to/create-api-keys/) and click **Generate API key**. You have full control over authentication from the **Security** tab of your deployment. Authentication is enabled by default. @@ -74,7 +74,7 @@ Managed Inference deployments have authentication enabled by default. As such, y 3. Click the **Inference** tab. Code examples in various environments display. Copy and paste them into your code editor or terminal. - Prompt structure may vary from one model to another. Refer to the specific instructions for use in our [dedicated documentation](/ai-data/managed-inference/reference-content/). + Prompt structure may vary from one model to another. Refer to the specific instructions for use in our [dedicated documentation](/managed-inference/reference-content/). ## How to delete a deployment diff --git a/ai-data/managed-inference/reference-content/bge-multilingual-gemma2.mdx b/ai-data/managed-inference/reference-content/bge-multilingual-gemma2.mdx index 13e1d00ce1..3e51e1b013 100644 --- a/ai-data/managed-inference/reference-content/bge-multilingual-gemma2.mdx +++ b/ai-data/managed-inference/reference-content/bge-multilingual-gemma2.mdx @@ -61,7 +61,7 @@ curl https://.ifr.fr-par.scaleway.com/v1/embeddings \ }' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. ### Receiving Inference responses diff --git a/ai-data/managed-inference/reference-content/llama-3-70b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3-70b-instruct.mdx index 93c9fab280..1844efb25e 100644 --- a/ai-data/managed-inference/reference-content/llama-3-70b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3-70b-instruct.mdx @@ -65,7 +65,7 @@ curl -s \ --data '{"model":"meta/llama-3-70b-instruct:fp8", "messages":[{"role": "user","content": "Sing me a song about Xavier Niel"}], "max_tokens": 500, "top_p": 1, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -81,5 +81,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/llama-3-8b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3-8b-instruct.mdx index 39c71eee01..d4054e4097 100644 --- a/ai-data/managed-inference/reference-content/llama-3-8b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3-8b-instruct.mdx @@ -69,7 +69,7 @@ curl -s \ --data '{"model":"meta/llama-3-8b-instruct:fp8", "messages":[{"role": "user","content": "There is a llama in my garden, what should I do?"}], "max_tokens": 500, "top_p": 1, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -85,5 +85,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct.mdx index 08f9d8afb7..1117df6d61 100644 --- a/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct.mdx @@ -64,7 +64,7 @@ curl -s \ --data '{"model":"meta/llama-3.1-70b-instruct:fp8", "messages":[{"role": "user","content": "There is a llama in my garden, what should I do?"}], "max_tokens": 500, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -80,5 +80,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/llama-3.1-8b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3.1-8b-instruct.mdx index 34eba1c95e..0318375220 100644 --- a/ai-data/managed-inference/reference-content/llama-3.1-8b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3.1-8b-instruct.mdx @@ -65,7 +65,7 @@ curl -s \ --data '{"model":"meta/llama-3.1-8b-instruct:fp8", "messages":[{"role": "user","content": "There is a llama in my garden, what should I do?"}], "max_tokens": 500, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -81,5 +81,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct.mdx index 52b4e1eed6..c2528ef456 100644 --- a/ai-data/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct.mdx @@ -43,7 +43,7 @@ NVIDIA employed Reinforcement Learning from Human Feedback (RLHF) to fine-tune t ## Why is it useful? - As of October 2024, Llama 3.1 Nemotron 70B has achieved top rankings in multiple automatic alignment benchmarks. It boasts an overall score of 94.1 on RewardBench, with specific scores of 97.5 for chat performance and 98.1 in reasoning tasks. -- Just like with the original Llama 3.1, this model brings a context window up to 128K tokens and [supports tool calling](/ai-data/managed-inference/reference-content/function-calling-support). +- Just like with the original Llama 3.1, this model brings a context window up to 128K tokens and [supports tool calling](/managed-inference/reference-content/function-calling-support). - With 70 billion parameters, this model is highly capable of generating sophisticated, human-like responses in a wide range of applications, from casual chatbots to complex technical systems. ## How to use it @@ -61,7 +61,7 @@ curl -s \ --data '{"model":"meta/llama-3.1-nemotron-70b-instruct:fp8", "messages":[{"role": "user","content": "There is a llama in my garden, what should I do?"}], "max_tokens": 500, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -77,5 +77,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/llama-3.3-70b-instruct.mdx b/ai-data/managed-inference/reference-content/llama-3.3-70b-instruct.mdx index 07bea41d69..df9402482e 100644 --- a/ai-data/managed-inference/reference-content/llama-3.3-70b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/llama-3.3-70b-instruct.mdx @@ -36,7 +36,7 @@ meta/llama-3.3-70b-instruct:bf16 ## Model introduction -Released December 6, 2024, Meta’s Llama 3.3 70b is a fine-tune of the [Llama 3.1 70b](/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct/) model. +Released December 6, 2024, Meta’s Llama 3.3 70b is a fine-tune of the [Llama 3.1 70b](/managed-inference/reference-content/llama-3.1-70b-instruct/) model. This model is still text-only (text in/text out). However, Llama 3.3 was designed to approach the performance of Llama 3.1 405B on some applications. ## Why is it useful? @@ -59,7 +59,7 @@ curl -s \ --data '{"model":"meta/llama-3.3-70b-instruct:bf16", "messages":[{"role": "user","content": "There is a llama in my garden, what should I do?"}], "max_tokens": 500, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -75,5 +75,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/mistral-7b-instruct-v0.3.mdx b/ai-data/managed-inference/reference-content/mistral-7b-instruct-v0.3.mdx index d1686e6680..0e299bab0e 100644 --- a/ai-data/managed-inference/reference-content/mistral-7b-instruct-v0.3.mdx +++ b/ai-data/managed-inference/reference-content/mistral-7b-instruct-v0.3.mdx @@ -58,7 +58,7 @@ curl -s \ --data '{"model":"mistral/mistral-7b-instruct-v0.3:bf16", "messages":[{"role": "user","content": "Explain Public Cloud in a nutshell."}], "top_p": 1, "temperature": 0.7, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -74,5 +74,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/mistral-nemo-instruct-2407.mdx b/ai-data/managed-inference/reference-content/mistral-nemo-instruct-2407.mdx index 86fd086549..e7d8e3c2a2 100644 --- a/ai-data/managed-inference/reference-content/mistral-nemo-instruct-2407.mdx +++ b/ai-data/managed-inference/reference-content/mistral-nemo-instruct-2407.mdx @@ -64,7 +64,7 @@ curl -s \ --data '{"model":"mistral/mistral-nemo-instruct-2407:fp8", "messages":[{"role": "user","content": "Sing me a song about Xavier Niel"}], "top_p": 1, "temperature": 0.35, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -80,5 +80,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/mixtral-8x7b-instruct-v0.1.mdx b/ai-data/managed-inference/reference-content/mixtral-8x7b-instruct-v0.1.mdx index 7744171ca4..6a082ee588 100644 --- a/ai-data/managed-inference/reference-content/mixtral-8x7b-instruct-v0.1.mdx +++ b/ai-data/managed-inference/reference-content/mixtral-8x7b-instruct-v0.1.mdx @@ -60,7 +60,7 @@ curl -s \ --data '{"model":"mistral/mixtral-8x7b-instruct-v0.1:fp8", "messages":[{"role": "user","content": "Sing me a song about Scaleway"}], "max_tokens": 200, "top_p": 1, "temperature": 1, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -76,5 +76,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. diff --git a/ai-data/managed-inference/reference-content/molmo-72b-0924.mdx b/ai-data/managed-inference/reference-content/molmo-72b-0924.mdx index fc11e5f1af..b07a5c6283 100644 --- a/ai-data/managed-inference/reference-content/molmo-72b-0924.mdx +++ b/ai-data/managed-inference/reference-content/molmo-72b-0924.mdx @@ -84,7 +84,7 @@ curl -s \ }' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -145,7 +145,7 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the visual language model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. ## Frequently Asked Questions diff --git a/ai-data/managed-inference/reference-content/moshika-0.1-8b.mdx b/ai-data/managed-inference/reference-content/moshika-0.1-8b.mdx index 61e29e6efb..7cb82cd1e8 100644 --- a/ai-data/managed-inference/reference-content/moshika-0.1-8b.mdx +++ b/ai-data/managed-inference/reference-content/moshika-0.1-8b.mdx @@ -72,7 +72,7 @@ curl -i --http1.1 \ --url "https://.ifr.fr-par.scaleway.com/api/chat" ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. Authentication can be done using the `token` query parameter, which should be set to your IAM API key, if headers are not supported (e.g., in a browser). diff --git a/ai-data/managed-inference/reference-content/moshiko-0.1-8b.mdx b/ai-data/managed-inference/reference-content/moshiko-0.1-8b.mdx index 967d23d885..2796ca4150 100644 --- a/ai-data/managed-inference/reference-content/moshiko-0.1-8b.mdx +++ b/ai-data/managed-inference/reference-content/moshiko-0.1-8b.mdx @@ -71,7 +71,7 @@ curl -i --http1.1 \ --url "https://.ifr.fr-par.scaleway.com/api/chat" ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. Authentication can be done using the `token` query parameter, which should be set to your IAM API key, if headers are not supported (e.g., in a browser). diff --git a/ai-data/managed-inference/reference-content/pixtral-12b-2409.mdx b/ai-data/managed-inference/reference-content/pixtral-12b-2409.mdx index 85fca68626..2c22572c72 100644 --- a/ai-data/managed-inference/reference-content/pixtral-12b-2409.mdx +++ b/ai-data/managed-inference/reference-content/pixtral-12b-2409.mdx @@ -87,7 +87,7 @@ curl -s \ }' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -146,7 +146,7 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the visual language model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. ## Frequently Asked Questions diff --git a/ai-data/managed-inference/reference-content/qwen2.5-coder-32b-instruct.mdx b/ai-data/managed-inference/reference-content/qwen2.5-coder-32b-instruct.mdx index d53b6de176..582ffcfb98 100644 --- a/ai-data/managed-inference/reference-content/qwen2.5-coder-32b-instruct.mdx +++ b/ai-data/managed-inference/reference-content/qwen2.5-coder-32b-instruct.mdx @@ -74,5 +74,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/ai-data/managed-inference/reference-content/sentence-t5-xxl.mdx b/ai-data/managed-inference/reference-content/sentence-t5-xxl.mdx index bc4bb03d51..bdb962da0e 100644 --- a/ai-data/managed-inference/reference-content/sentence-t5-xxl.mdx +++ b/ai-data/managed-inference/reference-content/sentence-t5-xxl.mdx @@ -62,7 +62,7 @@ curl https://.ifr.fr-par.scaleway.com/v1/embeddings \ }' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. ### Receiving Inference responses diff --git a/ai-data/managed-inference/reference-content/wizardlm-70b-v1.0.mdx b/ai-data/managed-inference/reference-content/wizardlm-70b-v1.0.mdx index 4fbb99bc69..4d302cd398 100644 --- a/ai-data/managed-inference/reference-content/wizardlm-70b-v1.0.mdx +++ b/ai-data/managed-inference/reference-content/wizardlm-70b-v1.0.mdx @@ -58,7 +58,7 @@ curl -s \ --data '{"model":"wizardlm/wizardlm-70b-v1.0:fp8", "messages":[{"role": "user","content": "Say hello to Scaleway's Inference"}], "max_tokens": 200, "top_p": 1, "temperature": 1, "stream": false}' ``` -Make sure to replace `` and `` with your actual [IAM API key](/identity-and-access-management/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. +Make sure to replace `` and `` with your actual [IAM API key](/iam/how-to/create-api-keys/) and the Deployment UUID you are targeting. The model name allows Scaleway to put your prompts in the expected format. @@ -74,5 +74,5 @@ Upon sending the HTTP request to the public or private endpoints exposed by the Process the output data according to your application's needs. The response will contain the output generated by the LLM model based on the input provided in the request. - Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/ai-data/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. + Despite efforts for accuracy, the possibility of generated text containing inaccuracies or [hallucinations](/managed-inference/concepts/#hallucinations) exists. Always verify the content generated independently. \ No newline at end of file diff --git a/bare-metal/apple-silicon/concepts.mdx b/bare-metal/apple-silicon/concepts.mdx index 0400022fad..ac8d0d9883 100644 --- a/bare-metal/apple-silicon/concepts.mdx +++ b/bare-metal/apple-silicon/concepts.mdx @@ -30,4 +30,4 @@ The Mac mini is a physical hardware designed by Apple, powered by the [Apple sil ## VNC -Virtual Network Computing (VNC) is a remote desktop-sharing protocol. It allows you to visualize the graphical screen output of a remote computer and transfer local keyboard and mouse events to the remote computer using a network connection. The protocol is platform-independent, which means that various clients exist for Linux, Windows, and macOS-based computers. The VNC server used on the Mac mini is directly integrated with the macOS system without any restrictions from our side. Check out our documentation on [how to connect to your Mac mini via VNC](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/#accessing-the-remote-desktop). \ No newline at end of file +Virtual Network Computing (VNC) is a remote desktop-sharing protocol. It allows you to visualize the graphical screen output of a remote computer and transfer local keyboard and mouse events to the remote computer using a network connection. The protocol is platform-independent, which means that various clients exist for Linux, Windows, and macOS-based computers. The VNC server used on the Mac mini is directly integrated with the macOS system without any restrictions from our side. Check out our documentation on [how to connect to your Mac mini via VNC](/apple-silicon/how-to/access-remote-desktop-mac-mini/#accessing-the-remote-desktop). \ No newline at end of file diff --git a/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx b/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx index 9d5049cccb..759b6fed2f 100644 --- a/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini.mdx @@ -13,7 +13,7 @@ categories: - bare-metal --- -This guide provides detailed instructions on how to access your [Mac mini](/bare-metal/apple-silicon/concepts/#mac-mini) using remote desktop clients. +This guide provides detailed instructions on how to access your [Mac mini](/apple-silicon/concepts/#mac-mini) using remote desktop clients. The macOS on your Mac mini uses the VNC protocol with additional Apple-specific enhancements to provide a remote desktop access. Remote desktop allows you to visualize the graphical screen output of a remote computer and interact with it using your local keyboard and mouse. @@ -21,9 +21,9 @@ The VNC protocol is platform-independent, supporting Linux, Windows, and macOS, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## Accessing the remote desktop @@ -145,7 +145,7 @@ The VNC protocol is platform-independent, supporting Linux, Windows, and macOS, - If you encounter issues connecting to the remote desktop of your Mac mini, refer to our documentation on [Troubleshooting remote desktop connections to Mac mini servers](/bare-metal/apple-silicon/troubleshooting/cant-connect-using-vnc/). + If you encounter issues connecting to the remote desktop of your Mac mini, refer to our documentation on [Troubleshooting remote desktop connections to Mac mini servers](/apple-silicon/troubleshooting/cant-connect-using-vnc/). diff --git a/bare-metal/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx b/bare-metal/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx index f3d440db1e..5373ea25f2 100644 --- a/bare-metal/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx +++ b/bare-metal/apple-silicon/how-to/connect-to-mac-mini-ssh.mdx @@ -13,13 +13,13 @@ categories: - bare-metal --- -You can connect directly to the terminal of your Mac mini using the SSH protocol and your [SSH key](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key). +You can connect directly to the terminal of your Mac mini using the SSH protocol and your [SSH key](/organizations-and-projects/concepts/#ssh-key). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## Connecting to a Mac mini using SSH @@ -44,7 +44,7 @@ You can connect directly to the terminal of your Mac mini using the SSH protocol * You can find the default username and IP address of your Mac mini on it's overview page in the Scaleway console. - * For more detailed guidance on connecting via SSH, refer to our documentation on [how to connect to an Instance](/compute/instances/how-to/connect-to-instance/). + * For more detailed guidance on connecting via SSH, refer to our documentation on [how to connect to an Instance](/instances/how-to/connect-to-instance/). diff --git a/bare-metal/apple-silicon/how-to/create-mac-mini.mdx b/bare-metal/apple-silicon/how-to/create-mac-mini.mdx index 3bf01ded80..afd5416717 100644 --- a/bare-metal/apple-silicon/how-to/create-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/create-mac-mini.mdx @@ -13,13 +13,13 @@ categories: - bare-metal --- -This page shows how to create your first [Mac mini](/bare-metal/apple-silicon/concepts/#mac-mini) with the Scaleway console. +This page shows how to create your first [Mac mini](/apple-silicon/concepts/#mac-mini) with the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) Due to license constraints, the minimum lease for Apple silicon is 24 hours. As a result, the earliest you can delete a Mac mini is 24 hours after the start of its lease. diff --git a/bare-metal/apple-silicon/how-to/delete-mac-mini.mdx b/bare-metal/apple-silicon/how-to/delete-mac-mini.mdx index 85c984fbb2..d45ab31adf 100644 --- a/bare-metal/apple-silicon/how-to/delete-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/delete-mac-mini.mdx @@ -13,13 +13,13 @@ categories: - bare-metal --- -This page shows how to delete your [Mac mini](/bare-metal/apple-silicon/concepts/#mac-mini). +This page shows how to delete your [Mac mini](/apple-silicon/concepts/#mac-mini). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) Deleting your Mac mini is an irreversible action. Any data stored on it will be lost. diff --git a/bare-metal/apple-silicon/how-to/install-package-manager-mac-mini.mdx b/bare-metal/apple-silicon/how-to/install-package-manager-mac-mini.mdx index a954c1b24a..4723c79021 100644 --- a/bare-metal/apple-silicon/how-to/install-package-manager-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/install-package-manager-mac-mini.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) [Homebrew](https://brew.sh/) is a package manager for macOS. It allows you to manage the packages installed on your Mac mini and provides a way to install additional software on your machine. diff --git a/bare-metal/apple-silicon/how-to/reboot-mac-mini.mdx b/bare-metal/apple-silicon/how-to/reboot-mac-mini.mdx index 9402f1ee03..903f2e403e 100644 --- a/bare-metal/apple-silicon/how-to/reboot-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/reboot-mac-mini.mdx @@ -13,13 +13,13 @@ categories: - bare-metal --- -This page shows how to reboot your [Mac mini](/bare-metal/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is unreachable, or you want to reboot it remotely. +This page shows how to reboot your [Mac mini](/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is unreachable, or you want to reboot it remotely. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays. diff --git a/bare-metal/apple-silicon/how-to/reinstall-mac-mini.mdx b/bare-metal/apple-silicon/how-to/reinstall-mac-mini.mdx index 3fe3d6ef0b..18c165e166 100644 --- a/bare-metal/apple-silicon/how-to/reinstall-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/reinstall-mac-mini.mdx @@ -13,14 +13,14 @@ categories: - bare-metal --- -This page shows how to reinstall your [Mac mini](/bare-metal/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is not reachable, or you want to start from scratch on the machine. +This page shows how to reinstall your [Mac mini](/apple-silicon/concepts/#mac-mini) from the Scaleway console. This is useful if your Mac mini is not reachable, or you want to start from scratch on the machine. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays. diff --git a/bare-metal/apple-silicon/how-to/shutdown-mac-mini.mdx b/bare-metal/apple-silicon/how-to/shutdown-mac-mini.mdx index 14e9b306cd..887dde4045 100644 --- a/bare-metal/apple-silicon/how-to/shutdown-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/shutdown-mac-mini.mdx @@ -24,9 +24,9 @@ Due to operational constraints, a Scaleway Mac mini should not be fully shut dow - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## Temporarily stopping usage @@ -41,7 +41,7 @@ To temporarily stop using your Mac mini: ## Permanently stopping usage -To permanently stop using your Mac mini and cease billing, you need to delete your Mac mini from your account. For detailed instructions, refer to [How to Delete a Mac mini](/bare-metal/apple-silicon/how-to/delete-mac-mini/). +To permanently stop using your Mac mini and cease billing, you need to delete your Mac mini from your account. For detailed instructions, refer to [How to Delete a Mac mini](/apple-silicon/how-to/delete-mac-mini/). Mac mini and macOS are trademarks of Apple Inc., registered in the U.S. and other countries and regions. iOS is a trademark or registered trademark of Cisco in the U.S. and other countries and is used by Apple under license. Scaleway is not affiliated with Apple Inc. diff --git a/bare-metal/apple-silicon/how-to/update-os-mac-mini.mdx b/bare-metal/apple-silicon/how-to/update-os-mac-mini.mdx index d39a37de53..6f39bd78ea 100644 --- a/bare-metal/apple-silicon/how-to/update-os-mac-mini.mdx +++ b/bare-metal/apple-silicon/how-to/update-os-mac-mini.mdx @@ -18,9 +18,9 @@ This guide provides instructions on updating the operating system of a Scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## Recommended method: macOS provided by Scaleway @@ -43,7 +43,7 @@ The recommended method to update the macOS is to reinstall your Mac mini with an ### Upgrading the OS via remote desktop -1. Log into your Mac mini using a [remote desktop client](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/) +1. Log into your Mac mini using a [remote desktop client](/apple-silicon/how-to/access-remote-desktop-mac-mini/) 2. Go to **System settings > General > Software update** 3. Launch the installation of the update. diff --git a/bare-metal/apple-silicon/how-to/upgrade-macos-to-beta.mdx b/bare-metal/apple-silicon/how-to/upgrade-macos-to-beta.mdx index 4a894d1c42..3f87c2cc48 100644 --- a/bare-metal/apple-silicon/how-to/upgrade-macos-to-beta.mdx +++ b/bare-metal/apple-silicon/how-to/upgrade-macos-to-beta.mdx @@ -18,11 +18,11 @@ This guide explains the steps to upgrade the macOS of a Scaleway Mac mini to a b - A Scaleway account logged into the [console](https://console.scaleway.com/) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) -1. Access your Mac mini via a [remote desktop connection](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/). +1. Access your Mac mini via a [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/). 2. Back up your Mac mini. @@ -44,6 +44,6 @@ This guide explains the steps to upgrade the macOS of a Scaleway Mac mini to a b 6. Click the **Upgrade Now** button to start downloading and installing the beta version on your Mac. - Reverting from a macOS beta version to a previous stable version without reinstalling the operating system entirely is not officially supported by Apple. The only way to revert is to perform a full [reinstallation](/bare-metal/apple-silicon/how-to/reinstall-mac-mini/) of the previous macOS version. + Reverting from a macOS beta version to a previous stable version without reinstalling the operating system entirely is not officially supported by Apple. The only way to revert is to perform a full [reinstallation](/apple-silicon/how-to/reinstall-mac-mini/) of the previous macOS version. diff --git a/bare-metal/apple-silicon/index.mdx b/bare-metal/apple-silicon/index.mdx index 9cee7d7294..7e81602482 100644 --- a/bare-metal/apple-silicon/index.mdx +++ b/bare-metal/apple-silicon/index.mdx @@ -8,7 +8,7 @@ meta: productName="Apple silicon" productLogo="appleSilicon" description="Scaleway Apple silicon are our Mac mini M2 pro, M2 and M1 dedicated machines. Enjoy unparalleled speed and performance to handle all your computing needs with the latest generations of Mac mini hardware." - url="/bare-metal/apple-silicon/quickstart" + url="/apple-silicon/quickstart" label="Apple silicon Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and delete a Mac mini in a few steps." label="View Quickstart" - url="/bare-metal/apple-silicon/quickstart/" + url="/apple-silicon/quickstart/" /> diff --git a/bare-metal/apple-silicon/quickstart.mdx b/bare-metal/apple-silicon/quickstart.mdx index b9fab87ea4..5b11bfd215 100644 --- a/bare-metal/apple-silicon/quickstart.mdx +++ b/bare-metal/apple-silicon/quickstart.mdx @@ -19,9 +19,9 @@ Apple silicon as-a-Service is tailored for developing, building, testing, and si ## Requirements -- Be the [Owner](/identity-and-access-management/iam/concepts/#owner) of the Organization in which the actions will be performed, or an IAM user with the [necessary permissions](/identity-and-access-management/iam/concepts/#permission) +- Be the [Owner](/iam/concepts/#owner) of the Organization in which the actions will be performed, or an IAM user with the [necessary permissions](/iam/concepts/#permission) - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account ## How to create a Mac mini @@ -49,7 +49,7 @@ Apple silicon as-a-Service is tailored for developing, building, testing, and si You can access your Mac mini using VNC, a remote desktop-sharing protocol. It allows you to visualize the graphical screen output of a remote computer and transfer local keyboard and mouse events to the remote computer using a network connection. -Refer to our detailed documentation for Windows, Linux, and macOS for OS specific information: [How to access the remote desktop of a Mac mini](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/). +Refer to our detailed documentation for Windows, Linux, and macOS for OS specific information: [How to access the remote desktop of a Mac mini](/apple-silicon/how-to/access-remote-desktop-mac-mini/). The VNC port on Mac mini systems is **randomly assigned** during system installation and may therefore be different from the default VNC port 5900. To connect successfully via VNC, use the specific port shown in the **Overview** section of your Mac mini’s configuration. diff --git a/bare-metal/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx b/bare-metal/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx index c2d8376c96..7cf62097a8 100644 --- a/bare-metal/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx +++ b/bare-metal/apple-silicon/troubleshooting/cant-connect-using-ssh.mdx @@ -25,14 +25,14 @@ The reboot **must** be carried out via the console, and not via any other method - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) 1. Click **Apple silicon** in the **Bare Metal** section of the side menu. A list of your Mac minis displays. 2. Click the Mac mini you want to configure. Your Mac mini information page displays. 3. Scroll down to the **Reboot Mac mini** section. Click **Reboot** to reboot the Mac mini. - Ensure you have [generated and uploaded your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) before rebooting your Mac mini. + Ensure you have [generated and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/) before rebooting your Mac mini. 4. Click **Reboot Mac mini** to confirm. The Mac mini reboots and your SSH key will be uploaded during the boot process. Banned host lists are reset as well. \ No newline at end of file diff --git a/bare-metal/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx b/bare-metal/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx index ea37dff587..a49cb469db 100644 --- a/bare-metal/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx +++ b/bare-metal/apple-silicon/troubleshooting/cant-connect-using-vnc.mdx @@ -18,8 +18,8 @@ This documentation provides a structured approach to diagnose and resolve issues - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## 1. Verify the server status @@ -40,8 +40,8 @@ PING X.X.X.X (X.X.X.X): 56 data bytes 5 packets transmitted, 5 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 0.182/0.207/0.261/0.028 ms ``` -- If `ping` fails, try [rebooting the server](/bare-metal/apple-silicon/how-to/reboot-mac-mini/). -- If rebooting fails or if the server was forced to shut down, wait 24 hours for automatic restart. See [How to shutdown a Mac mini](/bare-metal/apple-silicon/how-to/shutdown-mac-mini/) for more information. +- If `ping` fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/). +- If rebooting fails or if the server was forced to shut down, wait 24 hours for automatic restart. See [How to shutdown a Mac mini](/apple-silicon/how-to/shutdown-mac-mini/) for more information. ## 2. Verify the VNC connection @@ -58,7 +58,7 @@ Expected output: ``` Connection to port [tcp/rfb] succeeded! ``` -- If the connection fails, try [rebooting the server](/bare-metal/apple-silicon/how-to/reboot-mac-mini/). +- If the connection fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/). - If necessary, restart screen sharing via SSH. See [Restarting screen sharing via SSH](#restarting-screen-sharing-via-ssh). ## 3. Verify the SSH server response @@ -70,12 +70,12 @@ Expected output: ``` Connection to port 22 [tcp/ssh] succeeded! ``` -- If the connection fails, try [rebooting the server](/bare-metal/apple-silicon/how-to/reboot-mac-mini/). +- If the connection fails, try [rebooting the server](/apple-silicon/how-to/reboot-mac-mini/). ## 4. Check for connection blacklisting If VNC connection attempts repeatedly fail, the connection might be blacklisted, or the Apple screen sharing service might be unresponsive. -- [Reboot the server](/bare-metal/apple-silicon/how-to/reboot-mac-mini/) to clear the `fail2ban` table. +- [Reboot the server](/apple-silicon/how-to/reboot-mac-mini/) to clear the `fail2ban` table. ## 5. Verify your connection credentials @@ -88,7 +88,7 @@ If VNC connection attempts repeatedly fail, the connection might be blacklisted, - SSH keys provided post-installation are not considered. ## 6. Verify remote connection client compatibility -Ensure your remote connection client is compatible with macOS. Incompatible remote desktop (VNC) clients can cause failed connection attempts. For recommended VNC clients, see [How to access to the remote desktop of a Mac mini](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/#comparison-matrix-of-remote-desktop-clients). +Ensure your remote connection client is compatible with macOS. Incompatible remote desktop (VNC) clients can cause failed connection attempts. For recommended VNC clients, see [How to access to the remote desktop of a Mac mini](/apple-silicon/how-to/access-remote-desktop-mac-mini/#comparison-matrix-of-remote-desktop-clients). ## 7. Reinstall the Mac mini @@ -100,7 +100,7 @@ Follow these steps to reinstall macOS on your Mac mini: 2. Navigate to your Mac mini server. 3. Select the option to reinstall a version of macOS. -For detailed instructions, refer to [How to reinstall a Mac mini](/bare-metal/apple-silicon/how-to/reinstall-mac-mini/). +For detailed instructions, refer to [How to reinstall a Mac mini](/apple-silicon/how-to/reinstall-mac-mini/). Reinstalling your Mac mini will erase all data on the disk and reset all configurations to default settings. Ensure you have a backup of your data before proceeding. diff --git a/bare-metal/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx b/bare-metal/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx index 69202248c9..3d555d0638 100644 --- a/bare-metal/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx +++ b/bare-metal/apple-silicon/troubleshooting/filevault-preventing-system-boot.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) Apple FileVault is a disk encryption feature. Ensure that FileVault is **not enabled** on your Mac mini. If enabled, it will prevent your system from booting. diff --git a/bare-metal/dedibox/how-to/activate-ipv6-block.mdx b/bare-metal/dedibox/how-to/activate-ipv6-block.mdx index 3b0cd83e3e..760b501fd7 100644 --- a/bare-metal/dedibox/how-to/activate-ipv6-block.mdx +++ b/bare-metal/dedibox/how-to/activate-ipv6-block.mdx @@ -16,9 +16,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server 1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays. 2. Click the **IPv6s** tab to enter the IPv6 section of the console. diff --git a/bare-metal/dedibox/how-to/attach-detach-failover-ip.mdx b/bare-metal/dedibox/how-to/attach-detach-failover-ip.mdx index 5d317ec35b..42ee511ded 100644 --- a/bare-metal/dedibox/how-to/attach-detach-failover-ip.mdx +++ b/bare-metal/dedibox/how-to/attach-detach-failover-ip.mdx @@ -20,10 +20,10 @@ Each failover IP can be routed to any of your Dedibox servers at any time by usi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- Ordered a [Dedibox server](/bare-metal/dedibox/how-to/order-dedibox/) and a [failover IP](/bare-metal/dedibox/how-to/order-failover-ip/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/) ## How to attach a failover IP diff --git a/bare-metal/dedibox/how-to/configure-failover-ip.mdx b/bare-metal/dedibox/how-to/configure-failover-ip.mdx index bf7941f960..c7496300eb 100644 --- a/bare-metal/dedibox/how-to/configure-failover-ip.mdx +++ b/bare-metal/dedibox/how-to/configure-failover-ip.mdx @@ -18,15 +18,15 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- Ordered a [Dedibox server](/bare-metal/dedibox/how-to/order-dedibox/) and a [failover IP](/bare-metal/dedibox/how-to/order-failover-ip/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/) -The following pages provide information on how to configure a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) on Dedibox servers running various operating systems: +The following pages provide information on how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running various operating systems: -* [CentOS](/dedibox-network/ip-failover/how-to/configure-centos/) -* [Debian and Ubuntu Linux](/dedibox-network/ip-failover/how-to/configure-debian-ubuntu/) -* [FreeBSD](/dedibox-network/ip-failover/how-to/configure-freebsd/) -* [Windows Server](/dedibox-network/ip-failover/how-to/configure-windows/) +* [CentOS](/dedibox-ip-failover/how-to/configure-centos/) +* [Debian and Ubuntu Linux](/dedibox-ip-failover/how-to/configure-debian-ubuntu/) +* [FreeBSD](/dedibox-ip-failover/how-to/configure-freebsd/) +* [Windows Server](/dedibox-ip-failover/how-to/configure-windows/) -Learn more about failover IPs with our [dedicated documentation](/dedibox-network/ip-failover/quickstart/). \ No newline at end of file +Learn more about failover IPs with our [dedicated documentation](/dedibox-ip-failover/quickstart/). \ No newline at end of file diff --git a/bare-metal/dedibox/how-to/configure-ipv6-dedibox.mdx b/bare-metal/dedibox/how-to/configure-ipv6-dedibox.mdx index b49c5a5d2b..2ef16caa64 100644 --- a/bare-metal/dedibox/how-to/configure-ipv6-dedibox.mdx +++ b/bare-metal/dedibox/how-to/configure-ipv6-dedibox.mdx @@ -16,11 +16,11 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created and uploaded your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Created](/bare-metal/dedibox/how-to/order-dedibox/) and [installed](/bare-metal/dedibox/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation -- [Activated](/bare-metal/dedibox/how-to/activate-ipv6-block/) an IPv6 block +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Created](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation +- [Activated](/dedibox-scaleway/how-to/activate-ipv6-block/) an IPv6 block The Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. The Dedibox network is wholly IPv6 compatible in all Availability Zones. @@ -30,4 +30,4 @@ Each Dedibox customer account comes with a /48 IPv6 block that can be divided in * as many /56 as you have servers. * as many /64 as you have failover IPs. -You can assign these blocks to your Dedibox servers by using DHCPv6 and the DUID assigned to each of these blocks. To find more information on IPv6 on Dedibox, refer to our [quickstart](/dedibox-network/ipv6/quickstart/). \ No newline at end of file +You can assign these blocks to your Dedibox servers by using DHCPv6 and the DUID assigned to each of these blocks. To find more information on IPv6 on Dedibox, refer to our [quickstart](/dedibox-ipv6/quickstart/). \ No newline at end of file diff --git a/bare-metal/dedibox/how-to/configure-reverse-failover-ip.mdx b/bare-metal/dedibox/how-to/configure-reverse-failover-ip.mdx index bbddf16b1c..e183574678 100644 --- a/bare-metal/dedibox/how-to/configure-reverse-failover-ip.mdx +++ b/bare-metal/dedibox/how-to/configure-reverse-failover-ip.mdx @@ -18,9 +18,9 @@ You can edit the reverse DNS of a failover IP address to a custom value. This ca - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- Ordered a [Dedibox server](/bare-metal/dedibox/how-to/order-dedibox/) and a [failover IP](/bare-metal/dedibox/how-to/order-failover-ip/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- Ordered a [Dedibox server](/dedibox-scaleway/how-to/order-dedibox/) and a [failover IP](/dedibox-scaleway/how-to/order-failover-ip/) 1. Click **Dedibox** in the **Bare Metal** section of the side menu. 2. Click the **Failover IPs** tab to display a list of your failover IPs. diff --git a/bare-metal/dedibox/how-to/connect-to-dedibox.mdx b/bare-metal/dedibox/how-to/connect-to-dedibox.mdx index 11c1521397..c62c9b9b6e 100644 --- a/bare-metal/dedibox/how-to/connect-to-dedibox.mdx +++ b/bare-metal/dedibox/how-to/connect-to-dedibox.mdx @@ -22,10 +22,10 @@ You can also use FTP, SFTP, or SCP to transfer data to and from your server. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created and uploaded your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Created](/bare-metal/dedibox/how-to/order-dedibox/) and [installed](/bare-metal/dedibox/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Created](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server and transferred your SSH key to it during installation ## How to connect via SSH @@ -64,7 +64,7 @@ To connect to your Instance from Windows, you will need to use a small applicati Dedibox servers and their associated IP addresses displays. 4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**. -5. Click the **Browse** button and select the private key file you [generated previously](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/). +5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. The terminal window displays. 8. Enter your username and password to authenticate against the server with your SSH key. diff --git a/bare-metal/dedibox/how-to/install-dedibox.mdx b/bare-metal/dedibox/how-to/install-dedibox.mdx index 2b617df5e7..a16d2fafe0 100644 --- a/bare-metal/dedibox/how-to/install-dedibox.mdx +++ b/bare-metal/dedibox/how-to/install-dedibox.mdx @@ -16,10 +16,10 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server ## How to install a Dedibox @@ -30,9 +30,9 @@ After the delivery of your server, you can start installing it. 3. Click **Install** to launch the OS installation wizard. 4. Select the type and version of the operating system you want to install. - For more information about OS types, refer to the [dedicated servers concepts page](/bare-metal/dedibox/concepts/#os-type). + For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type). -5. Personalize the following [partitioning](/bare-metal/dedibox/concepts/#partitioning) parameters: +5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters: - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap) - the mount point of the partition - the partition size @@ -43,8 +43,8 @@ After the delivery of your server, you can start installing it. 6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key. - * To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) at this stage so that it can be transferred to your server during installation. - * Existing SSH keys from your current Dedibox console are not transferred to the Scaleway console. [Upload these keys](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) into your Scaleway console to use them with your Dedibox servers. + * To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/organizations-and-projects/how-to/create-ssh-key/) at this stage so that it can be transferred to your server during installation. + * Existing SSH keys from your current Dedibox console are not transferred to the Scaleway console. [Upload these keys](/organizations-and-projects/how-to/create-ssh-key#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) into your Scaleway console to use them with your Dedibox servers. 7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Reinstall Dedibox server**. diff --git a/bare-metal/dedibox/how-to/link-dedibox-account.mdx b/bare-metal/dedibox/how-to/link-dedibox-account.mdx index c54b3175af..32da16baf3 100644 --- a/bare-metal/dedibox/how-to/link-dedibox-account.mdx +++ b/bare-metal/dedibox/how-to/link-dedibox-account.mdx @@ -25,7 +25,7 @@ You can now manage your current and future Dedibox servers from the Scaleway con - A Dedibox account logged into the [console](https://console.online.net) -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server You can come back to your current [Dedibox console](https://console.online.net/) at any time after you have received an invitation by email. Refer to our [FAQ](/faq/dedibox-in-scaleway-console/) for more information. @@ -42,7 +42,7 @@ Follow these steps to link your Dedibox account to your Scaleway account: To link your Dedibox account to a different Scaleway account, click **Choose another account** and enter the new account credentials. -5. Choose the [Organization](/identity-and-access-management/iam/concepts/#organization) in your Scaleway account to link your Dedibox servers, then click **Select Organization**. +5. Choose the [Organization](/iam/concepts/#organization) in your Scaleway account to link your Dedibox servers, then click **Select Organization**. If needed, click **Create a new Organization** to create a new Organization for your servers. diff --git a/bare-metal/dedibox/how-to/modify-server-options.mdx b/bare-metal/dedibox/how-to/modify-server-options.mdx index 446214745a..9b86f1097b 100644 --- a/bare-metal/dedibox/how-to/modify-server-options.mdx +++ b/bare-metal/dedibox/how-to/modify-server-options.mdx @@ -16,9 +16,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server 1. Click **Dedibox** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Dedibox dashboard displays. 2. Choose the server you want to configure from the list. Click its name to display that server's information page. diff --git a/bare-metal/dedibox/how-to/order-dedibox.mdx b/bare-metal/dedibox/how-to/order-dedibox.mdx index 213dc3ee41..0462019a2e 100644 --- a/bare-metal/dedibox/how-to/order-dedibox.mdx +++ b/bare-metal/dedibox/how-to/order-dedibox.mdx @@ -16,9 +16,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts 1. Click **Dedibox** in the **Bare Metal** section of the side menu. The Dedibox overview page displays. 2. Click **+ Order a Dedibox server** to launch the creation wizard. diff --git a/bare-metal/dedibox/how-to/order-failover-ip.mdx b/bare-metal/dedibox/how-to/order-failover-ip.mdx index c5a6092339..d58b03fd3e 100644 --- a/bare-metal/dedibox/how-to/order-failover-ip.mdx +++ b/bare-metal/dedibox/how-to/order-failover-ip.mdx @@ -23,9 +23,9 @@ Failover IPs can be bought as single IP addresses with a maximum number of IPs p - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server 1. Click **Dedibox** in the **Bare Metal** section of the side menu. 2. Click the **Failover IPs** tab to display a list of your failover IPs. diff --git a/bare-metal/dedibox/how-to/reinstall-dedibox.mdx b/bare-metal/dedibox/how-to/reinstall-dedibox.mdx index 0b1b8eb6eb..51fd1f12c1 100644 --- a/bare-metal/dedibox/how-to/reinstall-dedibox.mdx +++ b/bare-metal/dedibox/how-to/reinstall-dedibox.mdx @@ -16,10 +16,10 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server ## How to reinstall a Dedibox dedicated server @@ -34,9 +34,9 @@ You can reinstall the operating system running on your Dedibox at any time. This 3. On the server's dashboard, scroll down to **Reinstall Dedibox Server**. Then click **Reinstall Dedibox server** to launch the OS installation wizard. 4. Select the type and version of the operating system you want to install. - For more information about OS types, refer to the [dedicated servers concepts page](/bare-metal/dedibox/concepts/#os-type). + For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type). -5. Personalize the following [partitioning](/bare-metal/dedibox/concepts/#partitioning) parameters: +5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters: - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap) - the mount point of the partition - the partition size @@ -47,7 +47,7 @@ You can reinstall the operating system running on your Dedibox at any time. This 6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key. - To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. + To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. 7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Reinstall Dedibox server**. diff --git a/bare-metal/dedibox/how-to/terminate-dedibox.mdx b/bare-metal/dedibox/how-to/terminate-dedibox.mdx index 3fd21a82a1..b0bbebbc0b 100644 --- a/bare-metal/dedibox/how-to/terminate-dedibox.mdx +++ b/bare-metal/dedibox/how-to/terminate-dedibox.mdx @@ -16,9 +16,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) a Dedibox server 1. Click **Dedibox** in the **Bare Metal** section of the side menu. 2. Choose the Dedibox server you want to delete by clicking on its name. diff --git a/bare-metal/dedibox/how-to/use-rescue-mode.mdx b/bare-metal/dedibox/how-to/use-rescue-mode.mdx index 1c1ac79773..19a92ecade 100644 --- a/bare-metal/dedibox/how-to/use-rescue-mode.mdx +++ b/bare-metal/dedibox/how-to/use-rescue-mode.mdx @@ -13,7 +13,7 @@ dates: - This documentation concerns rescue mode for [Dedibox servers](https://www.scaleway.com/en/dedibox/). To use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/) refer to the corresponding [documentation](/compute/instances/how-to/use-boot-modes/#how-to-use-rescue-mode). + This documentation concerns rescue mode for [Dedibox servers](https://www.scaleway.com/en/dedibox/). To use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/) refer to the corresponding [documentation](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode). Rescue mode allows you to boot a [Scaleway Dedibox server](https://www.scaleway.com/en/dedibox/) from the network. It downloads a rescue operating system, that runs completely in the RAM of the server. This allows you to perform maintenance and data recovery operations, even if the machine is not reachable in normal mode. @@ -21,10 +21,10 @@ Rescue mode allows you to boot a [Scaleway Dedibox server](https://www.scaleway. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts -- [Ordered](/bare-metal/dedibox/how-to/order-dedibox/) and [installed](/bare-metal/dedibox/how-to/install-dedibox/) a Dedibox server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Ordered](/dedibox-scaleway/how-to/order-dedibox/) and [installed](/dedibox-scaleway/how-to/install-dedibox/) a Dedibox server 1. Click **Dedibox** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Dedibox dashboard displays. 2. Choose the server you want to reboot into rescue mode from the list. Click its name to display that server's information page. diff --git a/bare-metal/dedibox/index.mdx b/bare-metal/dedibox/index.mdx index bcf60afc76..71104de102 100644 --- a/bare-metal/dedibox/index.mdx +++ b/bare-metal/dedibox/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox" productLogo="dedibox" description="Scaleway Dedibox are high-quality dedicated servers that benefit from extreme reliability and best-in-class redundancy for any workload requirement." - url="/bare-metal/dedibox/quickstart" + url="/dedibox-scaleway/quickstart" label="Dedibox Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and manage a Dedibox in a few steps." label="View Quickstart" - url="/bare-metal/dedibox/quickstart/" + url="/dedibox-scaleway/quickstart/" /> diff --git a/bare-metal/dedibox/quickstart.mdx b/bare-metal/dedibox/quickstart.mdx index cd36a3bf4b..53d2b71781 100644 --- a/bare-metal/dedibox/quickstart.mdx +++ b/bare-metal/dedibox/quickstart.mdx @@ -16,9 +16,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -- [Linked](/bare-metal/dedibox/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts +- [Linked](/dedibox-scaleway/how-to/link-dedibox-account/) your Dedibox and Scaleway accounts ## How to order a Dedibox @@ -42,9 +42,9 @@ After the delivery of your server, you can begin installing it. 3. Click **Install** to launch the OS installation wizard. 4. Select the type and version of the operating system you want to install. - For more information about OS types, refer to the [dedicated servers concepts page](/bare-metal/dedibox/concepts/#os-type). + For more information about OS types, refer to the [dedicated servers concepts page](/dedibox-scaleway/concepts/#os-type). -5. Personalize the following [partitioning](/bare-metal/dedibox/concepts/#partitioning) parameters: +5. Personalize the following [partitioning](/dedibox-scaleway/concepts/#partitioning) parameters: - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap) - the mount point of the partition - the partition size @@ -55,7 +55,7 @@ After the delivery of your server, you can begin installing it. 6. Configure the system parameters. You can edit parameters such as the name of the server, and add a username, password, and SSH key. - To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. + To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. 7. Tick the checkbox to confirm that your server can be shut down in case of abuse. Then click **Install Dedibox server**. @@ -76,8 +76,8 @@ You can also use FTP, SFTP, or SCP to transfer data to and from your server. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Created and uploaded your SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key) -- [Created](/bare-metal/dedibox/how-to/order-dedibox) and [installed](/bare-metal/dedibox/how-to/install-dedibox) a Dedibox and transferred your SSH key to the server during installation +- [Created and uploaded your SSH key](/organizations-and-projects/how-to/create-ssh-key) +- [Created](/dedibox-scaleway/how-to/order-dedibox) and [installed](/dedibox-scaleway/how-to/install-dedibox) a Dedibox and transferred your SSH key to the server during installation ## How to connect via SSH @@ -110,7 +110,7 @@ To connect to your Instance from Windows, you will need to use a small applicati Dedibox servers and their associated IP addresses will display. 4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**. -5. Click the **Browse** button and select the private key file you [generated previously](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/). +5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. The terminal window displays. 8. Enter your username and password to authenticate against the server with your SSH key. diff --git a/bare-metal/elastic-metal/api-cli/elastic-metal-with-api.mdx b/bare-metal/elastic-metal/api-cli/elastic-metal-with-api.mdx index ebe9be701c..7fc794bfd2 100644 --- a/bare-metal/elastic-metal/api-cli/elastic-metal-with-api.mdx +++ b/bare-metal/elastic-metal/api-cli/elastic-metal-with-api.mdx @@ -23,16 +23,16 @@ The **one-command deployment feature** accelerates server provisioning by combin - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) ## Deploying Elastic Metal servers using the API -Besides creating your Elastic Metal servers from the graphical [Scaleway console](/bare-metal/elastic-metal/how-to/create-server/), you can also create and manage them directly from the command line using the [CLI-tool](https://github.com/scaleway/scaleway-cli) or the [API](https://www.scaleway.com/en/developers/api/elastic-metal/). +Besides creating your Elastic Metal servers from the graphical [Scaleway console](/elastic-metal/how-to/create-server/), you can also create and manage them directly from the command line using the [CLI-tool](https://github.com/scaleway/scaleway-cli) or the [API](https://www.scaleway.com/en/developers/api/elastic-metal/). - You need to [generate API keys](/identity-and-access-management/iam/how-to/create-api-keys/) to access the Scaleway API. + You need to [generate API keys](/iam/how-to/create-api-keys/) to access the Scaleway API. 1. Open a terminal on your computer and set your secret API key, your SSH key ID, and your Project ID as variables. @@ -154,4 +154,4 @@ Besides creating your Elastic Metal servers from the graphical [Scaleway console Your new Elastic Metal server will be installed and ready to be used in usually less than **15 minutes**, all API features are listed in the [API documentation](https://www.scaleway.com/en/developers/api/elastic-metal/). -For more information about Elastic Metal servers, refer to our [dedicated product documentation](/bare-metal/elastic-metal/) and the [FAQ](/faq/elastic-metal/). \ No newline at end of file +For more information about Elastic Metal servers, refer to our [dedicated product documentation](/elastic-metal/) and the [FAQ](/faq/elastic-metal/). \ No newline at end of file diff --git a/bare-metal/elastic-metal/api-cli/elastic-metal-with-cli.mdx b/bare-metal/elastic-metal/api-cli/elastic-metal-with-cli.mdx index e4a804e8ce..0dd62e5dd4 100644 --- a/bare-metal/elastic-metal/api-cli/elastic-metal-with-cli.mdx +++ b/bare-metal/elastic-metal/api-cli/elastic-metal-with-cli.mdx @@ -24,10 +24,10 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Installed and configured the Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- [Installed and configured the Scaleway CLI](/scaleway-cli/quickstart/) ## Creating an Elastic Metal server @@ -159,7 +159,7 @@ The [Scaleway Command Line Interface (CLI)](https://github.com/scaleway/scaleway There are many other functionalities you can access for your Elastic Metal server via the Scaleway CLI. In the following examples, replace `your-elastic-metal-server-ID` with your server's ID. - * Before powering off your server, we recommend you [log into your server as root](/bare-metal/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS. + * Before powering off your server, we recommend you [log into your server as root](/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS. * Type `scw baremetal server get name-of-server-ID zone=fr-par-2` in your terminal if you are not sure what the IP address of your Elastic Metal server is. It will display in the `IPs.0.Address` field. @@ -213,7 +213,7 @@ PingStatus up ### Powering off your server - Before powering off your Elastic Metal server, we recommend you [log into your server as root](/bare-metal/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS. + Before powering off your Elastic Metal server, we recommend you [log into your server as root](/elastic-metal/how-to/connect-to-server/) and execute the `halt` command to shut down the OS. diff --git a/bare-metal/elastic-metal/concepts.mdx b/bare-metal/elastic-metal/concepts.mdx index d98310954f..4caccd4b03 100644 --- a/bare-metal/elastic-metal/concepts.mdx +++ b/bare-metal/elastic-metal/concepts.mdx @@ -37,7 +37,7 @@ Public IP addresses are routed on the internet. You can enter the public IP addr ## Private Networks -[Private Networks allow your Elastic Metal servers to communicate with other Scaleway resources](/bare-metal/elastic-metal/how-to/use-private-networks/) in an isolated and secure network without requiring a connection to the public internet. +[Private Networks allow your Elastic Metal servers to communicate with other Scaleway resources](/elastic-metal/how-to/use-private-networks/) in an isolated and secure network without requiring a connection to the public internet. ## Region and Availability Zone diff --git a/bare-metal/elastic-metal/how-to/activate-remote-access.mdx b/bare-metal/elastic-metal/how-to/activate-remote-access.mdx index 65373cc03d..dcdb1eecb6 100644 --- a/bare-metal/elastic-metal/how-to/activate-remote-access.mdx +++ b/bare-metal/elastic-metal/how-to/activate-remote-access.mdx @@ -20,9 +20,9 @@ Using remote access, you can access the machine for debugging purposes, even if - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server compatible with [remote access](/bare-metal/elastic-metal/concepts/#remote-access) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server compatible with [remote access](/elastic-metal/concepts/#remote-access) Remote access is an **optional feature** and not available on all Elastic Metal servers. The following steps can be done only on Elastic Metal servers providing remote access. diff --git a/bare-metal/elastic-metal/how-to/add-virtual-mac-address.mdx b/bare-metal/elastic-metal/how-to/add-virtual-mac-address.mdx index ced0d88327..578fb9ad75 100644 --- a/bare-metal/elastic-metal/how-to/add-virtual-mac-address.mdx +++ b/bare-metal/elastic-metal/how-to/add-virtual-mac-address.mdx @@ -13,14 +13,14 @@ categories: - bare-metal --- -Virtual MAC addresses act as virtual interface identifiers necessary for virtualization. When running multiple virtual machines on a single physical Elastic Metal server, you can configure the [MAC address](https://en.wikipedia.org/wiki/MAC_address) of the virtual network interface to match the virtual MAC associated with the [flexible IP](/bare-metal/elastic-metal/concepts/#flexible-ip), ensuring network connectivity for the virtual machine. +Virtual MAC addresses act as virtual interface identifiers necessary for virtualization. When running multiple virtual machines on a single physical Elastic Metal server, you can configure the [MAC address](https://en.wikipedia.org/wiki/MAC_address) of the virtual network interface to match the virtual MAC associated with the [flexible IP](/elastic-metal/concepts/#flexible-ip), ensuring network connectivity for the virtual machine. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An installed Elastic Metal server ([how to create an Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An installed Elastic Metal server ([how to create an Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server)) Virtual MAC addresses are only necessary for virtualization. If you plan to configure the flexible IP as a secondary interface on the host OS, a virtual MAC is not required. @@ -39,4 +39,4 @@ Virtual MAC addresses act as virtual interface identifiers necessary for virtual If the virtual MAC address is no longer needed, you can remove it from the flexible IP by clicking the **Delete** button. -For more information on configuring the flexible IP on a virtual machine, refer to our [documentation](/bare-metal/elastic-metal/how-to/configure-flexible-ip/). \ No newline at end of file +For more information on configuring the flexible IP on a virtual machine, refer to our [documentation](/elastic-metal/how-to/configure-flexible-ip/). \ No newline at end of file diff --git a/bare-metal/elastic-metal/how-to/adjust-available-bandwidth.mdx b/bare-metal/elastic-metal/how-to/adjust-available-bandwidth.mdx index a421632bcb..8c662f32fd 100644 --- a/bare-metal/elastic-metal/how-to/adjust-available-bandwidth.mdx +++ b/bare-metal/elastic-metal/how-to/adjust-available-bandwidth.mdx @@ -16,8 +16,8 @@ Every Elastic Metal server comes with a designated bandwidth allowance. Increase - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) ## Upgrading bandwidth for your Elastic Metal server diff --git a/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip.mdx index bbb7ddd9fd..0c60053853 100644 --- a/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip.mdx +++ b/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip.mdx @@ -13,18 +13,18 @@ categories: - bare-metal --- -You can order up to 64 flexible IPs (IPv4 or IPv6) for each of your Elastic Metal servers. These [Elastic Metal flexible IPs](/bare-metal/elastic-metal/concepts/#flexible-ip) can be attached and detached from any of your Elastic Metal servers using the console's drag-and-drop interface. +You can order up to 64 flexible IPs (IPv4 or IPv6) for each of your Elastic Metal servers. These [Elastic Metal flexible IPs](/elastic-metal/concepts/#flexible-ip) can be attached and detached from any of your Elastic Metal servers using the console's drag-and-drop interface. - Scaleway offers flexible IPs for [Elastic Metal servers](/bare-metal/elastic-metal/concepts/#elastic-metal-server), [Instances](/compute/instances/concepts/#instance), and [Public Gateways](/network/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa. + Scaleway offers flexible IPs for [Elastic Metal servers](/elastic-metal/concepts/#elastic-metal-server), [Instances](/instances/concepts/#instance), and [Public Gateways](/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) -- An Elastic Metal [flexible IP address](/bare-metal/elastic-metal/how-to/order-flexible-ip/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- An Elastic Metal [flexible IP address](/elastic-metal/how-to/order-flexible-ip/) ## How to attach a flexible IP to an Elastic Metal server @@ -50,6 +50,6 @@ You can order up to 64 flexible IPs (IPv4 or IPv6) for each of your Elastic Meta 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays. 2. Click the **Flexible IPs** tab to display the list of failover IPs for Elastic Metal servers allocated to your account. -3. Configure your services and the [flexible IP](/bare-metal/elastic-metal/how-to/configure-flexible-ip/) on the new server to ensure uninterrupted service availability. +3. Configure your services and the [flexible IP](/elastic-metal/how-to/configure-flexible-ip/) on the new server to ensure uninterrupted service availability. 4. In the **Elastic Metal servers** panel, drag and drop the flexible IP from its current server to the new one to update its destination. 5. Click **Validate** to complete the switch. The green dot will start blinking blue, indicating that the flexible IP destination is being updated. Once the configuration is updated, the blinking dot will turn back to green, indicating that the flexible IP is now routed to the new server. \ No newline at end of file diff --git a/bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx b/bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx index b6e3fb5f73..4f1281da9b 100644 --- a/bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx +++ b/bare-metal/elastic-metal/how-to/configure-disk-partitions.mdx @@ -23,13 +23,13 @@ However, if you have specific requirements, you can define custom partitioning o - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) ## Example configuration -During [server installation](/bare-metal/elastic-metal/) click **Advanced JSON** configuration in step 5 of the server creation wizard. +During [server installation](/elastic-metal/) click **Advanced JSON** configuration in step 5 of the server creation wizard. You can then edit the partition configuration directly in the editor within your browser. The configuration is done via a JSON description of the partitioning. Below is an example of how to define a partitioning schema with RAID and NVMe disks. diff --git a/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx index e187dd7f67..d2ec3de43f 100644 --- a/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx +++ b/bare-metal/elastic-metal/how-to/configure-flexible-ip.mdx @@ -13,18 +13,18 @@ categories: - bare-metal --- -Learn how to configure a [flexible IP address](/bare-metal/elastic-metal/concepts/#flexible-ip) on your Elastic Metal server. The configuration depends on the Linux distribution running on your machine. You can configure your flexible IP on machines running one of [Ubuntu Linux](#how-to-configure-a-flexible-ip-on-ubuntu-linux), [Debian Linux](#how-to-configure-a-flexible-ip-on-debian-linux) or [CentOS](#how-to-configure-a-flexible-ip-on-centos). +Learn how to configure a [flexible IP address](/elastic-metal/concepts/#flexible-ip) on your Elastic Metal server. The configuration depends on the Linux distribution running on your machine. You can configure your flexible IP on machines running one of [Ubuntu Linux](#how-to-configure-a-flexible-ip-on-ubuntu-linux), [Debian Linux](#how-to-configure-a-flexible-ip-on-debian-linux) or [CentOS](#how-to-configure-a-flexible-ip-on-centos). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) -- A [flexible IP address](/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- A [flexible IP address](/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server - You can find information about the DNS resolver to use in each data center at the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers). + You can find information about the DNS resolver to use in each data center at the [network reference documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers). ## How to configure a flexible IP on Ubuntu Linux @@ -49,7 +49,7 @@ Since the LTS release of Ubuntu Version 18.04 (Bionic Beaver) the recommended wa addresses: [163.172.123.123/24, 212.83.123.123/32] gateway4: 163.172.123.1 nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) ``` @@ -136,5 +136,5 @@ Configure the networking of your VM's as follows: * The gateway of all flexible IPs is `62.210.0.1`. This allows you to move your VMs between your hypervisors without changing the network configuration of the virtual machine. - * When configuring a failover IP in a virtual machine, you must specify which route will be used by the VM. Refer to our [dedicated documentation](/dedibox-network/network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines) for further information. + * When configuring a failover IP in a virtual machine, you must specify which route will be used by the VM. Refer to our [dedicated documentation](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines) for further information. \ No newline at end of file diff --git a/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx b/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx index e8124bd55a..21c9f24a60 100644 --- a/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx +++ b/bare-metal/elastic-metal/how-to/configure-flexible-ipv6.mdx @@ -17,15 +17,15 @@ The configuration of a flexible IPv6 depends on the Linux distribution running o - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) - Ensure your flexible IPv6 is [attached](/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip/) to your Elastic Metal server before configuring it. + Ensure your flexible IPv6 is [attached](/elastic-metal/how-to/attach-detach-flexible-ip/) to your Elastic Metal server before configuring it. - Information about the DNS resolver to use in each data center is available in the [network reference documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers). + Information about the DNS resolver to use in each data center is available in the [network reference documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers). ## How to configure IPv6 on Debian @@ -71,10 +71,10 @@ Ubuntu uses [netplan](https://netplan.io) for network configuration since Ubuntu version: 2 ``` - Replace `eno1` with the correct name of your internet interface. - - Replace the [IP addresses of the resolving DNS servers (nameservers)](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) with the ones located in the same geographical location as your machine for best perfomances. + - Replace the [IP addresses of the resolving DNS servers (nameservers)](/account/reference-content/scaleway-network-information/#dns-cache-servers) with the ones located in the same geographical location as your machine for best perfomances. - The configuration example above is valid for the main IP address of your Dedibox server. For IPv6 on a [virtual machine](/dedibox-network/network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), use the unique gateway for the failover IPv4. + The configuration example above is valid for the main IP address of your Dedibox server. For IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), use the unique gateway for the failover IPv4. 2. Check and validate your configuration file: diff --git a/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx b/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx index c40d9ff2ed..37174e5c18 100644 --- a/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx +++ b/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor.mdx @@ -18,16 +18,16 @@ When you install your server with a virtualization solution like Proxmox, you ca This guide covers the steps for configuring the network interfaces on different distributions inside a virtual machine on a Proxmox host using flexible IPv6 addresses on Elastic Metal servers. - The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine. + The DNS cache server (nameserver) may be different depending on the physical location of your server. Refer to our [network information documentation](/account/reference-content/scaleway-network-information/#dns-cache-servers) to find the IPv6 addresses to use with your machine. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) with a hypervisor (Proxmox) installed on it -- A [flexible IPv6](/bare-metal/elastic-metal/how-to/order-flexible-ip/) -- A [virtual MAC address](/bare-metal/elastic-metal/how-to/add-virtual-mac-address/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Elastic Metal server](/elastic-metal/how-to/create-server/) with a hypervisor (Proxmox) installed on it +- A [flexible IPv6](/elastic-metal/how-to/order-flexible-ip/) +- A [virtual MAC address](/elastic-metal/how-to/add-virtual-mac-address/) ## Finding your IPv6 gateway diff --git a/bare-metal/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx index 0c82b45d3d..0ce0db46cc 100644 --- a/bare-metal/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx +++ b/bare-metal/elastic-metal/how-to/configure-reverse-dns-flexible-ip.mdx @@ -18,10 +18,10 @@ Reverse DNS (rDNS) is the opposite of classic forward DNS, mapping an IP address - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) -- A [flexible IP address](/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- A [flexible IP address](/elastic-metal/how-to/attach-detach-flexible-ip/) attached to your Elastic Metal server Ensure that a corresponding `A-Record` (IPv4) or `AAAA-Record` (IPv6) pointing to the IP address exists before editing the reverse DNS. diff --git a/bare-metal/elastic-metal/how-to/connect-to-server.mdx b/bare-metal/elastic-metal/how-to/connect-to-server.mdx index d7fa7a77fa..6937ffdcb8 100644 --- a/bare-metal/elastic-metal/how-to/connect-to-server.mdx +++ b/bare-metal/elastic-metal/how-to/connect-to-server.mdx @@ -18,9 +18,9 @@ This page shows you how to connect to your Scaleway Elastic Metal server via SSH - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) ## How to connect to an Elastic Metal server from OSX (Mac) and Linux @@ -63,7 +63,7 @@ To connect to your Elastic Metal server from Windows, you will need to use a sma 4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. Do this by expanding **Connection**, then **SSH**, and finally clicking on **Auth**: -5. Click the **Browse** button and select the private key file you [generated previously](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/). +5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the Elastic Metal server. Upon the first connection, PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. @@ -82,7 +82,7 @@ To connect to your Elastic Metal server from Windows, you will need to use a sma To connect to your Elastic Metal server running Windows, you need to download a remote access tool. In this tutorial, we use [Microsoft Remote Desktop](https://apps.apple.com/us/app/microsoft-remote-desktop/id1295203466?mt=12). -1. [Create an Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) and choose a Windows image to run on it. +1. [Create an Elastic Metal server](/elastic-metal/how-to/create-server/) and choose a Windows image to run on it. - Windows images are not available for the Aluminium range of Elastic Metal servers. - Make sure you save your password securely after creating your Elastic Metal server. diff --git a/bare-metal/elastic-metal/how-to/create-server.mdx b/bare-metal/elastic-metal/how-to/create-server.mdx index ed6c47262c..47ea80fd0f 100644 --- a/bare-metal/elastic-metal/how-to/create-server.mdx +++ b/bare-metal/elastic-metal/how-to/create-server.mdx @@ -17,8 +17,8 @@ Scaleway [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) pro - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ### Steps to create an Elastic Metal server @@ -35,14 +35,14 @@ Scaleway [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/) pro - Choose your preferred billing method: **hourly** or **monthly**. - Select a server configuration from the available options. - Choose an OS to run on your server or opt for no preinstalled image. - - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/bare-metal/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration. + - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration. - Enter a name and, optionally, add tags to identify your server. - Add your SSH key (required if installing an image on your server). Depending on the OS image, you may also be asked to configure the panel user for your server. - Optionally, configure the available public bandwidth for your server. This option may not be available for all offers. - - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/network/vpc/concepts/#private-networks) + - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/vpc/concepts/#private-networks) - Review the estimated environmental footprint of your Elastic Metal server. - For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. - Review the estimated cost based on your selected configuration. diff --git a/bare-metal/elastic-metal/how-to/create-virtual-mac-group.mdx b/bare-metal/elastic-metal/how-to/create-virtual-mac-group.mdx index 26e0f982a2..d4e3a043ef 100644 --- a/bare-metal/elastic-metal/how-to/create-virtual-mac-group.mdx +++ b/bare-metal/elastic-metal/how-to/create-virtual-mac-group.mdx @@ -20,10 +20,10 @@ Once the virtual MAC group is active, IPs that share the same MAC address are li - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Created](/bare-metal/elastic-metal/how-to/create-server/) and [installed](/bare-metal/elastic-metal/how-to/install-server/) an Elastic Metal server -- [Ordered more than one flexible IP](/bare-metal/elastic-metal/how-to/order-flexible-ip/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Created](/elastic-metal/how-to/create-server/) and [installed](/elastic-metal/how-to/install-server/) an Elastic Metal server +- [Ordered more than one flexible IP](/elastic-metal/how-to/order-flexible-ip/) You need to have at least two flexible IPs in your account to create a virtual MAC group. @@ -42,6 +42,6 @@ The IPs are now linked together in a virtual MAC group and share the same virtua When moving one of the IPs of the group to another server, all other IPs within the group are automatically moved to the same server. -To remove a flexible IP from a virtual MAC group, click , then **Generate MAC** and generate a new MAC address as described in the [adding a virtual MAC Address](/bare-metal/elastic-metal/how-to/add-virtual-mac-address/) documentation. +To remove a flexible IP from a virtual MAC group, click , then **Generate MAC** and generate a new MAC address as described in the [adding a virtual MAC Address](/elastic-metal/how-to/add-virtual-mac-address/) documentation. diff --git a/bare-metal/elastic-metal/how-to/enable-smtp.mdx b/bare-metal/elastic-metal/how-to/enable-smtp.mdx index 2fb1b03546..1a46a7907b 100644 --- a/bare-metal/elastic-metal/how-to/enable-smtp.mdx +++ b/bare-metal/elastic-metal/how-to/enable-smtp.mdx @@ -19,19 +19,19 @@ If you want to send emails from your server, you can enable SMTP for each Availa - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) -- [Verified your identity](/console/account/how-to/verify-identity/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Verified your identity](/account/how-to/verify-identity/) - This guide explains how to enable SMTP on Elastic Metal servers. If you need to enable SMTP on other resources, refer to our documentation on [how to send emails from your Instance](/compute/instances/how-to/send-emails-from-your-instance/) and [how to enable SMTP on Public Gateways](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp). + This guide explains how to enable SMTP on Elastic Metal servers. If you need to enable SMTP on other resources, refer to our documentation on [how to send emails from your Instance](/instances/how-to/send-emails-from-your-instance/) and [how to enable SMTP on Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp). 1. Click **Elastic Metal** in the **Bare Metal** section on the side menu of the [Scaleway console](https://console.scaleway.com). 2. Click the **General Settings** tab. The SMTP configuration displays. - You must [verify your identity](/console/account/how-to/verify-identity/) before you can enable the SMTP ports. + You must [verify your identity](/account/how-to/verify-identity/) before you can enable the SMTP ports. 3. Toggle the switch to **ON** beside each Availability Zone for which you want to enable SMTP. diff --git a/bare-metal/elastic-metal/how-to/get-use-loyalty-reward.mdx b/bare-metal/elastic-metal/how-to/get-use-loyalty-reward.mdx index d61bfbfec6..cb8cf74002 100644 --- a/bare-metal/elastic-metal/how-to/get-use-loyalty-reward.mdx +++ b/bare-metal/elastic-metal/how-to/get-use-loyalty-reward.mdx @@ -20,7 +20,7 @@ The value of the reward is a cloud service voucher in the sum of the commitment - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An Elastic Metal server that has been up and running for 12 consecutive months diff --git a/bare-metal/elastic-metal/how-to/install-server.mdx b/bare-metal/elastic-metal/how-to/install-server.mdx index 6da56758f6..a5b9d5e7ab 100644 --- a/bare-metal/elastic-metal/how-to/install-server.mdx +++ b/bare-metal/elastic-metal/how-to/install-server.mdx @@ -19,9 +19,9 @@ If you ordered your server without a preinstalled operating system, you can inst - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) This procedure is not necessary if you preinstalled an OS on your Elastic Metal server during its creation. @@ -32,9 +32,9 @@ If you ordered your server without a preinstalled operating system, you can inst 2. Click **Install** next to the server you want to install. The server installation wizard displays. 3. Select the operating system you want to install on the machine. - Elastic Metal servers are installed with a default partition layout. For custom partitioning, you can manually reinstall your server using [remote access](/bare-metal/elastic-metal/how-to/activate-remote-access/). + Elastic Metal servers are installed with a default partition layout. For custom partitioning, you can manually reinstall your server using [remote access](/elastic-metal/how-to/activate-remote-access/). -4. Add your [SSH key](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys. Select the keys to grant access to the server by checking the corresponding boxes. +4. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys. Select the keys to grant access to the server by checking the corresponding boxes. 5. Click **Install server** to begin the installation process. The OS installation can take up to one hour. You will be able to access the machine once the installation is complete. diff --git a/bare-metal/elastic-metal/how-to/kubernetes-on-riscv.mdx b/bare-metal/elastic-metal/how-to/kubernetes-on-riscv.mdx index 3e6f7043e9..3c3069ca99 100644 --- a/bare-metal/elastic-metal/how-to/kubernetes-on-riscv.mdx +++ b/bare-metal/elastic-metal/how-to/kubernetes-on-riscv.mdx @@ -16,21 +16,21 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - [Created a Kosmos cluster](/containers/kubernetes/how-to/create-kosmos-cluster/) on which you have [configured a pool of external nodes](/containers/kubernetes/how-to/edit-kosmos-cluster/#how-to-configure-external-nodes-to-join-the-cluster) - - [Created an Elastic Metal RV1 server](/bare-metal/elastic-metal/how-to/create-server/) - - [Created an API key](/identity-and-access-management/iam/how-to/create-api-keys/) with the `KubernetesExternalNodeRegister` permission set. - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Created a Kosmos cluster](/kubernetes/how-to/create-kosmos-cluster/) on which you have [configured a pool of external nodes](/kubernetes/how-to/edit-kosmos-cluster/#how-to-configure-external-nodes-to-join-the-cluster) + - [Created an Elastic Metal RV1 server](/elastic-metal/how-to/create-server/) + - [Created an API key](/iam/how-to/create-api-keys/) with the `KubernetesExternalNodeRegister` permission set. + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) RISC-V is not yet officially supported in Kubernetes, but to let you test this technology with Kube containers, we have prepared an image with the necessary pre-built binaries. With Scaleway Kosmos and our Elastic Metal RV1, you can follow this guide to launch RISC-V containers on Kubernetes effortlessly, and in just a few minutes. -1. [Install the Elastic Metal server](/bare-metal/elastic-metal/how-to/install-server/) with the `Kosmos` image. +1. [Install the Elastic Metal server](/elastic-metal/how-to/install-server/) with the `Kosmos` image. 2. Go to the **Nodes** tab of your Kosmos cluster and click **Add external node**. 3. Take note of the `POOL_ID` and `POOL_REGION` as you will need them in the following steps. Ignore the instructions on the page to connect your server to the pool. -4. [Connect to your Elastic Metal RV1 server via SSH](/bare-metal/elastic-metal/how-to/connect-to-server/). +4. [Connect to your Elastic Metal RV1 server via SSH](/elastic-metal/how-to/connect-to-server/). 5. Export noted env variables and secret key. ``` diff --git a/bare-metal/elastic-metal/how-to/order-flexible-ip.mdx b/bare-metal/elastic-metal/how-to/order-flexible-ip.mdx index 6dadd5df03..9286874c23 100644 --- a/bare-metal/elastic-metal/how-to/order-flexible-ip.mdx +++ b/bare-metal/elastic-metal/how-to/order-flexible-ip.mdx @@ -13,18 +13,18 @@ categories: - bare-metal --- -[Flexible IP addresses for Elastic Metal servers](/bare-metal/elastic-metal/concepts/#flexible-ip) are additional IP addresses available for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/). +[Flexible IP addresses for Elastic Metal servers](/elastic-metal/concepts/#flexible-ip) are additional IP addresses available for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/). They allow you to move an IP from one server to another without changing your entire configuration. Flexible IPs can also be used as additional IP addresses to create virtual machines on your Elastic Metal server. - Scaleway offers flexible IPs for [Elastic Metal servers](/bare-metal/elastic-metal/concepts/#elastic-metal-server), [Instances](/compute/instances/concepts/#instance), and [Public Gateways](/network/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa. + Scaleway offers flexible IPs for [Elastic Metal servers](/elastic-metal/concepts/#elastic-metal-server), [Instances](/instances/concepts/#instance), and [Public Gateways](/public-gateways/concepts/#public-gateway). Each set of flexible IPs is independent and can only be used with its respective product. Instance flexible IPs cannot be attached to Elastic Metal servers or Public Gateways, and vice versa. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [installed Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [installed Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays. 2. Click the **Flexible IPs** tab at the top of the page to display the flexible IP configuration page. diff --git a/bare-metal/elastic-metal/how-to/reboot-server.mdx b/bare-metal/elastic-metal/how-to/reboot-server.mdx index e804703fe6..0ac757e0e0 100644 --- a/bare-metal/elastic-metal/how-to/reboot-server.mdx +++ b/bare-metal/elastic-metal/how-to/reboot-server.mdx @@ -18,9 +18,9 @@ If your [Elastic Metal server](https://www.scaleway.com/en/elastic-metal/) is no - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays. diff --git a/bare-metal/elastic-metal/how-to/reinstall-server.mdx b/bare-metal/elastic-metal/how-to/reinstall-server.mdx index 262aedf4f9..e13c2a7811 100644 --- a/bare-metal/elastic-metal/how-to/reinstall-server.mdx +++ b/bare-metal/elastic-metal/how-to/reinstall-server.mdx @@ -18,9 +18,9 @@ An Elastic Metal server can be reinstalled at any time from the [Scaleway consol - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) Reinstalling your server permanently erases the disk and all its data. Make sure to have a backup before reinstalling your server. @@ -30,7 +30,7 @@ An Elastic Metal server can be reinstalled at any time from the [Scaleway consol 2. Click next to the server you want to reinstall. A drop-down menu displays. 3. Click **Reinstall** in the menu to enter the installation wizard. 4. Choose the operating system that you want to install on the machine. -5. Add your [SSH key](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it displays in the list of keys. Choose the keys to grant access to the server by ticking or unticking the corresponding checkbox. +5. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key). If you have already [uploaded a key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it displays in the list of keys. Choose the keys to grant access to the server by ticking or unticking the corresponding checkbox. 6. Click **Reinstall server** to launch the installation. It will take about 10 minutes to complete. diff --git a/bare-metal/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx b/bare-metal/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx index f107d06d28..a381499afd 100644 --- a/bare-metal/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx +++ b/bare-metal/elastic-metal/how-to/send-metrics-logs-to-cockpit.mdx @@ -13,15 +13,15 @@ categories: - bare-metal --- -Monitoring your dedicated servers with [Scaleway Cockpit](/observability/cockpit/quickstart/) offers detailed information about performance and health, ensuring optimal functionality and proactive issue resolution. +Monitoring your dedicated servers with [Scaleway Cockpit](/cockpit/quickstart/) offers detailed information about performance and health, ensuring optimal functionality and proactive issue resolution. Cockpit provides a user-friendly interface for real-time monitoring of CPU, memory, disk usage, and network activity, enhancing the reliability and performance of bare metal servers. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Elastic Metal](/bare-metal/elastic-metal/quickstart/) or [Dedibox](/bare-metal/dedibox/quickstart/) server running on a Linux operating system +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Elastic Metal](/elastic-metal/quickstart/) or [Dedibox](/dedibox-scaleway/quickstart/) server running on a Linux operating system * Having the default configuration on your agents might lead to more of your resources’ metrics being sent, a high consumption and a high bill at the end of the month. @@ -30,12 +30,12 @@ Cockpit provides a user-friendly interface for real-time monitoring of CPU, memo ## Accessing Cockpit -1. Create a token with the `push` permission for metrics/logs to Cockpit by following the instructions provided [in the dedicated documentation](/observability/cockpit/how-to/create-token/). -2. Configure the Grafana Agent to push metrics/logs to Cockpit. Refer to the [official documentation](/observability/cockpit/api-cli/configuring-grafana-agent/) for detailed instructions. +1. Create a token with the `push` permission for metrics/logs to Cockpit by following the instructions provided [in the dedicated documentation](/cockpit/how-to/create-token/). +2. Configure the Grafana Agent to push metrics/logs to Cockpit. Refer to the [official documentation](/cockpit/api-cli/configuring-grafana-agent/) for detailed instructions. For efficient cost management and near real-time resource monitoring, it is recommended to set the interval to 1 minute. -3. [Retrieve your Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/), then use them to [access your Cockpit dashboards](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/). +3. [Retrieve your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/), then use them to [access your Cockpit dashboards](/cockpit/how-to/access-grafana-and-managed-dashboards/). ## Importing dashboards diff --git a/bare-metal/elastic-metal/how-to/shutdown-server.mdx b/bare-metal/elastic-metal/how-to/shutdown-server.mdx index de90e70f9e..e162e5ecaf 100644 --- a/bare-metal/elastic-metal/how-to/shutdown-server.mdx +++ b/bare-metal/elastic-metal/how-to/shutdown-server.mdx @@ -18,9 +18,9 @@ An Elastic Metal server can be shut down from the [Scaleway console](https://con - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays. diff --git a/bare-metal/elastic-metal/how-to/use-private-networks.mdx b/bare-metal/elastic-metal/how-to/use-private-networks.mdx index 69725c8f42..d1cb5bdea4 100644 --- a/bare-metal/elastic-metal/how-to/use-private-networks.mdx +++ b/bare-metal/elastic-metal/how-to/use-private-networks.mdx @@ -13,7 +13,7 @@ categories: - bare-metal --- -[Private Networks](/network/vpc/concepts/#private-networks) allow your Elastic Metal servers to communicate in an isolated and secure network without needing to be connected to the public internet. This is an optional-billed feature, available with our Elastic Metal server ranges. +[Private Networks](/vpc/concepts/#private-networks) allow your Elastic Metal servers to communicate in an isolated and secure network without needing to be connected to the public internet. This is an optional-billed feature, available with our Elastic Metal server ranges. Each server can be connected to one or several Private Networks, letting you build your own network topologies. Private Networks' built-in DHCP server manages the allocation of private IP addresses for Elastic Metal servers (and other resources) when they are attached to the network. @@ -22,8 +22,8 @@ Private Networks allow your Elastic Metal servers to communicate with other Scal - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to enable and disable the Private Networks feature @@ -35,7 +35,7 @@ You can enable/disable Private Networks on compatible Elastic Metal servers eith ### During the creation of your Elastic Metal server -You can choose to enable the Private Networks feature during the [creation of your Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/). Simply use the toggle icon when prompted by the creation wizard to enable the feature. If you do not enable the feature, it remains disabled by default. +You can choose to enable the Private Networks feature during the [creation of your Elastic Metal server](/elastic-metal/how-to/create-server/). Simply use the toggle icon when prompted by the creation wizard to enable the feature. If you do not enable the feature, it remains disabled by default. ### After the creation of your Elastic Metal server @@ -52,7 +52,7 @@ You can choose to enable the Private Networks feature during the [creation of yo You can attach/detach Elastic Metal servers to a Private Network from either the Elastic Metal section of the console, or the VPC section. -You can also reserve IP addresses with IPAM and attach them to specific MAC addresses, to facilitate the attachment of virtual machines hosted on your server, to Private Networks. See the IPAM documentation on [reserving a private IP with an attached MAC address](/network/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address) for more information. +You can also reserve IP addresses with IPAM and attach them to specific MAC addresses, to facilitate the attachment of virtual machines hosted on your server, to Private Networks. See the IPAM documentation on [reserving a private IP with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address) for more information. ### From the Elastic Metal section of the console @@ -65,17 +65,17 @@ You can also reserve IP addresses with IPAM and attach them to specific MAC addr - Select **Attach to a new Private Network**, and enter a name for the new Private Network you wish to create. The Private Network will have default settings, meaning: - - It is created in your [default VPC](/network/vpc/concepts/#default-vpc) for the region - - It has an auto-generated [CIDR block](/network/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network. + - It is created in your [default VPC](/vpc/concepts/#default-vpc) for the region + - It has an auto-generated [CIDR block](/vpc/concepts/#cidr-block) used to allocate private IP addresses to servers attached to the network. Each attached Elastic Metal server will get an IPv4 and an IPv6 address on the Private Network. -6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/network/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network. +6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a [reserved IP address](/ipam/concepts/#reserved-ip-address) for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Elastic Metal server will have on this Private Network. 7. Click **Attach to Private Network** to confirm. ### From the VPC section of the console Creating a new Private Network from the VPC section of the console allows you to control which VPC you create it in, and to optionally create a custom CIDR block for the network. -See our dedicated documentation [how to create a Private Network](/network/vpc/how-to/create-private-network/) and [how to attach resources](/network/vpc/how-to/attach-resources-to-pn/) from the VPC section of the console. +See our dedicated documentation [how to create a Private Network](/vpc/how-to/create-private-network/) and [how to attach resources](/vpc/how-to/attach-resources-to-pn/) from the VPC section of the console. ## How to configure the network interface on your Elastic Metal server for Private Networks @@ -86,7 +86,7 @@ You must configure the virtual network interface on each Elastic Metal server yo 1. Make a note of your Elastic Metal server's VLAN ID. You can view this in the **Private Networks** tab of the Elastic Metal server in question. -2. [Connect to your Elastic Metal server via SSH](/bare-metal/elastic-metal/how-to/connect-to-server/). +2. [Connect to your Elastic Metal server via SSH](/elastic-metal/how-to/connect-to-server/). 3. Find the network interface using the `ip link show` command: ```bash ip link show @@ -112,7 +112,7 @@ You must configure the virtual network interface on each Elastic Metal server yo sudo ip link set eno1.1234 up ``` - If DHCP is [activated on your Private Network](/network/vpc/how-to/activate-dhcp/) and you are using a DHCP client, you do not need to continue to the next step. Your Elastic Metal server should be assigned an IP address which is compatible with our [internal IPAM](/network/vpc/concepts/#ipam). + If DHCP is [activated on your Private Network](/vpc/how-to/activate-dhcp/) and you are using a DHCP client, you do not need to continue to the next step. Your Elastic Metal server should be assigned an IP address which is compatible with our [internal IPAM](/vpc/concepts/#ipam). If you have not activated DHCP or do not have a DHCP client, proceed to the next step to manually configure an IP address. @@ -145,7 +145,7 @@ You must configure the virtual network interface on each Elastic Metal server yo 1. Log into your server as `Administrateur` using the Remote Desktop client. - The default language of Windows Server installations is French. Make sure to use the user `Administrateur` when connecting to your server. If required, you can [change the language of the operating system](/dedibox/dedicated-servers/how-to/change-win-server-language/). + The default language of Windows Server installations is French. Make sure to use the user `Administrateur` when connecting to your server. If required, you can [change the language of the operating system](/dedicated-servers/how-to/change-win-server-language/). 2. Launch the **Server Manager** application. 3. Click **Local Server** in the menu on the left. Then click **NIC Teaming** in the **Properties** section. @@ -172,6 +172,6 @@ You must configure the virtual network interface on each Elastic Metal server yo Before deleting a Private Network, you must detach all resources attached to it. -See our dedicated documentation [how to delete a Private Network](/network/vpc/how-to/delete-private-network/). +See our dedicated documentation [how to delete a Private Network](/vpc/how-to/delete-private-network/). diff --git a/bare-metal/elastic-metal/how-to/use-rescue-mode.mdx b/bare-metal/elastic-metal/how-to/use-rescue-mode.mdx index 6045cc0685..55ca878852 100644 --- a/bare-metal/elastic-metal/how-to/use-rescue-mode.mdx +++ b/bare-metal/elastic-metal/how-to/use-rescue-mode.mdx @@ -16,15 +16,15 @@ categories: Rescue mode allows you to boot an [Elastic Metal server](https://www.scaleway.com/en/elastic-metal/) from the network. It loads a rescue operating system based on [Ubuntu Linux](https://ubuntu.com/) that runs entirely in the server's RAM. This enables you to perform maintenance and data recovery operations, even if the machine is otherwise unreachable in its normal mode. - This documentation specifically covers rescue mode for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/). If you need to use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/), please refer to the corresponding [documentation](/compute/instances/how-to/use-boot-modes/#how-to-use-rescue-mode). + This documentation specifically covers rescue mode for [Elastic Metal servers](https://www.scaleway.com/en/elastic-metal/). If you need to use rescue mode on [Instances](https://www.scaleway.com/en/virtual-instances/), please refer to the corresponding [documentation](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. This opens the Elastic Metal dashboard. diff --git a/bare-metal/elastic-metal/how-to/view-the-event-logs.mdx b/bare-metal/elastic-metal/how-to/view-the-event-logs.mdx index b5fa2468b3..9cb722bbe1 100644 --- a/bare-metal/elastic-metal/how-to/view-the-event-logs.mdx +++ b/bare-metal/elastic-metal/how-to/view-the-event-logs.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) 1. Click **Elastic Metal** in the **Bare Metal** section of the [Scaleway console](https://console.scaleway.com) side menu. The Elastic Metal dashboard displays. diff --git a/bare-metal/elastic-metal/index.mdx b/bare-metal/elastic-metal/index.mdx index 0506394943..ae013641c9 100644 --- a/bare-metal/elastic-metal/index.mdx +++ b/bare-metal/elastic-metal/index.mdx @@ -8,7 +8,7 @@ meta: productName="Elastic Metal" productLogo="elasticMetal" description="Elastic Metal is the ultimate solution for demanding workloads and data-intensive applications. Deploy dedicated servers on the go with security and performance." - url="/bare-metal/elastic-metal/quickstart" + url="/elastic-metal/quickstart" label="Elastic Metal Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and delete an Elastic Metal server in a few steps." label="View Quickstart" - url="/bare-metal/elastic-metal/quickstart/" + url="/elastic-metal/quickstart/" /> diff --git a/bare-metal/elastic-metal/quickstart.mdx b/bare-metal/elastic-metal/quickstart.mdx index bbc695ee33..d94c8bcc1e 100644 --- a/bare-metal/elastic-metal/quickstart.mdx +++ b/bare-metal/elastic-metal/quickstart.mdx @@ -13,13 +13,13 @@ categories: - bare-metal --- -Scaleway Elastic Metal are dedicated physical servers you can order on-demand, like Instances. These servers are ideal for large workloads, big data, and applications that require increased security and dedicated resources. You can install an OS or other [image](/bare-metal/elastic-metal/concepts/#image) on your Elastic Metal server and connect to it via SSH to use it as you require. You can power off the server when you are not using or delete it from your account once you have finished with it. +Scaleway Elastic Metal are dedicated physical servers you can order on-demand, like Instances. These servers are ideal for large workloads, big data, and applications that require increased security and dedicated resources. You can install an OS or other [image](/elastic-metal/concepts/#image) on your Elastic Metal server and connect to it via SSH to use it as you require. You can power off the server when you are not using or delete it from your account once you have finished with it. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## How to create an Elastic Metal server @@ -36,14 +36,14 @@ Scaleway Elastic Metal are dedicated physical servers you can order on-demand, l - Choose your preferred billing method: **hourly** or **monthly**. - Select a server configuration from the available options. - Choose an OS to run on your server or opt for no preinstalled image. - - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/bare-metal/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration. + - Configure server partitioning. You can either choose a default configuration or [configure your own partitioning](/elastic-metal/how-to/configure-disk-partitions/) using a JSON configuration. - Enter a name and, optionally, add tags to identify your server. - Add your SSH key (required if installing an image on your server). Depending on the OS image, you may also be asked to configure the panel user for your server. - Optionally, configure the available public bandwidth for your server. This option may not be available for all offers. - - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/network/vpc/concepts/#private-networks) + - Optionally, decide whether to enable the Private Networks feature. [Learn more about Private Networks](/vpc/concepts/#private-networks) - Review the estimated environmental footprint of your Elastic Metal server. - For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. - Review the estimated cost based on your selected configuration. @@ -61,9 +61,9 @@ You can monitor the delivery progress from the list of Elastic Metal servers in 2. Choose the Elastic Metal server you want to install from the list. 3. Click **Install** to launch the OS installation wizard. 4. Choose the operating system that you want to install on the machine. -5. Add your [SSH key](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key). +5. Add your [SSH key](/organizations-and-projects/concepts/#ssh-key). - If you have already [uploaded an SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys. + If you have already [uploaded an SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface), it will appear in the list of keys. 6. Check the corresponding boxes to grant access to the server. 7. Click **Install server**. diff --git a/bare-metal/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx b/bare-metal/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx index 997dbc098d..7235e11537 100644 --- a/bare-metal/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx +++ b/bare-metal/elastic-metal/reference-content/elastic-metal-rv1-guidelines.mdx @@ -110,7 +110,7 @@ Due to hardware specificities, it is not possible to use the kernel provided by major Linux distributions directly on EM-RV1 servers. Instead, we provide a custom upgrade channel. Follow the steps below to update your kernel: -1. [Reboot your EM-RV1 server in rescue mode](/bare-metal/elastic-metal/how-to/use-rescue-mode/). +1. [Reboot your EM-RV1 server in rescue mode](/elastic-metal/how-to/use-rescue-mode/). 2. Log into the machine over SSH using the `rescue` user. 3. Update the kernel: ```bash diff --git a/bare-metal/elastic-metal/reference-content/end-of-support-esxi.mdx b/bare-metal/elastic-metal/reference-content/end-of-support-esxi.mdx index 2d8949f681..115629c9e0 100644 --- a/bare-metal/elastic-metal/reference-content/end-of-support-esxi.mdx +++ b/bare-metal/elastic-metal/reference-content/end-of-support-esxi.mdx @@ -22,7 +22,7 @@ This change does not affect servers currently running ESXi images. However, it w For more information about Broadcom's decision to retire the vSphere Free Edition images, refer to their official knowledge base article: [End Of General Availability of the free vSphere Hypervisor (ESXi 7.x and 8.x)](https://knowledge.broadcom.com/external/article?legacyId=2107518). -You may still be able to install ESXi on Elastic Metal or Dedibox servers using the [KVM-over-IP](/dedibox/kvm-over-ip/quickstart/) system. However, note that we cannot provide support for its configuration or operation. +You may still be able to install ESXi on Elastic Metal or Dedibox servers using the [KVM-over-IP](/dedibox-kvm-over-ip/quickstart/) system. However, note that we cannot provide support for its configuration or operation. For the best experience, we recommend using one of the officially supported hypervisors: diff --git a/bare-metal/elastic-metal/reference-content/shared-responsibility-model.mdx b/bare-metal/elastic-metal/reference-content/shared-responsibility-model.mdx index 9963611778..662f4f1dd1 100644 --- a/bare-metal/elastic-metal/reference-content/shared-responsibility-model.mdx +++ b/bare-metal/elastic-metal/reference-content/shared-responsibility-model.mdx @@ -48,7 +48,7 @@ It is your responsibility to ensure data redundancy if necessary, by relying on In the event of a disk or a hardware failure, we cannot guarantee that you will regain access to your machine and data. The failure may require a complete replacement of the machine. Therefore, it is your responsibility to ensure in advance that you have a backup or redundancy of your data on another server. **We cannot be held responsible for the loss of your data.** -Backups and snapshots must be configured by you. Please refer to our documentation for assistance in setting up backups for [Dedibox](/dedibox/dedicated-servers/how-to/use-dedibackup-ftp-backup/), [Elastic Metal](/faq/elastic-metal/#how-do-i-back-up-an-elastic-metal-server), and [Apple silicon](/faq/apple-silicon/#how-can-i-back-up-my-mac-mini). +Backups and snapshots must be configured by you. Please refer to our documentation for assistance in setting up backups for [Dedibox](/dedicated-servers/how-to/use-dedibackup-ftp-backup/), [Elastic Metal](/faq/elastic-metal/#how-do-i-back-up-an-elastic-metal-server), and [Apple silicon](/faq/apple-silicon/#how-can-i-back-up-my-mac-mini). Restoring snapshots or backups needs to be triggered by you. ## Configuration and version management @@ -97,7 +97,7 @@ We do not have the technical capability to access your machine once it is instal ## Identity and access management -Elastic Metal servers provide [IAM permissions](/identity-and-access-management/iam/reference-content/permission-sets/) sets which allow or restrict specific actions a user or application can perform, such as creating or deleting Elastic Metal servers. You remain responsible for giving these permissions to the relevant users or applications and reviewing these accesses frequently. +Elastic Metal servers provide [IAM permissions](/iam/reference-content/permission-sets/) sets which allow or restrict specific actions a user or application can perform, such as creating or deleting Elastic Metal servers. You remain responsible for giving these permissions to the relevant users or applications and reviewing these accesses frequently. Dedibox servers provide [outsourcing services features](https://www.scaleway.com/en/dedibox/outsourcing/), allowing you to delegate resource management. You remain responsible for giving access and management permissions to the relevant users or outsourcing providers and reviewing these accesses frequently. diff --git a/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx b/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx index 08f59ae3d0..dcb66f3f6e 100644 --- a/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx +++ b/bare-metal/elastic-metal/troubleshooting/enable-ssh-virtualization-distribution.mdx @@ -23,7 +23,7 @@ Elastic Metal servers support the installation of virtualization solutions Proxm - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) with Proxmox VE +- An [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) with Proxmox VE ## Enabling SSH on Proxmox VE diff --git a/bare-metal/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx b/bare-metal/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx index c97a28c058..b2027eabb8 100644 --- a/bare-metal/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx +++ b/bare-metal/elastic-metal/troubleshooting/replace-failed-drive-software-raid.mdx @@ -16,12 +16,12 @@ dates: RAID1 configurations offer redundancy by mirroring data across two drives. If one drive fails, the other continues operating, ensuring data integrity. This guide explains how to replace a failed drive and rebuild the RAID1 array using the `mdadm` utility. -Each Elastic Metal server uses a RAID1 configuration after installation from the Scaleway console. If you want to change the RAID configuration of the server, you can modify the RAID array using [rescue mode](/bare-metal/elastic-metal/how-to/use-rescue-mode/). +Each Elastic Metal server uses a RAID1 configuration after installation from the Scaleway console. If you want to change the RAID configuration of the server, you can modify the RAID array using [rescue mode](/elastic-metal/how-to/use-rescue-mode/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An Elastic Metal server with at least two disks in RAID1 ## Removing the failed disk from the RAID configuration @@ -30,7 +30,7 @@ Each Elastic Metal server uses a RAID1 configuration after installation from the We recommend [backing up your data](/en/docs/tutorials/restic-s3-backup/) before proceeding. -1. Boot server in [rescue mode](/bare-metal/elastic-metal/how-to/use-rescue-mode/) from the Scaleway console. +1. Boot server in [rescue mode](/elastic-metal/how-to/use-rescue-mode/) from the Scaleway console. 2. Log in to the server using the rescue account: ``` ssh em-XXX@ diff --git a/bare-metal/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx b/bare-metal/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx index 6ab368956b..db758b61dc 100644 --- a/bare-metal/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx +++ b/bare-metal/elastic-metal/troubleshooting/reset-admin-password-windows-server.mdx @@ -21,8 +21,8 @@ If you have lost this password, you can reset it via rescue mode. This guide exp - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An Elastic Metal server [installed](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An Elastic Metal server [installed](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) ## Removing the old Administrator password @@ -30,7 +30,7 @@ If you have lost this password, you can reset it via rescue mode. This guide exp We recommend [backing up your data](/tutorials/restic-s3-backup/) before proceeding. -1. Reboot your Elastic Metal server into [rescue mode](/bare-metal/elastic-metal/how-to/use-rescue-mode/). +1. Reboot your Elastic Metal server into [rescue mode](/elastic-metal/how-to/use-rescue-mode/). 2. Log into rescue mode. 3. Install the packages `ntfs-3g` and `chntpw` using the APT package manager. ``` @@ -113,11 +113,11 @@ If you have lost this password, you can reset it via rescue mode. This guide exp Write hive files? (y/n) [n] : y 0 - OK ``` -10. Reboot the server back into [normal mode](/bare-metal/elastic-metal/how-to/use-rescue-mode/#rebooting-back-to-normal-mode). +10. Reboot the server back into [normal mode](/elastic-metal/how-to/use-rescue-mode/#rebooting-back-to-normal-mode). ## Setting a new Administrator password -1. [Activate remote access](/bare-metal/elastic-metal/how-to/activate-remote-access/) on your server to connect via the KVM over IP device. +1. [Activate remote access](/elastic-metal/how-to/activate-remote-access/) on your server to connect via the KVM over IP device. 2. Open the remote console to access the screen output. 3. Open the start menu and select the `Administrator` username to access user settings. 4. Click the password panel, then **Add** to create a new password. diff --git a/bin/clean-categories b/bin/clean-categories new file mode 100755 index 0000000000..54229fcdf2 --- /dev/null +++ b/bin/clean-categories @@ -0,0 +1,89 @@ +#!/bin/bash + +CATEGORIES=(ai-data bare-metal compute console containers dedibox dedibox-console developer-tools environmental-footprint identity-and-access-management labs managed-databases managed-services network observability partners serverless storage) + +CATEGORIES_REGEX="($(IFS='|'; echo "${CATEGORIES[*]}"))" + +#echo "Capturing group : $CATEGORIES_REGEX" + +for FILE in $(find . -type f -name '*.mdx') + do + if [ -f "$FILE" ]; then + echo "Traitement du fichier : $FILE" + + # Remplacer les exceptions + + # dedibox-console + sed -i.bak -E "s#dedibox-console/account#dedibox-account#g" "$FILE" + # dedibox/vps/quickstart.mdx + sed -i.bak -E "s#dedibox-console/classic-hosting/#classic-hosting/#g" "$FILE" + # dedibox-console/classic-hosting/how-to/change-password-mysql-database.mdx + sed -i.bak -E "s#dedibox-console/cpanel-hosting/#cpanel-hosting/#g" "$FILE" + # dedibox-console/cpanel-hosting/reference-content.mdx + + # dedibox-network + sed -i.bak -E "s#dedibox-network/network/#dedibox-network/#g" "$FILE" + # dedibox-network/network/index.mdx + sed -i.bak -E "s#dedibox-network/rpn/#dedibox-rpn/#g" "$FILE" + # dedibox-network/rpn/index.mdx + sed -i.bak -E "s#dedibox-network/ipv6/#dedibox-ipv6/#g" "$FILE" + # dedibox-network/ipv6/concepts.mdx + sed -i.bak -E "s#dedibox-network/domains/#dedibox-domains/#g" "$FILE" + # dedibox-network/dns/concepts.mdx + sed -i.bak -E "s#dedibox-network/dns/#dedibox-dns/#g" "$FILE" + # dedibox-network/dns/index.mdx + sed -i.bak -E "s#dedibox-network/ip-failover/#dedibox-ip-failover/#g" "$FILE" + # dedibox-network/ipv6/concepts.mdx + + # dedibox + sed -i.bak -E "s#dedibox/vps/#dedibox-vps/#g" "$FILE" + # dedibox/vps/how-to/delete-vps.mdx + sed -i.bak -E "s#dedibox/kvm-over-ip/#dedibox-kvm-over-ip/#g" "$FILE" + # dedibox/kvm-over-ip/how-to/dell-idrac9.mdx + + # storage + sed -i.bak -E "s#storage/object/#object-storage/#g" "$FILE" + # compute/instances/api-cli/snapshot-import-export-feature.mdx + sed -i.bak -E "s#storage/block/#block-storage/#g" "$FILE" + # compute/gpu/how-to/use-gpu-with-docker.mdx + + # serverless + sed -i.bak -E "s#serverless/sql-databases/#serverless-sql-databases/#g" "$FILE" + # faq/serverless-sql-databases.mdx + sed -i.bak -E "s#serverless/functions/#serverless-functions/#g" "$FILE" + # faq/serverless-jobs.mdx + sed -i.bak -E "s#serverless/containers/#serverless-containers/#g" "$FILE" + # serverless/containers/concepts.mdx + sed -i.bak -E "s#serverless/jobs/#serverless-jobs/#g" "$FILE" + # changelog/november2024/2024-11-05-jobs-added-serverless-jobs-integrates-secret-manager.mdx + + # managed-database + sed -i.bak -E "s#managed-databases/postgresql-and-mysql/#managed-databases-for-postgresql-and-mysql/#g" "$FILE" + # changelog/august2024/2024-08-02-postgresql-and-mysql-added-encryption-at-rest-available.mdx + sed -i.bak -E "s#managed-databases/redis/#managed-databases-for-redis/#g" "$FILE" + # faq/databases-for-redis.mdx + sed -i.bak -E "s#managed-databases/mongodb/#managed-mongodb-databases/#g" "$FILE" + # managed-databases/mongodb/how-to/manage-snapshots.mdx + + # bare-metal + sed -i.bak -E "s#bare-metal/dedibox/#dedibox-scaleway/#g" "$FILE" + # bare-metal/dedibox/how-to/activate-ipv6-block.mdx + + # Dans le markdown & les compodants mdx : + # On supprime la catégorie des url relatives + # On prends garde à ne pas modifier les pages catégories (ex: /managed-databases/) ces URL n'ayant que la catégorie, si on la supprime on se retrouve avec une redirection sur la home + sed -i.bak -E "s#\(/$CATEGORIES_REGEX/([^/\)]+)#\(/\2#g" "$FILE" + sed -i.bak -E "s#\"/$CATEGORIES_REGEX/([^/\)]+)#\"/\2#g" "$FILE" + + # Remplacer les URLs absolues + sed -i.bak -E "s#(https://www\.scaleway\.com/en/docs)/($CATEGORIES_REGEX)/([^/]+)#\1/\4#g" "$FILE" + + # Nettoyer les doublons de slashes + sed -i.bak 's#docs//#docs/#g' "$FILE" + + # Supprimer les fichiers .bak + rm "$FILE.bak" + else + echo "Aucun fichier trouvé." + fi +done \ No newline at end of file diff --git a/changelog/april2023/2023-04-11-load-balancers-added-http-redirect-and-unconditional.mdx b/changelog/april2023/2023-04-11-load-balancers-added-http-redirect-and-unconditional.mdx index 8117a88514..0300f84c61 100644 --- a/changelog/april2023/2023-04-11-load-balancers-added-http-redirect-and-unconditional.mdx +++ b/changelog/april2023/2023-04-11-load-balancers-added-http-redirect-and-unconditional.mdx @@ -15,5 +15,5 @@ HTTP redirects come as a new type of ACL configured within a frontend. You can f Furthermores, we are introducing the ability to create unconditioned ACLs, allowing you to explicitly define a default and catch all behavior for your frontend’s ACL. -Check out our documentation to find out [how to create and manage your ACLs](/network/load-balancer/how-to/create-manage-acls/) to get started, or our [reference documentation](/network/load-balancer/reference-content/acls/) for a deeper dive into ACLs. +Check out our documentation to find out [how to create and manage your ACLs](/load-balancer/how-to/create-manage-acls/) to get started, or our [reference documentation](/load-balancer/reference-content/acls/) for a deeper dive into ACLs. diff --git a/changelog/april2023/2023-04-19-cockpit-added-observability---documentation--.mdx b/changelog/april2023/2023-04-19-cockpit-added-observability---documentation--.mdx index 1928674eea..487d151014 100644 --- a/changelog/april2023/2023-04-19-cockpit-added-observability---documentation--.mdx +++ b/changelog/april2023/2023-04-19-cockpit-added-observability---documentation--.mdx @@ -11,7 +11,7 @@ product: cockpit Limitations for our Mimir metrics ingestor is now available! -Refer to [our Mimir metrics documentation](/observability/cockpit/reference-content/cockpit-limitations/#limits-for-mimir) to find out about the limitations for Mimir. +Refer to [our Mimir metrics documentation](/cockpit/reference-content/cockpit-limitations/#limits-for-mimir) to find out about the limitations for Mimir. If you need custom limitations, feel free to [reach out to us](https://www.scaleway.com/fr/betas/#observability). diff --git a/changelog/april2023/2023-04-26-object-storage-added-iam-at-the-resource.mdx b/changelog/april2023/2023-04-26-object-storage-added-iam-at-the-resource.mdx index ff96369743..515ea6b927 100644 --- a/changelog/april2023/2023-04-26-object-storage-added-iam-at-the-resource.mdx +++ b/changelog/april2023/2023-04-26-object-storage-added-iam-at-the-resource.mdx @@ -11,5 +11,5 @@ product: object-storage It is now possible to designate users or applications as principals of bucket policies, providing access management granularity at the resource level on top of IAM. -Check out our documentation to start [setting up granular access to Object Storage](https://www.scaleway.com/en/docs/storage/object/api-cli/combining-iam-and-object-storage). +Check out our documentation to start [setting up granular access to Object Storage](https://www.scaleway.com/en/docs/object-storage/api-cli/combining-iam-and-object-storage). diff --git a/changelog/april2023/2023-04-27-transactional-email-added-domain-reputation-management-policy.mdx b/changelog/april2023/2023-04-27-transactional-email-added-domain-reputation-management-policy.mdx index 5d5c34f609..e1a5ddc89e 100644 --- a/changelog/april2023/2023-04-27-transactional-email-added-domain-reputation-management-policy.mdx +++ b/changelog/april2023/2023-04-27-transactional-email-added-domain-reputation-management-policy.mdx @@ -9,5 +9,5 @@ category: managed-services product: transactional-email --- -Find out [how we protect the reputation of your domain](/managed-services/transactional-email/reference-content/protecting-your-domain-reputation/) with progressive emailing! +Find out [how we protect the reputation of your domain](/transactional-email/reference-content/protecting-your-domain-reputation/) with progressive emailing! diff --git a/changelog/april2023/2023-04-27-transactional-email-added-new-iam-permissions-set.mdx b/changelog/april2023/2023-04-27-transactional-email-added-new-iam-permissions-set.mdx index 9eb87f4993..44cd44dcac 100644 --- a/changelog/april2023/2023-04-27-transactional-email-added-new-iam-permissions-set.mdx +++ b/changelog/april2023/2023-04-27-transactional-email-added-new-iam-permissions-set.mdx @@ -9,7 +9,7 @@ category: managed-services product: transactional-email --- -We have integrated the following [IAM permissions,](/identity-and-access-management/iam/reference-content/permission-sets/) allowing separate management of emails and domains on Transactional Email: +We have integrated the following [IAM permissions,](/iam/reference-content/permission-sets/) allowing separate management of emails and domains on Transactional Email: - `TransactionalEmailDomainFullAccess` - `TransactionalEmailDomainReadyOnly` - `TransactionalEmailEmailFullAccess` diff --git a/changelog/april2023/2023-04-28-secret-manager-added-secret-manager-is-generally.mdx b/changelog/april2023/2023-04-28-secret-manager-added-secret-manager-is-generally.mdx index 2df158a752..e3d52b00d1 100644 --- a/changelog/april2023/2023-04-28-secret-manager-added-secret-manager-is-generally.mdx +++ b/changelog/april2023/2023-04-28-secret-manager-added-secret-manager-is-generally.mdx @@ -11,5 +11,5 @@ product: secret-manager Secret Manager is now in General Availability. -For more information, refer to the [Secret Manager product documentation](/identity-and-access-management/secret-manager/quickstart/) or the [Secret Manager product website](https://www.scaleway.com/en/secret-manager/) +For more information, refer to the [Secret Manager product documentation](/secret-manager/quickstart/) or the [Secret Manager product website](https://www.scaleway.com/en/secret-manager/) diff --git a/changelog/april2024/2024-04-04-cockpit-added-transactional-email-dashboard-is-now-avai.mdx b/changelog/april2024/2024-04-04-cockpit-added-transactional-email-dashboard-is-now-avai.mdx index 6ff58ef551..a7a6eddc99 100644 --- a/changelog/april2024/2024-04-04-cockpit-added-transactional-email-dashboard-is-now-avai.mdx +++ b/changelog/april2024/2024-04-04-cockpit-added-transactional-email-dashboard-is-now-avai.mdx @@ -13,8 +13,8 @@ Your monitoring experience just got even better with the addition of a Transacti Gain insights into every aspect of your email delivery with a comprehensive array of metrics, including: -- **Current [domain reputation](/managed-services/transactional-email/concepts/#reputation-score):** Stay informed about your domain's reputation score. -- **Reputation score evolution:** Track how your reputation score evolves, and make informed decisions to maintain or enhance it. Read [our dedicated documentation](/managed-services/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how. +- **Current [domain reputation](/transactional-email/concepts/#reputation-score):** Stay informed about your domain's reputation score. +- **Reputation score evolution:** Track how your reputation score evolves, and make informed decisions to maintain or enhance it. Read [our dedicated documentation](/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how. - **Total emails sent:** Keep track of the volume of emails your system is processing. - **Total email drops:** Identify delivery issues and take proactive measures to address them. - **General activity overview:** Get a bird's-eye view of your email activity trends over time. diff --git a/changelog/april2024/2024-04-04-load-balancers-added-public-ipv6-addresses-are-now-avai.mdx b/changelog/april2024/2024-04-04-load-balancers-added-public-ipv6-addresses-are-now-avai.mdx index f3efa5af76..3fc16e70b1 100644 --- a/changelog/april2024/2024-04-04-load-balancers-added-public-ipv6-addresses-are-now-avai.mdx +++ b/changelog/april2024/2024-04-04-load-balancers-added-public-ipv6-addresses-are-now-avai.mdx @@ -9,5 +9,5 @@ category: network product: load-balancers --- -You can now add a public IPv6 address to both new and existing Load Balancers. This feature is available for all regions, and IPv6 addresses can be attached in addition to existing IPv4 addresses. Find out more in our [documentation](https://www.scaleway.com/en/docs/network/load-balancer/how-to/create-manage-flex-ips/). +You can now add a public IPv6 address to both new and existing Load Balancers. This feature is available for all regions, and IPv6 addresses can be attached in addition to existing IPv4 addresses. Find out more in our [documentation](https://www.scaleway.com/en/docs/load-balancer/how-to/create-manage-flex-ips/). diff --git a/changelog/april2024/2024-04-15-transactional-email-security-dmarc-policy.mdx b/changelog/april2024/2024-04-15-transactional-email-security-dmarc-policy.mdx index 43121fb567..a93c2c024a 100644 --- a/changelog/april2024/2024-04-15-transactional-email-security-dmarc-policy.mdx +++ b/changelog/april2024/2024-04-15-transactional-email-security-dmarc-policy.mdx @@ -9,6 +9,6 @@ category: managed-services product: transactional-email --- -After SPF, DKIM, and MX, we are introducing the DMARC policy to provide further protection for your domains against identity theft and phishing attacks. [Read our dedicated documentation](/managed-services/transactional-email/how-to/add-dmarc-record/) to understand DMARC, and learn how to configure it. +After SPF, DKIM, and MX, we are introducing the DMARC policy to provide further protection for your domains against identity theft and phishing attacks. [Read our dedicated documentation](/transactional-email/how-to/add-dmarc-record/) to understand DMARC, and learn how to configure it. diff --git a/changelog/april2024/2024-04-19-transactional-email-added-xml-attachments-are-now-avail.mdx b/changelog/april2024/2024-04-19-transactional-email-added-xml-attachments-are-now-avail.mdx index 3cafafb2cd..cb9afe1575 100644 --- a/changelog/april2024/2024-04-19-transactional-email-added-xml-attachments-are-now-avail.mdx +++ b/changelog/april2024/2024-04-19-transactional-email-added-xml-attachments-are-now-avail.mdx @@ -13,6 +13,6 @@ You can now send XML attachments in your transactional emails. The following MIM - `application/xml` - `text/xml` -Find out about the full range of available attachment types in our [documentation](https://www.scaleway.com/en/docs/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/). +Find out about the full range of available attachment types in our [documentation](https://www.scaleway.com/en/docs/transactional-email/reference-content/tem-capabilities-and-limits/). diff --git a/changelog/april2024/2024-04-25-messaging-and-queuing-changed-increased-messaging-resou.mdx b/changelog/april2024/2024-04-25-messaging-and-queuing-changed-increased-messaging-resou.mdx index d2664eb044..4d18377368 100644 --- a/changelog/april2024/2024-04-25-messaging-and-queuing-changed-increased-messaging-resou.mdx +++ b/changelog/april2024/2024-04-25-messaging-and-queuing-changed-increased-messaging-resou.mdx @@ -17,5 +17,5 @@ Scaleway Messaging and Queuing is evolving. We have increased the limitations on This update empowers you to handle larger workloads and enables more robust communication. -For detailed information on the limitations and capabilities of our Messaging and Queuing protocols, please refer to the [Messaging and Queuing documentation](/serverless/messaging/reference-content/limitations/). +For detailed information on the limitations and capabilities of our Messaging and Queuing protocols, please refer to the [Messaging and Queuing documentation](/messaging/reference-content/limitations/). diff --git a/changelog/april2024/2024-04-30-console-added-console-search.mdx b/changelog/april2024/2024-04-30-console-added-console-search.mdx index 578fdd07f1..e08aad13ed 100644 --- a/changelog/april2024/2024-04-30-console-added-console-search.mdx +++ b/changelog/april2024/2024-04-30-console-added-console-search.mdx @@ -11,6 +11,6 @@ product: console We are happy to announce that you can now find resources thanks to the new search in the console. Find them by their name or ID. More product integrations will come. -Refer to our [dedicated documentation](/console/account/how-to/use-the-search-bar/) to see which products are available now. +Refer to our [dedicated documentation](/account/how-to/use-the-search-bar/) to see which products are available now. diff --git a/changelog/august2023/2023-08-22-cockpit-changed-cockpit-feature-request-is.mdx b/changelog/august2023/2023-08-22-cockpit-changed-cockpit-feature-request-is.mdx index d4d0a05117..e27abd0e0a 100644 --- a/changelog/august2023/2023-08-22-cockpit-changed-cockpit-feature-request-is.mdx +++ b/changelog/august2023/2023-08-22-cockpit-changed-cockpit-feature-request-is.mdx @@ -10,7 +10,7 @@ product: cockpit --- We are happy to announce that we closed one of the [most wanted features](https://feature-request.scaleway.com/posts/38/log-centralization-and-management) at Scaleway (open since Jan. 21). -Almost every Scaleway products are available in Cockpit for metrics and/or logs. New features and capabilities will be added to the product. Refer to our [product documentation](https://www.scaleway.com/en/docs/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to see what is already available or planned. +Almost every Scaleway products are available in Cockpit for metrics and/or logs. New features and capabilities will be added to the product. Refer to our [product documentation](https://www.scaleway.com/en/docs/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to see what is already available or planned. For all future feature requirements, we encourage you to open a specific feature request of what you need to integrate into Cockpit. diff --git a/changelog/august2023/2023-08-31-postgresql-and-mysql-added-promote-a-read-replica.mdx b/changelog/august2023/2023-08-31-postgresql-and-mysql-added-promote-a-read-replica.mdx index b32a9c6267..e227a2f2c1 100644 --- a/changelog/august2023/2023-08-31-postgresql-and-mysql-added-promote-a-read-replica.mdx +++ b/changelog/august2023/2023-08-31-postgresql-and-mysql-added-promote-a-read-replica.mdx @@ -11,5 +11,5 @@ product: postgresql-and-mysql You can now promote a Read Replica node to a standalone Database Instance. This is useful for database failure recovery or sharding. -For more information, refer to the [How to manage Read Replica](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page. +For more information, refer to the [How to manage Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page. diff --git a/changelog/august2024/2024-08-02-postgresql-and-mysql-added-encryption-at-rest-available.mdx b/changelog/august2024/2024-08-02-postgresql-and-mysql-added-encryption-at-rest-available.mdx index a14a66d819..5373af6532 100644 --- a/changelog/august2024/2024-08-02-postgresql-and-mysql-added-encryption-at-rest-available.mdx +++ b/changelog/august2024/2024-08-02-postgresql-and-mysql-added-encryption-at-rest-available.mdx @@ -9,5 +9,5 @@ category: databases product: postgresql-and-mysql --- -Encryption-at-rest can now be activated on new PostgreSQL & MySQL instances. Read [this documentation](https://www.scaleway.com/en/docs/managed-databases/postgresql-and-mysql/concepts/#encryption-at-rest) for more information. +Encryption-at-rest can now be activated on new PostgreSQL & MySQL instances. Read [this documentation](https://www.scaleway.com/en/docs/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) for more information. diff --git a/changelog/august2024/2024-08-26-managed-inference-added-chat-and-embedding-apis-now-ret.mdx b/changelog/august2024/2024-08-26-managed-inference-added-chat-and-embedding-apis-now-ret.mdx index bb352d677b..2a6e6a82ce 100644 --- a/changelog/august2024/2024-08-26-managed-inference-added-chat-and-embedding-apis-now-ret.mdx +++ b/changelog/august2024/2024-08-26-managed-inference-added-chat-and-embedding-apis-now-ret.mdx @@ -13,6 +13,6 @@ Managed Inference endpoints now return usage stats (number of tokens in prompt, For streaming responses, the usage field is incremented in each chunk, and completed in the very last chunk of the response. -More details and examples in our [OpenAI API compatibility documentation](https://www.scaleway.com/en/docs/ai-data/managed-inference/reference-content/openai-compatibility/). +More details and examples in our [OpenAI API compatibility documentation](https://www.scaleway.com/en/docs/managed-inference/reference-content/openai-compatibility/). diff --git a/changelog/databases/february2022/2022-02-02-postgresql-and-mysql-added-block-volume.mdx b/changelog/databases/february2022/2022-02-02-postgresql-and-mysql-added-block-volume.mdx index 9368d1dc21..c68a61f8da 100644 --- a/changelog/databases/february2022/2022-02-02-postgresql-and-mysql-added-block-volume.mdx +++ b/changelog/databases/february2022/2022-02-02-postgresql-and-mysql-added-block-volume.mdx @@ -11,7 +11,7 @@ product: postgresql-and-mysql With this feature, you can: -* [Change storage and node size](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) independently to optimize your costs and adapt to your application's traffic. +* [Change storage and node size](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) independently to optimize your costs and adapt to your application's traffic. * Scale up your storage volume from 5GB to 10TB with no downtime. * Make Snapshots of your data in seconds for any size of the volume and recover a previous state of your data in case of accidental data alteration. diff --git a/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx b/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx index e19da12a4b..3fe3245433 100644 --- a/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx +++ b/changelog/databases/november2022/2022-11-10-redis-new-availability-zone.mdx @@ -9,5 +9,5 @@ category: databases product: redistm --- -[Managed Database for Redis™](/managed-databases/redis/quickstart/) is now available in the Availability Zone `nl-ams-2`! +[Managed Database for Redis™](/managed-databases-for-redis/quickstart/) is now available in the Availability Zone `nl-ams-2`! diff --git a/changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx b/changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx index fd84c40c30..b68f659b26 100644 --- a/changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx +++ b/changelog/databases/november2022/2022-11-18-mysqlpgsql-changed-read-replica.mdx @@ -9,4 +9,4 @@ category: databases product: postgresql-and-mysql --- -Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/). +Add up to three Read Replicas to your PostgreSQL or MySQL Instance and offload your main node from read requests. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/). diff --git a/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx b/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx index 081877cef8..bd7ae0ce1c 100644 --- a/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx +++ b/changelog/databases/october2022/2022-10-06-redis-ga-changed.mdx @@ -9,7 +9,7 @@ category: databases product: redistm --- -[Managed Database for Redis™](/managed-databases/redis/how-to/create-a-database-for-redis/) is now in General Availability in the following Availability Zones: +[Managed Database for Redis™](/managed-databases-for-redis/how-to/create-a-database-for-redis/) is now in General Availability in the following Availability Zones: * `fr-par-1` * `fr-par-2` * `nl-ams-1` diff --git a/changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx b/changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx index d72c5ebc1a..496ff8e69d 100644 --- a/changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx +++ b/changelog/databases/september2022/2022-09-13-pnm-added-read-replica.mdx @@ -9,4 +9,4 @@ category: databases product: postgresql-and-mysql --- -Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/). +Read Replicas are now available for Managed Database for PostgreSQL and MySQL. Follow the how-to to [create your first Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/). diff --git a/changelog/december2023/2023-12-04-transactional-email-removed-no-more-tem-houry-quota.mdx b/changelog/december2023/2023-12-04-transactional-email-removed-no-more-tem-houry-quota.mdx index 7a07459b2c..44ade1d448 100644 --- a/changelog/december2023/2023-12-04-transactional-email-removed-no-more-tem-houry-quota.mdx +++ b/changelog/december2023/2023-12-04-transactional-email-removed-no-more-tem-houry-quota.mdx @@ -11,5 +11,5 @@ product: transactional-email Effective December 1st 2023, we have removed the hourly quota for our service, transitioning to a model based on individual customer behavior and traffic. This change is designed to enhance user flexibility while upholding service quality. -Find out more about Transactional Email's capabilities and limits on our [dedicated documentation](/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/). +Find out more about Transactional Email's capabilities and limits on our [dedicated documentation](/transactional-email/reference-content/tem-capabilities-and-limits/). diff --git a/changelog/december2023/2023-12-14-postgresql-and-mysql-added-block-storage-low-latency-fo.mdx b/changelog/december2023/2023-12-14-postgresql-and-mysql-added-block-storage-low-latency-fo.mdx index 98304d3ae3..dc5ebbacb0 100644 --- a/changelog/december2023/2023-12-14-postgresql-and-mysql-added-block-storage-low-latency-fo.mdx +++ b/changelog/december2023/2023-12-14-postgresql-and-mysql-added-block-storage-low-latency-fo.mdx @@ -11,5 +11,5 @@ product: postgresql-and-mysql Block Storage Low Latency with high resiliency and 5k IOPs is now available in Public Beta on PLAY2, PRO2 & POP2 offers in the Paris and Amsterdam regions. -For more information, refer to [Scaleway Documentation](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency). +For more information, refer to [Scaleway Documentation](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency). diff --git a/changelog/december2023/2023-12-15-kubernetes-added-dedicated-control-plane-offers-now-ava.mdx b/changelog/december2023/2023-12-15-kubernetes-added-dedicated-control-plane-offers-now-ava.mdx index c99451c785..1fa5dc7530 100644 --- a/changelog/december2023/2023-12-15-kubernetes-added-dedicated-control-plane-offers-now-ava.mdx +++ b/changelog/december2023/2023-12-15-kubernetes-added-dedicated-control-plane-offers-now-ava.mdx @@ -11,5 +11,5 @@ product: kubernetes Upgrade your Kubernetes Kapsule or Kosmos clusters in Warsaw for mission-critical, at scale workloads and get highly available API servers and service level agreements. -Dedicated control planes 4/8/16GB are available from the Scaleway console, the CLI, and Terraform (>= 2.28.0). Refer to [our documentation](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. +Dedicated control planes 4/8/16GB are available from the Scaleway console, the CLI, and Terraform (>= 2.28.0). Refer to [our documentation](/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. diff --git a/changelog/december2023/2023-12-19-kubernetes-removed-managed-ingress-controllers-at-clust.mdx b/changelog/december2023/2023-12-19-kubernetes-removed-managed-ingress-controllers-at-clust.mdx index 4ef1100168..1033531715 100644 --- a/changelog/december2023/2023-12-19-kubernetes-removed-managed-ingress-controllers-at-clust.mdx +++ b/changelog/december2023/2023-12-19-kubernetes-removed-managed-ingress-controllers-at-clust.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Ending the [deprecation cycle](/changelog/?a=kubernetes-52c54d18-c203&tags=containers_kubernetes/), Kubernetes clusters do not have managed ingresses anymore. Users can deploy a [pre-configured ingress controller](/containers/kubernetes/how-to/deploy-ingress-controller/) after cluster creation using the Easy Deploy feature within the Scaleway console. +Ending the [deprecation cycle](/changelog/?a=kubernetes-52c54d18-c203&tags=containers_kubernetes/), Kubernetes clusters do not have managed ingresses anymore. Users can deploy a [pre-configured ingress controller](/kubernetes/how-to/deploy-ingress-controller/) after cluster creation using the Easy Deploy feature within the Scaleway console. diff --git a/changelog/december2024/2024-12-03-redistm-added-redis-2-node-ha-in-public-beta.mdx b/changelog/december2024/2024-12-03-redistm-added-redis-2-node-ha-in-public-beta.mdx index c91ed37c76..99de342e95 100644 --- a/changelog/december2024/2024-12-03-redistm-added-redis-2-node-ha-in-public-beta.mdx +++ b/changelog/december2024/2024-12-03-redistm-added-redis-2-node-ha-in-public-beta.mdx @@ -9,5 +9,5 @@ category: databases product: redistm --- -Our 2-node High Availability offer is now in Public Beta. Refer to our [Quickstart documentation](https://www.scaleway.com/en/docs/managed-databases/redis/quickstart/) to try it out! +Our 2-node High Availability offer is now in Public Beta. Refer to our [Quickstart documentation](https://www.scaleway.com/en/docs/managed-databases-for-redis/quickstart/) to try it out! diff --git a/changelog/december2024/2024-12-05-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx b/changelog/december2024/2024-12-05-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx index dcc2d8587b..9ff2ba4b64 100644 --- a/changelog/december2024/2024-12-05-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx +++ b/changelog/december2024/2024-12-05-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx @@ -14,4 +14,4 @@ We have redefined our Messaging and Queuing offering into three distinct product - Queues (formerly SQS) - Topics & Events (formerly SNS) -Learn more about each product in our [documentation](/serverless/messaging/). +Learn more about each product in our [documentation](/messaging/). diff --git a/changelog/elastic-metal/may2022/2022-05-01-elastic-metal-added-smtp-block.mdx b/changelog/elastic-metal/may2022/2022-05-01-elastic-metal-added-smtp-block.mdx index a3acd5cda4..a72e1228bd 100644 --- a/changelog/elastic-metal/may2022/2022-05-01-elastic-metal-added-smtp-block.mdx +++ b/changelog/elastic-metal/may2022/2022-05-01-elastic-metal-added-smtp-block.mdx @@ -10,4 +10,4 @@ product: elastic-metal --- For security reasons, SMTP ports are now blocked by default on every new Elastic Metal server delivered. -You can [enable them](/bare-metal/elastic-metal/how-to/enable-smtp/) in the Scaleway console (through general settings) when your [identity is validated](/console/account/how-to/verify-identity/). \ No newline at end of file +You can [enable them](/elastic-metal/how-to/enable-smtp/) in the Scaleway console (through general settings) when your [identity is validated](/account/how-to/verify-identity/). \ No newline at end of file diff --git a/changelog/elastic-metal/october2022/2022-10-06-elastic-metal-added-windows-datacenter-images.mdx b/changelog/elastic-metal/october2022/2022-10-06-elastic-metal-added-windows-datacenter-images.mdx index 1189f4c502..c6e03dc07c 100644 --- a/changelog/elastic-metal/october2022/2022-10-06-elastic-metal-added-windows-datacenter-images.mdx +++ b/changelog/elastic-metal/october2022/2022-10-06-elastic-metal-added-windows-datacenter-images.mdx @@ -9,4 +9,4 @@ category: bare-metal product: elastic-metal --- -[Windows 2022 Standard and Datacenter images](/bare-metal/elastic-metal/how-to/connect-to-server/#how-to-connect-to-a-windows-server-using-remote-access) and licences are now available on Elastic Metal servers (Aluminium range excluded). +[Windows 2022 Standard and Datacenter images](/elastic-metal/how-to/connect-to-server/#how-to-connect-to-a-windows-server-using-remote-access) and licences are now available on Elastic Metal servers (Aluminium range excluded). diff --git a/changelog/february2023/2023-02-07-kubernetes-added-kubernetes-versions-1.25-and.mdx b/changelog/february2023/2023-02-07-kubernetes-added-kubernetes-versions-1.25-and.mdx index e479fdc739..da8a833842 100644 --- a/changelog/february2023/2023-02-07-kubernetes-added-kubernetes-versions-1.25-and.mdx +++ b/changelog/february2023/2023-02-07-kubernetes-added-kubernetes-versions-1.25-and.mdx @@ -11,5 +11,5 @@ product: kubernetes Scaleway managed Kubernetes products now support the latest minor versions `1.25` and `1.26`. Patch versions `1.24.8` and `1.24.9` have also been released. -Find more details in [our version support policy](/containers/kubernetes/reference-content/version-support-policy/). +Find more details in [our version support policy](/kubernetes/reference-content/version-support-policy/). diff --git a/changelog/february2023/2023-02-07-kubernetes-removed-flannel-weave.mdx b/changelog/february2023/2023-02-07-kubernetes-removed-flannel-weave.mdx index e25951dde2..aa461e2bc4 100644 --- a/changelog/february2023/2023-02-07-kubernetes-removed-flannel-weave.mdx +++ b/changelog/february2023/2023-02-07-kubernetes-removed-flannel-weave.mdx @@ -10,5 +10,5 @@ product: kubernetes --- From k8s version 1.25 onwards, all new clusters created in Scaleway Kubernetes will either be with `cilium` or `calico` as CNI. -To benefit from the newest minor versions, we recommend you recreate your clusters on one of the supported CNIs. Find more details on [our migration policies here](/containers/kubernetes/reference-content/version-support-policy/). +To benefit from the newest minor versions, we recommend you recreate your clusters on one of the supported CNIs. Find more details on [our migration policies here](/kubernetes/reference-content/version-support-policy/). diff --git a/changelog/february2023/2023-02-09-transactional-email-added-tem-image-attachment.mdx b/changelog/february2023/2023-02-09-transactional-email-added-tem-image-attachment.mdx index ae777079e9..999e39141b 100644 --- a/changelog/february2023/2023-02-09-transactional-email-added-tem-image-attachment.mdx +++ b/changelog/february2023/2023-02-09-transactional-email-added-tem-image-attachment.mdx @@ -15,5 +15,5 @@ You can now send images as attachments in your transactional emails. The support * `png` * `gif` -[Find out about all the attachment types available.](/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/) +[Find out about all the attachment types available.](/transactional-email/reference-content/tem-capabilities-and-limits/) diff --git a/changelog/february2024/2024-02-05-kubernetes-deprecated-force-internal-ip-annotation-in-k.mdx b/changelog/february2024/2024-02-05-kubernetes-deprecated-force-internal-ip-annotation-in-k.mdx index b1c0fcb198..8e0ec3735b 100644 --- a/changelog/february2024/2024-02-05-kubernetes-deprecated-force-internal-ip-annotation-in-k.mdx +++ b/changelog/february2024/2024-02-05-kubernetes-deprecated-force-internal-ip-annotation-in-k.mdx @@ -11,7 +11,7 @@ product: kubernetes The [service.beta.kubernetes.io/scw-loadbalancer-force-internal-ip](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md#servicebetakubernetesioscw-loadbalancer-force-internal-ip) annotation is now `deprecated` due to incompatibilities with newer Load Balancer instances using **routed IPs**. -- Public-only Kapsule users should transition to [using the Private Network feature](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/#how-can-i-migrate-my-existing-clusters-to-private-networks) for enhanced security and performance. +- Public-only Kapsule users should transition to [using the Private Network feature](https://www.scaleway.com/en/docs/kubernetes/reference-content/secure-cluster-with-private-network/#how-can-i-migrate-my-existing-clusters-to-private-networks) for enhanced security and performance. - Kosmos users with Scaleway pools should stop using this annotation. Please refer to the related [CCM documentation](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md#servicebetakubernetesioscw-loadbalancer-force-internal-ip). diff --git a/changelog/february2024/2024-02-06-kubernetes-added-kubernetes-version-129-is-now-availabl.mdx b/changelog/february2024/2024-02-06-kubernetes-added-kubernetes-version-129-is-now-availabl.mdx index 816592f466..c348dabb35 100644 --- a/changelog/february2024/2024-02-06-kubernetes-added-kubernetes-version-129-is-now-availabl.mdx +++ b/changelog/february2024/2024-02-06-kubernetes-added-kubernetes-version-129-is-now-availabl.mdx @@ -13,5 +13,5 @@ Scaleway managed Kubernetes products will support the latest minor version 1.29 Patch versions 1.29.1, 1.28.6, 1.27.10, 1.26.13, 1.25.16 have also been released. -Read our newest [version support policy](/containers/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. +Read our newest [version support policy](/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. diff --git a/changelog/february2024/2024-02-12-containers-deprecated-deprecation-of-logs-endpoint.mdx b/changelog/february2024/2024-02-12-containers-deprecated-deprecation-of-logs-endpoint.mdx index 3fc73f280b..6f6d8233a9 100644 --- a/changelog/february2024/2024-02-12-containers-deprecated-deprecation-of-logs-endpoint.mdx +++ b/changelog/february2024/2024-02-12-containers-deprecated-deprecation-of-logs-endpoint.mdx @@ -10,6 +10,6 @@ product: containers --- Due to infrequent usage and changes affecting the storage of user logs, we are announcing the deprecation of the `/logs` endpoint (or `ListLogs` for our SDK users). -However, users can still access their container logs conveniently via their [Cockpit interface](/observability/cockpit/quickstart/). A dedicated dashboard called "Serverless Containers Logs" is accessible there. For detailed instructions, refer to our [documentation](https://www.scaleway.com/en/developers/api/serverless-containers/#logs). +However, users can still access their container logs conveniently via their [Cockpit interface](/cockpit/quickstart/). A dedicated dashboard called "Serverless Containers Logs" is accessible there. For detailed instructions, refer to our [documentation](https://www.scaleway.com/en/developers/api/serverless-containers/#logs). For users who are already using Cockpit for log access (logs have been directed to Cockpit for the past 6 months), there will be no disruption. Note, the `/logs` endpoint will be fully deprecated in one month, effective March 12, 2024. \ No newline at end of file diff --git a/changelog/february2024/2024-02-12-functions-deprecated-deprecation-of-logs-endpoint.mdx b/changelog/february2024/2024-02-12-functions-deprecated-deprecation-of-logs-endpoint.mdx index 312241b3d1..3f9ecac045 100644 --- a/changelog/february2024/2024-02-12-functions-deprecated-deprecation-of-logs-endpoint.mdx +++ b/changelog/february2024/2024-02-12-functions-deprecated-deprecation-of-logs-endpoint.mdx @@ -10,6 +10,6 @@ product: functions --- Due to infrequent usage and changes affecting the storage of user logs, we are announcing the deprecation of the `/logs` endpoint (or `ListLogs` for our SDK users). -However, users can still access their function logs conveniently via their [Cockpit interface](/observability/cockpit/quickstart/). A dedicated dashboard called "Serverless Functions Logs" is accessible there. For detailed instructions, refer to our [documentation](https://www.scaleway.com/en/developers/api/serverless-functions/#logs). +However, users can still access their function logs conveniently via their [Cockpit interface](/cockpit/quickstart/). A dedicated dashboard called "Serverless Functions Logs" is accessible there. For detailed instructions, refer to our [documentation](https://www.scaleway.com/en/developers/api/serverless-functions/#logs). For users who are already using Cockpit for log access (logs have been directed to Cockpit for the past 6 months), there will be no disruption. Note, the `/logs` endpoint will be fully deprecated in one month, effective March 12, 2024. \ No newline at end of file diff --git a/changelog/february2024/2024-02-15-webhosting-added-dedicated-ip-for-web-hosting.mdx b/changelog/february2024/2024-02-15-webhosting-added-dedicated-ip-for-web-hosting.mdx index 4665a1c25c..88ce097405 100644 --- a/changelog/february2024/2024-02-15-webhosting-added-dedicated-ip-for-web-hosting.mdx +++ b/changelog/february2024/2024-02-15-webhosting-added-dedicated-ip-for-web-hosting.mdx @@ -12,5 +12,5 @@ product: webhosting Web Hosting with dedicated IP is now available! Looking to safeguard your online reputation and ensure your IP remains unaffected from shared usage? -This feature is tailored for you! [Enable your dedicated IP](/managed-services/webhosting/how-to/order-dedicated-ip/) during your hosting order or later via the console, and we will provide you with a dedicated IP linked directly to your hosting plan. +This feature is tailored for you! [Enable your dedicated IP](/webhosting/how-to/order-dedicated-ip/) during your hosting order or later via the console, and we will provide you with a dedicated IP linked directly to your hosting plan. diff --git a/changelog/february2024/2024-02-22-messaging-and-queuing-added-messaging-and-queuing-is-av.mdx b/changelog/february2024/2024-02-22-messaging-and-queuing-added-messaging-and-queuing-is-av.mdx index d0fa7529b0..cef915cbf3 100644 --- a/changelog/february2024/2024-02-22-messaging-and-queuing-added-messaging-and-queuing-is-av.mdx +++ b/changelog/february2024/2024-02-22-messaging-and-queuing-added-messaging-and-queuing-is-av.mdx @@ -9,5 +9,5 @@ category: serverless product: messaging-and-queuing --- -You can now manage your Messaging and Queuing resources in the AMS region. All three protocols (SQS, NATS & SNS) are available in the region. For more information, refer to our [Messaging and Queuing documentation](/serverless/messaging/). +You can now manage your Messaging and Queuing resources in the AMS region. All three protocols (SQS, NATS & SNS) are available in the region. For more information, refer to our [Messaging and Queuing documentation](/messaging/). diff --git a/changelog/february2024/2024-02-22-messaging-and-queuing-added-sns-subscriptions-creation-.mdx b/changelog/february2024/2024-02-22-messaging-and-queuing-added-sns-subscriptions-creation-.mdx index 96f7a8a9c5..c002a44912 100644 --- a/changelog/february2024/2024-02-22-messaging-and-queuing-added-sns-subscriptions-creation-.mdx +++ b/changelog/february2024/2024-02-22-messaging-and-queuing-added-sns-subscriptions-creation-.mdx @@ -10,5 +10,5 @@ product: messaging-and-queuing --- You can now manage your SNS subscriptions [directly from the Scaleway console](https://console.scaleway.com/messaging/protocols/). You can subscribe to HTTP/S endpoints and Serverless Compute resources (Functions & Containers). -You can refer to our documentation to find out [how to create and manage SNS subscriptions](/serverless/messaging/how-to/create-manage-subscriptions/). +You can refer to our documentation to find out [how to create and manage SNS subscriptions](/messaging/how-to/create-manage-subscriptions/). diff --git a/changelog/february2024/2024-02-29-billing-changed-new-billing-space.mdx b/changelog/february2024/2024-02-29-billing-changed-new-billing-space.mdx index 306197dc85..0c517cea8d 100644 --- a/changelog/february2024/2024-02-29-billing-changed-new-billing-space.mdx +++ b/changelog/february2024/2024-02-29-billing-changed-new-billing-space.mdx @@ -21,7 +21,7 @@ Our brand-new Billing Space is now live and ready for you to explore. Accessible Explore these new features today and manage your billing more efficiently than ever before! - Refer to the [Billing documentation](/console/billing/) for more information. + Refer to the [Billing documentation](/billing/) for more information. diff --git a/changelog/iam/december2022/2022-12-07-iam-general-availability-dev-tools.mdx b/changelog/iam/december2022/2022-12-07-iam-general-availability-dev-tools.mdx index 9cf7d31b80..d330ef3cb6 100644 --- a/changelog/iam/december2022/2022-12-07-iam-general-availability-dev-tools.mdx +++ b/changelog/iam/december2022/2022-12-07-iam-general-availability-dev-tools.mdx @@ -13,4 +13,4 @@ Projects can be created, managed and deleted from the CLI, Terraform and other d IAM must be used to generate an API key with the permissions to manage Projects. -Find out more on the [Managing projects using Scaleway APIs](/identity-and-access-management/iam/api-cli/managing-projects/) documentation page. +Find out more on the [Managing projects using Scaleway APIs](/iam/api-cli/managing-projects/) documentation page. diff --git a/changelog/iam/december2022/2022-12-07-iam-general-availibility.mdx b/changelog/iam/december2022/2022-12-07-iam-general-availibility.mdx index cebf392fa6..346cbe907e 100644 --- a/changelog/iam/december2022/2022-12-07-iam-general-availibility.mdx +++ b/changelog/iam/december2022/2022-12-07-iam-general-availibility.mdx @@ -17,6 +17,6 @@ IAM features are available though Console, CLI and Terraform. For Organizations created before December 5th, IAM can be activated by the Owner of the Organization on the console. Accounts created since December 5th 2022 have IAM activated by default. -Find out more in our dedicated [IAM documentation](/identity-and-access-management/iam/reference-content/overview/). +Find out more in our dedicated [IAM documentation](/iam/reference-content/overview/). diff --git a/changelog/instances/march2022/2022-03-01-instances-added-boot-on-block.mdx b/changelog/instances/march2022/2022-03-01-instances-added-boot-on-block.mdx index a48a05d705..33047824c1 100644 --- a/changelog/instances/march2022/2022-03-01-instances-added-boot-on-block.mdx +++ b/changelog/instances/march2022/2022-03-01-instances-added-boot-on-block.mdx @@ -10,7 +10,7 @@ product: instances --- All Instance offers, including DEV, GP, RENDER, and Stardust can now boot on Block volumes. This type of storage is safer and can be moved from one Instance to another. -Make sure you check our [documentation](/compute/instances/how-to/create-an-instance/) to create an Instance booting on a block volume or to [change the boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume) of your Instance. +Make sure you check our [documentation](/instances/how-to/create-an-instance/) to create an Instance booting on a block volume or to [change the boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume) of your Instance. For API users, note that the local volume `min_size` returned by a call to `/instance/v1/zones/{zone}/products/servers` is now `0`, whereas it was previously equal to the `max_size`. diff --git a/changelog/instances/november2022/2022-11-23-instances-fixed-debian-bullseye-os-image.mdx b/changelog/instances/november2022/2022-11-23-instances-fixed-debian-bullseye-os-image.mdx index 266f5e7167..fb78fa007e 100644 --- a/changelog/instances/november2022/2022-11-23-instances-fixed-debian-bullseye-os-image.mdx +++ b/changelog/instances/november2022/2022-11-23-instances-fixed-debian-bullseye-os-image.mdx @@ -13,4 +13,4 @@ We released a fix for the Debian Bullseye OS image to avoid an issue when updati For ENT1 Instances, we are working with Debian to include the bug fixes. Please watch the changelog for the update. If you encounter an issue with the Debian Bullseye OS image after updating the operating-system (error: `filesystem is mounted as read-only`), -follow our [documentation](/compute/instances/troubleshooting/reboot-from-faulty-kernel/) to boot your Instance in recovery mode and recover to a working kernel version. \ No newline at end of file +follow our [documentation](/instances/troubleshooting/reboot-from-faulty-kernel/) to boot your Instance in recovery mode and recover to a working kernel version. \ No newline at end of file diff --git a/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx b/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx index f4461b740e..3a23e7d75c 100644 --- a/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx +++ b/changelog/instances/september2022/2022-09-06-instances-added-play2.mdx @@ -10,7 +10,7 @@ product: instances --- A new generation of Development Instances is now available: PLAY2. -Scaleway’s PLAY2 Instances are designed for testing and development purposes. PLAY2 Instances are the second generation of [Development Instances](/compute/instances/concepts/#development-instance) after DEV1. They are small, agile and meet performance requirements for standard testing and development scenarios. [Learn more about PLAY2 Instances](https://www.scaleway.com/en/cost-optimized-instances/) on their dedicated product page. +Scaleway’s PLAY2 Instances are designed for testing and development purposes. PLAY2 Instances are the second generation of [Development Instances](/instances/concepts/#development-instance) after DEV1. They are small, agile and meet performance requirements for standard testing and development scenarios. [Learn more about PLAY2 Instances](https://www.scaleway.com/en/cost-optimized-instances/) on their dedicated product page. PLAY2 Instances are currently available in: - fr-par-2 - nl-ams-2 diff --git a/changelog/january2023/2023-01-19-functions-fixed-missing-logs-in-console.mdx b/changelog/january2023/2023-01-19-functions-fixed-missing-logs-in-console.mdx index f6ad2a64e3..58ff3d108a 100644 --- a/changelog/january2023/2023-01-19-functions-fixed-missing-logs-in-console.mdx +++ b/changelog/january2023/2023-01-19-functions-fixed-missing-logs-in-console.mdx @@ -11,5 +11,5 @@ product: functions Users were experiencing an issue on the console and the API where logs were not appearing. This bug is now fixed. -We also recommend you use the Serverless Functions dashboards in the [Scaleway Cockpit](/observability/cockpit/quickstart/) to monitor all your metrics and logs and access advanced features (ordering, filtering...) +We also recommend you use the Serverless Functions dashboards in the [Scaleway Cockpit](/cockpit/quickstart/) to monitor all your metrics and logs and access advanced features (ordering, filtering...) diff --git a/changelog/january2023/2023-01-19-transactional-email-changed-tem.mdx b/changelog/january2023/2023-01-19-transactional-email-changed-tem.mdx index 5b69d3f272..c067af1ea4 100644 --- a/changelog/january2023/2023-01-19-transactional-email-changed-tem.mdx +++ b/changelog/january2023/2023-01-19-transactional-email-changed-tem.mdx @@ -9,7 +9,7 @@ category: managed-services product: transactional-email --- -- The new Transactional Email sending domain `scw-tem.cloud` is now available. If you are a new client, you can use this sending domain by default. If you were using the previous sending domain, you can [configure a new SPF record](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) with `scw-tem.cloud` and delete the old SPF record. +- The new Transactional Email sending domain `scw-tem.cloud` is now available. If you are a new client, you can use this sending domain by default. If you were using the previous sending domain, you can [configure a new SPF record](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) with `scw-tem.cloud` and delete the old SPF record. - Emails returned with error code 452 (recipient's mailbox is full) will be deleted with no further attempts made to resend. diff --git a/changelog/january2023/2023-01-25-kubernetes-removed-kubernetes-1.20-is-no.mdx b/changelog/january2023/2023-01-25-kubernetes-removed-kubernetes-1.20-is-no.mdx index 267db00220..0a61d84927 100644 --- a/changelog/january2023/2023-01-25-kubernetes-removed-kubernetes-1.20-is-no.mdx +++ b/changelog/january2023/2023-01-25-kubernetes-removed-kubernetes-1.20-is-no.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Kubernetes 1.20 is no longer supported on our [Kubernetes products](/containers/kubernetes/quickstart/) starting January 15th. Clusters in this specific version will automatically be upgraded to 1.21 on February 15th, 2023. +Kubernetes 1.20 is no longer supported on our [Kubernetes products](/kubernetes/quickstart/) starting January 15th. Clusters in this specific version will automatically be upgraded to 1.21 on February 15th, 2023. diff --git a/changelog/january2024/2024-01-05-messaging-and-queuing-added-sns-topic-creation-availabl.mdx b/changelog/january2024/2024-01-05-messaging-and-queuing-added-sns-topic-creation-availabl.mdx index adc89bddf4..ced4284684 100644 --- a/changelog/january2024/2024-01-05-messaging-and-queuing-added-sns-topic-creation-availabl.mdx +++ b/changelog/january2024/2024-01-05-messaging-and-queuing-added-sns-topic-creation-availabl.mdx @@ -10,5 +10,5 @@ product: messaging-and-queuing --- You can now create and manage your SNS Topics directly in the console. -For more information, you can refer to our [How to create topics documentation](https://www.scaleway.com/en/docs/serverless/messaging/how-to/create-manage-topics/). +For more information, you can refer to our [How to create topics documentation](https://www.scaleway.com/en/docs/messaging/how-to/create-manage-topics/). diff --git a/changelog/january2024/2024-01-09-kubernetes-added-proxy-registry.mdx b/changelog/january2024/2024-01-09-kubernetes-added-proxy-registry.mdx index 6bcc239d17..3f9fc3eafd 100644 --- a/changelog/january2024/2024-01-09-kubernetes-added-proxy-registry.mdx +++ b/changelog/january2024/2024-01-09-kubernetes-added-proxy-registry.mdx @@ -10,5 +10,5 @@ product: kubernetes --- Kubernetes Kapsule now benefits from a proxy registry in all regions, caching required system images for new clusters and new nodes. -This addition eliminates rate limiting from the official container registries used to pull system images, and eases scaling large node pools in [full isolation](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) mode. +This addition eliminates rate limiting from the official container registries used to pull system images, and eases scaling large node pools in [full isolation](https://www.scaleway.com/en/docs/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) mode. diff --git a/changelog/january2025/2025-01-07-kubernetes-added-ip-whitelisting-for-kubernetes-kapsule.mdx b/changelog/january2025/2025-01-07-kubernetes-added-ip-whitelisting-for-kubernetes-kapsule.mdx index 8704b00a24..3415d06baa 100644 --- a/changelog/january2025/2025-01-07-kubernetes-added-ip-whitelisting-for-kubernetes-kapsule.mdx +++ b/changelog/january2025/2025-01-07-kubernetes-added-ip-whitelisting-for-kubernetes-kapsule.mdx @@ -11,6 +11,6 @@ product: kubernetes Kubernetes Kapsule users can now restrict cluster access by specifying allowed IPs in CIDR notation. The default configuration `0.0.0.0/0` allows connections from all IPs. - Kosmos clusters require unrestricted access from Scaleway IP subnets. This security enhancement reduces the risk of unauthorized access. Find more information in the [documentation](https://www.scaleway.com/en/docs/containers/kubernetes/how-to/manage-allowed-ips/). + Kosmos clusters require unrestricted access from Scaleway IP subnets. This security enhancement reduces the risk of unauthorized access. Find more information in the [documentation](https://www.scaleway.com/en/docs/kubernetes/how-to/manage-allowed-ips/). diff --git a/changelog/january2025/2025-01-09-cockpit-added-custom-retention-for-cockpits-datasources.mdx b/changelog/january2025/2025-01-09-cockpit-added-custom-retention-for-cockpits-datasources.mdx index 087d5450e8..d5b523644e 100644 --- a/changelog/january2025/2025-01-09-cockpit-added-custom-retention-for-cockpits-datasources.mdx +++ b/changelog/january2025/2025-01-09-cockpit-added-custom-retention-for-cockpits-datasources.mdx @@ -9,4 +9,4 @@ category: observability product: cockpit --- -Since January 1st 2025, you can [edit the retention duration](/observability/cockpit/how-to/change-data-retention/) of all your logs, metrics and traces data sources, and apply a different retention period to each of them depending on your needs. Extended retention was previously managed by Cockpit's premium plans which are now deprecated. Increasing your data retention above the default values is free of charge **during the beta phase only**, and will become billable again in a couple of months. +Since January 1st 2025, you can [edit the retention duration](/cockpit/how-to/change-data-retention/) of all your logs, metrics and traces data sources, and apply a different retention period to each of them depending on your needs. Extended retention was previously managed by Cockpit's premium plans which are now deprecated. Increasing your data retention above the default values is free of charge **during the beta phase only**, and will become billable again in a couple of months. diff --git a/changelog/january2025/2025-01-09-generative-apis-added-new-models-support-llama-33.mdx b/changelog/january2025/2025-01-09-generative-apis-added-new-models-support-llama-33.mdx index 8bad1c14c2..ddd6c79181 100644 --- a/changelog/january2025/2025-01-09-generative-apis-added-new-models-support-llama-33.mdx +++ b/changelog/january2025/2025-01-09-generative-apis-added-new-models-support-llama-33.mdx @@ -9,7 +9,7 @@ category: ai-data product: generative-apis --- -[Llama 3.3 70B](/ai-data/generative-apis/reference-content/supported-models/#request-a-model) is now available on Generative APIs. +[Llama 3.3 70B](/generative-apis/reference-content/supported-models/#request-a-model) is now available on Generative APIs. Llama 3.3 is a fine-tuned version of the Llama 3.1 70b model, which was designed to approach the performance of Llama 3.1 405B on some applications. diff --git a/changelog/january2025/2025-01-15-kubernetes-removed-container-storage-interface-csi-driv.mdx b/changelog/january2025/2025-01-15-kubernetes-removed-container-storage-interface-csi-driv.mdx index 5bc8e82afe..7caa8d9749 100644 --- a/changelog/january2025/2025-01-15-kubernetes-removed-container-storage-interface-csi-driv.mdx +++ b/changelog/january2025/2025-01-15-kubernetes-removed-container-storage-interface-csi-driv.mdx @@ -13,5 +13,5 @@ The Scaleway Block Volume Container Storage Interface (CSI) driver **v0.2** will To ensure continued compatibility, **we recommend upgrading to the latest version (v0.3)** as soon as possible. -Refer to our dedicated documentation and learn how to upgrade: [Managing Block Storage volumes with Scaleway CSI](/containers/kubernetes/api-cli/managing-storage/) +Refer to our dedicated documentation and learn how to upgrade: [Managing Block Storage volumes with Scaleway CSI](/kubernetes/api-cli/managing-storage/) diff --git a/changelog/january2025/2025-01-16-mongodb-added-managed-mongodbr-in-public-beta.mdx b/changelog/january2025/2025-01-16-mongodb-added-managed-mongodbr-in-public-beta.mdx index 80ef6e49a0..d6532ddd3e 100644 --- a/changelog/january2025/2025-01-16-mongodb-added-managed-mongodbr-in-public-beta.mdx +++ b/changelog/january2025/2025-01-16-mongodb-added-managed-mongodbr-in-public-beta.mdx @@ -9,5 +9,5 @@ category: databases product: mongodb --- -Managed MongoDB® Databases are now in Public Beta. [Connect to the console](https://console.scaleway.com/mongo-db/databases/fr-par) to try it out. Refer to the [Managed MongoDB® Databases documentation](https://www.scaleway.com/en/docs/managed-databases/mongodb/) for more information. +Managed MongoDB® Databases are now in Public Beta. [Connect to the console](https://console.scaleway.com/mongo-db/databases/fr-par) to try it out. Refer to the [Managed MongoDB® Databases documentation](https://www.scaleway.com/en/docs/managed-mongodb-databases/) for more information. diff --git a/changelog/january2025/2025-01-16-postgresql-and-mysql-added-encryption-at-rest-general-a.mdx b/changelog/january2025/2025-01-16-postgresql-and-mysql-added-encryption-at-rest-general-a.mdx index 93a20582ea..9a44a32279 100644 --- a/changelog/january2025/2025-01-16-postgresql-and-mysql-added-encryption-at-rest-general-a.mdx +++ b/changelog/january2025/2025-01-16-postgresql-and-mysql-added-encryption-at-rest-general-a.mdx @@ -9,5 +9,5 @@ category: databases product: postgresql-and-mysql --- -Encryption at rest is now GA for Managed PostgreSQL & MySQL. Refer to the [Setting up encryption at rest documentation](https://www.scaleway.com/en/docs/managed-databases/postgresql-and-mysql/api-cli/setting-up-encryption-at-rest/) to learn how to activate it. To understand potential impacts on performance, refer to the [Encryption at rest performance benchmark](https://www.scaleway.com/en/docs/managed-databases/postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark/) performed by our Managed Databases team. +Encryption at rest is now GA for Managed PostgreSQL & MySQL. Refer to the [Setting up encryption at rest documentation](https://www.scaleway.com/en/docs/managed-databases-for-postgresql-and-mysql/api-cli/setting-up-encryption-at-rest/) to learn how to activate it. To understand potential impacts on performance, refer to the [Encryption at rest performance benchmark](https://www.scaleway.com/en/docs/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark/) performed by our Managed Databases team. diff --git a/changelog/july2023/2023-07-06-kubernetes-removed-kubernetes-1.21-is-no.mdx b/changelog/july2023/2023-07-06-kubernetes-removed-kubernetes-1.21-is-no.mdx index 818c5061df..e6fed15ee9 100644 --- a/changelog/july2023/2023-07-06-kubernetes-removed-kubernetes-1.21-is-no.mdx +++ b/changelog/july2023/2023-07-06-kubernetes-removed-kubernetes-1.21-is-no.mdx @@ -10,5 +10,5 @@ product: kubernetes --- Clusters using this specific version will automatically be upgraded to 1.22 on July 17th, 2023. -Find more details in [our version support policy](/containers/kubernetes/reference-content/version-support-policy/). +Find more details in [our version support policy](/kubernetes/reference-content/version-support-policy/). diff --git a/changelog/july2023/2023-07-06-secret-manager-added-secret-manager-metrics-in.mdx b/changelog/july2023/2023-07-06-secret-manager-added-secret-manager-metrics-in.mdx index 5b8fc46e15..f2807da956 100644 --- a/changelog/july2023/2023-07-06-secret-manager-added-secret-manager-metrics-in.mdx +++ b/changelog/july2023/2023-07-06-secret-manager-added-secret-manager-metrics-in.mdx @@ -9,5 +9,5 @@ category: security-identity product: secret-manager --- -Secret Manager metrics are now displayed in Cockpit by default, allowing you to have more control over your metrics. Read our [documentation](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. +Secret Manager metrics are now displayed in Cockpit by default, allowing you to have more control over your metrics. Read our [documentation](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. diff --git a/changelog/july2023/2023-07-18-kubernetes-added-new-kubernetes-operator-to.mdx b/changelog/july2023/2023-07-18-kubernetes-added-new-kubernetes-operator-to.mdx index c5b7f0aba2..6f54105d78 100644 --- a/changelog/july2023/2023-07-18-kubernetes-added-new-kubernetes-operator-to.mdx +++ b/changelog/july2023/2023-07-18-kubernetes-added-new-kubernetes-operator-to.mdx @@ -11,5 +11,5 @@ product: kubernetes NVIDIA's [GPU operator](https://docs.nvidia.com/datacenter/cloud-native/gpu-operator/latest/overview.html) is installed by default on all new GPU pools, automatically bringing required software on your GPU worker nodes. -Find out how to activate or configure the operator in the [documentation](/containers/kubernetes/how-to/use-nvidia-gpu-operator/). +Find out how to activate or configure the operator in the [documentation](/kubernetes/how-to/use-nvidia-gpu-operator/). diff --git a/changelog/july2023/2023-07-18-public-gateways-changed-the-public-gateway-is.mdx b/changelog/july2023/2023-07-18-public-gateways-changed-the-public-gateway-is.mdx index b9da42d91b..d264a776b3 100644 --- a/changelog/july2023/2023-07-18-public-gateways-changed-the-public-gateway-is.mdx +++ b/changelog/july2023/2023-07-18-public-gateways-changed-the-public-gateway-is.mdx @@ -16,4 +16,4 @@ Public Gateway now focuses on its primary functions such as: - SSH Bastion: allowing and monitoring SSH connections - Local DNS server: customizing resource names on the Private Network -See our [dedicated documentation](https://www.scaleway.com/en/docs/network/vpc/reference-content/vpc-migration/) for full details. +See our [dedicated documentation](https://www.scaleway.com/en/docs/vpc/reference-content/vpc-migration/) for full details. diff --git a/changelog/july2023/2023-07-19-kubernetes-added-kapsule-and-kosmos-control.mdx b/changelog/july2023/2023-07-19-kubernetes-added-kapsule-and-kosmos-control.mdx index 4c0949ab6f..27830ddc00 100644 --- a/changelog/july2023/2023-07-19-kubernetes-added-kapsule-and-kosmos-control.mdx +++ b/changelog/july2023/2023-07-19-kubernetes-added-kapsule-and-kosmos-control.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Your control plane metrics and logs are now provided in Cockpit by default, allowing you to monitor all managed components with actionable insights. Read our [Cockpit Reference Documentation](https://www.scaleway.com/en/docs/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. +Your control plane metrics and logs are now provided in Cockpit by default, allowing you to monitor all managed components with actionable insights. Read our [Cockpit Reference Documentation](https://www.scaleway.com/en/docs/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. diff --git a/changelog/july2024/2024-07-02-object-storage-added-bucket-policies-can-now-be-configu.mdx b/changelog/july2024/2024-07-02-object-storage-added-bucket-policies-can-now-be-configu.mdx index 74f5537ffe..824f1c749b 100644 --- a/changelog/july2024/2024-07-02-object-storage-added-bucket-policies-can-now-be-configu.mdx +++ b/changelog/july2024/2024-07-02-object-storage-added-bucket-policies-can-now-be-configu.mdx @@ -13,5 +13,5 @@ Bucket policies can now be created, viewed and edited from the [Scaleway console Simple and intuitive access management reduces configuration errors and enhances security. Granting granular access to your Object Storage resources has never been easier with our user-friendly interface that allows you to configure both IAM and bucket policies. -Find out how [create and manage your bucket policies](/storage/object/how-to/create-bucket-policy/) from the Scaleway console. +Find out how [create and manage your bucket policies](/object-storage/how-to/create-bucket-policy/) from the Scaleway console. diff --git a/changelog/july2024/2024-07-09-kubernetes-added-kubernetes-version-130-is-now-availabl.mdx b/changelog/july2024/2024-07-09-kubernetes-added-kubernetes-version-130-is-now-availabl.mdx index 774c16fb01..ef6f93ca0a 100644 --- a/changelog/july2024/2024-07-09-kubernetes-added-kubernetes-version-130-is-now-availabl.mdx +++ b/changelog/july2024/2024-07-09-kubernetes-added-kubernetes-version-130-is-now-availabl.mdx @@ -13,5 +13,5 @@ Scaleway managed Kubernetes products will support the latest minor version 1.30 In addition to patch versions 1.30.1, 1.30.2, and 1.30.3, releases 1.29.2 to 1.29.6, 1.28.8 to 1.28.11, 1.27.11 to 1.27.15, and 1.26.14 to 1.26.15 are also available. -Read our newest [version support policy](/containers/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. +Read our newest [version support policy](/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. diff --git a/changelog/july2024/2024-07-12-transactional-email-added-microsoft-excel-attachments-a.mdx b/changelog/july2024/2024-07-12-transactional-email-added-microsoft-excel-attachments-a.mdx index bbce8f3842..3ce607abcb 100644 --- a/changelog/july2024/2024-07-12-transactional-email-added-microsoft-excel-attachments-a.mdx +++ b/changelog/july2024/2024-07-12-transactional-email-added-microsoft-excel-attachments-a.mdx @@ -13,5 +13,5 @@ You can now send Excel attachments in your transactional emails. The following M * `application/vnd.openxmlformats-officedocument.spreadsheet` * `application/vnd.ms-excel` -Find out about the full range of available attachment types in our [Transactional Email capabilities and limits](/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/) documentation page. +Find out about the full range of available attachment types in our [Transactional Email capabilities and limits](/transactional-email/reference-content/tem-capabilities-and-limits/) documentation page. diff --git a/changelog/july2024/2024-07-25-secret-manager-added-secret-types-are-available-on-cons.mdx b/changelog/july2024/2024-07-25-secret-manager-added-secret-types-are-available-on-cons.mdx index 8a1fbb7f94..8efba58124 100644 --- a/changelog/july2024/2024-07-25-secret-manager-added-secret-types-are-available-on-cons.mdx +++ b/changelog/july2024/2024-07-25-secret-manager-added-secret-types-are-available-on-cons.mdx @@ -11,9 +11,9 @@ product: secret-manager Secret types are now displayed in the Scaleway console for better usability of secrets. -All secrets not explicitly tagged appear as opaque, but you can now decide to create new secrets of a specific [type](/identity-and-access-management/secret-manager/concepts/#secret-types) (among opaque, username/password, database credentials, SSH key, SSL/TLS certificate and key/value), and secrets versions will be of the same type. +All secrets not explicitly tagged appear as opaque, but you can now decide to create new secrets of a specific [type](/secret-manager/concepts/#secret-types) (among opaque, username/password, database credentials, SSH key, SSL/TLS certificate and key/value), and secrets versions will be of the same type. -Read [our documentation](/identity-and-access-management/secret-manager/api-cli/create-secret-with-type/) for more details on how to create secret types using the Scaleway API. +Read [our documentation](/secret-manager/api-cli/create-secret-with-type/) for more details on how to create secret types using the Scaleway API. diff --git a/changelog/june2023/2023-06-01-load-balancers-removed-sni-routes-to-http.mdx b/changelog/june2023/2023-06-01-load-balancers-removed-sni-routes-to-http.mdx index ea41815236..e4d74f4684 100644 --- a/changelog/june2023/2023-06-01-load-balancers-removed-sni-routes-to-http.mdx +++ b/changelog/june2023/2023-06-01-load-balancers-removed-sni-routes-to-http.mdx @@ -13,5 +13,5 @@ Following our deprecation notice, it is no longer possible to create and use SNI All Load Balancers that were still using SNI routes with HTTP backends on June 1st have now been automatically updated to use the HTTP Host header route instead. -For more information please refer to our [product documentation](https://www.scaleway.com/en/docs/network/load-balancer/reference-content/sni-route-deprecation/). +For more information please refer to our [product documentation](https://www.scaleway.com/en/docs/load-balancer/reference-content/sni-route-deprecation/). diff --git a/changelog/june2023/2023-06-13-containers-changed-serverless-containers-in-cockpit.mdx b/changelog/june2023/2023-06-13-containers-changed-serverless-containers-in-cockpit.mdx index c7fa98e15f..3d8581b2e7 100644 --- a/changelog/june2023/2023-06-13-containers-changed-serverless-containers-in-cockpit.mdx +++ b/changelog/june2023/2023-06-13-containers-changed-serverless-containers-in-cockpit.mdx @@ -9,5 +9,5 @@ category: serverless product: containers --- -Serverless Containers logs and metrics are now displayed in Cockpit by default, allowing you to have more control over your logs and metrics. Read [our documentation](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. +Serverless Containers logs and metrics are now displayed in Cockpit by default, allowing you to have more control over your logs and metrics. Read [our documentation](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. diff --git a/changelog/june2023/2023-06-13-functions-changed-serverless-functions-logs-and.mdx b/changelog/june2023/2023-06-13-functions-changed-serverless-functions-logs-and.mdx index 616d71151a..44aefcd2fb 100644 --- a/changelog/june2023/2023-06-13-functions-changed-serverless-functions-logs-and.mdx +++ b/changelog/june2023/2023-06-13-functions-changed-serverless-functions-logs-and.mdx @@ -9,5 +9,5 @@ category: serverless product: functions --- -Serverless Functions logs and metrics are now displayed in Cockpit by default, allowing you to have more control over your logs and metrics. Read [our documentation](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. +Serverless Functions logs and metrics are now displayed in Cockpit by default, allowing you to have more control over your logs and metrics. Read [our documentation](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which other products are integrated into Cockpit. diff --git a/changelog/june2023/2023-06-22-instances-fix-wrong-user-cloud-init-config.mdx b/changelog/june2023/2023-06-22-instances-fix-wrong-user-cloud-init-config.mdx index d0ec45c46a..eddadf9a75 100644 --- a/changelog/june2023/2023-06-22-instances-fix-wrong-user-cloud-init-config.mdx +++ b/changelog/june2023/2023-06-22-instances-fix-wrong-user-cloud-init-config.mdx @@ -14,4 +14,4 @@ user configuration made by the custom-built upstream `cloud-init` 23.2. It now uses the official Debian Unstable `cloud-init` package. -Users who want to fix their existing Instances may follow [this guide](/compute/instances/troubleshooting/fix-cloud-init-debian12/). +Users who want to fix their existing Instances may follow [this guide](/instances/troubleshooting/fix-cloud-init-debian12/). diff --git a/changelog/june2023/2023-06-27-load-balancers-added-backends-now-have-the.mdx b/changelog/june2023/2023-06-27-load-balancers-added-backends-now-have-the.mdx index 5a86eaaa1e..b70fb1cb66 100644 --- a/changelog/june2023/2023-06-27-load-balancers-added-backends-now-have-the.mdx +++ b/changelog/june2023/2023-06-27-load-balancers-added-backends-now-have-the.mdx @@ -15,8 +15,8 @@ We have completely redesigned the backend management experience in the console: - You now have access to many backend configuration settings that were previously only available through API On top of this we have taken the opportunity to introduce 2 new features: -- [Backend protection](https://www.scaleway.com/en/docs/network/load-balancer/reference-content/configuring-backends/#backend-protection) allows limiting the number of sessions on backend servers -- [Backend retry logic](https://www.scaleway.com/en/docs/network/load-balancer/reference-content/configuring-backends/#retries) allows fine tuning how to retry failed connections to backend servers +- [Backend protection](https://www.scaleway.com/en/docs/load-balancer/reference-content/configuring-backends/#backend-protection) allows limiting the number of sessions on backend servers +- [Backend retry logic](https://www.scaleway.com/en/docs/load-balancer/reference-content/configuring-backends/#retries) allows fine tuning how to retry failed connections to backend servers -For more information you can have a look at our updated [reference documentation](https://www.scaleway.com/en/docs/network/load-balancer/reference-content/). +For more information you can have a look at our updated [reference documentation](https://www.scaleway.com/en/docs/load-balancer/reference-content/). diff --git a/changelog/june2024/2024-06-03-kubernetes-deprecated-kubernetes-worker-nodes-with-nat-.mdx b/changelog/june2024/2024-06-03-kubernetes-deprecated-kubernetes-worker-nodes-with-nat-.mdx index 3a042b7f99..928ac03d93 100644 --- a/changelog/june2024/2024-06-03-kubernetes-deprecated-kubernetes-worker-nodes-with-nat-.mdx +++ b/changelog/june2024/2024-06-03-kubernetes-deprecated-kubernetes-worker-nodes-with-nat-.mdx @@ -15,6 +15,6 @@ With Routed IPs, your worker nodes will receive a flexible IP address, maintaini NAT IPs will reach end of life on October 1st, 2024. -- All information on the migration methods are provided in our [documentation about moving Kubernetes nodes to routed IPs](/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip/). +- All information on the migration methods are provided in our [documentation about moving Kubernetes nodes to routed IPs](/kubernetes/reference-content/move-kubernetes-nodes-routed-ip/). - [Read our blog post](https://www.scaleway.com/en/news/routed-ips-are-coming-to-all-scaleway-products/) to find out more about the changes behind this evolution. diff --git a/changelog/june2024/2024-06-25-messaging-and-queuing-changed-messaging-and-queuing-sns.mdx b/changelog/june2024/2024-06-25-messaging-and-queuing-changed-messaging-and-queuing-sns.mdx index c1b18e19eb..3409232b64 100644 --- a/changelog/june2024/2024-06-25-messaging-and-queuing-changed-messaging-and-queuing-sns.mdx +++ b/changelog/june2024/2024-06-25-messaging-and-queuing-changed-messaging-and-queuing-sns.mdx @@ -9,6 +9,6 @@ category: serverless product: messaging-and-queuing --- -[Scaleway Messaging and Queuing SNS](https://www.scaleway.com/en/docs/serverless/messaging/quickstart/#quickstart-for-topics-and-events) is a fully managed pub/sub solution for sending notifications and messages between cloud products. It is natively integrated with our Serverless ecosystem. +[Scaleway Messaging and Queuing SNS](https://www.scaleway.com/en/docs/messaging/quickstart/#quickstart-for-topics-and-events) is a fully managed pub/sub solution for sending notifications and messages between cloud products. It is natively integrated with our Serverless ecosystem. It is now in General Availability, ready for your production use cases. diff --git a/changelog/june2024/2024-06-25-vpc-added-vpc-routing-is-now-in-general-availability.mdx b/changelog/june2024/2024-06-25-vpc-added-vpc-routing-is-now-in-general-availability.mdx index acc9480835..4993b55128 100644 --- a/changelog/june2024/2024-06-25-vpc-added-vpc-routing-is-now-in-general-availability.mdx +++ b/changelog/june2024/2024-06-25-vpc-added-vpc-routing-is-now-in-general-availability.mdx @@ -9,5 +9,5 @@ category: network product: vpc --- -[VPC Routing](/network/vpc/concepts/#routing) aims to simplify and streamline the creation of routes between Private Networks within a VPC. It provides the perfect way to create multi-PN architectures. Management of custom routes will be available at the beginning of Q3 2024. +[VPC Routing](/vpc/concepts/#routing) aims to simplify and streamline the creation of routes between Private Networks within a VPC. It provides the perfect way to create multi-PN architectures. Management of custom routes will be available at the beginning of Q3 2024. diff --git a/changelog/kubernetes/november2022/2022-11-03-dedicated-control-plane-offer.mdx b/changelog/kubernetes/november2022/2022-11-03-dedicated-control-plane-offer.mdx index b8f321729a..4371336e33 100644 --- a/changelog/kubernetes/november2022/2022-11-03-dedicated-control-plane-offer.mdx +++ b/changelog/kubernetes/november2022/2022-11-03-dedicated-control-plane-offer.mdx @@ -9,4 +9,4 @@ category: containers product: kubernetes --- -Discover our [new dedicated control-plane offer](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/) for heavy workloads! \ No newline at end of file +Discover our [new dedicated control-plane offer](/kubernetes/reference-content/kubernetes-control-plane-offers/) for heavy workloads! \ No newline at end of file diff --git a/changelog/kubernetes/october2022/2022-10-06-deploying-ingress-controller-in-kubernetes-cluster-deprecated.mdx b/changelog/kubernetes/october2022/2022-10-06-deploying-ingress-controller-in-kubernetes-cluster-deprecated.mdx index 3435057ee1..915dd6e173 100644 --- a/changelog/kubernetes/october2022/2022-10-06-deploying-ingress-controller-in-kubernetes-cluster-deprecated.mdx +++ b/changelog/kubernetes/october2022/2022-10-06-deploying-ingress-controller-in-kubernetes-cluster-deprecated.mdx @@ -9,4 +9,4 @@ category: containers product: kubernetes --- -The option to deploy an ingress controller in a Kubernetes cluster at cluster creation is no longer possible. Users can still [deploy a pre-configured Ingress Controller](/containers/kubernetes/how-to/deploy-ingress-controller/) after cluster creation using the Easy Deploy feature within the [Scaleway console](https://console.scaleway.com/). \ No newline at end of file +The option to deploy an ingress controller in a Kubernetes cluster at cluster creation is no longer possible. Users can still [deploy a pre-configured Ingress Controller](/kubernetes/how-to/deploy-ingress-controller/) after cluster creation using the Easy Deploy feature within the [Scaleway console](https://console.scaleway.com/). \ No newline at end of file diff --git a/changelog/kubernetes/october2022/2022-10-06-kubernetes-version-1.19-removed.mdx b/changelog/kubernetes/october2022/2022-10-06-kubernetes-version-1.19-removed.mdx index 9bd514aba5..e32f3fde82 100644 --- a/changelog/kubernetes/october2022/2022-10-06-kubernetes-version-1.19-removed.mdx +++ b/changelog/kubernetes/october2022/2022-10-06-kubernetes-version-1.19-removed.mdx @@ -9,4 +9,4 @@ category: containers product: kubernetes --- -Kubernetes 1.19 is no longer supported on our [Kubernetes products](/containers/kubernetes/quickstart/) starting October 15th. Clusters in this specific version will automatically be upgraded to 1.20 at that date. \ No newline at end of file +Kubernetes 1.19 is no longer supported on our [Kubernetes products](/kubernetes/quickstart/) starting October 15th. Clusters in this specific version will automatically be upgraded to 1.20 at that date. \ No newline at end of file diff --git a/changelog/managed-services/november2022/2022-11-10-transactional-email.mdx b/changelog/managed-services/november2022/2022-11-10-transactional-email.mdx index afa3d7a8b4..c40d89b200 100644 --- a/changelog/managed-services/november2022/2022-11-10-transactional-email.mdx +++ b/changelog/managed-services/november2022/2022-11-10-transactional-email.mdx @@ -9,4 +9,4 @@ category: managed-services product: transactional-email --- -Discover [Transactional Email](/managed-services/transactional-email/quickstart/), a fully managed solution dedicated to sending your transactional emails! \ No newline at end of file +Discover [Transactional Email](/transactional-email/quickstart/), a fully managed solution dedicated to sending your transactional emails! \ No newline at end of file diff --git a/changelog/march2024/2024-03-01-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx b/changelog/march2024/2024-03-01-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx index d3ad7ebca8..7c015e0bc6 100644 --- a/changelog/march2024/2024-03-01-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx +++ b/changelog/march2024/2024-03-01-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx @@ -11,5 +11,5 @@ product: kubernetes Clusters using the Kubernetes 1.23 version will be automatically upgraded to the Kubernetes 1.24 version after March 15th, 2024. -Find more details in our [version support policy](/containers/kubernetes/reference-content/version-support-policy/). +Find more details in our [version support policy](/kubernetes/reference-content/version-support-policy/). diff --git a/changelog/march2024/2024-03-13-kubernetes-added-kubernetes-audit-logs.mdx b/changelog/march2024/2024-03-13-kubernetes-added-kubernetes-audit-logs.mdx index 990c187ebb..babedd3006 100644 --- a/changelog/march2024/2024-03-13-kubernetes-added-kubernetes-audit-logs.mdx +++ b/changelog/march2024/2024-03-13-kubernetes-added-kubernetes-audit-logs.mdx @@ -9,10 +9,10 @@ category: containers product: kubernetes --- -Audit logs are enabled by default for Kubernetes clusters with [dedicated control planes](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). +Audit logs are enabled by default for Kubernetes clusters with [dedicated control planes](/kubernetes/reference-content/kubernetes-control-plane-offers/). For security and compliance, audit logging allows to keep a chronological record of calls made to the Kubernetes API server, investigate suspicious API requests, collect statistics, or create monitoring alerts for unwanted API calls. All audit logs are centralized in Cockpit for free. -Find more information in our [dedicated documentation](/containers/kubernetes/how-to/access-audit-logs/) +Find more information in our [dedicated documentation](/kubernetes/how-to/access-audit-logs/) 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 c1ac5b0b35..e3d134638e 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 @@ -9,6 +9,6 @@ category: storage product: block-storage --- -We are excited to introduce our new [Block Storage Low Latency](/storage/block/quickstart/) offers with 5K and 15K IOPS! +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/). diff --git a/changelog/march2024/2024-03-19-kubernetes-added-kubernetes-kapsule-and-kubernetes-kosm.mdx b/changelog/march2024/2024-03-19-kubernetes-added-kubernetes-kapsule-and-kubernetes-kosm.mdx index fda2b62d25..94753d59cc 100644 --- a/changelog/march2024/2024-03-19-kubernetes-added-kubernetes-kapsule-and-kubernetes-kosm.mdx +++ b/changelog/march2024/2024-03-19-kubernetes-added-kubernetes-kapsule-and-kubernetes-kosm.mdx @@ -13,6 +13,6 @@ product: kubernetes In public beta stage, Scaleway Kubernetes clusters on versions >=1.28 can now add COP-ARM node pools. For seamless deployments, read our documentation: -- [how to deploy both x86 and ARM images](https://www.scaleway.com/en/docs/containers/kubernetes/how-to/deploy-x86-arm-images/) -- [troubleshooting issues with containers not starting on ARM Instances](https://www.scaleway.com/en/docs/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances/) +- [how to deploy both x86 and ARM images](https://www.scaleway.com/en/docs/kubernetes/how-to/deploy-x86-arm-images/) +- [troubleshooting issues with containers not starting on ARM Instances](https://www.scaleway.com/en/docs/kubernetes/troubleshooting/containers-not-starting-arm-instances/) diff --git a/changelog/march2024/2024-03-19-kubernetes-changed-container-storage-interface-v03-now-.mdx b/changelog/march2024/2024-03-19-kubernetes-changed-container-storage-interface-v03-now-.mdx index 05b6d14733..7f0a02d63a 100644 --- a/changelog/march2024/2024-03-19-kubernetes-changed-container-storage-interface-v03-now-.mdx +++ b/changelog/march2024/2024-03-19-kubernetes-changed-container-storage-interface-v03-now-.mdx @@ -9,7 +9,7 @@ category: containers product: kubernetes --- -New Kubernetes Kapsule clusters now natively incorporate version 0.3 of Scaleway's Container Storage Interface, granting users access to [Block Storage Low Latency volumes](/storage/block/quickstart/) via the three storage classes: `sbs-default`, `sbs-5k`, or `sbs-15k`. +New Kubernetes Kapsule clusters now natively incorporate version 0.3 of Scaleway's Container Storage Interface, granting users access to [Block Storage Low Latency volumes](/block-storage/quickstart/) via the three storage classes: `sbs-default`, `sbs-5k`, or `sbs-15k`. Read our [tutorial to get started with Kubernetes Storage](/tutorials/get-started-kubernetes-storage/) for more information. diff --git a/changelog/march2024/2024-03-25-postgresql-and-mysql-added-ability-to-remove-public-end.mdx b/changelog/march2024/2024-03-25-postgresql-and-mysql-added-ability-to-remove-public-end.mdx index 8b7de6be2b..e64a89572a 100644 --- a/changelog/march2024/2024-03-25-postgresql-and-mysql-added-ability-to-remove-public-end.mdx +++ b/changelog/march2024/2024-03-25-postgresql-and-mysql-added-ability-to-remove-public-end.mdx @@ -11,5 +11,5 @@ product: postgresql-and-mysql Network management on Managed Databases for PostgreSQL and MySQL has been improved! You can now add/remove public endpoints directly from the [Scaleway console](https://console.scaleway.com). This includes endpoints attached to both Database Instances and Read-Replicas. -Refer to [our documentation](/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint/) for more information. +Refer to [our documentation](/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint/) for more information. diff --git a/changelog/march2024/2024-03-28-billing-added-discover-our-cost-manager-tool.mdx b/changelog/march2024/2024-03-28-billing-added-discover-our-cost-manager-tool.mdx index a760f3f7de..c6ae1004d1 100644 --- a/changelog/march2024/2024-03-28-billing-added-discover-our-cost-manager-tool.mdx +++ b/changelog/march2024/2024-03-28-billing-added-discover-our-cost-manager-tool.mdx @@ -18,4 +18,4 @@ We are introducing our Cost Manager tool, which helps you to: Discover the Cost Manager tool in the billing section of your [Scaleway console](https://console.scaleway.com/billing/consumption). -Refer to the [How to use the cost manager](/console/billing/how-to/use-the-cost-manager/) documentation page for more information. +Refer to the [How to use the cost manager](/billing/how-to/use-the-cost-manager/) documentation page for more information. diff --git a/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx b/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx index 604c6b2e31..92d61519ac 100644 --- a/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx +++ b/changelog/march2024/2024-03-28-jobs-added-serverless-jobs-is-now-in-ga.mdx @@ -9,5 +9,5 @@ category: serverless product: jobs --- -Serverless Jobs is now in GA. Severless Jobs allows you to to run simple tasks per batch in the cloud without having to worry about infrastructure management. Find out more about it in [our dedicated documentation](/serverless/jobs/). +Serverless Jobs is now in GA. Severless Jobs allows you to to run simple tasks per batch in the cloud without having to worry about infrastructure management. Find out more about it in [our dedicated documentation](/serverless-jobs/). diff --git a/changelog/may2023/2023-05-02-kubernetes-added-kubernetes-version-1.27-now.mdx b/changelog/may2023/2023-05-02-kubernetes-added-kubernetes-version-1.27-now.mdx index 3a913457e1..1ffc9f57fe 100644 --- a/changelog/may2023/2023-05-02-kubernetes-added-kubernetes-version-1.27-now.mdx +++ b/changelog/may2023/2023-05-02-kubernetes-added-kubernetes-version-1.27-now.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Scaleway Kubernetes products now support the latest minor version 1.27 "Chill Vibes". Read [our version support policy](/containers/kubernetes/reference-content/version-support-policy/) for more information. +Scaleway Kubernetes products now support the latest minor version 1.27 "Chill Vibes". Read [our version support policy](/kubernetes/reference-content/version-support-policy/) for more information. diff --git a/changelog/may2023/2023-05-10-transactional-email-changed-tem-in-ga.mdx b/changelog/may2023/2023-05-10-transactional-email-changed-tem-in-ga.mdx index d794af5150..3a3e13a0b0 100644 --- a/changelog/may2023/2023-05-10-transactional-email-changed-tem-in-ga.mdx +++ b/changelog/may2023/2023-05-10-transactional-email-changed-tem-in-ga.mdx @@ -9,5 +9,5 @@ category: managed-services product: transactional-email --- -Scaleway Transactional Email is now in General Availability! Transactional Email is a fully managed solution dedicated to sending your transactional emails. Check out our [dedicated documentation for more information](/managed-services/transactional-email/). +Scaleway Transactional Email is now in General Availability! Transactional Email is a fully managed solution dedicated to sending your transactional emails. Check out our [dedicated documentation for more information](/transactional-email/). diff --git a/changelog/may2023/2023-05-12-functions-added-functions-triggers-in-beta.mdx b/changelog/may2023/2023-05-12-functions-added-functions-triggers-in-beta.mdx index 93e19fefe2..1c256c0c48 100644 --- a/changelog/may2023/2023-05-12-functions-added-functions-triggers-in-beta.mdx +++ b/changelog/may2023/2023-05-12-functions-added-functions-triggers-in-beta.mdx @@ -10,5 +10,5 @@ product: functions --- Functions can now be triggered from Message Queues hosted in Messaging and Queuing SQS namespaces. -Simply add an [SQS Trigger](/serverless/functions/how-to/add-trigger-to-a-function/) from the console and when a new message is sent to the queue, it will trigger your function. +Simply add an [SQS Trigger](/serverless-functions/how-to/add-trigger-to-a-function/) from the console and when a new message is sent to the queue, it will trigger your function. diff --git a/changelog/may2023/2023-05-15-kubernetes-added-kubernetes-kapsule-is-now.mdx b/changelog/may2023/2023-05-15-kubernetes-added-kubernetes-kapsule-is-now.mdx index a4c531bddd..05030883b7 100644 --- a/changelog/may2023/2023-05-15-kubernetes-added-kubernetes-kapsule-is-now.mdx +++ b/changelog/may2023/2023-05-15-kubernetes-added-kubernetes-kapsule-is-now.mdx @@ -12,5 +12,5 @@ product: kubernetes By default, every new Kubernetes Kapsule cluster created from the Scaleway console is now attached to a Private Network, free of charge, fully configured, and supported on Terraform and CLI. Migrate now your public Kubernetes clusters from the Scaleway console. -Find out more information on the [Kubernetes Private Network documentation](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/) +Find out more information on the [Kubernetes Private Network documentation](https://www.scaleway.com/en/docs/kubernetes/reference-content/secure-cluster-with-private-network/) diff --git a/changelog/may2023/2023-05-15-kubernetes-changed-enable-or-disable-ssh.mdx b/changelog/may2023/2023-05-15-kubernetes-changed-enable-or-disable-ssh.mdx index 14742a445c..340ea35088 100644 --- a/changelog/may2023/2023-05-15-kubernetes-changed-enable-or-disable-ssh.mdx +++ b/changelog/may2023/2023-05-15-kubernetes-changed-enable-or-disable-ssh.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Kubernetes Kapsule nodes come now pre-installed with an SSH server that a security group protects. This SSH server is intended solely for debugging purposes. To activate or deactivate the SSH server on your nodes, refer to the [documentation](https://www.scaleway.com/en/docs/containers/kubernetes/how-to/enable-disable-ssh/) for detailed instructions. +Kubernetes Kapsule nodes come now pre-installed with an SSH server that a security group protects. This SSH server is intended solely for debugging purposes. To activate or deactivate the SSH server on your nodes, refer to the [documentation](https://www.scaleway.com/en/docs/kubernetes/how-to/enable-disable-ssh/) for detailed instructions. diff --git a/changelog/may2023/2023-05-25-kubernetes-changed-new-program-to-add.mdx b/changelog/may2023/2023-05-25-kubernetes-changed-new-program-to-add.mdx index a48f276692..1b121eda35 100644 --- a/changelog/may2023/2023-05-25-kubernetes-changed-new-program-to-add.mdx +++ b/changelog/may2023/2023-05-25-kubernetes-changed-new-program-to-add.mdx @@ -11,5 +11,5 @@ product: kubernetes Kubernetes Kosmos lets you provision external nodes seamlessly with its new agent, bringing various security fixes, ARM and Debian support, and using a new IAM permission. -Find out more information on the [Kosmos documentation](https://www.scaleway.com/en/docs/containers/kubernetes/how-to/edit-kosmos-cluster/#how-to-add-external-nodes-to-your-multi-cloud-pool). +Find out more information on the [Kosmos documentation](https://www.scaleway.com/en/docs/kubernetes/how-to/edit-kosmos-cluster/#how-to-add-external-nodes-to-your-multi-cloud-pool). diff --git a/changelog/may2024/2024-05-03-postgresql-and-mysql-added-self-apply-scheduled-mainten.mdx b/changelog/may2024/2024-05-03-postgresql-and-mysql-added-self-apply-scheduled-mainten.mdx index 14dd5089c8..ce8da563f8 100644 --- a/changelog/may2024/2024-05-03-postgresql-and-mysql-added-self-apply-scheduled-mainten.mdx +++ b/changelog/may2024/2024-05-03-postgresql-and-mysql-added-self-apply-scheduled-mainten.mdx @@ -11,5 +11,5 @@ product: postgresql-and-mysql Database maintenance operations are set up, run, and scheduled by Scaleway, but you can now select when to apply them to avoid interruptions during peak times. -Refer to the [How to apply maintenance](/managed-databases/postgresql-and-mysql/how-to/apply-maintenance/) documentation page for more information. +Refer to the [How to apply maintenance](/managed-databases-for-postgresql-and-mysql/how-to/apply-maintenance/) documentation page for more information. diff --git a/changelog/may2024/2024-05-22-kubernetes-removed-kapsule-clusters-with-only-public-ip.mdx b/changelog/may2024/2024-05-22-kubernetes-removed-kapsule-clusters-with-only-public-ip.mdx index 08a2797e98..c95f391ca9 100644 --- a/changelog/may2024/2024-05-22-kubernetes-removed-kapsule-clusters-with-only-public-ip.mdx +++ b/changelog/may2024/2024-05-22-kubernetes-removed-kapsule-clusters-with-only-public-ip.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Ending the deprecation cycle and completing the planned migration, all Kapsule clusters are natively deployed with a [Scaleway Private Network](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster). +Ending the deprecation cycle and completing the planned migration, all Kapsule clusters are natively deployed with a [Scaleway Private Network](/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster). diff --git a/changelog/may2024/2024-05-22-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx b/changelog/may2024/2024-05-22-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx index ad0435222c..07d348d041 100644 --- a/changelog/may2024/2024-05-22-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx +++ b/changelog/may2024/2024-05-22-kubernetes-removed-scaleway-kubernetes-products-no-long.mdx @@ -11,5 +11,5 @@ product: kubernetes Clusters using the Kubernetes 1.24 version will be upgraded to Kubernetes 1.25 after May 15th, 2024. Scaleway will change the CNI configuration to `none` for clusters still running unsupported CNIs (Flannel, Weave). -Find more details in our [version support policy](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/version-support-policy/#supported-container-network-interfaces-cni). +Find more details in our [version support policy](https://www.scaleway.com/en/docs/kubernetes/reference-content/version-support-policy/#supported-container-network-interfaces-cni). diff --git a/changelog/may2024/2024-05-24-cockpit-added-cockpit-available-in-all-region.mdx b/changelog/may2024/2024-05-24-cockpit-added-cockpit-available-in-all-region.mdx index 6c7925f764..2f9bbc4f83 100644 --- a/changelog/may2024/2024-05-24-cockpit-added-cockpit-available-in-all-region.mdx +++ b/changelog/may2024/2024-05-24-cockpit-added-cockpit-available-in-all-region.mdx @@ -9,5 +9,5 @@ category: observability product: cockpit --- -Cockpit is now available in all three Scaleway regions: Paris, Amsterdam, and Warsaw. From the Scaleway console, you can now decide in which region to enable the [alert manager](/observability/cockpit/concepts/#alert-manager) and your [preconfigured alerts](/observability/cockpit/concepts/#preconfigured-alerts). You can also choose the regions in which to create your [data types](/observability/cockpit/concepts/#data-types), [data sources](/observability/cockpit/concepts/#data-sources), and [tokens](/observability/cockpit/concepts/#tokens). +Cockpit is now available in all three Scaleway regions: Paris, Amsterdam, and Warsaw. From the Scaleway console, you can now decide in which region to enable the [alert manager](/cockpit/concepts/#alert-manager) and your [preconfigured alerts](/cockpit/concepts/#preconfigured-alerts). You can also choose the regions in which to create your [data types](/cockpit/concepts/#data-types), [data sources](/cockpit/concepts/#data-sources), and [tokens](/cockpit/concepts/#tokens). diff --git a/changelog/network/january2023/2023-01-06-load-balancers-added-load-balancers-now-support.mdx b/changelog/network/january2023/2023-01-06-load-balancers-added-load-balancers-now-support.mdx index 885484f02b..6c2de48ea7 100644 --- a/changelog/network/january2023/2023-01-06-load-balancers-added-load-balancers-now-support.mdx +++ b/changelog/network/january2023/2023-01-06-load-balancers-added-load-balancers-now-support.mdx @@ -15,5 +15,5 @@ HTTP/2 is now supported both at the frontend and the backend of Scaleway Load Ba HTTP/3 is the next generation of HTTP protocol, built on top of QUIC. HTTP/3 represents a big step forward for internet performance and security. As this is a very new protocol, you have to enable HTTP/3 support if you wish to use it with a Scaleway Load Balancer. HTTP/3 is currently only supported at the frontend. -[Find out how to set up your Load Balancers for HTTP/2 and HTTP/3.](/network/load-balancer/reference-content/http2-http3/) +[Find out how to set up your Load Balancers for HTTP/2 and HTTP/3.](/load-balancer/reference-content/http2-http3/) diff --git a/changelog/network/march2022/2022-03-01-private-networks-added-ssh-bastion.mdx b/changelog/network/march2022/2022-03-01-private-networks-added-ssh-bastion.mdx index c2e7ee398e..4bbeea85d0 100644 --- a/changelog/network/march2022/2022-03-01-private-networks-added-ssh-bastion.mdx +++ b/changelog/network/march2022/2022-03-01-private-networks-added-ssh-bastion.mdx @@ -9,4 +9,4 @@ category: network product: public-gateways --- -The [SSH Bastion](/network/public-gateways/how-to/use-ssh-bastion/) feature helps you control and secure all your SSH keys for developer and sysadmin access. Moreover, it will help to reduce the attack surface of any malicious actors. +The [SSH Bastion](/public-gateways/how-to/use-ssh-bastion/) feature helps you control and secure all your SSH keys for developer and sysadmin access. Moreover, it will help to reduce the attack surface of any malicious actors. diff --git a/changelog/network/november2022/2022-11-17-domains-and-dns-available.mdx b/changelog/network/november2022/2022-11-17-domains-and-dns-available.mdx index 2ee51eaa4d..d2596cf6ad 100644 --- a/changelog/network/november2022/2022-11-17-domains-and-dns-available.mdx +++ b/changelog/network/november2022/2022-11-17-domains-and-dns-available.mdx @@ -9,4 +9,4 @@ category: network product: domains-and-dns --- -[Domains and DNS](/network/domains-and-dns/quickstart/) is a service that allows you to [register](/network/domains-and-dns/how-to/register-internal-domain/) and [manage your domains](/network/domains-and-dns/how-to/manage-external-domain/) directly from the [Scaleway console](https://console.scaleway.com/). \ No newline at end of file +[Domains and DNS](/domains-and-dns/quickstart/) is a service that allows you to [register](/domains-and-dns/how-to/register-internal-domain/) and [manage your domains](/domains-and-dns/how-to/manage-external-domain/) directly from the [Scaleway console](https://console.scaleway.com/). \ No newline at end of file diff --git a/changelog/november2023/2023-11-07-cockpit-added-beta-traces.mdx b/changelog/november2023/2023-11-07-cockpit-added-beta-traces.mdx index 0aa7ebddf1..4eca92e408 100644 --- a/changelog/november2023/2023-11-07-cockpit-added-beta-traces.mdx +++ b/changelog/november2023/2023-11-07-cockpit-added-beta-traces.mdx @@ -11,5 +11,5 @@ product: cockpit Along with metrics and logs, you can now push and pull traces from your Cockpit. Gain real-time insights and trace the heartbeat of your system with our new traces feature, based on Grafana Tempo. -Read [our documentation](/observability/cockpit/how-to/activate-push-traces/) to find out how to start using our traces feature. +Read [our documentation](/cockpit/how-to/activate-push-traces/) to find out how to start using our traces feature. diff --git a/changelog/november2023/2023-11-08-object-storage-added-new-bucket-policy-version-allowing.mdx b/changelog/november2023/2023-11-08-object-storage-added-new-bucket-policy-version-allowing.mdx index e6426e78ea..d702ecbe3f 100644 --- a/changelog/november2023/2023-11-08-object-storage-added-new-bucket-policy-version-allowing.mdx +++ b/changelog/november2023/2023-11-08-object-storage-added-new-bucket-policy-version-allowing.mdx @@ -10,5 +10,5 @@ product: object-storage --- With version 2023-04-17 of bucket policies, you can grant users and applications granular permissions to specific buckets and objects. -Check out our documentation to discover this new [bucket policy version](https://www.scaleway.com/en/docs/storage/object/api-cli/bucket-policy/) , and learn [how to combine IAM and bucket policies](https://www.scaleway.com/en/docs/storage/object/api-cli/combining-iam-and-object-storage/) to set up granular access to Object Storage! +Check out our documentation to discover this new [bucket policy version](https://www.scaleway.com/en/docs/object-storage/api-cli/bucket-policy/) , and learn [how to combine IAM and bucket policies](https://www.scaleway.com/en/docs/object-storage/api-cli/combining-iam-and-object-storage/) to set up granular access to Object Storage! diff --git a/changelog/november2023/2023-11-20-transactional-email-added-domain-reputation-score.mdx b/changelog/november2023/2023-11-20-transactional-email-added-domain-reputation-score.mdx index 7a7621a02e..fdaa027934 100644 --- a/changelog/november2023/2023-11-20-transactional-email-added-domain-reputation-score.mdx +++ b/changelog/november2023/2023-11-20-transactional-email-added-domain-reputation-score.mdx @@ -9,5 +9,5 @@ category: managed-services product: transactional-email --- -We have recently introduced [domain reputation score](/managed-services/transactional-email/concepts/#reputation-score). Every domain within your Organization has a score, reflecting its overall health. The higher the score, the better the delivery performance for your domain. Refer to our documentation for [guidelines on maintaining a favorable reputation score](/managed-services/transactional-email/reference-content/understanding-tem-reputation-score/). +We have recently introduced [domain reputation score](/transactional-email/concepts/#reputation-score). Every domain within your Organization has a score, reflecting its overall health. The higher the score, the better the delivery performance for your domain. Refer to our documentation for [guidelines on maintaining a favorable reputation score](/transactional-email/reference-content/understanding-tem-reputation-score/). diff --git a/changelog/november2023/2023-11-20-transactional-email-added-email-flags.mdx b/changelog/november2023/2023-11-20-transactional-email-added-email-flags.mdx index deb0fc1179..d11cea3b8c 100644 --- a/changelog/november2023/2023-11-20-transactional-email-added-email-flags.mdx +++ b/changelog/november2023/2023-11-20-transactional-email-added-email-flags.mdx @@ -9,9 +9,9 @@ category: managed-services product: transactional-email --- -Get more information on your email delivery issues with [flags](/managed-services/transactional-email/concepts/#flags). Whether it is a [hard bounce](/managed-services/transactional-email/concepts/#hard-bounce), [soft bounce](/managed-services/transactional-email/concepts/#soft-bounce), [mailbox full](/managed-services/transactional-email/concepts/#flags), or other issues, these flags provide immediate insights into the reasons behind delivery failures. +Get more information on your email delivery issues with [flags](/transactional-email/concepts/#flags). Whether it is a [hard bounce](/transactional-email/concepts/#hard-bounce), [soft bounce](/transactional-email/concepts/#soft-bounce), [mailbox full](/transactional-email/concepts/#flags), or other issues, these flags provide immediate insights into the reasons behind delivery failures. You can filter on these flags via the API and from the **Email activity** tab of your Transactional Email domain in the Scaleway console. -For more information, refer to the [flags concept page](/managed-services/transactional-email/concepts/#flags) or the [documentation](/managed-services/transactional-email/how-to/manage-email-activity/) on how to manage your email activity. +For more information, refer to the [flags concept page](/transactional-email/concepts/#flags) or the [documentation](/transactional-email/how-to/manage-email-activity/) on how to manage your email activity. diff --git a/changelog/november2023/2023-11-21-load-balancers-added-load-balancer-logs-are-now-availab.mdx b/changelog/november2023/2023-11-21-load-balancers-added-load-balancer-logs-are-now-availab.mdx index 032d721847..64a7634567 100644 --- a/changelog/november2023/2023-11-21-load-balancers-added-load-balancer-logs-are-now-availab.mdx +++ b/changelog/november2023/2023-11-21-load-balancers-added-load-balancer-logs-are-now-availab.mdx @@ -11,5 +11,5 @@ product: load-balancers Load Balancer now generates logs when the state of backend servers changes, or when your frontend TLS certificates expire. These logs are sent to your Scaleway Cockpit and you can browse them via the dedicated **LB Logs Overview** dashboard. They provide information not only on the changes in state of backend servers, but also the reasons for these changes. With these logs, you will be equipped to properly troubleshoot backend server issues. -Read more about Load Balancer logs in our [documentation](https://www.scaleway.com/en/docs/network/load-balancer/how-to/monitor-lb-cockpit/#how-to-view-and-understand-your-load-balancer-logs). +Read more about Load Balancer logs in our [documentation](https://www.scaleway.com/en/docs/load-balancer/how-to/monitor-lb-cockpit/#how-to-view-and-understand-your-load-balancer-logs). diff --git a/changelog/november2023/2023-11-23-secret-manager-changed-secret-manager-console-pages-hav.mdx b/changelog/november2023/2023-11-23-secret-manager-changed-secret-manager-console-pages-hav.mdx index f0fffe2bc5..6363d3c3a7 100644 --- a/changelog/november2023/2023-11-23-secret-manager-changed-secret-manager-console-pages-hav.mdx +++ b/changelog/november2023/2023-11-23-secret-manager-changed-secret-manager-console-pages-hav.mdx @@ -9,7 +9,7 @@ category: security-identity product: secret-manager --- -In the Secret Manager section of the [Scaleway console](https://console.scaleway.com), you can now select a [region](/identity-and-access-management/secret-manager/concepts/#region) to display secrets and folders inside this region. Whenever you create a secret, you no longer need to specify the region, as it will be created in the region you are currently working on. +In the Secret Manager section of the [Scaleway console](https://console.scaleway.com), you can now select a [region](/secret-manager/concepts/#region) to display secrets and folders inside this region. Whenever you create a secret, you no longer need to specify the region, as it will be created in the region you are currently working on. -Find out more about Secret Manager in our [dedicated documentation](/identity-and-access-management/secret-manager/quickstart/). +Find out more about Secret Manager in our [dedicated documentation](/secret-manager/quickstart/). diff --git a/changelog/november2023/2023-11-27-iam-added-iam-audit-logs.mdx b/changelog/november2023/2023-11-27-iam-added-iam-audit-logs.mdx index 66f276f753..fe0bc8843b 100644 --- a/changelog/november2023/2023-11-27-iam-added-iam-audit-logs.mdx +++ b/changelog/november2023/2023-11-27-iam-added-iam-audit-logs.mdx @@ -13,5 +13,5 @@ Audit logs about **IAM resources such as applications, users, API keys, groups a You can check who created, updated or deleted an IAM resource in the **dedicated Logs tab on Console, or using the Scaleway CLI**. -For more information, refer to the [IAM logs documentation](/identity-and-access-management/iam/how-to/view-logs/). +For more information, refer to the [IAM logs documentation](/iam/how-to/view-logs/). diff --git a/changelog/november2024/2024-11-05-containers-added-serverless-network-metrics.mdx b/changelog/november2024/2024-11-05-containers-added-serverless-network-metrics.mdx index 4b0684b1db..8e2d7e27ed 100644 --- a/changelog/november2024/2024-11-05-containers-added-serverless-network-metrics.mdx +++ b/changelog/november2024/2024-11-05-containers-added-serverless-network-metrics.mdx @@ -9,6 +9,6 @@ category: serverless product: containers --- -In the Serverless Containers metrics panel, we added access to network information on received and transmitted data. Refer to the [dedicated documentation](/serverless/containers/how-to/monitor-container/) for more information on how to monitor a container. +In the Serverless Containers metrics panel, we added access to network information on received and transmitted data. Refer to the [dedicated documentation](/serverless-containers/how-to/monitor-container/) for more information on how to monitor a container. diff --git a/changelog/november2024/2024-11-05-functions-added-serverless-network-metrics.mdx b/changelog/november2024/2024-11-05-functions-added-serverless-network-metrics.mdx index 39dd680c6b..b2f0c638ae 100644 --- a/changelog/november2024/2024-11-05-functions-added-serverless-network-metrics.mdx +++ b/changelog/november2024/2024-11-05-functions-added-serverless-network-metrics.mdx @@ -9,6 +9,6 @@ category: serverless product: functions --- -In the metrics panel for Serverless Functions, we added access to network information on received and transmitted data. Refer to the [dedicated documentation](/serverless/functions/how-to/monitor-function/) for more information on how to monitor a function. +In the metrics panel for Serverless Functions, we added access to network information on received and transmitted data. Refer to the [dedicated documentation](/serverless-functions/how-to/monitor-function/) for more information on how to monitor a function. diff --git a/changelog/november2024/2024-11-05-generative-apis-added-generative-apis-now-available-in-.mdx b/changelog/november2024/2024-11-05-generative-apis-added-generative-apis-now-available-in-.mdx index 522bfcdd2b..275cf4f770 100644 --- a/changelog/november2024/2024-11-05-generative-apis-added-generative-apis-now-available-in-.mdx +++ b/changelog/november2024/2024-11-05-generative-apis-added-generative-apis-now-available-in-.mdx @@ -10,7 +10,7 @@ product: generative-apis --- Generative APIs let you access popular AI models via API. This new service is 100% hosted in Europe, providing low latency and full data privacy for AI-powered applications. -[Get started with Generative APIs](https://www.scaleway.com/en/docs/ai-data/generative-apis/quickstart/) +[Get started with Generative APIs](https://www.scaleway.com/en/docs/generative-apis/quickstart/) diff --git a/changelog/november2024/2024-11-05-jobs-added-serverless-jobs-integrates-secret-manager.mdx b/changelog/november2024/2024-11-05-jobs-added-serverless-jobs-integrates-secret-manager.mdx index f31d4658d8..3b77219f5b 100644 --- a/changelog/november2024/2024-11-05-jobs-added-serverless-jobs-integrates-secret-manager.mdx +++ b/changelog/november2024/2024-11-05-jobs-added-serverless-jobs-integrates-secret-manager.mdx @@ -11,4 +11,4 @@ product: jobs Serverless Jobs is now natively integrated with Secret Manager. -This allows for seamless retrieval of your sensitive data like API keys, database credentials. This integration reduces complexity while enhancing security by keeping your secrets out of your codebase. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information. +This allows for seamless retrieval of your sensitive data like API keys, database credentials. This integration reduces complexity while enhancing security by keeping your secrets out of your codebase. Refer to the [dedicated documentation](/serverless-jobs/how-to/reference-secret-in-job/) for more information. diff --git a/changelog/november2024/2024-11-05-transactional-email-changed-webhook-event-update-to-ema.mdx b/changelog/november2024/2024-11-05-transactional-email-changed-webhook-event-update-to-ema.mdx index fbe1235d9e..7395e363a4 100644 --- a/changelog/november2024/2024-11-05-transactional-email-changed-webhook-event-update-to-ema.mdx +++ b/changelog/november2024/2024-11-05-transactional-email-changed-webhook-event-update-to-ema.mdx @@ -9,5 +9,5 @@ category: managed-services product: transactional-email --- -The `email_error` field has been replaced by two new fields: `response_code` and `response_message`. This change allows for more precise error identification and improved tracking of response details. See the [documentation](/managed-services/transactional-email/api-cli/webhook-events-payloads/) for full details. +The `email_error` field has been replaced by two new fields: `response_code` and `response_message`. This change allows for more precise error identification and improved tracking of response details. See the [documentation](/transactional-email/api-cli/webhook-events-payloads/) for full details. diff --git a/changelog/november2024/2024-11-06-object-storage-added-sse-c-encryption-is-now-in-ga-for-.mdx b/changelog/november2024/2024-11-06-object-storage-added-sse-c-encryption-is-now-in-ga-for-.mdx index d0bee41b5a..4b4333f575 100644 --- a/changelog/november2024/2024-11-06-object-storage-added-sse-c-encryption-is-now-in-ga-for-.mdx +++ b/changelog/november2024/2024-11-06-object-storage-added-sse-c-encryption-is-now-in-ga-for-.mdx @@ -10,5 +10,5 @@ product: object-storage --- Server-Side Encryption with Customer-Provided Keys (SSE-C) is now available across all Scaleway regions for new and existing buckets. SSE-C enhances data protection for sensitive or private data stored in Object Storage, allowing to easily encrypt data during upload for added security, while giving you full control over your encryption keys. -For more information [read our dedicated documentation to get started with SSE-C on Object Storage](/storage/object/api-cli/enable-sse-c/). +For more information [read our dedicated documentation to get started with SSE-C on Object Storage](/object-storage/api-cli/enable-sse-c/). diff --git a/changelog/november2024/2024-11-26-containers-added-dns-query-rate-limiting-update.mdx b/changelog/november2024/2024-11-26-containers-added-dns-query-rate-limiting-update.mdx index ddd286cdeb..acd5ba4485 100644 --- a/changelog/november2024/2024-11-26-containers-added-dns-query-rate-limiting-update.mdx +++ b/changelog/november2024/2024-11-26-containers-added-dns-query-rate-limiting-update.mdx @@ -13,5 +13,5 @@ To ensure platform stability and performance, we have implemented a rate limit o This rate limit **only applies** to queries that require a full DNS resolution, and is enforced independently for each Container instance. This rate limit is set at a level that is well above typical usage, so most users should not be impacted. If you do encounter any issues, [reach out to our support team](https://console.scaleway.com/support/tickets/create) for assistance. -Refer to the [dedicated documentation](/serverless/containers/reference-content/dns-query-rate-limit/) for more information on DNS query rate limiting. +Refer to the [dedicated documentation](/serverless-containers/reference-content/dns-query-rate-limit/) for more information on DNS query rate limiting. diff --git a/changelog/november2024/2024-11-26-functions-added-dns-query-rate-limiting-update.mdx b/changelog/november2024/2024-11-26-functions-added-dns-query-rate-limiting-update.mdx index 3efb2eb3d8..f10d494b24 100644 --- a/changelog/november2024/2024-11-26-functions-added-dns-query-rate-limiting-update.mdx +++ b/changelog/november2024/2024-11-26-functions-added-dns-query-rate-limiting-update.mdx @@ -13,4 +13,4 @@ To ensure platform stability and performance, we have implemented a rate limit o This rate limit **only applies** to queries that require a full DNS resolution, and is enforced independently for each Function instance. This rate limit is set at a level that is well above typical usage, so most users should not be impacted. If you encounter any issues, [reach out to our support team](https://console.scaleway.com/support/tickets/create) for assistance. -Refer to the [dedicated documentation](/serverless/functions/reference-content/dns-query-rate-limit/) for more information on DNS query rate limiting. +Refer to the [dedicated documentation](/serverless-functions/reference-content/dns-query-rate-limit/) for more information on DNS query rate limiting. diff --git a/changelog/november2024/2024-11-28-managed-inference-added-new-models-support-nemotron-and.mdx b/changelog/november2024/2024-11-28-managed-inference-added-new-models-support-nemotron-and.mdx index e5767177de..6d1aeaa481 100644 --- a/changelog/november2024/2024-11-28-managed-inference-added-new-models-support-nemotron-and.mdx +++ b/changelog/november2024/2024-11-28-managed-inference-added-new-models-support-nemotron-and.mdx @@ -9,6 +9,6 @@ category: ai-data product: managed-inference --- -[Llama 3.1 Nemotron 70B](/ai-data/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct/) and [Molmo 72B](/ai-data/managed-inference/reference-content/molmo-72b-0924) are available for deployment on Managed Inference. +[Llama 3.1 Nemotron 70B](/managed-inference/reference-content/llama-3.1-nemotron-70b-instruct/) and [Molmo 72B](/managed-inference/reference-content/molmo-72b-0924) are available for deployment on Managed Inference. Nemotron improves human-like responses in complex tasks, while Molmo provides increased accuracy on multimodal inputs (text and images). diff --git a/changelog/november2024/2024-11-28-secret-manager-added-audit-trail-is-in-public-beta-with.mdx b/changelog/november2024/2024-11-28-secret-manager-added-audit-trail-is-in-public-beta-with.mdx index 560f67f429..cc6b744a91 100644 --- a/changelog/november2024/2024-11-28-secret-manager-added-audit-trail-is-in-public-beta-with.mdx +++ b/changelog/november2024/2024-11-28-secret-manager-added-audit-trail-is-in-public-beta-with.mdx @@ -9,5 +9,5 @@ category: security-identity product: secret-manager --- -Audit Trail is available in Beta and integrated with Secret Manager. You can see and filter [events](/identity-and-access-management/audit-trail/concepts/#event) to understand any activity related to your secrets and versions, encompassing actions by users, applications, or Scaleway. +Audit Trail is available in Beta and integrated with Secret Manager. You can see and filter [events](/audit-trail/concepts/#event) to understand any activity related to your secrets and versions, encompassing actions by users, applications, or Scaleway. diff --git a/changelog/november2024/2024-11-29-kubernetes-added-kubernetes-version-131-is-now-availabl.mdx b/changelog/november2024/2024-11-29-kubernetes-added-kubernetes-version-131-is-now-availabl.mdx index 6634a6d5fe..6a6c414e46 100644 --- a/changelog/november2024/2024-11-29-kubernetes-added-kubernetes-version-131-is-now-availabl.mdx +++ b/changelog/november2024/2024-11-29-kubernetes-added-kubernetes-version-131-is-now-availabl.mdx @@ -12,5 +12,5 @@ product: kubernetes Scaleway managed Kubernetes products will support the latest minor version `1.31` Elli until February 2026. In addition to patch versions `1.31.0`, `1.31.1`, `1.31.2`, `1.31.3`, releases `1.30.1`, `1.30.2`, `1.30.3`, `1.29.2` to `1.29.6`, `1.28.8` to `1.28.11`, `1.27.11` to `1.27.15`, and `1.26.14` to `1.26.15` are also available. -Read our [version support policy](/containers/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. +Read our [version support policy](/kubernetes/reference-content/version-support-policy/) for more details on the 14-month support timeline. diff --git a/changelog/observability/october2022/2022-11-03-cockpit.mdx b/changelog/observability/october2022/2022-11-03-cockpit.mdx index cc8320d348..0339b8861c 100644 --- a/changelog/observability/october2022/2022-11-03-cockpit.mdx +++ b/changelog/observability/october2022/2022-11-03-cockpit.mdx @@ -9,4 +9,4 @@ category: observability product: cockpit --- -Discover [Scaleway Observability](/observability/cockpit/quickstart/), a fully managed solution for monitoring and troubleshooting your entire infrastructure in one place! \ No newline at end of file +Discover [Scaleway Observability](/cockpit/quickstart/), a fully managed solution for monitoring and troubleshooting your entire infrastructure in one place! \ No newline at end of file diff --git a/changelog/october2023/2023-10-03-iot-changed-new-iot-platform-server.mdx b/changelog/october2023/2023-10-03-iot-changed-new-iot-platform-server.mdx index bc48ce88d9..5e98d15260 100644 --- a/changelog/october2023/2023-10-03-iot-changed-new-iot-platform-server.mdx +++ b/changelog/october2023/2023-10-03-iot-changed-new-iot-platform-server.mdx @@ -11,5 +11,5 @@ product: iot The Certificate Authority used by all MQTT TLS connections to IoT Hubs has been updated. -As described in our [Certificate Authority update documentation](/managed-services/iot-hub/reference-content/certificate/), the `migration.iot.fr-par.scw.cloud` endpoint is no longer valid. +As described in our [Certificate Authority update documentation](/iot-hub/reference-content/certificate/), the `migration.iot.fr-par.scw.cloud` endpoint is no longer valid. diff --git a/changelog/october2023/2023-10-18-kubernetes-added-disable-public-ips-of-your-node-pools-.mdx b/changelog/october2023/2023-10-18-kubernetes-added-disable-public-ips-of-your-node-pools-.mdx index b8e48966b4..c4d5f3c409 100644 --- a/changelog/october2023/2023-10-18-kubernetes-added-disable-public-ips-of-your-node-pools-.mdx +++ b/changelog/october2023/2023-10-18-kubernetes-added-disable-public-ips-of-your-node-pools-.mdx @@ -19,5 +19,5 @@ The option is immutable after pool creation. Both isolation modes can be used in The feature is now available in Scaleway console (new node pools), Scaleway API, CLI and [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/k8s_pool#public_ip_disabled) (public_ip_disabled) -Find more details on our [reference documentation](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/). +Find more details on our [reference documentation](https://www.scaleway.com/en/docs/kubernetes/reference-content/secure-cluster-with-private-network/). diff --git a/changelog/october2023/2023-10-18-kubernetes-deprecated-kapsule-clusters-with-only-public.mdx b/changelog/october2023/2023-10-18-kubernetes-deprecated-kapsule-clusters-with-only-public.mdx index 8d93e46178..82ba2a8e85 100644 --- a/changelog/october2023/2023-10-18-kubernetes-deprecated-kapsule-clusters-with-only-public.mdx +++ b/changelog/october2023/2023-10-18-kubernetes-deprecated-kapsule-clusters-with-only-public.mdx @@ -17,5 +17,5 @@ Starting this deprecation cycle, existing Kapsule clusters must be connected to The default worker nodes' isolation configuration will keep public IPs for nodes to access the Internet, and add private endpoints for resources to communicate securely. Security groups aren't overridden at migration and RR wildcard DNS still point to public IPs. -More information on the migration steps is provided in [our reference documentation](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/secure-cluster-with-private-network/). +More information on the migration steps is provided in [our reference documentation](https://www.scaleway.com/en/docs/kubernetes/reference-content/secure-cluster-with-private-network/). diff --git a/changelog/october2023/2023-10-20-functions-added-trigger-private-functions-from-messagin.mdx b/changelog/october2023/2023-10-20-functions-added-trigger-private-functions-from-messagin.mdx index 2131926f13..7648590733 100644 --- a/changelog/october2023/2023-10-20-functions-added-trigger-private-functions-from-messagin.mdx +++ b/changelog/october2023/2023-10-20-functions-added-trigger-private-functions-from-messagin.mdx @@ -9,7 +9,7 @@ category: serverless product: functions --- -It is now possible to create [SQS and NATS triggers](https://www.scaleway.com/en/docs/serverless/functions/how-to/add-trigger-to-a-function/) on private functions. +It is now possible to create [SQS and NATS triggers](https://www.scaleway.com/en/docs/serverless-functions/how-to/add-trigger-to-a-function/) on private functions. For now, changing the privacy of a function from public to private will require you to delete and recreate the existing triggers. diff --git a/changelog/october2023/2023-10-24-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx b/changelog/october2023/2023-10-24-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx index 4a1df3364a..84924b37f3 100644 --- a/changelog/october2023/2023-10-24-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx +++ b/changelog/october2023/2023-10-24-messaging-and-queuing-changed-messaging-and-queuing-is-.mdx @@ -17,5 +17,5 @@ The Messaging and Queuing features are available via the Scaleway console, the C Your existing resources will need to be migrated, as communicated to all beta users. -Find out about Messaging and Queuing in our [dedicated documentation](/serverless/messaging/quickstart/). If you have any questions, reach out to the team on the #messaging-queuing community Slack channel. +Find out about Messaging and Queuing in our [dedicated documentation](/messaging/quickstart/). If you have any questions, reach out to the team on the #messaging-queuing community Slack channel. diff --git a/changelog/october2023/2023-10-25-kubernetes-added-support-for-kubernetes-kapsule-multi-a.mdx b/changelog/october2023/2023-10-25-kubernetes-added-support-for-kubernetes-kapsule-multi-a.mdx index 9a1695f3bd..80dc94d908 100644 --- a/changelog/october2023/2023-10-25-kubernetes-added-support-for-kubernetes-kapsule-multi-a.mdx +++ b/changelog/october2023/2023-10-25-kubernetes-added-support-for-kubernetes-kapsule-multi-a.mdx @@ -13,7 +13,7 @@ Enhance your cluster resilience by adding pools in multiple Availability Zones ( Scaleway's Console, API, CLI, and Terraform now all support multi-AZ Kubernetes Kapsule clusters. -Instructions are available in our [reference documentation](https://www.scaleway.com/en/docs/containers/kubernetes/reference-content/multi-az-clusters/). +Instructions are available in our [reference documentation](https://www.scaleway.com/en/docs/kubernetes/reference-content/multi-az-clusters/). Step-by-step guidance also provided in our [complete Terraform tutorial](https://www.scaleway.com/en/docs/tutorials/k8s-kapsule-multi-az/). Pre-requisite: Kubernetes Kapsule cluster connection to a Private Network. diff --git a/changelog/october2023/2023-10-26-kubernetes-removed-kubernetes-122-is-no-longer-supporte.mdx b/changelog/october2023/2023-10-26-kubernetes-removed-kubernetes-122-is-no-longer-supporte.mdx index 89d41bd361..9475e4c0c0 100644 --- a/changelog/october2023/2023-10-26-kubernetes-removed-kubernetes-122-is-no-longer-supporte.mdx +++ b/changelog/october2023/2023-10-26-kubernetes-removed-kubernetes-122-is-no-longer-supporte.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Clusters using the Kubernetes 1.22 version will be automatically upgraded to the Kubernetes 1.23 version on October 16th, 2023. Find more details in [our version support policy](/containers/kubernetes/reference-content/version-support-policy/#scaleway-kubernetes-kapsule-and-kosmos-release-calendar). +Clusters using the Kubernetes 1.22 version will be automatically upgraded to the Kubernetes 1.23 version on October 16th, 2023. Find more details in [our version support policy](/kubernetes/reference-content/version-support-policy/#scaleway-kubernetes-kapsule-and-kosmos-release-calendar). diff --git a/changelog/october2023/2023-10-30-console-added-cli-console.mdx b/changelog/october2023/2023-10-30-console-added-cli-console.mdx index fbd5ff2353..2ae02f740a 100644 --- a/changelog/october2023/2023-10-30-console-added-cli-console.mdx +++ b/changelog/october2023/2023-10-30-console-added-cli-console.mdx @@ -11,5 +11,5 @@ product: console New feature: Our integrated console CLI works with WebAssembly and uses your console credentials to offer you a seamless CLI experience without installing anything on your machine. Benefit from enhanced output formatting and discover a new way to manage your Scaleway resources. You can also install it natively on your local machine, as we support Windows, macOS, and Linux. -See our [product documentation](/developer-tools/scaleway-cli/quickstart/) for more information. +See our [product documentation](/scaleway-cli/quickstart/) for more information. diff --git a/changelog/october2024/2024-10-08-messaging-and-queuing-added-queues-subscription-availab.mdx b/changelog/october2024/2024-10-08-messaging-and-queuing-added-queues-subscription-availab.mdx index 48ef75be16..563182ac3c 100644 --- a/changelog/october2024/2024-10-08-messaging-and-queuing-added-queues-subscription-availab.mdx +++ b/changelog/october2024/2024-10-08-messaging-and-queuing-added-queues-subscription-availab.mdx @@ -11,5 +11,5 @@ product: messaging-and-queuing You can now subscribe directly to queues from your topics, from the [Scaleway console](https://console.scaleway.com), and via the [API](https://www.scaleway.com/en/developers/api/) for standard and FIFO topics. -For more information, refer to the [Subscriptions documentation](https://www.scaleway.com/en/docs/serverless/messaging/how-to/create-manage-subscriptions/). +For more information, refer to the [Subscriptions documentation](https://www.scaleway.com/en/docs/messaging/how-to/create-manage-subscriptions/). diff --git a/changelog/october2024/2024-10-14-sql-databases-added-extension-support.mdx b/changelog/october2024/2024-10-14-sql-databases-added-extension-support.mdx index 4f746bb5d3..97982f84d4 100644 --- a/changelog/october2024/2024-10-14-sql-databases-added-extension-support.mdx +++ b/changelog/october2024/2024-10-14-sql-databases-added-extension-support.mdx @@ -9,5 +9,5 @@ category: serverless product: sql-databases --- -Serverless SQL Databases now supports PostgreSQL extensions. Supported extensions include pgvector, PostGIS, timescaledb and [many others](https://www.scaleway.com/en/docs/serverless/sql-databases/reference-content/supported-postgresql-extensions/#supported-extensions). They can be activated using the [CREATE EXTENSION](https://www.scaleway.com/en/docs/serverless/sql-databases/reference-content/supported-postgresql-extensions/) command. +Serverless SQL Databases now supports PostgreSQL extensions. Supported extensions include pgvector, PostGIS, timescaledb and [many others](https://www.scaleway.com/en/docs/serverless-sql-databases/reference-content/supported-postgresql-extensions/#supported-extensions). They can be activated using the [CREATE EXTENSION](https://www.scaleway.com/en/docs/serverless-sql-databases/reference-content/supported-postgresql-extensions/) command. diff --git a/changelog/october2024/2024-10-14-transactional-email-added-autoconfig-is-now-available.mdx b/changelog/october2024/2024-10-14-transactional-email-added-autoconfig-is-now-available.mdx index 919fa17f7c..4b95315b10 100644 --- a/changelog/october2024/2024-10-14-transactional-email-added-autoconfig-is-now-available.mdx +++ b/changelog/october2024/2024-10-14-transactional-email-added-autoconfig-is-now-available.mdx @@ -10,5 +10,5 @@ product: transactional-email --- Simplify the configuration of your DNS records for Scaleway Domains to accelerate your email sending with TEM. With Autoconfig, configure your DNS in just one click for quick integration. -Learn more in our [dedicated documentation](https://www.scaleway.com/en/docs/managed-services/transactional-email/how-to/autoconfigure-domain/)! +Learn more in our [dedicated documentation](https://www.scaleway.com/en/docs/transactional-email/how-to/autoconfigure-domain/)! diff --git a/changelog/october2024/2024-10-17-transactional-email-changed-increase-in-minimum-quotas.mdx b/changelog/october2024/2024-10-17-transactional-email-changed-increase-in-minimum-quotas.mdx index 5454431049..8f98ab44c0 100644 --- a/changelog/october2024/2024-10-17-transactional-email-changed-increase-in-minimum-quotas.mdx +++ b/changelog/october2024/2024-10-17-transactional-email-changed-increase-in-minimum-quotas.mdx @@ -9,6 +9,6 @@ category: managed-services product: transactional-email --- -We have updated the default email sending quotas to better align with your needs. The new limits are available on the [capabilities and limits](/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/) page. These changes offer greater flexibility and optimization capabilities for managing your email volumes. +We have updated the default email sending quotas to better align with your needs. The new limits are available on the [capabilities and limits](/transactional-email/reference-content/tem-capabilities-and-limits/) page. These changes offer greater flexibility and optimization capabilities for managing your email volumes. diff --git a/changelog/october2024/2024-10-23-elastic-metal-added-disk-partitioning-configuration-now.mdx b/changelog/october2024/2024-10-23-elastic-metal-added-disk-partitioning-configuration-now.mdx index 0147009e42..3902877bb5 100644 --- a/changelog/october2024/2024-10-23-elastic-metal-added-disk-partitioning-configuration-now.mdx +++ b/changelog/october2024/2024-10-23-elastic-metal-added-disk-partitioning-configuration-now.mdx @@ -10,4 +10,4 @@ product: elastic-metal --- You can now partition the disk capacity of your server as needed during server setup by directly editing the JSON file in the Scaleway console. Eligible servers are marked with the green 'NEW' badge. -Refer to the [dedicated page](/bare-metal/elastic-metal/how-to/configure-disk-partitions/) for more details on custom partitioning. +Refer to the [dedicated page](/elastic-metal/how-to/configure-disk-partitions/) for more details on custom partitioning. diff --git a/changelog/october2024/2024-10-25-managed-inference-added-support-for-function-calling.mdx b/changelog/october2024/2024-10-25-managed-inference-added-support-for-function-calling.mdx index 7de0a9ef36..1cccb84321 100644 --- a/changelog/october2024/2024-10-25-managed-inference-added-support-for-function-calling.mdx +++ b/changelog/october2024/2024-10-25-managed-inference-added-support-for-function-calling.mdx @@ -13,5 +13,5 @@ Function calling allows a large language model (LLM) to interact with external t Parameters `tools` and `tool_choice` of our OpenAI-compatible chat API are now accepted for models with this capacity. -Read [our dedicated documentation](https://www.scaleway.com/en/docs/ai-data/managed-inference/reference-content/function-calling-support/) and [tutorial to get started](https://www.scaleway.com/en/docs/tutorials/building-ai-application-function-calling)! +Read [our dedicated documentation](https://www.scaleway.com/en/docs/managed-inference/reference-content/function-calling-support/) and [tutorial to get started](https://www.scaleway.com/en/docs/tutorials/building-ai-application-function-calling)! diff --git a/changelog/september2023/2023-09-01-kubernetes-added-kubernetes-version-1.28-is.mdx b/changelog/september2023/2023-09-01-kubernetes-added-kubernetes-version-1.28-is.mdx index 0b46740936..4543097ceb 100644 --- a/changelog/september2023/2023-09-01-kubernetes-added-kubernetes-version-1.28-is.mdx +++ b/changelog/september2023/2023-09-01-kubernetes-added-kubernetes-version-1.28-is.mdx @@ -13,5 +13,5 @@ Scaleway managed Kubernetes products now support the latest minor version 1.28 Patch versions 1.27.3, 1.27.4, 1.26.6, 1.26.7, 1.25.11, 1.25.12, 1.24.15, 1.24.16 have also been released. -Read [our version support policy](/containers/kubernetes/reference-content/version-support-policy/) for more information. +Read [our version support policy](/kubernetes/reference-content/version-support-policy/) for more information. diff --git a/changelog/september2023/2023-09-06-kubernetes-added-dedicated-control-plane-offers.mdx b/changelog/september2023/2023-09-06-kubernetes-added-dedicated-control-plane-offers.mdx index 3cc4e22553..4472f36a56 100644 --- a/changelog/september2023/2023-09-06-kubernetes-added-dedicated-control-plane-offers.mdx +++ b/changelog/september2023/2023-09-06-kubernetes-added-dedicated-control-plane-offers.mdx @@ -11,5 +11,5 @@ product: kubernetes Dedicated control planes are now generally available for Kapsule and Kosmos! Boost your Kubernetes performance thanks to our dedicated control planes, available with 4, 8 or 16GB RAM. An exclusive resource to orchestrate mission-critical, at scale and production workloads, highly available with a 99.5% uptime SLA! -Dedicated control planes are available in the [Scaleway console](https://console.scaleway.com/), the CLI, and Terraform. Refer to [our documentation](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. +Dedicated control planes are available in the [Scaleway console](https://console.scaleway.com/), the CLI, and Terraform. Refer to [our documentation](/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. diff --git a/changelog/september2023/2023-09-07-kubernetes-changed-kapsule-and-kosmos-clusters.mdx b/changelog/september2023/2023-09-07-kubernetes-changed-kapsule-and-kosmos-clusters.mdx index 63d3ab9aba..63f9b09f97 100644 --- a/changelog/september2023/2023-09-07-kubernetes-changed-kapsule-and-kosmos-clusters.mdx +++ b/changelog/september2023/2023-09-07-kubernetes-changed-kapsule-and-kosmos-clusters.mdx @@ -9,5 +9,5 @@ category: containers product: kubernetes --- -Starting September 1st 2023, Kapsule and Kosmos clusters are limited to 150 nodes maximum on first offer. However, to go beyond 150 nodes, Scaleway offers a range of dedicated control planes to cater to a wide range of use-cases. Refer to our [Kubernetes control plane offers overview](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. +Starting September 1st 2023, Kapsule and Kosmos clusters are limited to 150 nodes maximum on first offer. However, to go beyond 150 nodes, Scaleway offers a range of dedicated control planes to cater to a wide range of use-cases. Refer to our [Kubernetes control plane offers overview](/kubernetes/reference-content/kubernetes-control-plane-offers/) for more information. diff --git a/changelog/september2023/2023-09-18-transactional-email-added-the-scaleway-blackhole-mx.mdx b/changelog/september2023/2023-09-18-transactional-email-added-the-scaleway-blackhole-mx.mdx index 966e2fabe9..77439c164e 100644 --- a/changelog/september2023/2023-09-18-transactional-email-added-the-scaleway-blackhole-mx.mdx +++ b/changelog/september2023/2023-09-18-transactional-email-added-the-scaleway-blackhole-mx.mdx @@ -9,5 +9,5 @@ category: managed-services product: transactional-email --- -Scaleway has implemented a blackhole MX server you can use with Transactional Email, to prevent your emails from being rejected by recipient servers. This happens when you have no MX record or when you have configured a null MX record. [Find out how to configure Scaleway's MX.](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) +Scaleway has implemented a blackhole MX server you can use with Transactional Email, to prevent your emails from being rejected by recipient servers. This happens when you have no MX record or when you have configured a null MX record. [Find out how to configure Scaleway's MX.](/transactional-email/how-to/add-mx-record-to-your-domain/) diff --git a/changelog/september2023/2023-09-19-load-balancers-added-private-load-balancers-now.mdx b/changelog/september2023/2023-09-19-load-balancers-added-private-load-balancers-now.mdx index 2a0fad4913..e69f312a0e 100644 --- a/changelog/september2023/2023-09-19-load-balancers-added-private-load-balancers-now.mdx +++ b/changelog/september2023/2023-09-19-load-balancers-added-private-load-balancers-now.mdx @@ -9,5 +9,5 @@ category: network product: load-balancers --- -When creating a Load Balancer you can now choose whether you want it to be public (connected to the internet with a public IP address) or private (fully isolated from the internet and with no public IP address). Private Load Balancers let you balance internal traffic or make your internal services highly available without being exposed to the internet. Make sure you attach your private Load Balancer to a Private Network so your internal clients can access it. Read more about private Load Balancers in our [documentation](https://www.scaleway.com/en/docs/network/load-balancer/concepts/#private-load-balancer). +When creating a Load Balancer you can now choose whether you want it to be public (connected to the internet with a public IP address) or private (fully isolated from the internet and with no public IP address). Private Load Balancers let you balance internal traffic or make your internal services highly available without being exposed to the internet. Make sure you attach your private Load Balancer to a Private Network so your internal clients can access it. Read more about private Load Balancers in our [documentation](https://www.scaleway.com/en/docs/load-balancer/concepts/#private-load-balancer). diff --git a/changelog/september2023/2023-09-19-load-balancers-deprecated-static-attachment-of-load.mdx b/changelog/september2023/2023-09-19-load-balancers-deprecated-static-attachment-of-load.mdx index e2ecca3978..064fa4cab1 100644 --- a/changelog/september2023/2023-09-19-load-balancers-deprecated-static-attachment-of-load.mdx +++ b/changelog/september2023/2023-09-19-load-balancers-deprecated-static-attachment-of-load.mdx @@ -9,7 +9,7 @@ category: network product: load-balancers --- -With the release of [VPCs](/network/vpc/concepts/#vpc) and their managed [DHCP](/network/vpc/concepts/#dhcp) feature, we are reworking the way resources are attached to a Private Network, in order to offer a bullet-proof experience. To this end, the **static attachment mode** that allowed for manual configuration of an IP address when attaching a Load Balancer to a Private Network from the Scaleway console, is no longer available. This mode is not in line with the all-new Private Network management engine Scaleway is working on, and could result in non working configurations. In removing static attachment mode, we are encouraging adoption of best practices that will future-proof your architectures. Simultaneously, we are also working on a set of new features to manage your IP addressing space more granularly. +With the release of [VPCs](/vpc/concepts/#vpc) and their managed [DHCP](/vpc/concepts/#dhcp) feature, we are reworking the way resources are attached to a Private Network, in order to offer a bullet-proof experience. To this end, the **static attachment mode** that allowed for manual configuration of an IP address when attaching a Load Balancer to a Private Network from the Scaleway console, is no longer available. This mode is not in line with the all-new Private Network management engine Scaleway is working on, and could result in non working configurations. In removing static attachment mode, we are encouraging adoption of best practices that will future-proof your architectures. Simultaneously, we are also working on a set of new features to manage your IP addressing space more granularly. While the feature will no longer be available from the Scaleway console, it is still available in the API, though entering a deprecation cycle. diff --git a/changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx b/changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx index 7fe4bd10d7..75703fb489 100644 --- a/changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx +++ b/changelog/september2023/2023-09-19-postgresql-and-mysql-added-cross-availability-zone-read.mdx @@ -11,5 +11,5 @@ product: postgresql-and-mysql The Cross-AZ Read Replica feature ensures your data is replicated in a dedicated read-only node, which is located in another AZ within the same Region as your main node. - For more information, refer to the [How to create Read Replicas](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/) documentation page. + For more information, refer to the [How to create Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) documentation page. diff --git a/changelog/september2023/2023-09-21-messaging-and-queuing-added-messaging-and-queuing-metrics.mdx b/changelog/september2023/2023-09-21-messaging-and-queuing-added-messaging-and-queuing-metrics.mdx index 149d79e5e2..10664d49de 100644 --- a/changelog/september2023/2023-09-21-messaging-and-queuing-added-messaging-and-queuing-metrics.mdx +++ b/changelog/september2023/2023-09-21-messaging-and-queuing-added-messaging-and-queuing-metrics.mdx @@ -9,5 +9,5 @@ category: serverless product: messaging-and-queuing --- - Cockpit integration is available for SQS, NATS & SNS. Refer to our [product documentation](/serverless/messaging/how-to/monitor-mnq-cockpit/) to find out how to monitor your Messaging and queuing metrics. + Cockpit integration is available for SQS, NATS & SNS. Refer to our [product documentation](/messaging/how-to/monitor-mnq-cockpit/) to find out how to monitor your Messaging and queuing metrics. diff --git a/changelog/september2023/2023-09-27-functions-added-you-can-now-test.mdx b/changelog/september2023/2023-09-27-functions-added-you-can-now-test.mdx index 334718df04..9dfa356af3 100644 --- a/changelog/september2023/2023-09-27-functions-added-you-can-now-test.mdx +++ b/changelog/september2023/2023-09-27-functions-added-you-can-now-test.mdx @@ -9,5 +9,5 @@ category: serverless product: functions --- -The new function Test feature allows you to run your code directly from the Scaleway console using a selection of methods, to make sure it behaves as expected. For more information, refer to the [dedicated documentation](/serverless/functions/how-to/test-a-function/). +The new function Test feature allows you to run your code directly from the Scaleway console using a selection of methods, to make sure it behaves as expected. For more information, refer to the [dedicated documentation](/serverless-functions/how-to/test-a-function/). diff --git a/changelog/september2023/2023-09-27-functions-changed-new-function-creation-workflow.mdx b/changelog/september2023/2023-09-27-functions-changed-new-function-creation-workflow.mdx index 7e29bb6e2f..c7e29dd3fd 100644 --- a/changelog/september2023/2023-09-27-functions-changed-new-function-creation-workflow.mdx +++ b/changelog/september2023/2023-09-27-functions-changed-new-function-creation-workflow.mdx @@ -9,5 +9,5 @@ category: serverless product: functions --- -The new function creation workflow allows you to easily create a namespace and function in 2 clicks. For more information, refer to the documentation on [how to create a function](/serverless/functions/quickstart/#how-to-create-a-function). +The new function creation workflow allows you to easily create a namespace and function in 2 clicks. For more information, refer to the documentation on [how to create a function](/serverless-functions/quickstart/#how-to-create-a-function). diff --git a/changelog/september2024/2024-09-03-kubernetes-changed-new-size-limits-for-etcd-stores-in-k.mdx b/changelog/september2024/2024-09-03-kubernetes-changed-new-size-limits-for-etcd-stores-in-k.mdx index ee4e54a679..60e8d6856b 100644 --- a/changelog/september2024/2024-09-03-kubernetes-changed-new-size-limits-for-etcd-stores-in-k.mdx +++ b/changelog/september2024/2024-09-03-kubernetes-changed-new-size-limits-for-etcd-stores-in-k.mdx @@ -11,5 +11,5 @@ product: kubernetes To maintain optimal performance of your managed Scaleway Kubernetes clusters, etcd stores in control planes are now subject to size limits: 55 MB for mutualized control planes and 200 MB for dedicated control planes. -For more details, please refer to our [dedicated documentation](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). +For more details, please refer to our [dedicated documentation](/kubernetes/reference-content/kubernetes-control-plane-offers/). diff --git a/changelog/september2024/2024-09-05-managed-inference-added-model-library-expanded.mdx b/changelog/september2024/2024-09-05-managed-inference-added-model-library-expanded.mdx index a0cd661976..e146cc5210 100644 --- a/changelog/september2024/2024-09-05-managed-inference-added-model-library-expanded.mdx +++ b/changelog/september2024/2024-09-05-managed-inference-added-model-library-expanded.mdx @@ -9,7 +9,7 @@ category: ai-data product: managed-inference --- -[Meta Llama 3.1 8b](/ai-data/managed-inference/reference-content/llama-3.1-8b-instruct/), [Meta Llama 3.1 70b](/ai-data/managed-inference/reference-content/llama-3.1-70b-instruct/) and [Mistral Nemo](/ai-data/managed-inference/reference-content/mistral-nemo-instruct-2407/) are available for deployment on Managed Inference. +[Meta Llama 3.1 8b](/managed-inference/reference-content/llama-3.1-8b-instruct/), [Meta Llama 3.1 70b](/managed-inference/reference-content/llama-3.1-70b-instruct/) and [Mistral Nemo](/managed-inference/reference-content/mistral-nemo-instruct-2407/) are available for deployment on Managed Inference. Released July 2024, these models all support a very large context window of up to 128k tokens, particularly useful for RAG applications. diff --git a/changelog/september2024/2024-09-11-ipam-added-ipam-is-now-in-general-availability.mdx b/changelog/september2024/2024-09-11-ipam-added-ipam-is-now-in-general-availability.mdx index 5eed0cda55..eae19a86fd 100644 --- a/changelog/september2024/2024-09-11-ipam-added-ipam-is-now-in-general-availability.mdx +++ b/changelog/september2024/2024-09-11-ipam-added-ipam-is-now-in-general-availability.mdx @@ -9,5 +9,5 @@ category: network product: ipam --- -[IP Address Manager (IPAM)](/network/ipam/quickstart/) offers several different functionalities in the Scaleway console such as viewing, tagging and filtering private IP addresses. Users can also reserve a private IP on one of their Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network. +[IP Address Manager (IPAM)](/ipam/quickstart/) offers several different functionalities in the Scaleway console such as viewing, tagging and filtering private IP addresses. Users can also reserve a private IP on one of their Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network. diff --git a/changelog/september2024/2024-09-16-object-storage-added-lifecycle-rules-now-allow-to-abort.mdx b/changelog/september2024/2024-09-16-object-storage-added-lifecycle-rules-now-allow-to-abort.mdx index 2a926f8d1b..8c5aa8b151 100644 --- a/changelog/september2024/2024-09-16-object-storage-added-lifecycle-rules-now-allow-to-abort.mdx +++ b/changelog/september2024/2024-09-16-object-storage-added-lifecycle-rules-now-allow-to-abort.mdx @@ -9,4 +9,4 @@ category: storage product: object-storage --- -It is now possible to configure a lifecycle rule from the Scaleway console to automatically abort your incomplete multipart uploads after a chosen number of days. Learn [how to start configuring lifecycle rules](/storage/object/how-to/manage-lifecycle-rules/) from the console. +It is now possible to configure a lifecycle rule from the Scaleway console to automatically abort your incomplete multipart uploads after a chosen number of days. Learn [how to start configuring lifecycle rules](/object-storage/how-to/manage-lifecycle-rules/) from the console. diff --git a/changelog/september2024/2024-09-16-object-storage-added-uncomplete-multipart-uploads-are-n.mdx b/changelog/september2024/2024-09-16-object-storage-added-uncomplete-multipart-uploads-are-n.mdx index c329c55c52..bd2b436257 100644 --- a/changelog/september2024/2024-09-16-object-storage-added-uncomplete-multipart-uploads-are-n.mdx +++ b/changelog/september2024/2024-09-16-object-storage-added-uncomplete-multipart-uploads-are-n.mdx @@ -9,4 +9,4 @@ category: storage product: object-storage --- -It is now possible to list and abort incomplete multipart uploads from the Scaleway console. Follow the [dedicated documentation](/storage/object/how-to/abort-incomplete-mpu) to navigate to your incomplete multipart uploads. +It is now possible to list and abort incomplete multipart uploads from the Scaleway console. Follow the [dedicated documentation](/object-storage/how-to/abort-incomplete-mpu) to navigate to your incomplete multipart uploads. diff --git a/changelog/september2024/2024-09-18-managed-inference-added-json-mode-and-structured-output.mdx b/changelog/september2024/2024-09-18-managed-inference-added-json-mode-and-structured-output.mdx index a42a37997b..346a6b3c16 100644 --- a/changelog/september2024/2024-09-18-managed-inference-added-json-mode-and-structured-output.mdx +++ b/changelog/september2024/2024-09-18-managed-inference-added-json-mode-and-structured-output.mdx @@ -9,7 +9,7 @@ category: ai-data product: managed-inference --- -All AI models can now reliably generate JSON output when required. The [Chat Completions API](https://www.scaleway.com/en/docs/ai-data/managed-inference/reference-content/openai-compatibility/#supported-parameters) supports the `response_format` parameter, which can be set to either `json_object` or `json_schema`, following OpenAI's specifications exactly. +All AI models can now reliably generate JSON output when required. The [Chat Completions API](https://www.scaleway.com/en/docs/managed-inference/reference-content/openai-compatibility/#supported-parameters) supports the `response_format` parameter, which can be set to either `json_object` or `json_schema`, following OpenAI's specifications exactly. -Refer to [our documentation for code examples](https://www.scaleway.com/en/docs/ai-data/generative-apis/how-to/use-structured-outputs/), including usage with Pydantic models or manual schema definitions. +Refer to [our documentation for code examples](https://www.scaleway.com/en/docs/generative-apis/how-to/use-structured-outputs/), including usage with Pydantic models or manual schema definitions. diff --git a/changelog/september2024/2024-09-25-managed-inference-added-analyze-images-with-mistrals-vi.mdx b/changelog/september2024/2024-09-25-managed-inference-added-analyze-images-with-mistrals-vi.mdx index 8b59ff2767..7014b906d1 100644 --- a/changelog/september2024/2024-09-25-managed-inference-added-analyze-images-with-mistrals-vi.mdx +++ b/changelog/september2024/2024-09-25-managed-inference-added-analyze-images-with-mistrals-vi.mdx @@ -13,5 +13,5 @@ You can now deploy your own secure `Pixtral-12b-2409` model with Scaleway Manage With a privacy-focused, fully managed stack, this solution opens up new possibilities for applications that require both textual and visual understanding, knowing your images remain safe. -Read [our dedicated documentation](https://www.scaleway.com/en/docs/ai-data/managed-inference/reference-content/pixtral-12b-2409) to get started with Pixtral. +Read [our dedicated documentation](https://www.scaleway.com/en/docs/managed-inference/reference-content/pixtral-12b-2409) to get started with Pixtral. diff --git a/changelog/september2024/2024-09-25-transactional-email-added-webhooks-ga-release-track-and.mdx b/changelog/september2024/2024-09-25-transactional-email-added-webhooks-ga-release-track-and.mdx index f0e879dccf..1e8b457ce5 100644 --- a/changelog/september2024/2024-09-25-transactional-email-added-webhooks-ga-release-track-and.mdx +++ b/changelog/september2024/2024-09-25-transactional-email-added-webhooks-ga-release-track-and.mdx @@ -10,5 +10,5 @@ product: transactional-email --- Receive instant notifications on your email status (queued, delivered, dropped ...) and trigger automated actions in your integration. Simply set up your endpoint URLs and choose the events you want to track for quick and seamless reactions! -Refer to the [How to create webhooks](/managed-services/transactional-email/how-to/create-webhooks/) documentation page for more information. +Refer to the [How to create webhooks](/transactional-email/how-to/create-webhooks/) documentation page for more information. diff --git a/changelog/september2024/2024-09-26-object-storage-changed-increase-of-object-storage-defau.mdx b/changelog/september2024/2024-09-26-object-storage-changed-increase-of-object-storage-defau.mdx index 3b59fe9ac3..5ecfc4ceb1 100644 --- a/changelog/september2024/2024-09-26-object-storage-changed-increase-of-object-storage-defau.mdx +++ b/changelog/september2024/2024-09-26-object-storage-changed-increase-of-object-storage-defau.mdx @@ -11,5 +11,5 @@ product: object-storage The default rate limiting threshold has been significantly increased on all requests for all Regions to better support intensive workloads. -For users who still reach the limit (429 error code), the process for asking for a rate limit upgrade remains unchanged, through [opening a support ticket](/console/account/how-to/open-a-support-ticket/). +For users who still reach the limit (429 error code), the process for asking for a rate limit upgrade remains unchanged, through [opening a support ticket](/account/how-to/open-a-support-ticket/). diff --git a/changelog/september2024/2024-09-27-billing-added-discover-our-new-compute-savings-plan-off.mdx b/changelog/september2024/2024-09-27-billing-added-discover-our-new-compute-savings-plan-off.mdx index c367f02be3..5d248e5809 100644 --- a/changelog/september2024/2024-09-27-billing-added-discover-our-new-compute-savings-plan-off.mdx +++ b/changelog/september2024/2024-09-27-billing-added-discover-our-new-compute-savings-plan-off.mdx @@ -9,7 +9,7 @@ category: billing product: billing --- -Scaleway’s Savings Plan is a commitment-based discount program that provides more cost-effective billing compared to the pay-as-you-go model. Currently, this offer can be used with [Instance products.](/console/billing/additional-content/understanding-savings-plans/#compute-savings-plan) Access Savings Plans in the [Scaleway console](https://console.scaleway.com) in the **Cost optimization** tab of your Billing space. +Scaleway’s Savings Plan is a commitment-based discount program that provides more cost-effective billing compared to the pay-as-you-go model. Currently, this offer can be used with [Instance products.](/billing/additional-content/understanding-savings-plans/#compute-savings-plan) Access Savings Plans in the [Scaleway console](https://console.scaleway.com) in the **Cost optimization** tab of your Billing space. -Read [our dedicated documentation](/console/billing/additional-content/understanding-savings-plans/) for more information and to purchase your first Savings Plan. +Read [our dedicated documentation](/billing/additional-content/understanding-savings-plans/) for more information and to purchase your first Savings Plan. diff --git a/changelog/serverless/january2023/2023-01-11-added-functions-php-extensions.mdx b/changelog/serverless/january2023/2023-01-11-added-functions-php-extensions.mdx index 088f14380a..28a9ebeadd 100644 --- a/changelog/serverless/january2023/2023-01-11-added-functions-php-extensions.mdx +++ b/changelog/serverless/january2023/2023-01-11-added-functions-php-extensions.mdx @@ -9,4 +9,4 @@ category: serverless product: functions --- -The PHP Runtime for Serverless Functions now supports [more extensions](/serverless/functions/reference-content/functions-runtimes-configuration/). \ No newline at end of file +The PHP Runtime for Serverless Functions now supports [more extensions](/serverless-functions/reference-content/functions-runtimes-configuration/). \ No newline at end of file diff --git a/changelog/serverless/july2022/2022-07-01-changed-functions-framework.mdx b/changelog/serverless/july2022/2022-07-01-changed-functions-framework.mdx index 7c4bb8e5d8..da4b207a18 100644 --- a/changelog/serverless/july2022/2022-07-01-changed-functions-framework.mdx +++ b/changelog/serverless/july2022/2022-07-01-changed-functions-framework.mdx @@ -9,4 +9,4 @@ category: serverless product: functions --- -The [Serverless Framework](/serverless/functions/concepts/#serverless-framework) now supports custom domains and serverless invoke. \ No newline at end of file +The [Serverless Framework](/serverless-functions/concepts/#serverless-framework) now supports custom domains and serverless invoke. \ No newline at end of file diff --git a/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx b/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx index b07a935754..5a8200ecd0 100644 --- a/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx +++ b/changelog/serverless/september2022/2022-09-07-mnq-added-sns-sqs.mdx @@ -9,4 +9,4 @@ category: serverless product: messaging-and-queuing --- -SNS and SQS are now available for Messaging in [private beta](https://www.scaleway.com/en/betas/). You can create an SNS/SQS namespace, generate credentials and use them to connect to the system. Find out more on the SNS/SQS [documentation overview](/serverless/messaging/reference-content/). \ No newline at end of file +SNS and SQS are now available for Messaging in [private beta](https://www.scaleway.com/en/betas/). You can create an SNS/SQS namespace, generate credentials and use them to connect to the system. Find out more on the SNS/SQS [documentation overview](/messaging/reference-content/). \ No newline at end of file diff --git a/changelog/serverless/september2022/2022-09-08-functions-changed-nodejs.mdx b/changelog/serverless/september2022/2022-09-08-functions-changed-nodejs.mdx index 5b4a97ba01..ff0ed5bf99 100644 --- a/changelog/serverless/september2022/2022-09-08-functions-changed-nodejs.mdx +++ b/changelog/serverless/september2022/2022-09-08-functions-changed-nodejs.mdx @@ -12,4 +12,4 @@ product: functions NodeJS 18 is now in general availability. -For more information please refer to our [dedicated documentation](/serverless/functions/reference-content/functions-lifecycle/). \ No newline at end of file +For more information please refer to our [dedicated documentation](/serverless-functions/reference-content/functions-lifecycle/). \ No newline at end of file diff --git a/changelog/serverless/september2022/2022-09-08-functions-deprecated-go.mdx b/changelog/serverless/september2022/2022-09-08-functions-deprecated-go.mdx index 3b7e3dd110..c9af106e67 100644 --- a/changelog/serverless/september2022/2022-09-08-functions-deprecated-go.mdx +++ b/changelog/serverless/september2022/2022-09-08-functions-deprecated-go.mdx @@ -11,4 +11,4 @@ product: functions - Golang and Go113 will reach end of support. We recommend you update to go1.17 or a newer version. -For more information please refer to our [dedicated documentation](/serverless/functions/reference-content/functions-lifecycle/). \ No newline at end of file +For more information please refer to our [dedicated documentation](/serverless-functions/reference-content/functions-lifecycle/). \ No newline at end of file diff --git a/changelog/serverless/september2022/2022-09-08-functions-deprecated-nodejs.mdx b/changelog/serverless/september2022/2022-09-08-functions-deprecated-nodejs.mdx index d02accb61a..edf6d9e340 100644 --- a/changelog/serverless/september2022/2022-09-08-functions-deprecated-nodejs.mdx +++ b/changelog/serverless/september2022/2022-09-08-functions-deprecated-nodejs.mdx @@ -12,4 +12,4 @@ product: functions - NodeJS 8 and NodeJS 10 will reach end of support. We recommend you update to Node 14 or a newer node version. - NodeJS 17 will reach end of support. We recommend you update to NodeJS 18. -For more information please refer to our [dedicated documentation](/serverless/functions/reference-content/functions-lifecycle/). \ No newline at end of file +For more information please refer to our [dedicated documentation](/serverless-functions/reference-content/functions-lifecycle/). \ No newline at end of file diff --git a/changelog/serverless/september2022/2022-09-08-functions-deprecated-python.mdx b/changelog/serverless/september2022/2022-09-08-functions-deprecated-python.mdx index 2f05d1a036..6a57ab788a 100644 --- a/changelog/serverless/september2022/2022-09-08-functions-deprecated-python.mdx +++ b/changelog/serverless/september2022/2022-09-08-functions-deprecated-python.mdx @@ -12,4 +12,4 @@ product: functions - Python and Python 2.7 will reach end of support. We recommend you update to a newer version of Python. - Python 3 will reach end of support. We recommend you update to Python 3.7. -For more information please refer to our [dedicated documentation](/serverless/functions/reference-content/functions-lifecycle/). \ No newline at end of file +For more information please refer to our [dedicated documentation](/serverless-functions/reference-content/functions-lifecycle/). \ No newline at end of file diff --git a/changelog/storage/december2022/2022-12-07-new-permission-sets.mdx b/changelog/storage/december2022/2022-12-07-new-permission-sets.mdx index 91537fab92..4e5ec72cec 100644 --- a/changelog/storage/december2022/2022-12-07-new-permission-sets.mdx +++ b/changelog/storage/december2022/2022-12-07-new-permission-sets.mdx @@ -11,4 +11,4 @@ product: object-storage Identity and Access Management (IAM) is now available to manage users and applications' access to objects and buckets. In each Scaleway Project, you can now give permissions to create, read, edit and/or delete object and buckets. -You can find a list of the new Object Storage permission sets in the [IAM permission sets](/identity-and-access-management/iam/reference-content/permission-sets/) documentation page. \ No newline at end of file +You can find a list of the new Object Storage permission sets in the [IAM permission sets](/iam/reference-content/permission-sets/) documentation page. \ No newline at end of file diff --git a/components/docs-editor.mdx b/components/docs-editor.mdx index b166a2faa7..aa720f4acb 100644 --- a/components/docs-editor.mdx +++ b/components/docs-editor.mdx @@ -475,7 +475,7 @@ The `icon` names are not random ones they come from Ultraviolet lib. icon="rocket" description="Learn how to create, manage and delete a Kubernetes cluster in a few steps." label="Read More" - url="/bare-metal/elastic-metal/quickstart/" + url="/elastic-metal/quickstart/" /> diff --git a/components/docs.mdx b/components/docs.mdx index 0f01e2c747..cd9aebd952 100644 --- a/components/docs.mdx +++ b/components/docs.mdx @@ -691,7 +691,7 @@ The above text come from a macro! | Content Type | Description | | :-----------------------------------------------------: | :---------------------------------------------------------------------------: | -| [Internal link](/dedibox-console/account/quickstart/) | Centered-align table | +| [Internal link](/dedibox-account/quickstart/) | Centered-align table | | [External link](https://www.scaleway.com) | Problem-oriented, we take you through a series of steps to reach a real goal. | | Tutorials | Learning-oriented, we take you through a series of steps to learn a concept | @@ -746,25 +746,25 @@ The above text come from a macro! - Choose an **Availability Zone**, which is the geographical region where your Instance will be deployed. - Choose an **Image** to run on your Instance. This can be an operating system, an InstantApp or a custom image. A complete list of all available Linux distributions and InstantApps can be found [here](https://www.scaleway.com/en/imagehub/). - When choosing an image for an Enterprise Instance, be aware this Instance type is not compatible with bootscripts, except for [rescue mode](/compute/instances/how-to/use-boot-modes#how-to-use-rescue-mode). InstantApps are also not available for this Instance type. + When choosing an image for an Enterprise Instance, be aware this Instance type is not compatible with bootscripts, except for [rescue mode](/instances/how-to/use-boot-modes#how-to-use-rescue-mode). InstantApps are also not available for this Instance type. - Choose an **Instance type**. Different Instance types have different prices, processing power, memory, storage options and bandwidth. - Add **Volumes**. Volumes are storage spaces used by your Instances. - - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/compute/instances/concepts#local-volumes) and/or [block](/compute/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume. - - **PRO2** and **Enterprise** Instances boot directly [on block volumes](/compute/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each. + - For **GP1 Instances** you can leave the default settings of a maximum local storage, or choose how much [local](/instances/concepts#local-volumes) and/or [block](/instances/concepts#block-volumes) storage you want. Your **system volume** is the volume on which your Instance will boot. The system volume can be either a local or a block volume. + - **PRO2** and **Enterprise** Instances boot directly [on block volumes](/instances/concepts/#boot-on-block). You can add several block volumes and define how much storage you want for each. Please note that: - a volume with an OS image should be at least 10GB (125GB for a GPU OS). - - if several Block Storage volumes are connected to your Instance, the first volume will contain the OS and is required to boot the Instance. You can [change your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume) after you create the Instance. + - if several Block Storage volumes are connected to your Instance, the first volume will contain the OS and is required to boot the Instance. You can [change your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume) after you create the Instance. - if you have two or more volumes with identical operating systems, or a volume with no operating system, choosing one of these as your boot volume may cause unpredictable boot behavior. - - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can also add [tags](/compute/instances/concepts#tags) to help you organize your Instance. - - Click **Advanced Options** if you want to configure a [flexible IP](/compute/instances/concepts#flexible-ip), a local bootscript or a [cloud-init configuration](/compute/instances/concepts#cloud-init). Otherwise, leave these options at their default values. - - Verify the [SSH Keys](/console/account/concepts#ssh-key) that will give you access to your Instance. + - Enter a **Name** for your Instance, or leave the randomly-generated name in place. Optionally, you can also add [tags](/instances/concepts#tags) to help you organize your Instance. + - Click **Advanced Options** if you want to configure a [flexible IP](/instances/concepts#flexible-ip), a local bootscript or a [cloud-init configuration](/instances/concepts#cloud-init). Otherwise, leave these options at their default values. + - Verify the [SSH Keys](/account/concepts#ssh-key) that will give you access to your Instance. - Verify the **Estimated Cost** of your Instance, based on the specifications you chose. 4. Click **Create a new Instance** to finish. The creation of your Instance begins, and you will be informed when the Instance is ready. - Your Instance is now created and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/compute/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. + Your Instance is now created and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. API diff --git a/compute/gpu/concepts.mdx b/compute/gpu/concepts.mdx index 9ea1a58b17..d9bbd6667e 100644 --- a/compute/gpu/concepts.mdx +++ b/compute/gpu/concepts.mdx @@ -13,7 +13,7 @@ categories: --- - GPU Instances share many concepts in common with traditional Instances. See also the [Instances Concepts page](/compute/instances/concepts/) for more information. + GPU Instances share many concepts in common with traditional Instances. See also the [Instances Concepts page](/instances/concepts/) for more information. ## AI-enabled applications @@ -47,7 +47,7 @@ In this context, the trustworthiness of AI systems, which operate with varying d ## Docker [Docker](https://www.docker.com/) is a platform as a service (PaaS) tool, that uses OS-level virtualization to deliver software in packages called containers. -Scaleway provides a number of pre-built Docker images, which allow you to [run a Docker container on your GPU Instance](/compute/gpu/how-to/use-gpu-with-docker/) and access a preinstalled Pipenv environment ideal for your AI projects. +Scaleway provides a number of pre-built Docker images, which allow you to [run a Docker container on your GPU Instance](/gpu/how-to/use-gpu-with-docker/) and access a preinstalled Pipenv environment ideal for your AI projects. ## Flexpoint @@ -126,7 +126,7 @@ Pipenv is a package and dependency manager for Python projects. It harnesses the - `Virtualenv` for creating different virtual Python environments - `Pipfile` for managing project dependencies -Pipenv is preinstalled on all of Scaleway's AI Docker images for GPU Instances, making it easy to [use virtual environments](/compute/gpu/how-to/use-pipenv/). Pipenv replaces Anaconda for this purpose. +Pipenv is preinstalled on all of Scaleway's AI Docker images for GPU Instances, making it easy to [use virtual environments](/gpu/how-to/use-pipenv/). Pipenv replaces Anaconda for this purpose. ## PyTorch diff --git a/compute/gpu/how-to/create-manage-gpu-instance.mdx b/compute/gpu/how-to/create-manage-gpu-instance.mdx index 2fd2b1dfba..3229a74809 100644 --- a/compute/gpu/how-to/create-manage-gpu-instance.mdx +++ b/compute/gpu/how-to/create-manage-gpu-instance.mdx @@ -15,17 +15,17 @@ categories: Scaleway GPU Instances feature dedicated high-end Nvidia GPUs, making them optimal for tasks such as data processing, artificial intelligence, rendering, and video encoding. -Once you've created your GPU Instance, [connecting to it via SSH](/compute/instances/how-to/connect-to-instance/) allows you to use our [pre-configured Docker images](/compute/gpu/how-to/use-gpu-with-docker/), providing instant access to a [preinstalled environment](/compute/gpu/how-to/use-preinstalled-env/) with your preferred AI libraries and tools already set up. +Once you've created your GPU Instance, [connecting to it via SSH](/instances/how-to/connect-to-instance/) allows you to use our [pre-configured Docker images](/gpu/how-to/use-gpu-with-docker/), providing instant access to a [preinstalled environment](/gpu/how-to/use-preinstalled-env/) with your preferred AI libraries and tools already set up. -Moreover, GPU Instances offer all the functionalities of our standard Instances, including [flexible IPs](/compute/instances/how-to/use-flexips/), [Security Groups](/compute/instances/how-to/use-security-groups/), [Private Networks](/compute/instances/how-to/use-private-networks/), backups, and more. +Moreover, GPU Instances offer all the functionalities of our standard Instances, including [flexible IPs](/instances/how-to/use-flexips/), [Security Groups](/instances/how-to/use-security-groups/), [Private Networks](/instances/how-to/use-private-networks/), backups, and more. -When you have completed your calculations using the GPU Instance, [deletion can be done through the Scaleway console](/compute/instances/how-to/delete-instance/), API, or our CLI tools. +When you have completed your calculations using the GPU Instance, [deletion can be done through the Scaleway console](/instances/how-to/delete-instance/), API, or our CLI tools. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account ## How to create a GPU Instance @@ -33,12 +33,12 @@ When you have completed your calculations using the GPU Instance, [deletion can 2. Click **+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers). 3. Follow these steps to configure your GPU Instance: - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/compute/gpu/reference-content/choosing-gpu-instance-type/) for more information. + - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled NVIDIA drivers and an NVIDIA Docker environment. You have the flexibility to customize your working environment using Docker with our provided Docker images or your own containers. - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. - * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/compute/gpu/how-to/use-scratch-storage-h100-instances/) + * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/) - **Network Configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. - **Instance Name and Tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. @@ -49,14 +49,14 @@ When you have completed your calculations using the GPU Instance, [deletion can ## How to connect to a GPU Instance -See our documentation on [how to connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +See our documentation on [how to connect to your Instance via SSH](/instances/how-to/connect-to-instance/). -Once you have connected via SSH, you can [launch a Docker container](/compute/gpu/how-to/use-gpu-with-docker/) to start working on your AI projects. +Once you have connected via SSH, you can [launch a Docker container](/gpu/how-to/use-gpu-with-docker/) to start working on your AI projects. ## How to use Instance features -For instructions on using any type of GPU Instance feature, including flexible IPs, placement groups, Private Networks, backups, and much more, check out our full [Instance how-to documentation](/compute/instances/how-to/). +For instructions on using any type of GPU Instance feature, including flexible IPs, placement groups, Private Networks, backups, and much more, check out our full [Instance how-to documentation](/instances/how-to/). ## How to delete a GPU Instance -See our documentation on [how to delete your Instance](/compute/instances/how-to/delete-instance/). \ No newline at end of file +See our documentation on [how to delete your Instance](/instances/how-to/delete-instance/). \ No newline at end of file diff --git a/compute/gpu/how-to/use-gpu-with-docker.mdx b/compute/gpu/how-to/use-gpu-with-docker.mdx index 7b1f82e42d..9e955c14ec 100644 --- a/compute/gpu/how-to/use-gpu-with-docker.mdx +++ b/compute/gpu/how-to/use-gpu-with-docker.mdx @@ -24,26 +24,26 @@ You can also run Docker images provided by other sources and use them with your - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account -- A [GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account +- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/) ## How to get started on a GPU Instance with Docker -1. [Connect](/compute/instances/how-to/connect-to-instance/) to your GPU Instance via SSH. -2. Choose a Docker image from the containers shipped with your GPU Instance. See our [additional content](/compute/gpu/reference-content/docker-images/) for more information about the available Docker images, including the specific commands to run each of them. +1. [Connect](/instances/how-to/connect-to-instance/) to your GPU Instance via SSH. +2. Choose a Docker image from the containers shipped with your GPU Instance. See our [additional content](/gpu/reference-content/docker-images/) for more information about the available Docker images, including the specific commands to run each of them. 3. Use the following command to pull/run the Docker container. Remember to replace `[OPTIONS]` with any relevant options parameters, and `` with the image name and tag of your chosen image, as shown in the additional content linked above: ``` docker run --rm -it [OPTIONS] [COMMAND] ``` - Once you have run your Docker container, you may find it useful to refer to our documentation on using [pipenv](/compute/gpu/how-to/use-pipenv/) and the container's [preinstalled environment](/compute/gpu/how-to/use-preinstalled-env/) for more help. + Once you have run your Docker container, you may find it useful to refer to our documentation on using [pipenv](/gpu/how-to/use-pipenv/) and the container's [preinstalled environment](/gpu/how-to/use-preinstalled-env/) for more help. ## How to map volumes -We recommend that you map volumes from your GPU Instance to your Docker containers, so that your work is not lost when you exit the Docker container. For increased data redundancy, we also recommend storing the directories you map to your Docker containers on [Block Storage](/storage/block/quickstart/). +We recommend that you map volumes from your GPU Instance to your Docker containers, so that your work is not lost when you exit the Docker container. For increased data redundancy, we also recommend storing the directories you map to your Docker containers on [Block Storage](/block-storage/quickstart/). ### How to map local volumes @@ -75,10 +75,10 @@ In the above example, everything in the `/root/mydata` directory on the Instance ### How to map Block Storage volumes -You can also map [Block Storage](https://www.scaleway.com/en/block-storage/) volumes into your containers. Block Storage is fully backed by SSDs. These three-time replicated, high-speed drives allow up to 5,000 IOPS. Once [attached](/storage/block/how-to/attach-a-volume/) and [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) in the host OS of the GPU Instance, you can map the volume like a local volume, as we did above. +You can also map [Block Storage](https://www.scaleway.com/en/block-storage/) volumes into your containers. Block Storage is fully backed by SSDs. These three-time replicated, high-speed drives allow up to 5,000 IOPS. Once [attached](/block-storage/how-to/attach-a-volume/) and [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) in the host OS of the GPU Instance, you can map the volume like a local volume, as we did above. - [Block Storage](/storage/block/quickstart/) volumes are independent of your GPU Instance and provide three-time replicated storage. It is recommended to use Block Storage for storing your datasets, training logs, model source code, etc. + [Block Storage](/block-storage/quickstart/) volumes are independent of your GPU Instance and provide three-time replicated storage. It is recommended to use Block Storage for storing your datasets, training logs, model source code, etc. ## Most common Docker commands @@ -179,7 +179,7 @@ The possible values of the `NVIDIA_VISIBLE_DEVICES` variable are: ## How to push and list Docker images stored on your Scaleway Registry - GPU Instances are compatible with [Scaleway Container Registry](/containers/container-registry/quickstart/). You can create a Container Registry to store and pull your own Docker images. + GPU Instances are compatible with [Scaleway Container Registry](/container-registry/quickstart/). You can create a Container Registry to store and pull your own Docker images. -See [detailed information](/containers/container-registry/how-to/pull-images/) on how to pull your own custom Docker images on your GPU Instance. \ No newline at end of file +See [detailed information](/container-registry/how-to/pull-images/) on how to pull your own custom Docker images on your GPU Instance. \ No newline at end of file diff --git a/compute/gpu/how-to/use-mig-with-kubernetes.mdx b/compute/gpu/how-to/use-mig-with-kubernetes.mdx index dc36ac8ed0..06696d00da 100644 --- a/compute/gpu/how-to/use-mig-with-kubernetes.mdx +++ b/compute/gpu/how-to/use-mig-with-kubernetes.mdx @@ -28,10 +28,10 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete - A Scaleway account logged into the [console](https://console.scaleway.com) -- A [Kubernetes cluster](/containers/kubernetes/quickstart/#how-to-create-a-kubernetes-cluster) with a [GPU Instance](https://www.scaleway.com/en/gpu-instances/) as node +- A [Kubernetes cluster](/kubernetes/quickstart/#how-to-create-a-kubernetes-cluster) with a [GPU Instance](https://www.scaleway.com/en/gpu-instances/) as node - MIG is fully supported on [Scaleway managed Kubernetes](/containers/kubernetes/quickstart/) clusters (Kapsule and Kosmos). + MIG is fully supported on [Scaleway managed Kubernetes](/kubernetes/quickstart/) clusters (Kapsule and Kosmos). ## Configure MIG partitions inside a Kubernetes cluster @@ -389,7 +389,7 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete MIG is disabled and the whole GPU is available. - To enable autoscaling with [Kubernetes Kapsule](/containers/kubernetes/quickstart/), it is necessary to designate a tag for the node pool. This tag will be automatically inherited as a label by all nodes within that pool. + To enable autoscaling with [Kubernetes Kapsule](/kubernetes/quickstart/), it is necessary to designate a tag for the node pool. This tag will be automatically inherited as a label by all nodes within that pool. Therefore, to create a node pool offering H100 nodes configured with the label `nvidia.com/mig.config=all-3g.40g`, simply assign the tag `noprefix=nvidia.com/mig.config=all-3g.40gb` to the corresponding Kapsule node pool. All nodes added by the autoscaler will automatically receive the label `MIG`. Note, that updates to a tag may take up to five minutes to fully propagate. diff --git a/compute/gpu/how-to/use-nvidia-mig-technology.mdx b/compute/gpu/how-to/use-nvidia-mig-technology.mdx index e2e35edb46..0e942d64d8 100644 --- a/compute/gpu/how-to/use-nvidia-mig-technology.mdx +++ b/compute/gpu/how-to/use-nvidia-mig-technology.mdx @@ -39,15 +39,15 @@ For more information about NVIDIA MIG, refer to the official [MIG documentation] - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [MIG-compatible GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [MIG-compatible GPU Instance](/gpu/how-to/create-manage-gpu-instance/) +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account ## How to enable MIG on a GPU Instance By default, the MIG feature of NVIDIA GPUs is disabled. To use it with your GPU Instance, you need to activate MIG. -1. [Connect to your GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance) as root using SSH. +1. [Connect to your GPU Instance](/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance) as root using SSH. 2. Check the status of the MIG mode of your Instance running `nvidia-smi`. It shows that MIG mode is disabled: ```s root@my-h100-instance:~# nvidia-smi -i 0 diff --git a/compute/gpu/how-to/use-pipenv.mdx b/compute/gpu/how-to/use-pipenv.mdx index 1b82dda148..ad3281145c 100644 --- a/compute/gpu/how-to/use-pipenv.mdx +++ b/compute/gpu/how-to/use-pipenv.mdx @@ -27,13 +27,13 @@ Pipenv is a powerful package and dependency manager for Python projects. It comb ### Requirements - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/) +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account ## Accessing the preinstalled Pipenv virtual environment -Refer to our [dedicated documentation](/compute/gpu/how-to/use-preinstalled-env/#working-with-the-preinstalled-environment-on-ubuntu-focal-gpu-os-11) on how to access the Pipenv virtual environment from your Scaleway GPU Instance. +Refer to our [dedicated documentation](/gpu/how-to/use-preinstalled-env/#working-with-the-preinstalled-environment-on-ubuntu-focal-gpu-os-11) on how to access the Pipenv virtual environment from your Scaleway GPU Instance. ## Managing packages with Pipenv @@ -126,7 +126,7 @@ Each Pipenv virtual environment has a Pipfile that details project dependencies, ``` - To avoid losing your virtual environment upon exiting the container, create this folder in a directory [mapped to one of your GPU Instance's local volumes](/compute/gpu/how-to/use-gpu-with-docker#how-to-map-local-volumes). + To avoid losing your virtual environment upon exiting the container, create this folder in a directory [mapped to one of your GPU Instance's local volumes](/gpu/how-to/use-gpu-with-docker#how-to-map-local-volumes). 5. Create a new virtual environment and generate a Pipfile: diff --git a/compute/gpu/how-to/use-preinstalled-env.mdx b/compute/gpu/how-to/use-preinstalled-env.mdx index 4fc4b8740a..a44a440850 100644 --- a/compute/gpu/how-to/use-preinstalled-env.mdx +++ b/compute/gpu/how-to/use-preinstalled-env.mdx @@ -13,24 +13,24 @@ categories: - compute --- -GPU Instances have different types of preinstalled environments, depending on the OS image you chose during [creation of the Instance](/compute/gpu/how-to/create-manage-gpu-instance/): +GPU Instances have different types of preinstalled environments, depending on the OS image you chose during [creation of the Instance](/gpu/how-to/create-manage-gpu-instance/): | OS image | Image release type | Preinstalled on image | Working environment | |:----------------------:|:------------------:|:---------------------------------------------------------------:|------------------------------------------------| | Ubuntu Focal GPU OS 12 | Latest | Nvidia drivers, Nvidia Docker environment (launch Docker container to access working environment) | Pipenv virtual environment accessed via Docker | -Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation on which you can [launch](/compute/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/compute/gpu/reference-content/docker-images/). This gives you access to a preinstalled Python environment managed with pipenv. A number of useful AI core packages and tools are installed, including `scipy`, `numpy`, `scikit-learn`, `jupyter`, `tensorflow`, and the Scaleway SDK. Depending on the [Docker image you choose](/compute/gpu/reference-content/docker-images/), other packages and tools will also be preinstalled, providing a convenient framework environment for you so that you can begin work immediately. +Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation on which you can [launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/). This gives you access to a preinstalled Python environment managed with pipenv. A number of useful AI core packages and tools are installed, including `scipy`, `numpy`, `scikit-learn`, `jupyter`, `tensorflow`, and the Scaleway SDK. Depending on the [Docker image you choose](/gpu/reference-content/docker-images/), other packages and tools will also be preinstalled, providing a convenient framework environment for you so that you can begin work immediately. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) added to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [GPU Instance](/gpu/how-to/create-manage-gpu-instance/) +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) added to your account ## Working with the preinstalled environment on Ubuntu Bionic ML legacy images -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). You are now directly within the conda `ai` preinstalled environment. 2. Use the [official conda documentation](https://docs.conda.io/projects/conda/en/latest/commands.html) if you need any help managing your conda environment. @@ -38,20 +38,20 @@ Using the latest Ubuntu Focal GPU OS11 image gives you a minimal OS installation For a full, detailed list of the Python packages and versions preinstalled in this environment, look at the content of the `/root/conda-ai-env-requirements.frozen` file. - As Docker is also preinstalled, you could choose to [launch one of Scaleway's ready-made Docker images](/compute/gpu/how-to/use-gpu-with-docker/) to access our latest working environments, if you wish. + As Docker is also preinstalled, you could choose to [launch one of Scaleway's ready-made Docker images](/gpu/how-to/use-gpu-with-docker/) to access our latest working environments, if you wish. 3. Type `exit` to disconnect from your GPU Instance when you have finished your work. ## Working with the preinstalled environment on Ubuntu Focal GPU OS 12 -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). You are now connected to your Instance, and see your OS. A minimum of packages, including Docker, are installed. Pipenv is **not** preinstalled here. You must launch a Scaleway AI Docker container to access the preinstalled Pipenv environment. -2. [Launch](/compute/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/compute/gpu/reference-content/docker-images/). +2. [Launch](/gpu/how-to/use-gpu-with-docker/) one of our ready-made [Docker images](/gpu/reference-content/docker-images/). You are now in the `ai` directory of the Docker container, in the activated Pipenv virtual environment, and can get right to work! - Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/compute/gpu/how-to/use-pipenv/). + Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/gpu/how-to/use-pipenv/). ### Launching an application in your local browser diff --git a/compute/gpu/index.mdx b/compute/gpu/index.mdx index f1e92636e7..83720a0e28 100644 --- a/compute/gpu/index.mdx +++ b/compute/gpu/index.mdx @@ -8,7 +8,7 @@ meta: productName="GPU Instances" productLogo="instance" description="Scaleway GPU Instances are equipped with dedicated high-end NVIDIA GPUs and offer the speed and efficiency you need to run your most demanding workloads." - url="/compute/gpu/quickstart/" + url="/gpu/quickstart/" label="Instances Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and delete a GPU Instance in a few steps." label="View Quickstart" - url="/compute/gpu/quickstart/" + url="/gpu/quickstart/" /> diff --git a/compute/gpu/quickstart.mdx b/compute/gpu/quickstart.mdx index e1dc002332..e23b7ece7d 100644 --- a/compute/gpu/quickstart.mdx +++ b/compute/gpu/quickstart.mdx @@ -15,9 +15,9 @@ categories: -Scaleway GPU Instances are virtual compute instances equipped with dedicated high-end Nvidia graphics processing units (GPUs). They are ideal for data processing, artificial intelligence, rendering, and video encoding. After you have created your GPU Instance, you can [connect to it via SSH](/compute/instances/how-to/connect-to-instance/) and run one of our ready-made [Docker images](/compute/gpu/how-to/use-gpu-with-docker/) to access a [preinstalled environment](/compute/gpu/how-to/use-preinstalled-env/) with all your [favorite AI libraries and tools](/compute/gpu/reference-content/docker-images/) preinstalled. +Scaleway GPU Instances are virtual compute instances equipped with dedicated high-end Nvidia graphics processing units (GPUs). They are ideal for data processing, artificial intelligence, rendering, and video encoding. After you have created your GPU Instance, you can [connect to it via SSH](/instances/how-to/connect-to-instance/) and run one of our ready-made [Docker images](/gpu/how-to/use-gpu-with-docker/) to access a [preinstalled environment](/gpu/how-to/use-preinstalled-env/) with all your [favorite AI libraries and tools](/gpu/reference-content/docker-images/) preinstalled. -In addition to this, GPU Instances have all the features of our regular Instances, including [flexible IPs](/compute/instances/how-to/use-flexips/), [security groups](/compute/instances/how-to/use-security-groups/), [Private Networks](/compute/instances/how-to/use-private-networks/), [backups](/compute/instances/how-to/create-a-backup/) and more. When you are done using your GPU Instance, you can easily [delete it](/compute/instances/how-to/delete-instance/) from the Scaleway console. +In addition to this, GPU Instances have all the features of our regular Instances, including [flexible IPs](/instances/how-to/use-flexips/), [security groups](/instances/how-to/use-security-groups/), [Private Networks](/instances/how-to/use-private-networks/), [backups](/instances/how-to/create-a-backup/) and more. When you are done using your GPU Instance, you can easily [delete it](/instances/how-to/delete-instance/) from the Scaleway console. ## How to create a GPU Instance @@ -25,12 +25,12 @@ In addition to this, GPU Instances have all the features of our regular Instance 2. Click **+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers). 3. Follow these steps to configure your GPU Instance: - **Availability Zone**: Choose the geographical region, represented by the Availability Zone, where your Instance will be deployed. - - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/compute/gpu/reference-content/choosing-gpu-instance-type/) for more information. + - **Instance Type (GPU)**: Select the desired GPU Instance type, considering factors such as processing power, memory, storage options, and bandwidth. Refer to our guide on [choosing the right GPU Instance type](/gpu/reference-content/choosing-gpu-instance-type/) for more information. - **Image**: Pick an operating system image suitable for your GPU Instance. For example, select **Ubuntu Jammy GPU OS 12**, which comes with preinstalled Nvidia drivers and an Nvidia Docker environment. You can customize your working environment using Docker with our provided Docker images or your own containers. - **Volumes**: Optionally, add storage volumes for your Instance. You can adjust settings such as Block and Local Storage volumes according to your requirements. * The recommended minimum volume size for GPU OS images is 125 GB. - * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/compute/gpu/how-to/use-scratch-storage-h100-instances/) + * If your GPU Instance supports scratch storage, the scratch volume displays but can not be edited. [Learn more about scratch storage.](/gpu/how-to/use-scratch-storage-h100-instances/) - **Network configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. @@ -41,7 +41,7 @@ In addition to this, GPU Instances have all the features of our regular Instance ## How to connect to your GPU Instance -See our documentation on [how to connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +See our documentation on [how to connect to your Instance via SSH](/instances/how-to/connect-to-instance/). ## How to launch a Docker container @@ -51,7 +51,7 @@ To access a preinstalled working environment with all your favorite Python packa If you created your GPU Instance with one of the legacy Ubuntu Bionic ML OS images, once you connect to your Instance you are already in a preinstalled ready-to-use Python environment, managed with conda. You do not need to follow the steps for launching a Docker container. -1. Choose one of our [Docker AI images](/compute/gpu/reference-content/docker-images/) (eg Tensorflox, Pytorch, Jax) based on your needs. +1. Choose one of our [Docker AI images](/gpu/reference-content/docker-images/) (eg Tensorflox, Pytorch, Jax) based on your needs. 2. Run the following command to launch the Docker container. In the following example, we launch a container based on the **Tensorflow** image: ```sh docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/tensorflow:latest /bin/bash @@ -62,7 +62,7 @@ To access a preinstalled working environment with all your favorite Python packa When you run your Docker container as shown above, the container launches and you are taken to its `ai` directory, where the Pipenv virtual environment is already activated. - Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/compute/gpu/how-to/use-pipenv/). + Use the command `pipenv graph` to see a list of all installed packages and their versions, as well as all the dependencies of each package. For more help with pipenv, see our [dedicated documentation](/gpu/how-to/use-pipenv/). ### Launching an application in your local browser diff --git a/compute/gpu/reference-content/choosing-gpu-instance-type.mdx b/compute/gpu/reference-content/choosing-gpu-instance-type.mdx index a0b899cc9b..dc317df561 100644 --- a/compute/gpu/reference-content/choosing-gpu-instance-type.mdx +++ b/compute/gpu/reference-content/choosing-gpu-instance-type.mdx @@ -30,13 +30,13 @@ Below, you will find a guide to help you make an informed decision: * **GPU type:** Scaleway offers different GPU types, such as various NVIDIA GPUs. Each GPU has varying levels of performance, memory, and capabilities. Choose a GPU that aligns with your specific workload requirements. * **GPU memory:** GPU memory bandwidth is an important criterion influencing overall performance. Then, larger GPU memory (VRAM) is crucial for memory-intensive tasks like training larger deep learning models, especially when using larger batch sizes. Modern GPUs offer specialized data formats designed to optimize deep learning performance. These formats, including Bfloat16, [FP8](https://docs.nvidia.com/deeplearning/transformer-engine/user-guide/examples/fp8_primer.html), int8 and int4, enable the storage of more data in memory and can enhance performance (for example, moving from FP16 to FP8 can double the number of TFLOPS). To make an informed decision, it is thus crucial to select the appropriate architecture. Options range from Pascal and Ampere to Ada Lovelace and Hopper. Ensuring that the GPU possesses sufficient memory capacity to accommodate your specific workload is essential, preventing any potential memory-related bottlenecks. Equally important, is matching the GPU's memory type to the nature of your workload. * **CPU and RAM:** A powerful CPU can be beneficial for tasks that involve preprocessing or post-processing. Sufficient system memory is also crucial to prevent memory-related bottlenecks or to cache your data in RAM. -* **GPU driver and software compatibility:** Ensure that the GPU Instance type you choose supports the GPU drivers and software frameworks you need for your workload. This includes CUDA libraries, machine learning frameworks (TensorFlow, PyTorch, etc.), and other specific software tools. For all [Scaleway GPU OS images](/compute/gpu/reference-content/docker-images/), we offer a driver version that enables the use of all GPUs, from the oldest to the latest models. As is the NGC CLI, `nvidia-docker` is preinstalled, enabling containers to be used with CUDA, cuDNN, and the main deep learning frameworks. +* **GPU driver and software compatibility:** Ensure that the GPU Instance type you choose supports the GPU drivers and software frameworks you need for your workload. This includes CUDA libraries, machine learning frameworks (TensorFlow, PyTorch, etc.), and other specific software tools. For all [Scaleway GPU OS images](/gpu/reference-content/docker-images/), we offer a driver version that enables the use of all GPUs, from the oldest to the latest models. As is the NGC CLI, `nvidia-docker` is preinstalled, enabling containers to be used with CUDA, cuDNN, and the main deep learning frameworks. * **Scaling:** Consider the scalability requirements of your workload. The most efficient way to scale up your workload is by using: * Bigger GPU * Up to 2 PCIe GPU with [H100 Instances](https://www.scaleway.com/en/h100-pcie-try-it-now/) or 8 PCIe GPU with [L4](https://www.scaleway.com/en/l4-gpu-instance/) or [L4OS](https://www.scaleway.com/en/contact-l40s/) Instances. * An HGX-based server setup with 8x NVlink GPUs * A [supercomputer architecture](https://www.scaleway.com/en/ai-supercomputers/) for a larger setup for workload-intensive tasks - * Another way to scale your workload is to use [Kubernetes and MIG](/compute/gpu/how-to/use-nvidia-mig-technology/): You can divide a single H100 GPU into as many as 7 MIG partitions. This means that instead of employing seven P100 GPUs to set up seven K8S pods, you could opt for a single H100 GPU with MIG to effectively deploy all seven K8S pods. + * Another way to scale your workload is to use [Kubernetes and MIG](/gpu/how-to/use-nvidia-mig-technology/): You can divide a single H100 GPU into as many as 7 MIG partitions. This means that instead of employing seven P100 GPUs to set up seven K8S pods, you could opt for a single H100 GPU with MIG to effectively deploy all seven K8S pods. * **Online resources:** Check for online resources, forums, and community discussions related to the specific GPU type you are considering. This can provide insights into common issues, best practices, and optimizations. Remember that there is no one-size-fits-all answer, and the right GPU Instance type will depend on your workload’s unique requirements and budget. It is important that you regularly reassess your choice as your workload evolves. Depending on which type best fits your evolving tasks, you can easily migrate from one GPU Instance type to another. @@ -56,8 +56,8 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | vCPUs | 10 | 24 | 48 | | RAM | 42 GB DDR3 | 240 GB DDR5 | 480 GB DDR5 | | Storage | Block/Local | Block | Block | -| [Scratch Storage](/compute/gpu/how-to/use-scratch-storage-h100-instances/) | No | Yes (3 TB NVMe) | Yes (6 TB NVMe) | -| [MIG compatibility](/compute/gpu/how-to/use-nvidia-mig-technology/) | No | Yes | Yes | +| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | No | Yes (3 TB NVMe) | Yes (6 TB NVMe) | +| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | Yes | Yes | | Bandwidth | 1 Gbps | 10 Gbps | 20 Gbps | | Better used for | Image / Video encoding (4K) | 7B LLM Fine-Tuning / Inference | 70B LLM Fine-Tuning / Inference | | What they are not made for | Large models (especially LLM) | Graphic or video encoding use cases | Graphic or video encoding use cases | @@ -73,8 +73,8 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | vCPUs | 8 | 16 | 32 | 64 | | RAM | 48 GB DDR4 | 96 GB DDR4 | 192 GB DDR4 | 384 GB DDR4 | | Storage | Block | Block | Block | Block | -| [Scratch Storage](/compute/gpu/how-to/use-scratch-storage-h100-instances/) | No | No | No | No | -| [MIG compatibility](/compute/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No | +| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | No | No | No | No | +| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No | | Bandwidth | 2.5 Gbps | 5 Gbps | 10 Gbps | 20 Gbps | | Better used for | Image Enconding (8K) | Video Enconding (8K) | 7B LLM Inference | 70B LLM Inference | | What they are not made for | Training of LLM | Training of LLM | Training of LLM | Training of LLM | @@ -90,8 +90,8 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | vCPUs | 8 | 16 | 32 | 64 | | RAM | 96 GB DDR4 | 192 GB DDR4 | 384 GB DDR4 | 768 GB DDR4 | | Storage | Block | Block | Block | Block | -| [Scratch Storage](/compute/gpu/how-to/use-scratch-storage-h100-instances/) | Yes (~1,6 TB NVMe) | Yes (~3,2 TB NVMe) | Yes (~6,4 TB NVMe) | Yes (~12,8 TB NVMe) | -| [MIG compatibility](/compute/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No | +| [Scratch Storage](/gpu/how-to/use-scratch-storage-h100-instances/) | Yes (~1,6 TB NVMe) | Yes (~3,2 TB NVMe) | Yes (~6,4 TB NVMe) | Yes (~12,8 TB NVMe) | +| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | No | No | No | No | | Bandwidth | 2,5 Gbps | 5 Gbps | 10 Gbps | 20 Gbps | | Use cases | GenAI (Image/Video) | GenAI (Image/Video) | 7B Text-to-image model fine-tuning / Inference | 70B text-to-image model fine-tuning / Inference | | What they are not made for | | | | | @@ -108,7 +108,7 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | Total CPU cores | 224 cores (total cluster) | 14,224 cores (total cluster) | | RAM | 4 TB (total cluster) | 254 TB (total cluster) | | Storage | 64TB of a3i DDN low latency storage | 1.8 PB of a3i DDN low latency storage | -| [MIG compatibility](/compute/gpu/how-to/use-nvidia-mig-technology/) | Yes | Yes | +| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | Yes | Yes | | Inter-GPU bandwidth | Infiniband 400 Gb/s | Infiniband 400 Gb/s | ### NVIDIA GH200 Superchip @@ -119,7 +119,7 @@ Remember that there is no one-size-fits-all answer, and the right GPU Instance t | NVIDIA architecture | GH200 Grace Hopper™ Architecture | | Performance | 990 TFLops (in FP166 Tensor Core) | | Specifications | - GH200 SuperChip with 72 ARM Neoverse V2 cores
- 480 GB of LPDDR5X DRAM
- 96GB of HBM3 GPU memory
(Memory is fully merged for up to 576GB of global usable memory) | -| [MIG compatibility](/compute/gpu/how-to/use-nvidia-mig-technology/) | Yes | +| [MIG compatibility](/gpu/how-to/use-nvidia-mig-technology/) | Yes | | Inter-GPU bandwidth (for clusters up to 256 GH200) | NVlink Switch System 900 GB/s | | Format & Features | Single chip up to GH200 clusters. (For larger setup needs, [contact us](https://www.scaleway.com/en/contact-ai-supercomputers/)) | | Use cases | - Extra large LLM and DL model inference
- HPC | diff --git a/compute/gpu/reference-content/gpu-instances-bandwidth-overview.mdx b/compute/gpu/reference-content/gpu-instances-bandwidth-overview.mdx index 0879a9f400..f1ca1d8402 100644 --- a/compute/gpu/reference-content/gpu-instances-bandwidth-overview.mdx +++ b/compute/gpu/reference-content/gpu-instances-bandwidth-overview.mdx @@ -28,7 +28,7 @@ GPU workloads often involve processing large datasets, requiring high-bandwidth - To maximize compatibility with [Block Storage Low Latency 15k](/storage/block/), select an Instance with **at least 3 GiB/s** of Block bandwidth. + To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth. ## GPU Range diff --git a/compute/gpu/reference-content/kubernetes-gpu-time-slicing.mdx b/compute/gpu/reference-content/kubernetes-gpu-time-slicing.mdx index 07f1742059..cfce68b262 100644 --- a/compute/gpu/reference-content/kubernetes-gpu-time-slicing.mdx +++ b/compute/gpu/reference-content/kubernetes-gpu-time-slicing.mdx @@ -40,7 +40,7 @@ Several elements within the Kubernetes cluster oversee the time-slicing of GPUs: ## Time-slicing compared to MIG -The most recent versions of NVIDIA GPUs introduce [Multi-instance GPU (MIG) mode](/compute/gpu/how-to/use-nvidia-mig-technology/). Fully integrated into Kubernetes in 2020, MIG allows a single GPU to be partitioned into smaller, predefined instances, essentially resembling miniaturized GPUs. +The most recent versions of NVIDIA GPUs introduce [Multi-instance GPU (MIG) mode](/gpu/how-to/use-nvidia-mig-technology/). Fully integrated into Kubernetes in 2020, MIG allows a single GPU to be partitioned into smaller, predefined instances, essentially resembling miniaturized GPUs. These instances provide memory and fault isolation directly at the hardware level. Instead of using the entire native GPU, you can run workloads on one of these predefined instances, enabling shared GPU access. Kubernetes GPU time-slicing divides the GPU resources at the container level within a Kubernetes cluster. Multiple containers (pods) share a single GPU, whereas MIG divides the GPU resources at the hardware level. Each MIG instance behaves like a separate GPU. diff --git a/compute/gpu/reference-content/understanding-nvidia-ngc.mdx b/compute/gpu/reference-content/understanding-nvidia-ngc.mdx index 48ceadd167..1060ce87f1 100644 --- a/compute/gpu/reference-content/understanding-nvidia-ngc.mdx +++ b/compute/gpu/reference-content/understanding-nvidia-ngc.mdx @@ -17,7 +17,7 @@ NVIDIA provides access to NVIDIA GPU Cloud (NGC) through providers including Sca Unleash the power of your applications' deployment with Scaleway and NGC, where seamless deployment is as effortless as following these three simple steps: 1. Deploy your Scaleway GPU Instance from the [Scaleway console](https://console.scaleway.com/instance/servers/create?imageKey=7bdc1afb-231f-486a-9b85-1b0478bc0e4a&offerName=RENDER-S&zone=fr-par-2), the [CLI tools](https://github.com/scaleway/scaleway-cli), or the [Scaleway API](https://www.scaleway.com/en/developers/api/instance/).1 - 1 You need [GPU Instance quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#gpu-instances) to be able to deploy GPU Instances. + 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/compute/gpu/troubleshooting/fix-driver-issues.mdx b/compute/gpu/troubleshooting/fix-driver-issues.mdx index c855aaefbc..ff51b1c5d5 100644 --- a/compute/gpu/troubleshooting/fix-driver-issues.mdx +++ b/compute/gpu/troubleshooting/fix-driver-issues.mdx @@ -13,7 +13,7 @@ categories: - compute --- -All Scaleway [GPU Instances](/compute/gpu/quickstart/) come with a Nvidia driver preinstalled. This means you do not have to install them by yourself. +All Scaleway [GPU Instances](/gpu/quickstart/) come with a Nvidia driver preinstalled. This means you do not have to install them by yourself. The drivers installed on each Instance are from the `nividia-headless-` packages. These are intended for use on Instances without a Windows Desktop or display server. diff --git a/compute/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx b/compute/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx index 53a358900e..2547739f5c 100644 --- a/compute/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx +++ b/compute/gpu/troubleshooting/install-nvidia-drivers-ubuntu.mdx @@ -70,5 +70,5 @@ If you encounter errors or issues during the installation process, consider the - [NVIDIA NGC Catalog](https://catalog.ngc.nvidia.com/) - [Frameworks Support Matrix - NVIDIA Docs](https://docs.nvidia.com/deeplearning/frameworks/support-matrix/index.html) -- [How to access the GPU using Docker](/compute/gpu/how-to/use-gpu-with-docker/) +- [How to access the GPU using Docker](/gpu/how-to/use-gpu-with-docker/) - [NVIDIA Container Toolkit documentation](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/index.html) \ No newline at end of file diff --git a/compute/instances/api-cli/attaching-a-volume.mdx b/compute/instances/api-cli/attaching-a-volume.mdx index a7cb6916e3..4ecb76b2e9 100644 --- a/compute/instances/api-cli/attaching-a-volume.mdx +++ b/compute/instances/api-cli/attaching-a-volume.mdx @@ -17,9 +17,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- A [Block Storage volume](/block-storage/how-to/create-a-volume/) 1. Query the current volumes of the Instance. @@ -101,7 +101,7 @@ dates: } } ``` -3. Use [SSH](/compute/instances/how-to/connect-to-instance/) to log into your server and verify that the new disk exists: +3. Use [SSH](/instances/how-to/connect-to-instance/) to log into your server and verify that the new disk exists: ```bash lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT diff --git a/compute/instances/api-cli/cli-cheatsheet.mdx b/compute/instances/api-cli/cli-cheatsheet.mdx index b232d0913e..d602ef845e 100644 --- a/compute/instances/api-cli/cli-cheatsheet.mdx +++ b/compute/instances/api-cli/cli-cheatsheet.mdx @@ -16,7 +16,7 @@ This page shows the most common Scaleway CLI commands for creating and managing -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization diff --git a/compute/instances/api-cli/creating-a-volume.mdx b/compute/instances/api-cli/creating-a-volume.mdx index 5d71e97353..a8a1c5f601 100644 --- a/compute/instances/api-cli/creating-a-volume.mdx +++ b/compute/instances/api-cli/creating-a-volume.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) 1. Create a block volume from the API by launching the following command: diff --git a/compute/instances/api-cli/creating-backups.mdx b/compute/instances/api-cli/creating-backups.mdx index 4c7d1acf67..6fcb40254b 100644 --- a/compute/instances/api-cli/creating-backups.mdx +++ b/compute/instances/api-cli/creating-backups.mdx @@ -13,13 +13,13 @@ categories: - compute --- -The Backup feature is used to back up your Instance data. It creates an image of a snapshot that contains all your volumes. You can create backups of your Instances using either the [Scaleway CLI tool](/developer-tools/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/instance/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - A running Instance ## Creating a backup @@ -27,7 +27,7 @@ The Backup feature is used to back up your Instance data. It creates an image of - Use the following commands to create a backup of your Instance using the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/). + Use the following commands to create a backup of your Instance using the [Scaleway CLI](/scaleway-cli/quickstart/). ```sh scw instance server backup server-id zone=fr-par-1 ``` diff --git a/compute/instances/api-cli/creating-managing-instances-with-cliv2.mdx b/compute/instances/api-cli/creating-managing-instances-with-cliv2.mdx index 2fa106f8de..7b8649517b 100644 --- a/compute/instances/api-cli/creating-managing-instances-with-cliv2.mdx +++ b/compute/instances/api-cli/creating-managing-instances-with-cliv2.mdx @@ -13,7 +13,7 @@ categories: - compute --- -Scaleway Instances provide you with resources to develop, test code and deploy your applications in no time. Instances are designed for modern workflows. They are with you from prototyping to large-scale deployment. You can [create](/compute/instances/how-to/create-an-instance/) and manage your Instances from the [console](https://console.scaleway.com/login), via the [API](https://www.scaleway.com/en/developers/api/instance/) or the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). +Scaleway Instances provide you with resources to develop, test code and deploy your applications in no time. Instances are designed for modern workflows. They are with you from prototyping to large-scale deployment. You can [create](/instances/how-to/create-an-instance/) and manage your Instances from the [console](https://console.scaleway.com/login), via the [API](https://www.scaleway.com/en/developers/api/instance/) or the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). ## Scaleway Command Line Interface (CLI) overview @@ -22,9 +22,9 @@ Scaleway Instances provide you with resources to develop, test code and deploy y - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the [Scaleway CLI v2](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) ## Configuring the CLI @@ -53,7 +53,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y ``` Enter a valid secret-key or an email ``` -3. Enter either the email address for your account (you will then be asked for your password), or your [API secret key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/): +3. Enter either the email address for your account (you will then be asked for your password), or your [API secret key](/organizations-and-projects/how-to/create-ssh-key/): ``` To improve this tool we rely on diagnostic and usage data. Sending such data is optional and can be disabled at any time by running "scw config set send-telemetry=false". @@ -119,7 +119,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y `scw instance server create zone=xx-xxx-x image=ubuntu_focal` - Replace `xx-xxx-x` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/compute/instances/concepts/#availability-zone) for more information about Availability Zones. + Replace `xx-xxx-x` with the Availability Zone you want to create your Instance in. If you want your Availability Zone to be France, Paris 1, for example, use `fr-par-1`. Refer to our [documentation](/instances/concepts/#availability-zone) for more information about Availability Zones. You will see an output like the following: @@ -191,7 +191,7 @@ Scaleway Instances provide you with resources to develop, test code and deploy y ## Creating and attaching a block volume to an Instance -1. Run the following command to create a [block volume](/compute/instances/concepts/#block-volumes): +1. Run the following command to create a [block volume](/instances/concepts/#block-volumes): `scw instance volume create size=10GB volume-type=b_ssd` diff --git a/compute/instances/api-cli/detaching-a-volume.mdx b/compute/instances/api-cli/detaching-a-volume.mdx index 6855680feb..4b7ed98055 100644 --- a/compute/instances/api-cli/detaching-a-volume.mdx +++ b/compute/instances/api-cli/detaching-a-volume.mdx @@ -16,7 +16,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization To detach a block volume from a running Instance, relaunch the API call and omit the volume you want to hot unplug. Like so: diff --git a/compute/instances/api-cli/increasing-volume-size.mdx b/compute/instances/api-cli/increasing-volume-size.mdx index af57a056f3..10516d807e 100644 --- a/compute/instances/api-cli/increasing-volume-size.mdx +++ b/compute/instances/api-cli/increasing-volume-size.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Block Storage volume](/compute/instances/api-cli/creating-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- A [Block Storage volume](/instances/api-cli/creating-a-volume/) 1. Inspect the volume and verify its name, size, and if the type is `b_ssd` by running the following request. diff --git a/compute/instances/api-cli/managing-instance-snapshot-via-cli.mdx b/compute/instances/api-cli/managing-instance-snapshot-via-cli.mdx index e2eeb04f12..b6961d6051 100644 --- a/compute/instances/api-cli/managing-instance-snapshot-via-cli.mdx +++ b/compute/instances/api-cli/managing-instance-snapshot-via-cli.mdx @@ -18,9 +18,9 @@ You can use the Scaleway CLI to create, export, and import snapshots of your Ins - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the [Scaleway CLI v2](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) ## Creating a snapshot using the CLI diff --git a/compute/instances/api-cli/migrating-instances.mdx b/compute/instances/api-cli/migrating-instances.mdx index 596d18a5a9..aa8367d26f 100644 --- a/compute/instances/api-cli/migrating-instances.mdx +++ b/compute/instances/api-cli/migrating-instances.mdx @@ -13,14 +13,14 @@ categories: - compute --- -It is possible to change the commercial type of an Instance by using the [Scaleway CLI tool](/developer-tools/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 by using the [Scaleway CLI tool](/scaleway-cli/quickstart/) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/). To do so, you need the Instance’s ID and a valid API key. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/), which must be stopped and not be in a placement group +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/), which must be stopped and not be in a placement group diff --git a/compute/instances/api-cli/snapshot-import-export-feature.mdx b/compute/instances/api-cli/snapshot-import-export-feature.mdx index c7d0305e8c..e4fa056e20 100644 --- a/compute/instances/api-cli/snapshot-import-export-feature.mdx +++ b/compute/instances/api-cli/snapshot-import-export-feature.mdx @@ -25,20 +25,20 @@ More information on the QCOW2 file format, and how to use it can be found in the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) with [Block Storage volumes](/storage/block/how-to/create-a-volume/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [snapshot](/compute/instances/how-to/create-a-snapshot/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) with [Block Storage volumes](/block-storage/how-to/create-a-volume/) +- A valid [API key](/iam/how-to/create-api-keys/) +- A [snapshot](/instances/how-to/create-a-snapshot/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Exporting snapshots 1. Create a Scaleway Object Storage bucket. - You need an Object Storage bucket to export your QCOW2 file into. Any bucket that belongs to the same project as the snapshot can be used. However, if you do not have one already, you can [create it](/storage/object/how-to/create-a-bucket/) in the console. + You need an Object Storage bucket to export your QCOW2 file into. Any bucket that belongs to the same project as the snapshot can be used. However, if you do not have one already, you can [create it](/object-storage/how-to/create-a-bucket/) in the console. 2. Create a snapshot from a volume. - To use this functionality, you must [create a snapshot](/compute/instances/how-to/create-a-snapshot/#how-to-create-a-snapshot) from the volume you want to export. + To use this functionality, you must [create a snapshot](/instances/how-to/create-a-snapshot/#how-to-create-a-snapshot) from the volume you want to export. 3. Call the `export` snapshot API endpoint to initiate the snapshot export. For example, using curl: diff --git a/compute/instances/api-cli/using-cloud-init.mdx b/compute/instances/api-cli/using-cloud-init.mdx index 5ecdbbead4..ce7a736947 100644 --- a/compute/instances/api-cli/using-cloud-init.mdx +++ b/compute/instances/api-cli/using-cloud-init.mdx @@ -22,8 +22,8 @@ Cloud-config files are special scripts designed to be run by the cloud-init proc - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded the [latest version of the Scaleway CLI](https://github.com/scaleway/scaleway-cli) ## Provisioning your Instance with Cloud-Init @@ -39,7 +39,7 @@ For `user_data` to be effective, it has to be added prior to the creation of the scw instance server create image=ubuntu_focal name=myinstance cloud-init=@/path/to/cloud-config-file ``` - `@/path/to/cloud-config-file` is the path of your [Cloud-Init](/compute/instances/how-to/use-boot-modes/#how-to-use-cloud-init) configuration file. Edit it as you wish. + `@/path/to/cloud-config-file` is the path of your [Cloud-Init](/instances/how-to/use-boot-modes/#how-to-use-cloud-init) configuration file. Edit it as you wish. 2. Start your Instance ``` diff --git a/compute/instances/api-cli/using-placement-groups.mdx b/compute/instances/api-cli/using-placement-groups.mdx index 02978e17b7..ce7cf7db47 100644 --- a/compute/instances/api-cli/using-placement-groups.mdx +++ b/compute/instances/api-cli/using-placement-groups.mdx @@ -16,11 +16,11 @@ Placement groups allow you to group your Instances. You can choose between two operating modes: `max_availability`, which ensures that Instances of a group do not run on the same underlying hardware, and `low_latency`, which brings Instances closer together to achieve higher network throughput. -If you prefer a visual environment, discover [how to manage placement groups from the Scaleway console](/compute/instances/how-to/use-placement-groups/). +If you prefer a visual environment, discover [how to manage placement groups from the Scaleway console](/instances/how-to/use-placement-groups/). -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Understanding placement groups diff --git a/compute/instances/api-cli/using-routed-ips.mdx b/compute/instances/api-cli/using-routed-ips.mdx index 02d8215dc7..d8f61c7b83 100644 --- a/compute/instances/api-cli/using-routed-ips.mdx +++ b/compute/instances/api-cli/using-routed-ips.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) * The routed IP feature **is not compatible** with legacy Instance types using the bootscript feature. @@ -39,7 +39,7 @@ Another feature of routed IP is the ability to assign multiple flexible IP addre * The routed IP feature is available in all Availability Zones. - * [Dynamic IPs](/compute/instances/concepts/#dynamic-ip) continue to be supported after the transition to routed IPs. + * [Dynamic IPs](/instances/concepts/#dynamic-ip) continue to be supported after the transition to routed IPs. * The field `enable_ipv6` is being deprecated and has no meaning for routed IP enabled Instances. diff --git a/compute/instances/concepts.mdx b/compute/instances/concepts.mdx index 08cd494d68..064e517f0e 100644 --- a/compute/instances/concepts.mdx +++ b/compute/instances/concepts.mdx @@ -16,7 +16,7 @@ categories: An Availability Zone refers to an isolated location within a specific region. Each Availability Zone provides its own services and infrastructure. For example, `fr-par-1`, `fr-par-2`, and `fr-par-3` are Availability Zones within the Paris region. -For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/console/account/reference-content/products-availability/) +For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/) ## Block volumes @@ -33,7 +33,7 @@ This setup ensures that all outbound and inbound traffic for an Instance is tran ## Cloud-init -Cloud-init is a multi-distribution package that [provides boot time customization for cloud servers](/compute/instances/how-to/use-boot-modes/#how-to-use-cloud-init). It enables an automatic Instance configuration as it boots into the cloud, turning a generic Ubuntu image into a configured server in a few seconds. +Cloud-init is a multi-distribution package that [provides boot time customization for cloud servers](/instances/how-to/use-boot-modes/#how-to-use-cloud-init). It enables an automatic Instance configuration as it boots into the cloud, turning a generic Ubuntu image into a configured server in a few seconds. ## Cost-Optimized Instances @@ -51,11 +51,11 @@ You can choose to give your Instance a dynamic IP address when creating or updat ## Flexible IP -Flexible IP addresses are public IP addresses that you can hold independently of any Instance. When you create a Scaleway Instance, by default, its public IP address is also a flexible IP address. Flexible IP addresses can be attached to and detached from any Instances you wish. You can keep a number of flexible IP addresses in your account at any given time. When you delete a flexible IP address, it is disassociated from your account to be used by other users. Find out more with our dedicated documentation on [how to use flexible IP addresses](/compute/instances/how-to/use-flexips/). See also [Dynamic IPs](#dynamic-ip). +Flexible IP addresses are public IP addresses that you can hold independently of any Instance. When you create a Scaleway Instance, by default, its public IP address is also a flexible IP address. Flexible IP addresses can be attached to and detached from any Instances you wish. You can keep a number of flexible IP addresses in your account at any given time. When you delete a flexible IP address, it is disassociated from your account to be used by other users. Find out more with our dedicated documentation on [how to use flexible IP addresses](/instances/how-to/use-flexips/). See also [Dynamic IPs](#dynamic-ip). ## GPU Instance -[GPU Instances](https://www.scaleway.com/en/gpu-instances/) are powerful Instances equipped with dedicated high-end Nvidia graphics processing units. See our [dedicated GPU documentation](/compute/gpu/) for more details. +[GPU Instances](https://www.scaleway.com/en/gpu-instances/) are powerful Instances equipped with dedicated high-end Nvidia graphics processing units. See our [dedicated GPU documentation](/gpu/) for more details. ## Image @@ -63,11 +63,11 @@ An image is a complete backup of your Instance. One image contains all the [volu ## Instance -An Instance is a virtual computing unit that offers resources for running applications. It functions as a self-contained entity with its own operating system, RAM, and storage. Each type of Instance has unique specifications. You can choose the type that best meets your requirements. Refer to our [Instance types documentation](/compute/instances/reference-content/choosing-instance-type/) for further details on the various Scaleway Instance options. +An Instance is a virtual computing unit that offers resources for running applications. It functions as a self-contained entity with its own operating system, RAM, and storage. Each type of Instance has unique specifications. You can choose the type that best meets your requirements. Refer to our [Instance types documentation](/instances/reference-content/choosing-instance-type/) for further details on the various Scaleway Instance options. ## InstantApp -An InstantApp is an image with a preinstalled application. By choosing an InstantApp when prompted to select an image during the [creation of your Instance](/compute/instances/how-to/create-an-instance/), you choose to install the specified application on your Instance. You can then start using the application immediately. +An InstantApp is an image with a preinstalled application. By choosing an InstantApp when prompted to select an image during the [creation of your Instance](/instances/how-to/create-an-instance/), you choose to install the specified application on your Instance. You can then start using the application immediately. ## IP mobility @@ -91,7 +91,7 @@ The local volume of an Instance is an all-SSD-based storage solution, using a RA ## Placement groups -Placement groups allow you to run multiple Compute Instances, each on a different physical hypervisor. Placement groups have two operating modes. The first one is called `max_availability`. It ensures that all the Compute Instances that belong to the same cluster will not run on the same underlying hardware. The second one is called `low_latency` and does the opposite, bringing Compute Instances closer together to achieve higher network throughput. [Learn how to use placement groups](/compute/instances/how-to/use-placement-groups/). +Placement groups allow you to run multiple Compute Instances, each on a different physical hypervisor. Placement groups have two operating modes. The first one is called `max_availability`. It ensures that all the Compute Instances that belong to the same cluster will not run on the same underlying hardware. The second one is called `low_latency` and does the opposite, bringing Compute Instances closer together to achieve higher network throughput. [Learn how to use placement groups](/instances/how-to/use-placement-groups/). ## Production-Optimized Instances @@ -105,7 +105,7 @@ Three variants of POP2 Instances are available: ## Power-off mode -The Power-off mode [shuts down an Instance](/compute/instances/how-to/power-off-instance/) by transferring all data on the local volume of the Instance to a volume store. The physical node is released back to the pool of available machines. The reserved flexible IP of the Instance remains available in the account. +The Power-off mode [shuts down an Instance](/instances/how-to/power-off-instance/) by transferring all data on the local volume of the Instance to a volume store. The physical node is released back to the pool of available machines. The reserved flexible IP of the Instance remains available in the account. Depending on the amount of data to be archived, this process can take some time. @@ -113,13 +113,13 @@ The Power-off mode [shuts down an Instance](/compute/instances/how-to/power-off- ## Private Networks -Private Networks allow your virtual Instances to communicate in an isolated and secure network without requiring a connection to the public internet. Each Instance can be [connected to one or several Private Networks](/compute/instances/how-to/use-private-networks/), letting you build your own network topologies. +Private Networks allow your virtual Instances to communicate in an isolated and secure network without requiring a connection to the public internet. Each Instance can be [connected to one or several Private Networks](/instances/how-to/use-private-networks/), letting you build your own network topologies. Private Networks are LAN-like layer 2 Ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Use this interface to communicate in a secure and isolated network, using private IP addresses of your choice. ## Protected Instance -Protected Instance is a feature that prevents any halt action from being performed on your Instance. This only applies to running Instances. [Enabling the Protected Instance feature](/compute/instances/how-to/use-protected-instance/) means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. +Protected Instance is a feature that prevents any halt action from being performed on your Instance. This only applies to running Instances. [Enabling the Protected Instance feature](/instances/how-to/use-protected-instance/) means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. ## Public IP @@ -129,31 +129,31 @@ Public IP addresses are routed on the internet. You can enter the public IP addr A region is a geographical area such as France (Paris: fr-par), the Netherlands (Amsterdam: nl-ams), or Poland (Warsaw: pl-waw) in which Scaleway products and resources are located. Each region contains multiple Availability Zones. -For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/console/account/reference-content/products-availability/) +For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/) ## Rescue mode -Rescue mode restarts your server via the network on a minimal operating system. You can [use rescue mode](/compute/instances/how-to/use-boot-modes/#how-to-use-rescue-mode) to debug your server and recover your system data. Rescue mode creates a ramdisk with the content of a downloaded rootfs. You will have access to all your disks and will be able to perform debug and rescue actions. After disabling rescue mode, you will have to reboot your server. Your server needs to be running to switch to rescue mode. +Rescue mode restarts your server via the network on a minimal operating system. You can [use rescue mode](/instances/how-to/use-boot-modes/#how-to-use-rescue-mode) to debug your server and recover your system data. Rescue mode creates a ramdisk with the content of a downloaded rootfs. You will have access to all your disks and will be able to perform debug and rescue actions. After disabling rescue mode, you will have to reboot your server. Your server needs to be running to switch to rescue mode. ## Reverse DNS -Reverse DNS is the opposite of classic "forward" DNS, and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your Instance. Find out how to [configure reverse DNS on your Instance](/compute/instances/how-to/configure-reverse-dns/) with our how-to documentation. +Reverse DNS is the opposite of classic "forward" DNS, and maps an IP address to a hostname. This can be useful if, for example, you want to send emails from your Instance. Find out how to [configure reverse DNS on your Instance](/instances/how-to/configure-reverse-dns/) with our how-to documentation. ## Routed flexible IP -A routed flexible IP means assigning a public IP address to an Instance (virtual machine) that is reachable directly from the internet. This means there's [no address translation](/compute/instances/concepts/#carrier-grade-nat-cgnat), and the Instance uses the public IP as its identity on the internet. +A routed flexible IP means assigning a public IP address to an Instance (virtual machine) that is reachable directly from the internet. This means there's [no address translation](/instances/concepts/#carrier-grade-nat-cgnat), and the Instance uses the public IP as its identity on the internet. The Instance can be accessed or can communicate directly using this public IP, which helps to make network configuration straightforward, with unrestricted inbound and outbound connections, crucial for services like web hosting or email servers. ## Security group -Security groups allow you to [create rules to drop or allow public traffic coming to and from your Instances](/compute/instances/how-to/use-security-groups/). You can set default policies for inbound and outbound traffic, and/or define rules to deal with traffic differently depending on its source. Security groups can be [stateful](#stateful-security-groups) or [stateless](#stateless-security-groups). Note that security groups for Elastic Metal servers cannot be stateful. +Security groups allow you to [create rules to drop or allow public traffic coming to and from your Instances](/instances/how-to/use-security-groups/). You can set default policies for inbound and outbound traffic, and/or define rules to deal with traffic differently depending on its source. Security groups can be [stateful](#stateful-security-groups) or [stateless](#stateless-security-groups). Note that security groups for Elastic Metal servers cannot be stateful. Security Groups only allow the filtering of **public** traffic to and from your Instances. To filter traffic within a Private Network, you can [configure a firewall](/tutorials/installation-uncomplicated-firewall/) directly on your Instance, or use `iptables` or `nftables` from the command line interface of your Instance. ## Snapshot -A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/compute/instances/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance. +A snapshot takes a picture of a specific volume at one point in time. For example, you may have a server with one volume containing the OS and another containing the application data and want to use different snapshot strategies on both volumes. [Creating snapshots of your volumes](/instances/how-to/create-a-snapshot/) gives you total freedom of which volumes you want to back up, while [images](#image) are more convenient for full backups of your Instance. ## Snapshot type @@ -161,15 +161,15 @@ An image is composed of snapshots of volumes. Snapshots can only be restored to ## Standby mode -Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/compute/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the Local Storage of the Instance. +Standby mode is a way to stop an Instance temporarily. When you [put an Instance in standby mode](/instances/how-to/use-standby-mode/), the server is halted, but the Instance remains allocated to your account, and all data remains on the Local Storage of the Instance. ## Stateful security groups -Stateful security groups disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. Traffic will always be permitted on connections that you initiated. This is useful for example if you want to initiate connections on many and various ports for messaging, video streaming, or other purposes. In this case, the traffic from/to that connection will not be blocked, even if you have defined a rule that would otherwise do so. [Learn how to use security groups](/compute/instances/how-to/use-security-groups/). +Stateful security groups disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. Traffic will always be permitted on connections that you initiated. This is useful for example if you want to initiate connections on many and various ports for messaging, video streaming, or other purposes. In this case, the traffic from/to that connection will not be blocked, even if you have defined a rule that would otherwise do so. [Learn how to use security groups](/instances/how-to/use-security-groups/). ## Stateless security groups -Stateless security groups strictly apply the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance or not. This is useful if you know exactly which ports you will always require for your Instance, e.g. port `22` for SSH. You can make your security group stateless, define a rule to allow traffic on port `22` and block incoming traffic on other ports regardless of whether a connection is initiated from your Instance on this port. [Learn how to use security groups](/compute/instances/how-to/use-security-groups/). +Stateless security groups strictly apply the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance or not. This is useful if you know exactly which ports you will always require for your Instance, e.g. port `22` for SSH. You can make your security group stateless, define a rule to allow traffic on port `22` and block incoming traffic on other ports regardless of whether a connection is initiated from your Instance on this port. [Learn how to use security groups](/instances/how-to/use-security-groups/). ## Tags diff --git a/compute/instances/how-to/configure-reverse-dns.mdx b/compute/instances/how-to/configure-reverse-dns.mdx index 106bff7c4f..fab048399c 100644 --- a/compute/instances/how-to/configure-reverse-dns.mdx +++ b/compute/instances/how-to/configure-reverse-dns.mdx @@ -22,8 +22,8 @@ Reverse DNS is the opposite of classic "forward" DNS and maps an IP address to a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) with its public (flexible) IP address attached to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) with its public (flexible) IP address attached to it - Configured a matching `A-record` pointing to your IP address. Note that if you have created the A record recently, it may take up to 24 hours for the operation to be completed. ## How to set up a reverse DNS record diff --git a/compute/instances/how-to/connect-to-instance.mdx b/compute/instances/how-to/connect-to-instance.mdx index e6ca64d565..986afa6e39 100644 --- a/compute/instances/how-to/connect-to-instance.mdx +++ b/compute/instances/how-to/connect-to-instance.mdx @@ -18,9 +18,9 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) @@ -66,7 +66,7 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the 4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. Do this by expanding **Connection**, then **SSH**, and finally clicking on **Auth**: - 5. Click the **Browse** button and select the private key file you [generated previously](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/). + 5. Click the **Browse** button and select the private key file you [generated previously](/organizations-and-projects/how-to/create-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the Instance. Upon the first connection, PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. @@ -116,4 +116,4 @@ This page shows how to connect to your Scaleway Instance via SSH. Thanks to the ## Troubleshooting connection problems -If you have any problems connecting to your Instance via SSH, refer to our [dedicated troubleshooting document](/compute/instances/troubleshooting/cant-connect-ssh/). +If you have any problems connecting to your Instance via SSH, refer to our [dedicated troubleshooting document](/instances/troubleshooting/cant-connect-ssh/). diff --git a/compute/instances/how-to/create-a-backup.mdx b/compute/instances/how-to/create-a-backup.mdx index 4b2cb7102d..2285ad3522 100644 --- a/compute/instances/how-to/create-a-backup.mdx +++ b/compute/instances/how-to/create-a-backup.mdx @@ -18,15 +18,15 @@ The image feature lets you create an image of your Instance, which contains all This feature is available on Instance types. Creating images of your Instance is free. However, keep in mind that as the image feature creates snapshots of your volumes, you will be billed for these snapshots. - This creates an image that is a complete backup of your Instance including **all** of its volumes. The [snapshot](/compute/instances/concepts/#snapshot) feature, on the other hand, creates snapshots of specific volumes. Consider [creating a snapshot](/compute/instances/how-to/create-a-snapshot/) if you want to use different snapshot strategies for different volumes of your Instance, e.g., if it has one volume containing the OS and another containing application data. + This creates an image that is a complete backup of your Instance including **all** of its volumes. The [snapshot](/instances/concepts/#snapshot) feature, on the other hand, creates snapshots of specific volumes. Consider [creating a snapshot](/instances/how-to/create-a-snapshot/) if you want to use different snapshot strategies for different volumes of your Instance, e.g., if it has one volume containing the OS and another containing application data. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) ## How to create an image @@ -48,7 +48,7 @@ There are two different ways to create a new Instance from your image: ### Using the Instance creation wizard -Follow the instructions for [creating an Instance](/compute/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My images** tab, and select the desired image. +Follow the instructions for [creating an Instance](/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My images** tab, and select the desired image. A new Instance is created from your image. diff --git a/compute/instances/how-to/create-a-block-volume.mdx b/compute/instances/how-to/create-a-block-volume.mdx index 055b88582b..219526bd50 100644 --- a/compute/instances/how-to/create-a-block-volume.mdx +++ b/compute/instances/how-to/create-a-block-volume.mdx @@ -17,7 +17,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. @@ -30,8 +30,8 @@ categories: 5. Enter the volume name and select a size. 6. Configure the volume type. You can either create a **Block Storage** or **Local Storage** volume. - To use **[Block Storage Low Latency](/storage/block/) 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](/compute/instances/reference-content/instances-bandwidth-overview/) documentation. + To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. + You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. @@ -39,5 +39,5 @@ categories: 7. Click **Create volume** to confirm. - You can also [create](/storage/block/how-to/create-a-volume/) Block Storage volumes from the [Block Storage console section](https://console.scaleway.com/block-storage/). + You can also [create](/block-storage/how-to/create-a-volume/) Block Storage volumes from the [Block Storage console section](https://console.scaleway.com/block-storage/). \ No newline at end of file diff --git a/compute/instances/how-to/create-a-snapshot.mdx b/compute/instances/how-to/create-a-snapshot.mdx index 277d3db3c9..25f6877098 100644 --- a/compute/instances/how-to/create-a-snapshot.mdx +++ b/compute/instances/how-to/create-a-snapshot.mdx @@ -13,7 +13,7 @@ categories: - compute --- -The snapshot feature allows you to create an image of a specific [volume](/compute/instances/concepts/#volumes) of your Instance. A snapshot is a full-volume copy stored in our secure data centers. They are usually used to recover volume data or to create a copy of a volume. +The snapshot feature allows you to create an image of a specific [volume](/instances/concepts/#volumes) of your Instance. A snapshot is a full-volume copy stored in our secure data centers. They are usually used to recover volume data or to create a copy of a volume. Several options are available to create snapshots from your Instance: @@ -21,15 +21,15 @@ Several options are available to create snapshots from your Instance: * **BSSD (Block Storage):** This snapshot type can be created from block volumes. BSSD snapshots can be converted to block volumes only. - The snapshot feature creates backups of specific volumes only. If you wish to create a backup image that is a complete backup of your Instance including **all** of its volumes, check out our documentation on [how to create an image](/compute/instances/how-to/create-a-backup/). + The snapshot feature creates backups of specific volumes only. If you wish to create a backup image that is a complete backup of your Instance including **all** of its volumes, check out our documentation on [how to create an image](/instances/how-to/create-a-backup/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) ## How to create a snapshot @@ -46,7 +46,7 @@ Several options are available to create snapshots from your Instance: ## How to create a volume from a snapshot -You can create a [volume](/compute/instances/concepts/#volumes) from a snapshot as follows: +You can create a [volume](/instances/concepts/#volumes) from a snapshot as follows: 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the **Snapshots** tab. @@ -58,11 +58,11 @@ You can create a [volume](/compute/instances/concepts/#volumes) from a snapshot The available volume types may change according to the type of snapshot you select. - The volume is created, and can be viewed in the [Volumes tab](https://console.scaleway.com/instance/volumes). Check out our documentation on [attaching volumes](/storage/block/how-to/attach-a-volume/) and [mounting volumes](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) to learn how to use the volume with your Instances. + The volume is created, and can be viewed in the [Volumes tab](https://console.scaleway.com/instance/volumes). Check out our documentation on [attaching volumes](/block-storage/how-to/attach-a-volume/) and [mounting volumes](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) to learn how to use the volume with your Instances. ## How to create an Instance from a snapshot -Follow the instructions for [creating an Instance](/compute/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My snapshots** tab, and select the desired snapshot. +Follow the instructions for [creating an Instance](/instances/how-to/create-an-instance/). At the **Choose an image** step of the creation wizard, click the **My snapshots** tab, and select the desired snapshot. diff --git a/compute/instances/how-to/create-an-instance.mdx b/compute/instances/how-to/create-an-instance.mdx index 745ac12008..670fba5c00 100644 --- a/compute/instances/how-to/create-an-instance.mdx +++ b/compute/instances/how-to/create-an-instance.mdx @@ -13,7 +13,7 @@ categories: - compute --- -This page shows how to create your first Scaleway Instance. An [Instance](/compute/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](/compute/instances/reference-content/choosing-instance-type/) you choose. After you have created your Instance you can [connect](/compute/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. +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). @@ -24,23 +24,23 @@ Select a tab below for instructions on how to create an Instance via either our - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - An [Instance](/compute/instances/how-to/create-an-instance/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) + - An [Instance](/instances/how-to/create-an-instance/) 1. Click **Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. 3. Complete the following steps: - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed. - **Choose an Instance type**.
- Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/). + Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). - **Choose an image** to run on your Instance.
- This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/). - - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance. + This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/). + - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB. - - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). + - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. - **Configure network** of the Instance. @@ -49,13 +49,13 @@ Select a tab below for instructions on how to create an Instance via either our You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance. - - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. + - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot. - - **Verify the [SSH keys](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. + - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. - **Verify the Estimated cost** of your Instance, based on the specifications you chose. 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. - Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/compute/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. + Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the SSH command to use to [connect to it](/instances/how-to/create-an-instance/), and other information, settings, and actions for the Instance. @@ -63,9 +63,9 @@ Select a tab below for instructions on how to create an Instance via either our - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - An [RSA key pair](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair) - - An [Instance](/compute/instances/how-to/create-an-instance/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - An [RSA key pair](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair) + - An [Instance](/instances/how-to/create-an-instance/) 1. Click **Instances** in the **Compute** section of the side menu. The [Instance dashboard](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation page](https://console.scaleway.com/instance/servers) displays. @@ -73,16 +73,16 @@ Select a tab below for instructions on how to create an Instance via either our - Choose an **Availability Zone**, which represents the geographical region where your Instance will be deployed. - **Choose a POP2-WIN** Instance type from the **Production-Optimized** range. - **Choose a Windows Server image** to run on your Instance. - - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance. + - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - **Add volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - Ensure that a volume containing a Windows Server image has a minimum capacity of 25 GB. - - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). + - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. - To use **[Block Storage Low Latency](/storage/block/) 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](/compute/instances/reference-content/instances-bandwidth-overview/) documentation. + To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. + You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. @@ -93,13 +93,13 @@ Select a tab below for instructions on how to create an Instance via either our You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance. - - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. + - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot. - - **Choose the [RSA SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)** that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated. + - **Choose the [RSA SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-a-rsa-ssh-key-pair)** that will give you access to your Instance. If you do not have an RSA SSH key yet, click **Add RSA SSH key** and follow the steps indicated. - Verify the **Estimated cost** of your Instance, based on the specifications you chose. 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. - Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the command to use to [retrieve the password and connect to it](/compute/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. + Your Instance is now created, and you are redirected to the **Overview** tab. From here, you can see information including your Instance's Public IP, the command to use to [retrieve the password and connect to it](/instances/how-to/connect-to-instance/), and other information, settings, and actions for the Instance. @@ -107,18 +107,18 @@ Select a tab below for instructions on how to create an Instance via either our - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) + - A valid [API key](/iam/how-to/create-api-keys/) - Installed [curl](https://curl.se/) on your local machine 1. Open a terminal and configure your environment variables with the `export` commands shown below. This is an optional step that seeks to simplify your usage of the API. Ensure that you replace the variables represented by triangle brackets in the example below with your own customized values: - - The API [access key and secret key](/identity-and-access-management/iam/concepts/#api-key) that you created. - - The Project ID of the [Project](/identity-and-access-management/iam/concepts/#project) you want to create the Instance in. You can find your Project ID in the [**Settings** tab](https://console.scaleway.com/project/settings) of the relevant Project in the Scaleway console. - - The [Availability Zone](/compute/instances/concepts/#availability-zone) you want to create the Instance in, e.g. `fr-par-1`. + - The API [access key and secret key](/iam/concepts/#api-key) that you created. + - The Project ID of the [Project](/iam/concepts/#project) you want to create the Instance in. You can find your Project ID in the [**Settings** tab](https://console.scaleway.com/project/settings) of the relevant Project in the Scaleway console. + - The [Availability Zone](/instances/concepts/#availability-zone) you want to create the Instance in, e.g. `fr-par-1`. ```bash @@ -207,10 +207,10 @@ Select a tab below for instructions on how to create an Instance via either our - A Scaleway account logged into the [console](https://console.scaleway.com) - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) + - A valid [API key](/iam/how-to/create-api-keys/) - Installed and configured the [Scaleway CLI](https://github.com/scaleway/scaleway-cli) on your local machine 1. Get the label of your OS of choice. diff --git a/compute/instances/how-to/create-image-from-snapshot.mdx b/compute/instances/how-to/create-image-from-snapshot.mdx index 866b05e90d..3bbb3dfe9b 100644 --- a/compute/instances/how-to/create-image-from-snapshot.mdx +++ b/compute/instances/how-to/create-image-from-snapshot.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) -- At least one [snapshot](/compute/instances/how-to/create-a-snapshot/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) +- At least one [snapshot](/instances/how-to/create-a-snapshot/) ## Creating an image from a snapshot via the Scaleway console @@ -39,7 +39,7 @@ categories: ## Creating an image via the Scaleway CLI -You can also create an image using the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/). Use the following command: +You can also create an image using the [Scaleway CLI](/scaleway-cli/quickstart/). Use the following command: ```bash scw instance image create snapshot-id="$SCW_VOLUME_ID_1" additional-volumes.0.id="$SCW_VOLUME_ID_2" arch="x86_64" diff --git a/compute/instances/how-to/delete-instance.mdx b/compute/instances/how-to/delete-instance.mdx index c9829ddcaa..03257c6b98 100644 --- a/compute/instances/how-to/delete-instance.mdx +++ b/compute/instances/how-to/delete-instance.mdx @@ -22,8 +22,8 @@ This page shows you how to delete an Instance. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to delete an Instance diff --git a/compute/instances/how-to/manage-volumes.mdx b/compute/instances/how-to/manage-volumes.mdx index 0fd17a969e..240fb4cf1d 100644 --- a/compute/instances/how-to/manage-volumes.mdx +++ b/compute/instances/how-to/manage-volumes.mdx @@ -16,13 +16,13 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Block Storage volume](/block-storage/how-to/create-a-volume/) ## How to attach a volume - You must have created a [volume](/compute/instances/how-to/create-a-block-volume/) that is not attached to any of your Instances before proceeding with the steps below. + You must have created a [volume](/instances/how-to/create-a-block-volume/) that is not attached to any of your Instances before proceeding with the steps below. 1. Click **Instances** from the left side menu. The Instances section displays. @@ -32,11 +32,11 @@ categories: 5. Click **Attach volume to Instance**. - Find out [how to mount a Block Storage volume to your Instance](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume). + Find out [how to mount a Block Storage volume to your Instance](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume). - To use **[Block Storage Low Latency](/storage/block/) 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](/compute/instances/reference-content/instances-bandwidth-overview/) documentation. + To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. + You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. @@ -52,18 +52,18 @@ categories: - Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase the partition size of your volume. + Refer to our [dedicated documentation](/block-storage/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase the partition size of your volume. ## How to detach a volume -You can detach a Block Storage volume from your Instance at any time. It is important to [unmount (detach) the device](/storage/block/api-cli/unmounting-a-volume/) from the operating system before detaching the Block Storage volume to avoid data loss. +You can detach a Block Storage volume from your Instance at any time. It is important to [unmount (detach) the device](/block-storage/api-cli/unmounting-a-volume/) from the operating system before detaching the Block Storage volume to avoid data loss. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Block Storage volume](/storage/block/concepts/#block-device) attached to a Scaleway Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Block Storage volume](/block-storage/concepts/#block-device) attached to a Scaleway Instance 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the Instance with the volume you want to detach. The Instance information page displays. @@ -74,7 +74,7 @@ You can detach a Block Storage volume from your Instance at any time. It is impo ## How to delete a volume - You must detach a Block Storage volume from an Instance to delete it. Refer to our [documentation](/storage/block/how-to/detach-a-volume/) to find out how to do so. + You must detach a Block Storage volume from an Instance to delete it. Refer to our [documentation](/block-storage/how-to/detach-a-volume/) to find out how to do so. 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. diff --git a/compute/instances/how-to/migrate-instances.mdx b/compute/instances/how-to/migrate-instances.mdx index 0033c3948d..0016de79df 100644 --- a/compute/instances/how-to/migrate-instances.mdx +++ b/compute/instances/how-to/migrate-instances.mdx @@ -13,20 +13,20 @@ categories: - compute --- -The Scaleway platform makes it very easy to migrate your data from one Instance to another or upgrade your Instance to a more powerful one if your requirements grow. In this how-to, we will upgrade an Instance by migrating from a [DEV1-S](/compute/instances/concepts/#development-instance) Instance to a [GP1-XS](/compute/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance. The new GP1-XS Instance will have the same [flexible IP](/compute/instances/concepts/#flexible-ip) as the original DEV1-S Instance. +The Scaleway platform makes it very easy to migrate your data from one Instance to another or upgrade your Instance to a more powerful one if your requirements grow. In this how-to, we will upgrade an Instance by migrating from a [DEV1-S](/instances/concepts/#development-instance) Instance to a [GP1-XS](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance. The new GP1-XS Instance will have the same [flexible IP](/instances/concepts/#flexible-ip) as the original DEV1-S Instance. -For more information about choosing the best Instance type to migrate to for your use case, see our [dedicated documentation](/compute/instances/reference-content/choosing-instance-type/). +For more information about choosing the best Instance type to migrate to for your use case, see our [dedicated documentation](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) (We are using a DEV1-S Instance) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) (We are using a DEV1-S Instance) ## How to back up the Instance -Follow the instructions to [create an image](/compute/instances/how-to/create-a-backup/#how-to-create-an-image) of your Instance. +Follow the instructions to [create an image](/instances/how-to/create-a-backup/#how-to-create-an-image) of your Instance. ## How to create a new Instance from an image @@ -36,13 +36,13 @@ Follow the instructions to [create an image](/compute/instances/how-to/create-a- 4. Click next to the Instance's image. 5. Select **Create Instance from image** on the drop-down list. You are redirected to the Instance Creation Wizard, where the image has been preselected for you at step 2. 6. Finish configuring the Instance according to your requirements. Notably: - - You are free to choose your Instance type. We chose to create a [GP1-XS](/compute/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance, upgrading from the [DEV1-S](/compute/instances/concepts/#development-instance) on which the image was based. + - You are free to choose your Instance type. We chose to create a [GP1-XS](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances) Instance, upgrading from the [DEV1-S](/instances/concepts/#development-instance) on which the image was based. - Click **Advanced options** and use the toggle to deselect **flexible IP**. This creates a the new Instance without a flexible IP, as we are going to attach the one from the existing Instance in the next step. 7. Click **Create Instance** to finish. The Instance is created and shows in your Instances list. ## How to move a flexible IP to a new Instance -Next, we will move the original DEV1-S Instance's [flexible IP address](/compute/instances/concepts/#flexible-ip) to the new GP1-XS Instance. +Next, we will move the original DEV1-S Instance's [flexible IP address](/instances/concepts/#flexible-ip) to the new GP1-XS Instance. 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the **Flexible IPs** tab. @@ -53,6 +53,6 @@ Next, we will move the original DEV1-S Instance's [flexible IP address](/compute ## How to delete the old Instance -Presuming that you no longer need the original DEV1-S Instance, you can [delete it](/compute/instances/how-to/delete-instance/). +Presuming that you no longer need the original DEV1-S Instance, you can [delete it](/instances/how-to/delete-instance/). diff --git a/compute/instances/how-to/migrate-routed-ips.mdx b/compute/instances/how-to/migrate-routed-ips.mdx index 227553e062..20d9b78cd4 100644 --- a/compute/instances/how-to/migrate-routed-ips.mdx +++ b/compute/instances/how-to/migrate-routed-ips.mdx @@ -13,24 +13,24 @@ categories: - compute --- -Prior to April 2024, all Instances got a NAT IP from their hosting node, which was routed to the Instance through a [carrier-grade NAT](/compute/instances/concepts/#carrier-grade-nat-cgnat) solution. This was in addition to the public (flexible) IP. The NAT IP let Instances communicate via an underlying internal network, without public IPs. However, if the underlying hypervisor changed, the NAT IP changed also. This could happen when you restarted your Instance. +Prior to April 2024, all Instances got a NAT IP from their hosting node, which was routed to the Instance through a [carrier-grade NAT](/instances/concepts/#carrier-grade-nat-cgnat) solution. This was in addition to the public (flexible) IP. The NAT IP let Instances communicate via an underlying internal network, without public IPs. However, if the underlying hypervisor changed, the NAT IP changed also. This could happen when you restarted your Instance. -Since October 2024 it is no no longer possible to create Instances with NAT IPs. Instead, Instances' public IPs are **routed** IPs. Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/compute/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported. +Since October 2024 it is no no longer possible to create Instances with NAT IPs. Instead, Instances' public IPs are **routed** IPs. Routing a public IP directly to an Instance bypasses NAT IPs, sending traffic to its [routed flexible IP](/instances/concepts/#routed-flexible-ip). The benefit is the IP stays consistent even if the Instance is restarted or moved. Routed IPs also let you assign multiple flexible IPv4s and IPv6s to an Instance, as both IPv4 and IPv6 are supported. In addition to the benefits explained above, routed IPs allow precise control over network configurations, simplify troubleshooting, ensure compatibility with more applications, and allow for enhanced security monitoring. We recommend that users with Instances still using NAT IPs move them to routed IPs by following the instructions below. * The routed IP feature **is incompatible** with legacy Instance types using the bootscript feature. * Ensure no static network configuration is in use for your public network interface (usually `ens2` or `eth0`) - * Ensure that you are not using the internal private IP of the Instance for internal communications. Instead, [attach your Instances to a VPC](/network/vpc/how-to/attach-resources-to-pn/). + * Ensure that you are not using the internal private IP of the Instance for internal communications. Instead, [attach your Instances to a VPC](/vpc/how-to/attach-resources-to-pn/). * You must update the `scaleway-ecosystem` and `cloud-init` packages before starting transition. - * Before proceeding with the migration, please review the [FAQ on IP autoconfiguration limitations](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature) and the [guide to fix unreachable Ubuntu Focal Instances with multiple public IPs](/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). These resources provide important information to ensure a seamless migration process. + * Before proceeding with the migration, please review the [FAQ on IP autoconfiguration limitations](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature) and the [guide to fix unreachable Ubuntu Focal Instances with multiple public IPs](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). These resources provide important information to ensure a seamless migration process. - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/compute/instances/how-to/create-an-instance/) that has not been moved to routed IPs +- An [Instance](/instances/how-to/create-an-instance/) that has not been moved to routed IPs ## Updating the required packages @@ -45,7 +45,7 @@ Before proceeding with the migration, consider the following guidelines regardin - `scaleway-ecosystem`: Older Instances may not have this package installed. In such cases, no action is required. - `cloud-init`: This package is commonly pre-installed on Instances due to its inclusion in upstream cloud images. For older Instances, a legacy version of `cloud-init` may not impact IPv4 functionality, but IPv6 functionality could be inconsistent with outdated versions. -To check if `scaleway-ecosystem` and `cloud-init` are installed and to update them if needed, [log into your Instance using SSH](/compute/instances/how-to/connect-to-instance/) and run the following commands: +To check if `scaleway-ecosystem` and `cloud-init` are installed and to update them if needed, [log into your Instance using SSH](/instances/how-to/connect-to-instance/) and run the following commands: * For **Ubuntu and Debian** Instances: ```bash @@ -76,7 +76,7 @@ If `scaleway-ecosystem` is not installed, no additional steps are needed for thi After the transition finishes, the notification icon will no longer be visible in your Instances list. - For detailed guidance on using the routed flexible IP feature via the Scaleway API or CLI tool, refer to our dedicated documentation [Routing public IPs to Instances using the Scaleway API](/compute/instances/api-cli/using-routed-ips/). + For detailed guidance on using the routed flexible IP feature via the Scaleway API or CLI tool, refer to our dedicated documentation [Routing public IPs to Instances using the Scaleway API](/instances/api-cli/using-routed-ips/). diff --git a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx index 81be52c7c9..5f2318a592 100644 --- a/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx +++ b/compute/instances/how-to/migrate-volumes-snapshots-to-sbs.mdx @@ -25,7 +25,7 @@ To facilitate the transition to Scaleway's new Block Storage management, two mai - **Advantage:** The migrated volume will fully support low latency, and it is possible to modify the IOPS up to 15k. All existing data of the old volume will be copied to the new Block Storage Low Latency volume. - **Drawback:** A snapshot must be manually created, exported, and imported. After importing, the snapshot must be converted into a volume, which must then be attached to the Instance. This process may require downtime. -Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/storage/block/quickstart/) instead of Compute. +Each method caters to different needs, balancing uninterrupted service against achieving maximum performance benefits. After migration, these resources will be managed under [Storage](/block-storage/quickstart/) instead of Compute. ## Comparison of migration methods @@ -34,8 +34,8 @@ Each method caters to different needs, balancing uninterrupted service against a | Instance API/CLI migration | No service interruption, volume remains accessible | Data characteristics remain the same; no performance boost | | Snapshot export/import | Full support for low latency and customizable IOPS | Requires downtime; manual snapshot handling | -This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage). -Alternatively, you can use the [snapshot export/import feature](/compute/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes. +This guide offers step-by-step instructions to migrate your volumes and snapshots using either the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool (recommended) or the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-volumes-migrate-a-volume-andor-snapshots-to-sbs-scaleway-block-storage). +Alternatively, you can use the [snapshot export/import feature](/instances/api-cli/snapshot-import-export-feature/) to migrate your unified volumes and snapshots to Block Storage Low Latency volumes. @@ -43,10 +43,10 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/compute/instances/how-to/create-an-instance/) using [Block Storage volumes](/storage/block/how-to/create-a-volume/) +- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/) - - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) tool. + - The easiest way to migrate your Block Storage volumes and snapshots is by using the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) tool. - If you encounter an error about quota limitations during the migration process, [contact our support team](https://console.scaleway.com/support/tickets/create) for assistance. @@ -64,7 +64,7 @@ Alternatively, you can use the [snapshot export/import feature](/compute/instanc ## Migrating using the Instance API/CLI migration endpoint (Plan and Apply): - During migration, unified snapshots will be converted into [Block Storage](/storage/block/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot. + During migration, unified snapshots will be converted into [Block Storage](/block-storage/) snapshots and removed from Compute. If a unified snapshot is part of an image, it will be replaced by the corresponding Block Storage snapshot. ### Migrating an existing Block Storage volume to Scaleway Block Storage management @@ -263,13 +263,13 @@ To convert your unified volumes and snapshots, you can use the snapshot export/i Follow the procedure below: -1. [Create a snapshot of your Block Storage legacy volume](/compute/instances/how-to/create-a-snapshot/). -2. [Export the snapshot](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). +1. [Create a snapshot of your Block Storage legacy volume](/instances/how-to/create-a-snapshot/). +2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). 3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). ## Going further -To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/storage/block/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). +To learn more about managing your migrated Block Storage volumes and snapshots from the Scaleway console, refer to the [Block Storage Quickstart Guide](/block-storage/quickstart/). Additionally, you can explore advanced features using the [Scaleway Block Storage API](https://www.scaleway.com/en/developers/api/block/). If you encounter any issues during migration, contact [Scaleway's support team](https://console.scaleway.com/support/tickets) for assistance. diff --git a/compute/instances/how-to/power-off-instance.mdx b/compute/instances/how-to/power-off-instance.mdx index d9002e56a0..8eccdff210 100644 --- a/compute/instances/how-to/power-off-instance.mdx +++ b/compute/instances/how-to/power-off-instance.mdx @@ -23,8 +23,8 @@ Powering off your Instance shuts it down by transferring all the data on the Ins - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to power off an Instance diff --git a/compute/instances/how-to/send-emails-from-your-instance.mdx b/compute/instances/how-to/send-emails-from-your-instance.mdx index d2b36d7aab..4b6bdc45c1 100644 --- a/compute/instances/how-to/send-emails-from-your-instance.mdx +++ b/compute/instances/how-to/send-emails-from-your-instance.mdx @@ -16,15 +16,15 @@ categories: By default, remote SMTP ports (25, 465, and 587) are blocked and cannot be accessed from our infrastructure to prevent spam. To send emails from your Instance, you need to open these ports in the security group configuration. - This document concerns enabling SMTP for Instances. If you want to enable SMTP on other resources, see our documentation on [enabling SMTP on Elastic Metal servers](/bare-metal/elastic-metal/how-to/enable-smtp/) and [enabling SMTP on Public Gateways](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp). + This document concerns enabling SMTP for Instances. If you want to enable SMTP on other resources, see our documentation on [enabling SMTP on Elastic Metal servers](/elastic-metal/how-to/enable-smtp/) and [enabling SMTP on Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-enable-smtp). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one [Instance](/compute/instances/how-to/create-an-instance/) -- Completed the [identity verification process (KYC)](/console/account/how-to/verify-identity/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one [Instance](/instances/how-to/create-an-instance/) +- Completed the [identity verification process (KYC)](/account/how-to/verify-identity/) 1. Click **Instances** on the side menu of the [Scaleway console](https://console.scaleway.com). diff --git a/compute/instances/how-to/snapshot-import-export-feature.mdx b/compute/instances/how-to/snapshot-import-export-feature.mdx index e80a2c7575..4bc452ebaf 100644 --- a/compute/instances/how-to/snapshot-import-export-feature.mdx +++ b/compute/instances/how-to/snapshot-import-export-feature.mdx @@ -22,10 +22,10 @@ More information on the QCOW2 file format and how to use it can be found in the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Instance](/compute/instances/how-to/create-an-instance/) using [Block Storage volumes](/storage/block/how-to/create-a-volume/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Instance](/instances/how-to/create-an-instance/) using [Block Storage volumes](/block-storage/how-to/create-a-volume/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Creating a snapshot from your existing Instance diff --git a/compute/instances/how-to/use-boot-modes.mdx b/compute/instances/how-to/use-boot-modes.mdx index d1bd268748..40993bdbb2 100644 --- a/compute/instances/how-to/use-boot-modes.mdx +++ b/compute/instances/how-to/use-boot-modes.mdx @@ -16,17 +16,17 @@ categories: You can boot your Instances using local boot or a rescue image. This page explains how to use each of these boot modes. - - You can choose to use **cloud-init** when [creating an Instance](/compute/instances/how-to/create-an-instance/) via **Advanced settings**. This enables you to control the mode of the Instance's very first boot. - - Your Instance must be [powered off](/compute/instances/how-to/power-off-instance/) in order to change its boot mode. + - You can choose to use **cloud-init** when [creating an Instance](/instances/how-to/create-an-instance/) via **Advanced settings**. This enables you to control the mode of the Instance's very first boot. + - Your Instance must be [powered off](/instances/how-to/power-off-instance/) in order to change its boot mode. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) ## How to use local boot @@ -58,7 +58,7 @@ Rescue mode restarts your Instance via the network on a minimal operating system ## How to use cloud-init -[Cloud-init](/compute/instances/concepts/#cloud-init) enables automatic configuration of an Instance as it boots into the cloud, turning it from a generic Ubuntu image into a configured server in a few seconds. +[Cloud-init](/instances/concepts/#cloud-init) enables automatic configuration of an Instance as it boots into the cloud, turning it from a generic Ubuntu image into a configured server in a few seconds. The cloud-init program can consume and execute data from the user-data field of the Scaleway console. The process then behaves differently depending on the format of the information it finds. One of the most popular formats for scripts within user-data is the cloud-config file format. Cloud-config files are special scripts designed to be run by the cloud-init process. These are generally used for initial configuration on the very first boot of a server. **Cloud-init is available for all Scaleway Instances OS images.** @@ -90,7 +90,7 @@ Follow the instructions below to reboot an existing Instance using cloud-init. ## How to change the boot volume -The [boot-on-block](/compute/instances/concepts/#boot-on-block) feature allows Instances to boot from attached [Block Storage](/compute/instances/concepts/#block-volumes) volumes instead of local volumes. When [creating an Instance](/compute/instances/how-to/create-an-instance/), you can select Block Storage as a boot volume. +The [boot-on-block](/instances/concepts/#boot-on-block) feature allows Instances to boot from attached [Block Storage](/instances/concepts/#block-volumes) volumes instead of local volumes. When [creating an Instance](/instances/how-to/create-an-instance/), you can select Block Storage as a boot volume. Once the Instance is created, you can select a different volume to boot from. diff --git a/compute/instances/how-to/use-flexips.mdx b/compute/instances/how-to/use-flexips.mdx index 118ab2fe3f..a3399229a9 100644 --- a/compute/instances/how-to/use-flexips.mdx +++ b/compute/instances/how-to/use-flexips.mdx @@ -13,14 +13,14 @@ categories: - compute --- -This page provides guidance on using [flexible IP addresses](/compute/instances/concepts/#flexible-ip) with your Scaleway Instances. +This page provides guidance on using [flexible IP addresses](/instances/concepts/#flexible-ip) with your Scaleway Instances. When creating an Instance, you have options for network connectivity: - **Flexible Routed IP addresses**: These are public IP addresses routed directly to your Instance. **Recommended.** -- **Flexible NAT IP addresses (Legacy)**: Comprising a public IP address (also a flexible IP address) and a private IP address routed to your Instance via a [CG-NAT](/compute/instances/concepts/#carrier-grade-nat-cgnat). +- **Flexible NAT IP addresses (Legacy)**: Comprising a public IP address (also a flexible IP address) and a private IP address routed to your Instance via a [CG-NAT](/instances/concepts/#carrier-grade-nat-cgnat). -Flexible IP addresses can be managed independently of any Instance. You can attach and detach them from any of your Instances and maintain multiple flexible IP addresses in your account simultaneously. They facilitate [live migration of IP addresses between your Instances](/compute/instances/how-to/migrate-instances/). +Flexible IP addresses can be managed independently of any Instance. You can attach and detach them from any of your Instances and maintain multiple flexible IP addresses in your account simultaneously. They facilitate [live migration of IP addresses between your Instances](/instances/how-to/migrate-instances/). You can assign up to five (5) flexible routed IP addresses to each Instance or one set of flexible NAT IP addresses. @@ -31,8 +31,8 @@ You can assign up to five (5) flexible routed IP addresses to each Instance or o - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) diff --git a/compute/instances/how-to/use-placement-groups.mdx b/compute/instances/how-to/use-placement-groups.mdx index b183664a28..2a9c3c9ba8 100644 --- a/compute/instances/how-to/use-placement-groups.mdx +++ b/compute/instances/how-to/use-placement-groups.mdx @@ -13,13 +13,13 @@ categories: - compute --- -[Placement groups](/compute/instances/concepts/#placement-groups) allow you to define if you want certain Instances to run on different physical hypervisors for maximum availability or as physically close together as possible for minimum latency. +[Placement groups](/instances/concepts/#placement-groups) allow you to define if you want certain Instances to run on different physical hypervisors for maximum availability or as physically close together as possible for minimum latency. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to create a placement group diff --git a/compute/instances/how-to/use-private-networks.mdx b/compute/instances/how-to/use-private-networks.mdx index 87102e1738..a82008f458 100644 --- a/compute/instances/how-to/use-private-networks.mdx +++ b/compute/instances/how-to/use-private-networks.mdx @@ -13,21 +13,21 @@ categories: - compute --- -[Private Networks](/network/vpc/concepts/#private-networks) allow your Instances to communicate in an isolated and secure network without needing to be connected to the public internet. Each Instance can be connected to one or several Private Networks, letting you build your own network topologies. +[Private Networks](/vpc/concepts/#private-networks) allow your Instances to communicate in an isolated and secure network without needing to be connected to the public internet. Each Instance can be connected to one or several Private Networks, letting you build your own network topologies. Private Networks are LAN-like layer 2 ethernet networks. A new network interface with a unique media access control address (MAC address) is configured on each Instance in a Private Network. Private Networks' built-in DHCP server manages the distribution of private IP addresses for Instances (and other resources) when they are attached to the network. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to create a new Private Network -The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings (created in your [default VPC](/network/vpc/concepts/#default-vpc) for the region, with an auto-generated [CIDR block](/network/vpc/concepts/#cidr-block)). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network. +The procedure below shows you how to create a new Private Network to attach to an existing Instance. The Private Network will have default settings (created in your [default VPC](/vpc/concepts/#default-vpc) for the region, with an auto-generated [CIDR block](/vpc/concepts/#cidr-block)). This CIDR block will be used to allocate private IP addresses to Instances attached to the network. Each Instance will get an IPv4 and an IPv6 address on the Private Network. -If you want to create a Private Network without immediately attaching any resources or create it in a specific VPC or with a custom CIDR block, follow [this procedure instead](/network/vpc/how-to/create-private-network/). +If you want to create a Private Network without immediately attaching any resources or create it in a specific VPC or with a custom CIDR block, follow [this procedure instead](/vpc/how-to/create-private-network/). 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the Instance you want to add a Private Network to. @@ -37,9 +37,9 @@ If you want to create a Private Network without immediately attaching any resour 6. Enter a **Name** for your Private Network, or leave the randomly-generated name in place. 7. Click **Attach to a Private Network** to finish. - Your Private Network is created in your [default VPC](/network/vpc/concepts/#default-vpc) for the region. The Private Network will have default settings, meaning an auto-generated [CIDR block](/network/vpc/concepts/#cidr-block). + Your Private Network is created in your [default VPC](/vpc/concepts/#default-vpc) for the region. The Private Network will have default settings, meaning an auto-generated [CIDR block](/vpc/concepts/#cidr-block). - You are taken back to the Private Networks tab, where your new Private Network is now displayed in the list and you can see the IP address for your Instance on the network. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). + You are taken back to the Private Networks tab, where your new Private Network is now displayed in the list and you can see the IP address for your Instance on the network. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). ## How to attach Instances to an existing Private Network @@ -52,10 +52,10 @@ If you want to create a Private Network without immediately attaching any resour Only Instances from the same region as your Private Network will be available in the drop-down menu. -7. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/network/ipam/concepts/#reserved-ip-address)** for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Instance will have on this Private Network. +7. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. You must make this choice for both the IPv4 and IPv6 address that the Instance will have on this Private Network. 8. Click **Attach to Private Network**. - You are taken back to the **Private Networks** tab, where you can see the private IP address for the Instance you just attached. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). + You are taken back to the **Private Networks** tab, where you can see the private IP address for the Instance you just attached. For more information about resources' private IP addresses on a Private Network, see our [dedicated documentation](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). ## How to detach Instances from a Private Network @@ -70,9 +70,9 @@ If you want to create a Private Network without immediately attaching any resour ## How to delete a Private Network - Before deleting a Private Network, you must [detach](/compute/instances/how-to/use-private-networks/#how-to-detach-instances-from-a-private-network) all Instances attached to it. + Before deleting a Private Network, you must [detach](/instances/how-to/use-private-networks/#how-to-detach-instances-from-a-private-network) all Instances attached to it. -This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/network/vpc/how-to/delete-private-network/). +This must be carried out from the VPC section of the console. Follow the procedure detailed in our [dedicated VPC documentation](/vpc/how-to/delete-private-network/). diff --git a/compute/instances/how-to/use-protected-instance.mdx b/compute/instances/how-to/use-protected-instance.mdx index 2ce0039e0d..6f872d3fcb 100644 --- a/compute/instances/how-to/use-protected-instance.mdx +++ b/compute/instances/how-to/use-protected-instance.mdx @@ -13,13 +13,13 @@ categories: - compute --- -The [Protected Instance](/compute/instances/concepts/#protected-instance) feature is used to prevent any `halt` action from being performed on your Instance. This only applies to running Instances. Enabling the Protected Instance feature means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. This feature is useful to avoid hazardous manipulations, such as batch deletion of Instances. +The [Protected Instance](/instances/concepts/#protected-instance) feature is used to prevent any `halt` action from being performed on your Instance. This only applies to running Instances. Enabling the Protected Instance feature means that you will not be able to delete, power off, or reboot your Instance, nor put it into standby mode. This feature is useful to avoid hazardous manipulations, such as batch deletion of Instances. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to activate the Protected Instance feature diff --git a/compute/instances/how-to/use-security-groups.mdx b/compute/instances/how-to/use-security-groups.mdx index 6b6aaf32c9..0284b33236 100644 --- a/compute/instances/how-to/use-security-groups.mdx +++ b/compute/instances/how-to/use-security-groups.mdx @@ -13,13 +13,13 @@ categories: - compute --- -[Security groups](/compute/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow traffic to and from your Instance. On this page, we show you how to create, edit, and configure a security group via the Scaleway console. +[Security groups](/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow traffic to and from your Instance. On this page, we show you how to create, edit, and configure a security group via the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to create a security group @@ -31,13 +31,13 @@ categories: 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the **Security groups** tab. The Security groups dashboard displays. - You will see that at least one **Default security group** already exists in your account. A default security group is auto-generated for each [Availability Zone](/compute/instances/concepts/#availability-zone) you have created Instances in. All your Instances within that Availability Zone are automatically added to that default security group unless you specify a different configuration. + You will see that at least one **Default security group** already exists in your account. A default security group is auto-generated for each [Availability Zone](/instances/concepts/#availability-zone) you have created Instances in. All your Instances within that Availability Zone are automatically added to that default security group unless you specify a different configuration. 3. Click **+ Create security group** to launch the security group creation wizard. 4. Complete the following steps: - Choose a **Name** for your security group or keep the randomly generated suggestion. Optionally, add a description. - Choose an **Availability Zone**, which is the geographical location in which your security group will be created. Only Instances from the same Availability Zone can be added to this security group. - - Define the inbound and outbound **rules** that will be applied to your security group, including whether you wish to enable SMTP ports. [Learn how to choose security group settings](/compute/instances/how-to/use-security-groups/#how-to-choose-security-group-settings). + - Define the inbound and outbound **rules** that will be applied to your security group, including whether you wish to enable SMTP ports. [Learn how to choose security group settings](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings). - Select the **Instances** you wish to add to the security group. 5. Click **Create security group** to finish. Your security group is created, and you are redirected to the **Security groups** tab, where it now appears. @@ -65,25 +65,25 @@ categories: - Click the **Add inbound rule** or **Add outbound rule** buttons that appear, - Create your rule and click when you have finished confirming the new rule. - See [How to choose security group settings](/compute/instances/how-to/use-security-groups/#how-to-choose-security-group-settings) for more information on these choices. + See [How to choose security group settings](/instances/how-to/use-security-groups/#how-to-choose-security-group-settings) for more information on these choices. ## How to choose security group settings ### Enabling SMTP By default, SMTP ports are blocked for security reasons to prevent email spam. This means that you cannot send outgoing emails from the Instance. We recommend leaving this default setting unless you specifically need to send emails from your Instance. -To enable or disable SMTP for a security group, follow the instructions for [how to edit a security group](/compute/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4. +To enable or disable SMTP for a security group, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4. ### Enabling stateful groups -By default, security groups created via the console are stateful. To disable or re-enable stateful groups, follow the [instructions for editing a security group](/compute/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4. -- **Stateless**: These strictly enforce the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance. [Learn more about stateless security groups](/compute/instances/concepts/#stateless-security-groups). -- **Stateful**: These disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. [Learn more about stateful security groups](/compute/instances/concepts/#stateful-security-groups). +By default, security groups created via the console are stateful. To disable or re-enable stateful groups, follow the [instructions for editing a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) and check the relevant box in the **Overview** tab at step 4. +- **Stateless**: These strictly enforce the default policy and inbound/outbound rules, regardless of whether a connection is initiated from your Instance. [Learn more about stateless security groups](/instances/concepts/#stateless-security-groups). +- **Stateful**: These disregard the default policy and inbound/outbound rules if a connection is initiated from your Instance. [Learn more about stateful security groups](/instances/concepts/#stateful-security-groups). ### Setting default inbound and outbound policies -You can set default policies to drop or accept all inbound traffic, and drop or accept all outbound traffic. We recommend blocking incoming traffic by default to prevent intrusions. To change your default inbound and outbound policies, follow the instructions for [how to edit a security group](/compute/instances/how-to/use-security-groups/#how-to-edit-a-security-group), checking the relevant boxes in the **Rules** tab at step 4. +You can set default policies to drop or accept all inbound traffic, and drop or accept all outbound traffic. We recommend blocking incoming traffic by default to prevent intrusions. To change your default inbound and outbound policies, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group), checking the relevant boxes in the **Rules** tab at step 4. ### Creating inbound and outbound rules -You can create customized inbound and outbound rules to drop or accept traffic on particular protocols, ports, and IP ranges. To do so, follow the instructions for [how to edit a security group](/compute/instances/how-to/use-security-groups/#how-to-edit-a-security-group), by clicking the edit icon in the **Rules tab** in step 4. +You can create customized inbound and outbound rules to drop or accept traffic on particular protocols, ports, and IP ranges. To do so, follow the instructions for [how to edit a security group](/instances/how-to/use-security-groups/#how-to-edit-a-security-group), by clicking the edit icon in the **Rules tab** in step 4. For each rule, choose the following options: - **Rule**: The value can either be **Drop** to drop connections that match the rule or **Accept** to accept these connections. diff --git a/compute/instances/how-to/use-serial-console.mdx b/compute/instances/how-to/use-serial-console.mdx index bf05ba9857..d642a6eb9e 100644 --- a/compute/instances/how-to/use-serial-console.mdx +++ b/compute/instances/how-to/use-serial-console.mdx @@ -18,15 +18,15 @@ This page shows how to connect to your Scaleway Instance from the Scaleway conso - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) - A password for your Linux user ## How to use the serial console (TTY) - You have to connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/) and define a user password before connecting to your Instance using the serial console. + You have to connect to your Instance using [SSH](/instances/how-to/connect-to-instance/) and define a user password before connecting to your Instance using the serial console. 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. diff --git a/compute/instances/how-to/use-standby-mode.mdx b/compute/instances/how-to/use-standby-mode.mdx index 8e174b2301..d96455949a 100644 --- a/compute/instances/how-to/use-standby-mode.mdx +++ b/compute/instances/how-to/use-standby-mode.mdx @@ -13,13 +13,13 @@ categories: - compute --- -[Standby mode](/compute/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance. +[Standby mode](/instances/concepts/#standby-mode) temporarily stops an Instance. The Instance remains allocated to your account and all data remains on the Local Storage of the Instance. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) ## How to put an Instance into standby mode @@ -33,7 +33,7 @@ categories: Your Instance is now in standby mode. - You are still billed for an Instance in standby mode, as well as for its storage and any flexible IPs attached to it. To avoid being charged for an unused Instance, you can [power it off](/compute/instances/how-to/power-off-instance/).

+ You are still billed for an Instance in standby mode, as well as for its storage and any flexible IPs attached to it. To avoid being charged for an unused Instance, you can [power it off](/instances/how-to/power-off-instance/).

[Find out when the billing of your Instance starts and stops](/faq/billing/#when-does-the-billing-of-an-instance-start-and-stop). diff --git a/compute/instances/index.mdx b/compute/instances/index.mdx index b8f0434204..356963f3b5 100644 --- a/compute/instances/index.mdx +++ b/compute/instances/index.mdx @@ -8,7 +8,7 @@ meta: productName="Instances" productLogo="instance" description="Scaleway Instances are lightning-fast virtual machines that can adapt to your every need, from learning purposes to high-performance workloads." - url="/compute/instances/quickstart" + url="/instances/quickstart" label="Instances Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and delete an Instance in a few steps." label="View Quickstart" - url="/compute/instances/quickstart/" + url="/instances/quickstart/" /> diff --git a/compute/instances/quickstart.mdx b/compute/instances/quickstart.mdx index 5ecc21d15b..ee0bc57672 100644 --- a/compute/instances/quickstart.mdx +++ b/compute/instances/quickstart.mdx @@ -13,13 +13,13 @@ categories: - compute --- -Scaleway [Instances](/compute/instances/concepts/#instance) are computing units that provide you with resources to run your applications. After you have created your Instance and installed your image of choice (e.g., an operating system), you can connect to it via SSH to use it as you wish. When you are done using the Instance, you can delete it from your account. +Scaleway [Instances](/instances/concepts/#instance) are computing units that provide you with resources to run your applications. After you have created your Instance and installed your image of choice (e.g., an operating system), you can connect to it via SSH to use it as you wish. When you are done using the Instance, you can delete it from your account. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## How to create an Instance @@ -28,14 +28,14 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units 3. Complete the following steps: - **Choose an Availability Zone**, which represents the geographical region where your Instance will be deployed. - **Choose an Instance type**.
- Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/compute/instances/reference-content/choosing-instance-type/). + Instance offers vary in pricing, processing power, memory, storage, and bandwidth. [Discover the best Instance type for your needs](/instances/reference-content/choosing-instance-type/). - **Choose an image** to run on your Instance.
- This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/compute/instances/reference-content/images-and-instantapps/). - - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/compute/instances/concepts/#tags) to help you organize your Instance. + This can be an operating system, an InstantApp, or a custom image. [Check all available Linux distributions and InstantApps](/instances/reference-content/images-and-instantapps/). + - **Name your Instance**, or leave the randomly-generated name in place. Optionally, you can add [tags](/instances/concepts/#tags) to help you organize your Instance. - **Add Volumes**, which are storage spaces used by your Instances. A block volume with a default name and 5,000 IOPS is automatically provided for your system volume. You can customize this volume and attach up to 16 local and/or block type volumes as needed. - Ensure that the volume containing your OS image has a minimum size of 10 GB. For a GPU OS, the recommended size is 125 GB. - - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). + - When multiple Block Storage volumes are linked to your Instance, the primary volume will host the OS and is essential for booting the Instance. Once the Instance is created can [modify your boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). - Booting from a volume that either lacks an OS or is among multiple volumes with identical operating systems can lead to inconsistent boot outcomes. - **Configure network** of the Instance. @@ -44,9 +44,9 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units You can attach up to 5 IPs to an Instance, combining IPv4 and IPv6 addresses, which is useful for running different services or applications on the same Instance. - - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/compute/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. + - (Optional) Click **Advanced options** to configure a [cloud-init configuration](/instances/concepts/#cloud-init). Otherwise, leave these options at their default values. You can configure a cloud-init script to automate Instance setup, such as setting up software, users, and system configurations at the first boot. - - **Verify the [SSH keys](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. + - **Verify the [SSH keys](/organizations-and-projects/concepts/#ssh-key)** that will give you access to your Instance. - **Verify the Estimated cost** of your Instance, based on the specifications you chose. 4. Click **Create Instance**. The creation of your Instance begins, and you will be informed when the Instance is ready. Once the Instance is created, you can connect to it using the SSH keys you have configured, and begin setting up your applications. @@ -78,7 +78,7 @@ To connect to your Instance from Windows, you will need to use a small applicati 2. Launch PuTTY on your computer. 3. Enter your Instance's IP address in the **Hostname** field. 4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. (**Connection** > **SSH** > **Auth**). -5. Click the **Browse** button and select the private key file you [created previously](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/). +5. Click the **Browse** button and select the private key file you [created previously](/organizations-and-projects/how-to/create-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the Instance. PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. The terminal window displays. 8. Enter the username `root` and press **Enter** to authenticate against the server with your SSH key. @@ -86,7 +86,7 @@ To connect to your Instance from Windows, you will need to use a small applicati You are now connected to your Instance. - For instructions on how to connect to Instances running Microsoft Windows Server OS, refer to our dedicated documentation [How to connect to Instances running Microsoft Windows Server OS](/compute/instances/how-to/connect-to-instance/). + For instructions on how to connect to Instances running Microsoft Windows Server OS, refer to our dedicated documentation [How to connect to Instances running Microsoft Windows Server OS](/instances/how-to/connect-to-instance/). ## How to delete an Instance diff --git a/compute/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx b/compute/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx index f0073fdafe..36c1ac75d7 100644 --- a/compute/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx +++ b/compute/instances/reference-content/add-instance-specific-ssh-keys-using-tags.mdx @@ -21,9 +21,9 @@ This can simplify key management and improve security, especially when you are r - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) ## The authorized_keys file diff --git a/compute/instances/reference-content/choosing-instance-type.mdx b/compute/instances/reference-content/choosing-instance-type.mdx index a219b2fdbc..ecfaed8d8b 100644 --- a/compute/instances/reference-content/choosing-instance-type.mdx +++ b/compute/instances/reference-content/choosing-instance-type.mdx @@ -12,7 +12,7 @@ dates: tags: instance, type, stardust, range, vcpu, hyperthread, core, ram, bandwidth, dedicated, shared, memory, hypervisor, vm, storage, dev1, play2, gp1, pro2, ent1, gpu, arm, learning, development, production, production-optimized, cost-optimized, memory-optimized, storage-optimized --- -Scaleway Instances are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/compute/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs. +Scaleway Instances are virtual machines in the cloud. You can create and manage Instances via our [console](https://console.scaleway.com/), [API](https://www.scaleway.com/en/developers/api/), [CLI](https://www.scaleway.com/en/cli/), or [other developer tools](https://www.scaleway.com/en/developers/). When you [create an Instance](/instances/how-to/create-an-instance/), you must select the **Instance type** you want to create. This page explains the different ranges of Instances available at Scaleway and helps you to choose the best one for your needs. ## Different Instances for different use cases @@ -31,7 +31,7 @@ Instances are virtual machines: multiple Instances can run on one "real" physica - **Dedicated**: Instances with dedicated vCPU do not share their compute resources with other Instances (1 vCPU = 1 CPU thread dedicated to that Instance). This type of Instance is particularly recommended for running production-grade compute-intensive applications. - Scaleway provides Instances equipped with either x86 or ARM CPUs. ARM Instances generally offer higher energy and cost efficiency, while x86 cloud instances provide wider software compatibility and stronger single-thread performance. [Learn more about the differences between ARM and x86-based Instances](/compute/instances/reference-content/understanding-differences-x86-arm/). + Scaleway provides Instances equipped with either x86 or ARM CPUs. ARM Instances generally offer higher energy and cost efficiency, while x86 cloud instances provide wider software compatibility and stronger single-thread performance. [Learn more about the differences between ARM and x86-based Instances](/instances/reference-content/understanding-differences-x86-arm/). * **Core**: A core is a physical unit of vCPU. More cores give an Instance more computing power. A description of an Instance's cores may look something like `4 x86 64bit`, where **4** refers to the number of cores, **x86** refers to the microprocessor family, and **64bit** refers to the chunk size used by the microprocessor for processing data. @@ -52,7 +52,7 @@ The table below shows the different ranges of Instances at Scaleway and their sp Use this table to help identify the right Instance range for your use case and computing needs. -| **Instance range** | [Learning](/compute/instances/reference-content/learning/) | [Cost-Optimized](/compute/instances/reference-content/cost-optimized/) | [Production-Optimized](/compute/instances/reference-content/production-optimized/) | [Workload-Optimized](/compute/instances/reference-content/workload-optimized/) | +| **Instance range** | [Learning](/instances/reference-content/learning/) | [Cost-Optimized](/instances/reference-content/cost-optimized/) | [Production-Optimized](/instances/reference-content/production-optimized/) | [Workload-Optimized](/instances/reference-content/workload-optimized/) | |-----------------------|----------------------------------------------------------------|----------------------------------------------------------------------------------------------------------|------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Use cases** | Discovering the Scaleway ecosystem
Hosting personal projects | Scaling your development and testing environment
Hosting CI/CD runners and containerized worker nodes | Hosting production workloads and business-critical applications
Ensuring predictable CPU performance in the face of high traffic | Hosting high-demanding analysis, in-memory calculation, big-data processing, high-performance or cache databases
Designed for high-performance web-serving, video encoding, machine learning, batch processing, CI/CD | | **Supported storage** | Resilient Block Storage or Local Storage | Resilient Block Storage or Local Storage, OR Resilient Block Storage only (depending on Instance type) | Resilient Block Storage | Resilient Block Storage | @@ -62,14 +62,14 @@ Use this table to help identify the right Instance range for your use case and c | **Maximum Bandwidth** | 100 Mbit/s | From 100 Mbps to 6 Gbps | From 400 Mbps to 20 Gbps | From 400 Mbps to 12.8 Gbps | For more information about each range, refer to our dedicated documentation pages: -- [Learning](/compute/instances/reference-content/learning/) -- [Cost-Optimized](/compute/instances/reference-content/cost-optimized/) -- [Production-Optimized](/compute/instances/reference-content/production-optimized/) -- [Workload-Optimized](/compute/instances/reference-content/workload-optimized/) +- [Learning](/instances/reference-content/learning/) +- [Cost-Optimized](/instances/reference-content/cost-optimized/) +- [Production-Optimized](/instances/reference-content/production-optimized/) +- [Workload-Optimized](/instances/reference-content/workload-optimized/) ## Instance types -Check out the [Instances page](https://www.scaleway.com/en/virtual-instances/) of our website for full details on each Instance type. Alternatively, head over to the [Instances datasheet](/compute/instances/reference-content/instances-datasheet/) to see all our available Instance types within each range. +Check out the [Instances page](https://www.scaleway.com/en/virtual-instances/) of our website for full details on each Instance type. Alternatively, head over to the [Instances datasheet](/instances/reference-content/instances-datasheet/) to see all our available Instance types within each range. ## Instance pricing diff --git a/compute/instances/reference-content/cost-optimized.mdx b/compute/instances/reference-content/cost-optimized.mdx index 89cf7c02ac..3bdde00911 100644 --- a/compute/instances/reference-content/cost-optimized.mdx +++ b/compute/instances/reference-content/cost-optimized.mdx @@ -13,7 +13,7 @@ categories: tags: instance type development DEV range cost-optimized general-purpose general purpose GP PLAY2 PRO2 play pro --- -An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/compute/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/compute/instances/concepts/#instantapp). +An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/instances/concepts/#instantapp). ## Development Instances and General Purpose Instances @@ -69,9 +69,9 @@ The table below displays the technical specifications of COP-ARM Instances: ## Complementary services To help build and manage your applications, consider complementing your Instance with the following compatible services: -- [Learn how to back up your Instance](/compute/instances/how-to/create-a-backup/) -- [Learn how to create snapshots of your Instance for specific volumes](/compute/instances/how-to/create-a-snapshot/) -- [Learn how to migrate your data from one Instance to another](/compute/instances/how-to/migrate-instances/) +- [Learn how to back up your Instance](/instances/how-to/create-a-backup/) +- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/) +- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/) ## Matching use cases diff --git a/compute/instances/reference-content/images-and-instantapps.mdx b/compute/instances/reference-content/images-and-instantapps.mdx index f43491d0a2..97c1e05eeb 100644 --- a/compute/instances/reference-content/images-and-instantapps.mdx +++ b/compute/instances/reference-content/images-and-instantapps.mdx @@ -21,7 +21,7 @@ Scaleway manages the deployment and maintenance of these OS images, ensuring the | Distribution | Description | |---|---| | | **Ubuntu 24.04** the latest long-term support (LTS) version of the world's most popular Linux operating system, offers reliability and stability with five years of guaranteed free updates.
[Deploy Ubuntu](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=607b12c2-685d-45f7-905f-57bc23863834&offerName=PRO2-S&zone=fr-par-1) | -| | **Ubuntu ML**, Scaleway’s [optimized version](/compute/gpu/reference-content/docker-images/) of Ubuntu is tailored for machine learning, featuring essential frameworks, tools, and packages. This includes the NVIDIA Container Toolkit (Docker), PyTorch, TensorFlow 2, NVIDIA RAPIDS, and JAX, ensuring a comprehensive and efficient ML environment.
[Deploy Ubuntu ML](https://console.scaleway.com/instance/servers/create/?area=fr-par-2&imageKey=a6c68db3-5613-4b08-acaa-2c92d8baf26c&offerName=L40S-1-48G&zone=fr-par-2) | +| | **Ubuntu ML**, Scaleway’s [optimized version](/gpu/reference-content/docker-images/) of Ubuntu is tailored for machine learning, featuring essential frameworks, tools, and packages. This includes the NVIDIA Container Toolkit (Docker), PyTorch, TensorFlow 2, NVIDIA RAPIDS, and JAX, ensuring a comprehensive and efficient ML environment.
[Deploy Ubuntu ML](https://console.scaleway.com/instance/servers/create/?area=fr-par-2&imageKey=a6c68db3-5613-4b08-acaa-2c92d8baf26c&offerName=L40S-1-48G&zone=fr-par-2) | | | **Debian**, the world-renowned free open-source operating system, featuring over 59,000 packages. Celebrated for its reliability, it is available in its stable branch, Debian 12 (Bookworm).
[Deploy Debian](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=fd6931c1-5326-4f8d-8fdf-57867b2830e3&offerName=PRO2-S&zone=fr-par-1) | | | **CentOS**, developed using Red Hat® Enterprise Linux®, is characterized by increased stability. It works on computers with both 64-bit and 32-bit architectures and is available as a free distribution. You can choose the version you need directly from the console.
[Deploy CentOS](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=cfb3fa01-6406-4be8-9e9d-29daee2582fa&offerName=PRO2-S) | | | **Fedora** is a modern Linux distribution with a focus on free software. It features a constantly evolving system supported by a large community and adheres to a regular release schedule. You can select the version you need directly from the console.
[Deploy Fedora](https://console.scaleway.com/instance/servers/create/?area=fr-par-1&imageKey=186859f6-0152-45dd-9eb8-21fc5e8d774e&offerName=PRO2-S) | diff --git a/compute/instances/reference-content/instances-bandwidth-overview.mdx b/compute/instances/reference-content/instances-bandwidth-overview.mdx index df027ebcef..5daf58fde3 100644 --- a/compute/instances/reference-content/instances-bandwidth-overview.mdx +++ b/compute/instances/reference-content/instances-bandwidth-overview.mdx @@ -27,7 +27,7 @@ Bandwidth impacts how your applications perform and interact with other systems. - To maximize compatibility with [Block Storage Low Latency 15k](/storage/block/), select an Instance with **at least 3 GiB/s** of Block bandwidth. + To maximize compatibility with [Block Storage Low Latency 15k](/block-storage/), select an Instance with **at least 3 GiB/s** of Block bandwidth. ## COPARM Range diff --git a/compute/instances/reference-content/learning.mdx b/compute/instances/reference-content/learning.mdx index 881e478305..d63ce85a32 100644 --- a/compute/instances/reference-content/learning.mdx +++ b/compute/instances/reference-content/learning.mdx @@ -13,7 +13,7 @@ categories: tags: instance type stardust range learning use-case --- -An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/compute/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Learning Instance supports the essential operating systems and distributions. +An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Learning Instance supports the essential operating systems and distributions. ## Learning range: Stardust Instances @@ -38,9 +38,9 @@ Scaleway's **Learning** range includes our Stardust Instances. Stardust Instance To help build and manage your applications, consider complementing your Stardust Instance with the following compatible services: -- [Learn how to back up your Instance](/compute/instances/how-to/create-a-backup/) -- [Learn how to create snapshots of your Instance for specific volumes](/compute/instances/how-to/create-a-snapshot/) -- [Learn how to migrate your data from one Instance to another](/compute/instances/how-to/migrate-instances/) +- [Learn how to back up your Instance](/instances/how-to/create-a-backup/) +- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/) +- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/) ## Matching use cases diff --git a/compute/instances/reference-content/manual-configuration-private-ips.mdx b/compute/instances/reference-content/manual-configuration-private-ips.mdx index 15964200d4..45c1e1043b 100644 --- a/compute/instances/reference-content/manual-configuration-private-ips.mdx +++ b/compute/instances/reference-content/manual-configuration-private-ips.mdx @@ -14,15 +14,15 @@ dates: - DHCP is activated by default on all newly-created Private Networks, and cannot be deactivated. - - If you have a Private Network created before July 12 2023, [check our migration documentation](/network/vpc/reference-content/vpc-migration/) to find out if DHCP has been automatically activated on your network. - - We recommend activating DHCP and letting us take care of the automatic IP address management of all resources on your Private Networks, including Instances, to ensure they are fully compatible with managed products and integrated with our [internal IPAM](/network/vpc/concepts/#ipam). + - If you have a Private Network created before July 12 2023, [check our migration documentation](/vpc/reference-content/vpc-migration/) to find out if DHCP has been automatically activated on your network. + - We recommend activating DHCP and letting us take care of the automatic IP address management of all resources on your Private Networks, including Instances, to ensure they are fully compatible with managed products and integrated with our [internal IPAM](/vpc/concepts/#ipam). The steps outlined in this document are intended for advanced users only and are not supported by Scaleway. ## How to configure the Private Network interface on your Instances -Once you have [added your Instances to a Private Network](/compute/instances/how-to/use-private-networks/), you can manually configure the virtual network interface on each one. You will also need to turn off the automatic DHCP scripts found on the Instance for Private Network, so that they do not conflict with the manual configuration you are creating. These steps are explained below. +Once you have [added your Instances to a Private Network](/instances/how-to/use-private-networks/), you can manually configure the virtual network interface on each one. You will also need to turn off the automatic DHCP scripts found on the Instance for Private Network, so that they do not conflict with the manual configuration you are creating. These steps are explained below. - We recommend not using publicly routed IP subnets within your Private Network. @@ -39,7 +39,7 @@ Once you have [added your Instances to a Private Network](/compute/instances/how - This is only recommended for expert users. -1. Connect to the Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to the Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Delete the file `/lib/udev/rules.d/72-scw-vpc-iface.rules` to disable the automatic DHCP scripts: ```bash rm /lib/udev/rules.d/72-scw-vpc-iface.rules diff --git a/compute/instances/reference-content/production-optimized.mdx b/compute/instances/reference-content/production-optimized.mdx index 85122d5b12..c8c1570778 100644 --- a/compute/instances/reference-content/production-optimized.mdx +++ b/compute/instances/reference-content/production-optimized.mdx @@ -13,7 +13,7 @@ categories: tags: instance type production production-optimized range POP2 ENT1 --- -An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/compute/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/compute/instances/concepts/#instantapp). +An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [Instantapps](/instances/concepts/#instantapp). Both ENT1 and POP2 Instance types have identical hardware specifications, dedicated vCPU allocation, the same pricing structure, and an accelerated booting process. @@ -63,9 +63,9 @@ See below the technical specifications of Production-Optimized Instances: ## Complementary services To help build and manage your applications, consider complementing your Production-Optimized Instances with the following compatible services: -- [Learn how to back up your Instance](/compute/instances/how-to/create-a-backup/) -- [Learn how to create snapshots of your Instance for specific volumes](/compute/instances/how-to/create-a-snapshot/) -- [Learn how to migrate your data from one Instance to another](/compute/instances/how-to/migrate-instances/) +- [Learn how to back up your Instance](/instances/how-to/create-a-backup/) +- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/) +- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/) ## Matching use cases Try Scaleway Production-Optimized Instances with the following tutorials: diff --git a/compute/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx b/compute/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx index ef266ad380..2a22622c68 100644 --- a/compute/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx +++ b/compute/instances/reference-content/understanding-automatic-network-hot-reconfiguration.mdx @@ -15,7 +15,7 @@ tags: instance network hot-reconfiguration The Scaleway Instances product includes a feature called **automatic network hot-reconfiguration**. -This mechanism automatically configures or deconfigures a [flexible IP address](/compute/instances/concepts/#flexible-ip) in the guest operating system when it is attached to or detached from an Instance. +This mechanism automatically configures or deconfigures a [flexible IP address](/instances/concepts/#flexible-ip) in the guest operating system when it is attached to or detached from an Instance. This guide explains how to enable or disable the automatic network hot-reconfiguration mechanism on your Instance. @@ -25,7 +25,7 @@ This guide explains how to enable or disable the automatic network hot-reconfigu ## Supported configurations -Before proceeding, ensure that your operating system supports the target network configuration: refer to Scaleway’s compatibility guidelines on [OS images and flexible IP type combinations](/compute/instances/reference-content/comaptibility-scw-os-images-flexible-ip/). +Before proceeding, ensure that your operating system supports the target network configuration: refer to Scaleway’s compatibility guidelines on [OS images and flexible IP type combinations](/instances/reference-content/comaptibility-scw-os-images-flexible-ip/). Starting from **October 10th, 2024**, all GNU/Linux-based operating systems and InstantApp images for Scaleway Instances have automatic network hot-reconfiguration enabled by default. @@ -42,7 +42,7 @@ If the output is `active`, the feature is enabled and ready to use. If the outpu Follow these steps to enable automatic network hot-reconfiguration on a Scaleway Instance where the feature is currently inactive. -1. Enable the QEMU Guest Agent. Refer to Scaleway’s documentation on [enabling the QEMU Guest Agent (GQA)](/compute/instances/reference-content/understanding-qemu-guest-agent/#opting-in) for further details. +1. Enable the QEMU Guest Agent. Refer to Scaleway’s documentation on [enabling the QEMU Guest Agent (GQA)](/instances/reference-content/understanding-qemu-guest-agent/#opting-in) for further details. 2. Install the latest Scaleway ecosystem package. diff --git a/compute/instances/reference-content/understanding-instance-pricing.mdx b/compute/instances/reference-content/understanding-instance-pricing.mdx index 858723bfa2..13e81d160c 100644 --- a/compute/instances/reference-content/understanding-instance-pricing.mdx +++ b/compute/instances/reference-content/understanding-instance-pricing.mdx @@ -24,15 +24,15 @@ Our [console](https://console.scaleway.com/) tries to make it as easy as possibl ## Hourly pricing -Instances are priced by the hour, with different [Instance types](/compute/instances/reference-content/choosing-instance-type/) having different hourly rates. You can check out the current prices for Instances in one of two ways: -- Go to the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console. Note that you must have [an account](/console/account/how-to/create-an-account/) to access this page. +Instances are priced by the hour, with different [Instance types](/instances/reference-content/choosing-instance-type/) having different hourly rates. You can check out the current prices for Instances in one of two ways: +- Go to the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console. Note that you must have [an account](/account/how-to/create-an-account/) to access this page. - See the dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available) of our website. ## Instance billing -- Your hourly billing begins when you [create the Instance](/compute/instances/how-to/create-an-instance/). -- Billing pauses if you [power off](/compute/instances/how-to/power-off-instance/) the Instance, and recommences when you power it back on. Any attached storage or flexible IPs are still billed while the Instance is powered off though - see full details [below](#flexible-ip-addresses-and-storage-volumes). -- Billing ends when you [delete the Instance](/compute/instances/how-to/create-an-instance/). +- Your hourly billing begins when you [create the Instance](/instances/how-to/create-an-instance/). +- Billing pauses if you [power off](/instances/how-to/power-off-instance/) the Instance, and recommences when you power it back on. Any attached storage or flexible IPs are still billed while the Instance is powered off though - see full details [below](#flexible-ip-addresses-and-storage-volumes). +- Billing ends when you [delete the Instance](/instances/how-to/create-an-instance/). You can power off your Instance or delete it at any time: no minimum commitment or notice period is required. @@ -42,15 +42,15 @@ At the end of each calendar month you will be invoiced for your hourly billed us ### Flexible IP address billing -When you create an Instance, by default a [flexible IP](/compute/instances/concepts/#flexible-ip) is created for it at the same time. This gives the Instance a public IP address. A flexible IP address is billed separately to the Instance and has its own hourly rate. You can see the hourly rate for a flexible IP address on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console or on our dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available). +When you create an Instance, by default a [flexible IP](/instances/concepts/#flexible-ip) is created for it at the same time. This gives the Instance a public IP address. A flexible IP address is billed separately to the Instance and has its own hourly rate. You can see the hourly rate for a flexible IP address on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console or on our dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available). -Your hourly billing for a flexible IP address begins when you reserve the IP address (either during the creation of an Instance or by [creating a new flexible IP address)](/compute/instances/how-to/use-flexips/#how-to-create-a-new-flexible-ip-address) and ends when you [delete the address](/compute/instances/how-to/use-flexips/#how-to-delete-a-flexible-ip-address) from your account. +Your hourly billing for a flexible IP address begins when you reserve the IP address (either during the creation of an Instance or by [creating a new flexible IP address)](/instances/how-to/use-flexips/#how-to-create-a-new-flexible-ip-address) and ends when you [delete the address](/instances/how-to/use-flexips/#how-to-delete-a-flexible-ip-address) from your account. - You can choose to create an Instance without a flexible IP address via the **Advanced settings** option. - Billing of an Instance stops when you power it off, but the Instance's flexible IP remains reserved to your account nonetheless. You will continue to be billed for the flexible IP even if your Instance is powered off, unless you delete the flexible IP. - When you delete an Instance via the console, you are asked whether you want to also delete its flexible IP. If you delete it, billing for this IP will end. If you keep it in your account, billing continues. - - See the [Billing FAQ](/faq/billing/) for more information about the billing of [dynamic IP addresses](/compute/instances/concepts/#dynamic-ip) as opposed to flexible IPs. + - See the [Billing FAQ](/faq/billing/) for more information about the billing of [dynamic IP addresses](/instances/concepts/#dynamic-ip) as opposed to flexible IPs. You can detach a flexible IP address from your Instance and delete it at any time: no minimum commitment or notice period is required. @@ -59,9 +59,9 @@ At the end of each calendar month, you will be invoiced for your hourly billed f ### Storage volume billing -When you create an Instance, you also need to create a certain amount of storage for it, in the form of [local or block volumes](/compute/instances/concepts/#volumes). Volumes are billed separately to Instances and have their own hourly rates. You can see the hourly rate for different types of volume on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console, or on the dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available) of our website. +When you create an Instance, you also need to create a certain amount of storage for it, in the form of [local or block volumes](/instances/concepts/#volumes). Volumes are billed separately to Instances and have their own hourly rates. You can see the hourly rate for different types of volume on the Instance [creation page](https://console.scaleway.com/instance/servers/create) of the Scaleway console, or on the dedicated [pricing page](https://www.scaleway.com/en/pricing/?tags=available) of our website. -Your hourly billing for a storage volume begins when you create the volume (either during the creation of an Instance, or by creating a [new volume](/storage/block/how-to/create-a-volume/)), and ends when you [delete](/storage/block/how-to/delete-a-volume/) the volume from your account. +Your hourly billing for a storage volume begins when you create the volume (either during the creation of an Instance, or by creating a [new volume](/block-storage/how-to/create-a-volume/)), and ends when you [delete](/block-storage/how-to/delete-a-volume/) the volume from your account. The billing of an Instance stops when it is powered off. @@ -92,10 +92,10 @@ The **Current consumption** panel on the main dashboard of your Scaleway console ### Billing alerts -The Scaleway console **Billing Alerts** feature allows you to set up alerts if your monthly consumption reaches a given budget threshold. An alert can be sent to you by SMS, email, or API webhook. Receiving alerts like this can remind you to delete your Instances or other resources to avoid going over your budget. Read our [dedicated documentation](/console/billing/how-to/use-billing-alerts/) on billing alerts to find out more about setting up this feature. +The Scaleway console **Billing Alerts** feature allows you to set up alerts if your monthly consumption reaches a given budget threshold. An alert can be sent to you by SMS, email, or API webhook. Receiving alerts like this can remind you to delete your Instances or other resources to avoid going over your budget. Read our [dedicated documentation](/billing/how-to/use-billing-alerts/) on billing alerts to find out more about setting up this feature. ## Paying your invoice -We initiate automatic payment of your monthly invoice via the [preferred payment method](/console/billing/how-to/add-payment-method/) you configured. +We initiate automatic payment of your monthly invoice via the [preferred payment method](/billing/how-to/add-payment-method/) you configured. For more information about invoices and payments, check out our dedicated [Billing FAQ page](/faq/billing/). \ No newline at end of file diff --git a/compute/instances/reference-content/understanding-qemu-guest-agent.mdx b/compute/instances/reference-content/understanding-qemu-guest-agent.mdx index f43cf2cf77..ffa3fecd10 100644 --- a/compute/instances/reference-content/understanding-qemu-guest-agent.mdx +++ b/compute/instances/reference-content/understanding-qemu-guest-agent.mdx @@ -25,7 +25,7 @@ This page provides essential insights into this mechanism. Running the QEMU Guest Agent (QGA) on your Instance currently enables the following feature: -- **Automatic network reconfiguration** upon flexible IP attachment or detachment [Learn how to enable/disable this feature](/compute/instances/reference-content/understanding-automatic-network-hot-reconfiguration/). +- **Automatic network reconfiguration** upon flexible IP attachment or detachment [Learn how to enable/disable this feature](/instances/reference-content/understanding-automatic-network-hot-reconfiguration/). Additional features may be added in the future. diff --git a/compute/instances/reference-content/workload-optimized.mdx b/compute/instances/reference-content/workload-optimized.mdx index 8237730427..1f7a22c69d 100644 --- a/compute/instances/reference-content/workload-optimized.mdx +++ b/compute/instances/reference-content/workload-optimized.mdx @@ -13,7 +13,7 @@ categories: tags: instance type workload workload-optimized range POP2-HM POP2-HC POP2-HN --- -An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/compute/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [InstantApps](/compute/instances/concepts/#instantapp). +An Instance is a virtual machine in the cloud. Scaleway supports several [types of Instances](/instances/reference-content/choosing-instance-type/), each with their own set of resources, unique value propositions, and technical specifications. Each Instance supports the essential operating systems and distributions, as well as customized [InstantApps](/instances/concepts/#instantapp). ## Workload-Optimized range: POP2-HM and POP2-HC Instances @@ -39,9 +39,9 @@ See below the technical specifications of Workload-Optimized Instances: ## Complementary services To help build and manage your applications, consider complementing your Workload-Optimized Instance with the following compatible services: -- [Learn how to back up your Instance](/compute/instances/how-to/create-a-backup/) -- [Learn how to create snapshots of your Instance for specific volumes](/compute/instances/how-to/create-a-snapshot/) -- [Learn how to migrate your data from one Instance to another](/compute/instances/how-to/migrate-instances/) +- [Learn how to back up your Instance](/instances/how-to/create-a-backup/) +- [Learn how to create snapshots of your Instance for specific volumes](/instances/how-to/create-a-snapshot/) +- [Learn how to migrate your data from one Instance to another](/instances/how-to/migrate-instances/) ## Matching use cases Try Scaleway Workload-Optimized Instances with the following tutorials: diff --git a/compute/instances/troubleshooting/bootscript-eol.mdx b/compute/instances/troubleshooting/bootscript-eol.mdx index 2fb72ee52a..681177db7c 100644 --- a/compute/instances/troubleshooting/bootscript-eol.mdx +++ b/compute/instances/troubleshooting/bootscript-eol.mdx @@ -17,11 +17,11 @@ Some legacy Instance types (e.g. **VC1-x**, **X64-x**, **Start1-x**) supported t If you are still using one of these Instance types with a bootscript, you have to change your boot configuration in order to keep your Instance operational. -You can find information about the Instances quotas allocated to your account at the following link: [Understanding Organization quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/). +You can find information about the Instances quotas allocated to your account at the following link: [Understanding Organization quotas](/organizations-and-projects/additional-content/organization-quotas/). - If you want to keep using legacy Instance types, you will not be able to create them through the console interface. However, you can still create them using the [Scaleway CLI](/compute/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/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). @@ -31,9 +31,9 @@ You can find information about the Instances quotas allocated to your account at - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) using a bootscript +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) using a bootscript ## How do I know if I am impacted? @@ -49,7 +49,7 @@ If your Instance is using the bootscript option to boot in normal mode you are i Local volume(s) that do not support UEFI cannot be used to boot any other type of Instance. You must retrieve and migrate manually your data to an Instance that supports UEFI boot. Unfortunately, Scaleway cannot access your data to identify if you are using an OS image with or without UEFI partitions. - To do so, [connect to your Instance](/compute/instances/how-to/connect-to-instance/) using SSH and run the following command to list the EFI directories: + To do so, [connect to your Instance](/instances/how-to/connect-to-instance/) using SSH and run the following command to list the EFI directories: ``` ls -ld /sys/firmware/efi ``` @@ -71,7 +71,7 @@ If your Instance is using the bootscript option to boot in normal mode you are i This option is the **recommended** procedure for most Instance types. - **This section applies if your Instance supports UEFI boot.** To continue using your current Instance, [change the boot type](/compute/instances/how-to/use-boot-modes/#how-to-use-local-boot) of the Instance to **Local boot**: + **This section applies if your Instance supports UEFI boot.** To continue using your current Instance, [change the boot type](/instances/how-to/use-boot-modes/#how-to-use-local-boot) of the Instance to **Local boot**: 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click the Instance you wish to start with a local boot. @@ -85,15 +85,15 @@ If your Instance is using the bootscript option to boot in normal mode you are i * If changing the boot type from bootscript to local boot is not successfully achieved via option 1, you can always use option 2 or 3 to migrate your Instance data to a new one. - * If you are a **STARDUST1** user, we recommend that you put your VM into [standby mode](/compute/instances/how-to/use-standby-mode/). This ensures your Instance will not lose its slot in the case of availability shortages. + * If you are a **STARDUST1** user, we recommend that you put your VM into [standby mode](/instances/how-to/use-standby-mode/). This ensures your Instance will not lose its slot in the case of availability shortages. #### Create a snapshot of the volume(s) and export it to Object Storage to retrieve the data - 1. [Create a snapshot](/compute/instances/how-to/create-a-snapshot/) of the volume using the **l_ssd** type of snapshot. - 2. [Export](/compute/instances/how-to/snapshot-import-export-feature/) the snapshot to an Object Storage bucket in the same region as the Instance. + 1. [Create a snapshot](/instances/how-to/create-a-snapshot/) of the volume using the **l_ssd** type of snapshot. + 2. [Export](/instances/how-to/snapshot-import-export-feature/) the snapshot to an Object Storage bucket in the same region as the Instance. 3. Retrieve your data from the Object Storage bucket and reuse it at your convenience. 4. Delete the old Instance that was using a bootscript once you have recovered your data. diff --git a/compute/instances/troubleshooting/cant-connect-ssh.mdx b/compute/instances/troubleshooting/cant-connect-ssh.mdx index 514104c8e7..c2df88545d 100644 --- a/compute/instances/troubleshooting/cant-connect-ssh.mdx +++ b/compute/instances/troubleshooting/cant-connect-ssh.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) Discover how to resolve common SSH connection problems with your Scaleway Instance. Learn to fix errors like "Permission denied (publickey)" and "Remote host identification has changed" with our step-by-step troubleshooting guides. @@ -37,8 +37,8 @@ In this case, the Instance rejected your attempt to connect. There is most proba When you create your Instance, check step 6 of the creation wizard and make sure you are uploading a public key to which you have the corresponding private key on your local machine. - You can view and manage your public SSH keys from the [credentials section of the console](https://console.scaleway.com/project/credentials). -- Credentials are specific to each [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) of your Organization. -- If you [add a new public key to your Project credentials](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) **after** creating a new Instance, it will not automatically be uploaded to the existing Instance. Scaleway only uploads the public SSH keys specified at the time of the Instance's creation. To add a new public SSH key after that point, you will need to connect to your Instance and add the additional public key yourself. Public keys are stored by default in `~/.ssh` with a filename similar to `id_rsa.pub`. +- Credentials are specific to each [Project](/organizations-and-projects/concepts/#project) of your Organization. +- If you [add a new public key to your Project credentials](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) **after** creating a new Instance, it will not automatically be uploaded to the existing Instance. Scaleway only uploads the public SSH keys specified at the time of the Instance's creation. To add a new public SSH key after that point, you will need to connect to your Instance and add the additional public key yourself. Public keys are stored by default in `~/.ssh` with a filename similar to `id_rsa.pub`. ### Check that you have the correct private key on your local machine @@ -123,7 +123,7 @@ You must upload the content of the public part of the SSH key pair to the Scalew 1. Log into the [Scaleway console](https://console.scaleway.com), and navigate to the [SSH keys](https://console.scaleway.com/project/ssh-keys) of your Project dashboard. 2. Click the **Add SSH key** button. 3. Paste the content of the public key (which you copied in the previous step) into the pop-up box, and optionally add a description. Then click **Add SSH key**. -4. [Reboot your Instance](/compute/instances/how-to/use-boot-modes/#how-to-use-local-boot) or run `scw-fetch-ssh-keys --upgrade` to download the new key onto the Instance. You will now be able to [connect to your Instances via SSH](/compute/instances/how-to/connect-to-instance/) +4. [Reboot your Instance](/instances/how-to/use-boot-modes/#how-to-use-local-boot) or run `scw-fetch-ssh-keys --upgrade` to download the new key onto the Instance. You will now be able to [connect to your Instances via SSH](/instances/how-to/connect-to-instance/) Do not edit the `authorized_keys` file on your Instance manually. All content in this file is overwritten during the boot process of the Instance. If you want to add SSH keys to it, upload them to the Scaleway console. @@ -137,4 +137,4 @@ You must upload the content of the public part of the SSH key pair to the Scalew ## Timeout when trying to connect -You may find the SSH connection attempt times out without connecting. This may be expected behavior if the Instance is attached to a Private Network on which there is also a Public Gateway advertising the default route. See our [dedicated troubleshooting](/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/) page for more help with this issue. \ No newline at end of file +You may find the SSH connection attempt times out without connecting. This may be expected behavior if the Instance is attached to a Private Network on which there is also a Public Gateway advertising the default route. See our [dedicated troubleshooting](/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/) page for more help with this issue. \ No newline at end of file diff --git a/compute/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/compute/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index fbd0f8dfee..42859c5bf0 100644 --- a/compute/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/compute/instances/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -15,10 +15,10 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) -The action to take depends on whether DHCP is [activated](/network/vpc/reference-content/vpc-migration/) on your Private Network. +The action to take depends on whether DHCP is [activated](/vpc/reference-content/vpc-migration/) on your Private Network. If it is not, disconnect the Instance from the Private Network, as there may be other factors impacting your Instance, like one of your Instances running a DHCP server. diff --git a/compute/instances/troubleshooting/change-rescue-mode.mdx b/compute/instances/troubleshooting/change-rescue-mode.mdx index 2c5c47bcf5..cbfc4946ff 100644 --- a/compute/instances/troubleshooting/change-rescue-mode.mdx +++ b/compute/instances/troubleshooting/change-rescue-mode.mdx @@ -18,9 +18,9 @@ The previous Instances rescue mode, which relied on bootscripts, was discontinue - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) +- A valid [API key](/iam/how-to/create-api-keys/) ## Updating rescue mode from the Scaleway console diff --git a/compute/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx b/compute/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx index e5fad0f11a..92af19f825 100644 --- a/compute/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx +++ b/compute/instances/troubleshooting/fix-broken-vpn-when-switching-openvpn-vm-to-routed-ip.mdx @@ -20,7 +20,7 @@ This can now be fixed by installing a new version of the OpenVPN scripts, which You can also avoid this situation altogether by installing the package prior to moving to a routed IP. - This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). + This guide addresses specific issues related to OpenVPN Instances. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). diff --git a/compute/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx b/compute/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx index 3dd8e9e059..6ee524c8bd 100644 --- a/compute/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx +++ b/compute/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye.mdx @@ -18,7 +18,7 @@ This guide outlines the steps to enable DNS resolution on a Scaleway Instance th - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Debian Bullseye (11) with an IPv6-only setup +- An [Instance](/instances/how-to/create-an-instance/) running Debian Bullseye (11) with an IPv6-only setup This guide explains how to switch from the traditional `ifupdown` toolset to the more modern `netplan` solution, which is used in recent Debian releases. The process is straightforward if your Instance is using the default network configuration provided by Scaleway metadata. @@ -44,7 +44,7 @@ scw -o json instance server get UUID | jq '.routed_ip_enabled and ([.public_ips[ ``` - Make sure you have installed the [Scaleway CLI tools](/developer-tools/scaleway-cli/quickstart/) on your local machine before running the command above. + Make sure you have installed the [Scaleway CLI tools](/scaleway-cli/quickstart/) on your local machine before running the command above. The command will output: diff --git a/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx b/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx index 79a4519945..09697c918f 100644 --- a/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx +++ b/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster.mdx @@ -16,7 +16,7 @@ categories: On older Debian Buster images, the installed custom version of `cloud-init` may interfere with IPv6 connectivity when the instance transitions to using routed IP. To avoid this, you should install a newer version of `cloud-init` before the migration to routed IP. This procedure also recovers connectivity for an instance already using routed IP. - This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). + This guide addresses specific issues related to older Debian Buster Instances transitioned to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). 1. Install the new `debian-stable` PPA. diff --git a/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx b/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx index fa60b45835..7d5dc1be36 100644 --- a/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx +++ b/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips.mdx @@ -20,7 +20,7 @@ The version of `systemd-networkd` used in Ubuntu Focal does not support the defi A modified `cloud-init` package named `cloud-init_24.2-0ubuntu1~20.04.1+scaleway` has been added to Scaleway's stable PPA to work around this situation. - This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). + This guide addresses specific issues related to Ubuntu Focal Instances with multiple public IPs. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). ## Your Instance has not been rebooted @@ -45,9 +45,9 @@ From this point on, your Instance may be safely rebooted and you will no longer ## Your Instance has rebooted and is no longer reachable -[Rescue mode](/compute/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. +[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. -1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/developer-tools/scaleway-cli/quickstart/): +1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/scaleway-cli/quickstart/): ``` scw instance server stop # Wait for the instance to be stopped. @@ -58,7 +58,7 @@ scw instance server start Replace `` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`. -2. Once the Instance is rebooted, log into your Instance using [SSH](/compute/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: +2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: ```sh cat /proc/partitions major minor #blocks name diff --git a/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx b/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx index 3057654b54..9de26efc4a 100644 --- a/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx +++ b/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance.mdx @@ -27,7 +27,7 @@ The affected O/S distributions are: - This guide addresses specific issues related to RHEL-based Instances after transitioning to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/compute/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). + This guide addresses specific issues related to RHEL-based Instances after transitioning to routed IP. For general information on routed IPs and migration procedures, refer to our [main migration guide](/instances/how-to/migrate-routed-ips/) and the [related FAQ](/faq/instances/#are-there-any-limitations-on-ip-autoconfiguration-with-the-routed-ip-feature). ## Your Instance has not been migrated to routed IP yet diff --git a/compute/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx b/compute/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx index d2debe21c1..82044fb0f1 100644 --- a/compute/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx +++ b/compute/instances/troubleshooting/fix-unreachable-noble-after-reboot.mdx @@ -38,9 +38,9 @@ timeout 10 ## Your Instance has rebooted and is no longer reachable -[Rescue mode](/compute/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. +[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. -1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/developer-tools/scaleway-cli/quickstart/): +1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the [CLI](/scaleway-cli/quickstart/): ``` scw instance server stop scw instance server update boot-type=rescue @@ -49,7 +49,7 @@ timeout 10 Replace `` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`. -2. Once the Instance is rebooted, log into your Instance using [SSH](/compute/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: +2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: ```sh cat /proc/partitions major minor #blocks name diff --git a/compute/instances/troubleshooting/reboot-from-faulty-kernel.mdx b/compute/instances/troubleshooting/reboot-from-faulty-kernel.mdx index bd8ecb0284..6bd57a2796 100644 --- a/compute/instances/troubleshooting/reboot-from-faulty-kernel.mdx +++ b/compute/instances/troubleshooting/reboot-from-faulty-kernel.mdx @@ -13,13 +13,13 @@ categories: - compute --- -[Rescue mode](/compute/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. +[Rescue mode](/instances/concepts/#rescue-mode) allows you to boot your Instance into a temporary operating system, running from the Instance's RAM. Rescue mode is often used to diagnose and resolve issues such as faulty kernel configurations, networking issues, firewall configurations, and more. - A Scaleway account logged into the [console](https://console.scaleway.com) -- An [Instance](/compute/instances/how-to/create-an-instance/) -- Installed and configured the Scaleway [CLI](/compute/instances/api-cli/creating-managing-instances-with-cliv2) on your local computer +- An [Instance](/instances/how-to/create-an-instance/) +- Installed and configured the Scaleway [CLI](/instances/api-cli/creating-managing-instances-with-cliv2) on your local computer 1. Switch the Instance's `boot-type` to `rescue` and reboot your Instance into rescue mode using the CLI-Tools: @@ -30,7 +30,7 @@ categories: Replace `{Instance_ID}` with the unique ID of your Instance, e.g. `0500ebd2-d70d-49af-a969-3ac09b6f7fff`. -2. Once the Instance is rebooted, log into your Instance using [SSH](/compute/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: +2. Once the Instance is rebooted, log into your Instance using [SSH](/instances/how-to/connect-to-instance/) and set up the environment to be able to chroot into it: ```sh cat /proc/partitions major minor #blocks name diff --git a/console/account/concepts.mdx b/console/account/concepts.mdx index 1643357db8..2fad1c9675 100644 --- a/console/account/concepts.mdx +++ b/console/account/concepts.mdx @@ -28,7 +28,7 @@ The Scaleway console allows you to view and manage your Scaleway products, billi ## KYC -**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/console/account/how-to/verify-identity/). +**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/account/how-to/verify-identity/). ## Login information @@ -48,7 +48,7 @@ Multifactor authentication (MFA) is any form of verification that requires two f ## Organization Quotas -Every [Organization](/identity-and-access-management/organizations-and-projects/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Quotas are per product (e.g. Instances) and product type (e.g. GP1-L Instance). Quotas are designed to prevent abuse, and can be viewed on the [Organization dashboard](https://console.scaleway.com/organization/settings) of the console. +Every [Organization](/organizations-and-projects/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Quotas are per product (e.g. Instances) and product type (e.g. GP1-L Instance). Quotas are designed to prevent abuse, and can be viewed on the [Organization dashboard](https://console.scaleway.com/organization/settings) of the console. ## Password @@ -56,7 +56,7 @@ A password is a string of characters associated to your account's email address ## Support plan -Scaleway provides four different types of [support plans](https://console.scaleway.com/support/plans): Basic, Silver, Gold and Platinum. Your support plan determines the level of service and dedicated assistance you have access to, and the guaranteed response time of your support requests. You can [configure your support plan in the console](/console/account/how-to/configure-support-plans/). +Scaleway provides four different types of [support plans](https://console.scaleway.com/support/plans): Basic, Silver, Gold and Platinum. Your support plan determines the level of service and dedicated assistance you have access to, and the guaranteed response time of your support requests. You can [configure your support plan in the console](/account/how-to/configure-support-plans/). ## UUID diff --git a/console/account/how-to/change-console-appearance.mdx b/console/account/how-to/change-console-appearance.mdx index 51a424ae0b..75f1d5822e 100644 --- a/console/account/how-to/change-console-appearance.mdx +++ b/console/account/how-to/change-console-appearance.mdx @@ -13,12 +13,12 @@ categories: - console --- -You can choose the color scheme of the [Scaleway console](/console/account/concepts/#console) according to your preferences. We offer a light, dark, darker, or system-based color scheme. +You can choose the color scheme of the [Scaleway console](/account/concepts/#console) according to your preferences. We offer a light, dark, darker, or system-based color scheme. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click on your name in the top right corner of the Scaleway console. A pop-up menu opens. diff --git a/console/account/how-to/change-language.mdx b/console/account/how-to/change-language.mdx index 1011ee26a4..3bb22bbf40 100644 --- a/console/account/how-to/change-language.mdx +++ b/console/account/how-to/change-language.mdx @@ -13,7 +13,7 @@ categories: - console --- -You can choose which language you would like to view the [Scaleway console](/console/account/concepts/#console) in. This language will also be used for any marketing and product communications Scaleway sends you. +You can choose which language you would like to view the [Scaleway console](/account/concepts/#console) in. This language will also be used for any marketing and product communications Scaleway sends you. diff --git a/console/account/how-to/close-account.mdx b/console/account/how-to/close-account.mdx index ec3f3f9b4b..0d81e2492b 100644 --- a/console/account/how-to/close-account.mdx +++ b/console/account/how-to/close-account.mdx @@ -13,7 +13,7 @@ categories: - console --- -If you do not want to use Scaleway services anymore, you can close your account and/or [erase your personal data](/console/account/how-to/manage-my-personal-data-gdpr/#how-to-erase-your-account-and-personal-data). +If you do not want to use Scaleway services anymore, you can close your account and/or [erase your personal data](/account/how-to/manage-my-personal-data-gdpr/#how-to-erase-your-account-and-personal-data). ## Closing your account or erasing your personal data: what’s the difference @@ -25,7 +25,7 @@ Closing your account will permanently delete your Organization’s servers, reso - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Ownership](/identity-and-access-management/iam/concepts/#owner) of the Organization you intend to delete +- [Ownership](/iam/concepts/#owner) of the Organization you intend to delete We recommend that you delete all resources before closing your account. Otherwise, the remaining resources will be billed for usage before their manual deletion, which can take up to 10 days. diff --git a/console/account/how-to/configure-support-plans.mdx b/console/account/how-to/configure-support-plans.mdx index 6a63b30ad4..2ca43582e1 100644 --- a/console/account/how-to/configure-support-plans.mdx +++ b/console/account/how-to/configure-support-plans.mdx @@ -16,7 +16,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization The default support plan for an Organization is the **Basic** plan, but it can be upgraded on the **Support Plan** tab of the Organization page: diff --git a/console/account/how-to/create-an-account.mdx b/console/account/how-to/create-an-account.mdx index edec622479..a18952bb0b 100644 --- a/console/account/how-to/create-an-account.mdx +++ b/console/account/how-to/create-an-account.mdx @@ -13,6 +13,6 @@ categories: - console --- -Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Create your Scaleway account to gain access to the [Scaleway console](/console/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and deploy our products and services with ease. +Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Create your Scaleway account to gain access to the [Scaleway console](/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and deploy our products and services with ease. diff --git a/console/account/how-to/enforce-mfa.mdx b/console/account/how-to/enforce-mfa.mdx index 3738f78155..0bc3b7e3b1 100644 --- a/console/account/how-to/enforce-mfa.mdx +++ b/console/account/how-to/enforce-mfa.mdx @@ -13,12 +13,12 @@ categories: - console --- -[Multifactor Authentication (MFA)](/console/account/concepts/#multifactor-authentication-mfa) adds an extra layer of security to your Organization. Enforcing MFA will make it mandatory for all users in the Organization. +[Multifactor Authentication (MFA)](/account/concepts/#multifactor-authentication-mfa) adds an extra layer of security to your Organization. Enforcing MFA will make it mandatory for all users in the Organization. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to enforce MFA diff --git a/console/account/how-to/manage-my-personal-data-gdpr.mdx b/console/account/how-to/manage-my-personal-data-gdpr.mdx index 911da1a7d3..eab476e9c6 100644 --- a/console/account/how-to/manage-my-personal-data-gdpr.mdx +++ b/console/account/how-to/manage-my-personal-data-gdpr.mdx @@ -18,7 +18,7 @@ Scaleway makes it easy for you to manage your personal data and privacy via the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization To access the privacy page, open the Organization drop-down menu in the top-right corner of the Scaleway console, and click **Privacy**. @@ -61,7 +61,7 @@ In exercising your right to data portability, you have the right to have your pe ## How to erase your account and personal data -If you do not want to use Scaleway services anymore, you can [close your account](/console/account/how-to/close-account/) and/or delete your personal data. +If you do not want to use Scaleway services anymore, you can [close your account](/account/how-to/close-account/) and/or delete your personal data. ### Closing your account or erasing your personal data: what’s the difference? @@ -74,7 +74,7 @@ Erasing your account and personal data will permanently delete your Organization - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Ownership](/identity-and-access-management/iam/concepts/#owner) of the Organization you intend to delete +- [Ownership](/iam/concepts/#owner) of the Organization you intend to delete Before requesting your personal data be deleted, ensure all your invoices are paid, and no resources are running. **Your request to erase your account will fail if you have unpaid consumption.** diff --git a/console/account/how-to/open-a-support-ticket.mdx b/console/account/how-to/open-a-support-ticket.mdx index 0d69e4d6ba..7ced6dd8a1 100644 --- a/console/account/how-to/open-a-support-ticket.mdx +++ b/console/account/how-to/open-a-support-ticket.mdx @@ -13,7 +13,7 @@ categories: - console --- -Scaleway provides 24/7 basic technical support by ticket for free. You can contact our support team directly from the console. You can also [upgrade your support level](/console/account/how-to/configure-support-plans/) to benefit from phone support and a dedicated account manager. +Scaleway provides 24/7 basic technical support by ticket for free. You can contact our support team directly from the console. You can also [upgrade your support level](/account/how-to/configure-support-plans/) to benefit from phone support and a dedicated account manager. @@ -73,5 +73,5 @@ Examples: - If you have lost access to the Scaleway console and want to create a ticket, you must first [follow this procedure](/console/account/how-to/use-2fa/#how-to-regain-access-to-your-account) to regain access to your account. + If you have lost access to the Scaleway console and want to create a ticket, you must first [follow this procedure](/account/how-to/use-2fa/#how-to-regain-access-to-your-account) to regain access to your account. diff --git a/console/account/how-to/recover-a-lost-password.mdx b/console/account/how-to/recover-a-lost-password.mdx index 4025a163d8..3f116bade8 100644 --- a/console/account/how-to/recover-a-lost-password.mdx +++ b/console/account/how-to/recover-a-lost-password.mdx @@ -21,7 +21,7 @@ If you forget or lose the password to your [Scaleway account](https://console.sc ## Log in without a password using a magic link -The [magic link](/console/account/how-to/log-in-to-the-console/) allows you to access your account without a password, using multifactor authentication. +The [magic link](/account/how-to/log-in-to-the-console/) allows you to access your account without a password, using multifactor authentication. Click **Send magic link** on the Login page of the Scaleway console. diff --git a/console/account/how-to/resolve-abuse.mdx b/console/account/how-to/resolve-abuse.mdx index 67e6665d03..a7da0aeb50 100644 --- a/console/account/how-to/resolve-abuse.mdx +++ b/console/account/how-to/resolve-abuse.mdx @@ -29,7 +29,7 @@ If you encounter any issue with the resolution of an abuse, ensure that you cont 2. Click the **case ID** to view the specifics of the complaint. 3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue. - If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/compute/instances/reference-content/preventing-outgoing-ddos/). + If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/). If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly. * For other types of abuse, here are some suggestions to help you to correct them: diff --git a/console/account/how-to/use-2fa.mdx b/console/account/how-to/use-2fa.mdx index 98ff71ceaf..85696dddf4 100644 --- a/console/account/how-to/use-2fa.mdx +++ b/console/account/how-to/use-2fa.mdx @@ -23,7 +23,7 @@ Multifactor authentication provides extra layers of security. In addition to you ## How to download an MFA app -To use [multifactor authentication](/console/account/concepts/#multifactor-authentication-mfa) on your account, you first need to download an MFA app onto your smartphone. Once configured, MFA apps display a constantly rotating set of codes to use with your different accounts when you are prompted for one during login. Popular MFA apps include: +To use [multifactor authentication](/account/concepts/#multifactor-authentication-mfa) on your account, you first need to download an MFA app onto your smartphone. Once configured, MFA apps display a constantly rotating set of codes to use with your different accounts when you are prompted for one during login. Popular MFA apps include: - [Authy](https://authy.com/download/) - [FreeOTP](https://freeotp.github.io/) - [Google Authenticator](https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=en&gl=US) @@ -51,11 +51,11 @@ If you no longer have access to the device in which you set up your MFA, you can - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Enabled MFA](#how-to-enable-mfa) on your account - If you have lost access to your account and are not able to log in, follow the [Cannot log into my account](/console/account/troubleshooting/cannot-log-into-my-account/) troubleshooting procedure. + If you have lost access to your account and are not able to log in, follow the [Cannot log into my account](/account/troubleshooting/cannot-log-into-my-account/) troubleshooting procedure. 1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**. diff --git a/console/account/how-to/verify-identity.mdx b/console/account/how-to/verify-identity.mdx index b15e1e0a25..680755d552 100644 --- a/console/account/how-to/verify-identity.mdx +++ b/console/account/how-to/verify-identity.mdx @@ -13,7 +13,7 @@ categories: - console --- -Verifying your identity allows you to [unlock resource quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/) and fully benefit from the console's features and products. +Verifying your identity allows you to [unlock resource quotas](/organizations-and-projects/additional-content/organization-quotas/) and fully benefit from the console's features and products. diff --git a/console/account/index.mdx b/console/account/index.mdx index 61453a0161..4701ee132d 100644 --- a/console/account/index.mdx +++ b/console/account/index.mdx @@ -8,7 +8,7 @@ meta: productName="Account" productLogo="accountBilling" description="Creating your Scaleway account gives you access to the Scaleway ecosystem via the Scaleway console and Scaleway API to create, deploy, and scale our products and services with ease." - url="/console/account/quickstart/" + url="/account/quickstart/" label="Scaleway account quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Discover how to create an account in a few easy steps." label="View Quickstart" - url="/console/account/quickstart/" + url="/account/quickstart/" /> diff --git a/console/account/quickstart.mdx b/console/account/quickstart.mdx index 7931933f0c..4fe47a73f1 100644 --- a/console/account/quickstart.mdx +++ b/console/account/quickstart.mdx @@ -13,7 +13,7 @@ categories: - console --- -Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Creating your Scaleway account gives you access to the [Scaleway console](/console/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and you can deploy our products and services with ease. +Scaleway is a complete cloud ecosystem, offering a single way for you to create, deploy and scale your infrastructure in the cloud. Creating your Scaleway account gives you access to the [Scaleway console](/account/concepts/#console) and [Scaleway API](https://www.scaleway.com/en/developers/api/), and you can deploy our products and services with ease. ## Console overview Follow this guided tour to discover how to navigate the console. @@ -25,13 +25,13 @@ Follow this guided tour to discover how to navigate the console. ## How to create resources -Once you have validated your payment method, you can start ordering resources like Instances, Kubernetes Kapsule, Object Storage and more. Find out more about [how to add resources to your Projects](/identity-and-access-management/organizations-and-projects/how-to/add-resources-project/). +Once you have validated your payment method, you can start ordering resources like Instances, Kubernetes Kapsule, Object Storage and more. Find out more about [how to add resources to your Projects](/organizations-and-projects/how-to/add-resources-project/). ## How to close an account Every account has an associated Organization, which in turn has an Owner. When you create your account, you are designated as the Owner of the Organization associated with your account. -When you [close your account](/console/account/how-to/close-account/), you delete all its resources and backups. Any guests who have joined your Organization will lose access because your Organization will no longer exist. +When you [close your account](/account/how-to/close-account/), you delete all its resources and backups. Any guests who have joined your Organization will lose access because your Organization will no longer exist. There is a delay of up to 10 days between the time your account is closed and the time the system deletes your resources. It is recommended to manually delete all your Organization's resources before closing your account. To reopen your account, [contact support](https://console.scaleway.com/support). diff --git a/console/account/troubleshooting/cannot-log-into-my-account.mdx b/console/account/troubleshooting/cannot-log-into-my-account.mdx index 726ba617a2..1cd24ae670 100644 --- a/console/account/troubleshooting/cannot-log-into-my-account.mdx +++ b/console/account/troubleshooting/cannot-log-into-my-account.mdx @@ -20,7 +20,7 @@ When logging into your Scaleway account, you may encounter the following message -This means you tried to log into your account from an unknown [IP address](/network/public-gateways/concepts/#ip-address). You may be logging in from a new device or location. As a security measure, we require you to use a [magic link](/console/account/concepts/#magic-link) to complete authentication. +This means you tried to log into your account from an unknown [IP address](/public-gateways/concepts/#ip-address). You may be logging in from a new device or location. As a security measure, we require you to use a [magic link](/account/concepts/#magic-link) to complete authentication. 1. Check your inbox for the latest email sent by the Scaleway team. 2. Click the **Authenticate myself** button in the email. @@ -28,20 +28,20 @@ This means you tried to log into your account from an unknown [IP address](/netw You are redirected to the Scaleway console and safely logged into your Scaleway account. -If [MFA](/console/account/concepts/#multifactor-authentication-mfa) is enforced for your account, you must also enter the security code received by SMS or provided by an authenticator smartphone app. +If [MFA](/account/concepts/#multifactor-authentication-mfa) is enforced for your account, you must also enter the security code received by SMS or provided by an authenticator smartphone app. ## I have forgotten my password If you forgot or lost your password, you need to reset it. There are several methods to recover it: - - [Passwordless authentication using a Magic Link](/console/account/how-to/recover-a-lost-password/#log-in-without-a-password-using-a-magic-link) - - [Password reset using email validation](/console/account/how-to/recover-a-lost-password/#reset-your-password-using-email-validation) - - [Password recovery in case of lost email account](/console/account/how-to/recover-a-lost-password/#recover-your-password-if-you-lost-access-to-your-email-account) + - [Passwordless authentication using a Magic Link](/account/how-to/recover-a-lost-password/#log-in-without-a-password-using-a-magic-link) + - [Password reset using email validation](/account/how-to/recover-a-lost-password/#reset-your-password-using-email-validation) + - [Password recovery in case of lost email account](/account/how-to/recover-a-lost-password/#recover-your-password-if-you-lost-access-to-your-email-account) ## I have lost my 2FA device -Refer to the [How to use two-factor authentication (MFA)](/console/account/how-to/use-2fa/) page to find the instructions to recover access to your MFA device. +Refer to the [How to use two-factor authentication (MFA)](/account/how-to/use-2fa/) page to find the instructions to recover access to your MFA device. Remember that if you lose both your MFA device and backup codes, you will need to gather all the following information: diff --git a/console/account/troubleshooting/protecting-yourself-fraud-phishing.mdx b/console/account/troubleshooting/protecting-yourself-fraud-phishing.mdx index 3eca5585e9..a051786819 100644 --- a/console/account/troubleshooting/protecting-yourself-fraud-phishing.mdx +++ b/console/account/troubleshooting/protecting-yourself-fraud-phishing.mdx @@ -37,7 +37,7 @@ Phishing is a method where attackers trick you into providing personal informati ### Multi-factor authentication (MFA) -Enable [Multi-factor authentication (MFA) on your Scaleway account](/console/account/how-to/use-2fa/#how-to-update-mfa) to add an extra layer of security. MFA requires a second form of verification beyond just a password. +Enable [Multi-factor authentication (MFA) on your Scaleway account](/account/how-to/use-2fa/#how-to-update-mfa) to add an extra layer of security. MFA requires a second form of verification beyond just a password. ### Strong password practices diff --git a/console/billing/additional-content/understanding-savings-plans.mdx b/console/billing/additional-content/understanding-savings-plans.mdx index 6ac70f6068..102dfd2bbd 100644 --- a/console/billing/additional-content/understanding-savings-plans.mdx +++ b/console/billing/additional-content/understanding-savings-plans.mdx @@ -84,7 +84,7 @@ Currently, we invoice all customers in euros (EUR). If your primary currency is ## How to purchase a Savings Plan -Follow the instructions on the [How to purchase a Savings Plan](/console/billing/how-to/purchase-savings-plan/) documentation plan to do so. +Follow the instructions on the [How to purchase a Savings Plan](/billing/how-to/purchase-savings-plan/) documentation plan to do so. ## Compute Savings Plan diff --git a/console/billing/api-cli/retrieve-monthly-consumption.mdx b/console/billing/api-cli/retrieve-monthly-consumption.mdx index a8ab8abd25..1e24232ac8 100644 --- a/console/billing/api-cli/retrieve-monthly-consumption.mdx +++ b/console/billing/api-cli/retrieve-monthly-consumption.mdx @@ -18,7 +18,7 @@ Follow the procedure below to download your monthly consumption using the Scalew - A Scaleway account and logged into the [console](https://console.scaleway.com/organization) -- Created an [API key](/identity-and-access-management/iam/how-to/create-api-keys/) with sufficient [IAM permissions](/identity-and-access-management/iam/reference-content/permission-sets/) to perform the actions described on this page +- Created an [API key](/iam/how-to/create-api-keys/) with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page - [Installed `curl`](https://curl.se/download.html) - Configured your environment variables. diff --git a/console/billing/concepts.mdx b/console/billing/concepts.mdx index edfee74a3d..531be45f11 100644 --- a/console/billing/concepts.mdx +++ b/console/billing/concepts.mdx @@ -14,7 +14,7 @@ categories: ## Billing alerts -The Billing Alerts functionality within the [Scaleway console](https://console.scaleway.com) allows users to oversee and control their expenses efficiently. This feature allows you to create alerts that notify [users](/identity-and-access-management/iam/concepts/#user) when predefined budget thresholds are met. Your alerts can be seamlessly delivered through SMS, email, or API webhook channels. +The Billing Alerts functionality within the [Scaleway console](https://console.scaleway.com) allows users to oversee and control their expenses efficiently. This feature allows you to create alerts that notify [users](/iam/concepts/#user) when predefined budget thresholds are met. Your alerts can be seamlessly delivered through SMS, email, or API webhook channels. ## Billing API @@ -56,12 +56,12 @@ IAM billing permissions can be given to users to allow them to read and/or manag - **Billing Manager:** Full access to billing management. This allows the user to list, read and edit billing contact information, payment information, billing alerts and invoices. - You can give users permissions via [policies](/identity-and-access-management/iam/concepts/#policy), or by adding them to a [group](/identity-and-access-management/iam/concepts/#group) already attached to a relevant policy. + You can give users permissions via [policies](/iam/concepts/#policy), or by adding them to a [group](/iam/concepts/#group) already attached to a relevant policy. ## KYC -**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/console/account/how-to/verify-identity/). +**K**now **Y**our **C**ustomer is the process of verifying a client's identity. An ID document such as a passport, driver's license or identity card is required to [complete KYC verification](/account/how-to/verify-identity/). ## Pay-as-you-go @@ -73,7 +73,7 @@ The payment methods registered on your account are used to pay your invoice. You ## Project -A Project is a grouping of Scaleway [resources](/identity-and-access-management/iam/concepts/#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-regional, meaning resources located in different [regions](/compute/instances/concepts/#region) can be grouped into one single Project. When grouping resources into different Projects, you can use [IAM](/identity-and-access-management/iam/concepts/#iam) to define custom access rights for each Project. +A Project is a grouping of Scaleway [resources](/iam/concepts/#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-regional, meaning resources located in different [regions](/instances/concepts/#region) can be grouped into one single Project. When grouping resources into different Projects, you can use [IAM](/iam/concepts/#iam) to define custom access rights for each Project. ## Pro-rata billing @@ -81,10 +81,10 @@ You are billed pro-rata on certain products for the initial month of a subscript ## Validation code -Also known as "magic code", "4-digit code" or "verification code". When you [add a payment method](/console/billing/how-to/add-payment-method/) to your account, Scaleway carries out a dummy transaction with a €1 authorization charge, to check the card's validity. This transaction appears on your bank account statement, where a 4-digit validation code shows in the description of the transaction. You are prompted to enter this code in the console to validate the new payment method. +Also known as "magic code", "4-digit code" or "verification code". When you [add a payment method](/billing/how-to/add-payment-method/) to your account, Scaleway carries out a dummy transaction with a €1 authorization charge, to check the card's validity. This transaction appears on your bank account statement, where a 4-digit validation code shows in the description of the transaction. You are prompted to enter this code in the console to validate the new payment method. ## Voucher -A Scaleway voucher provides you with a discount or credits to use on our services. You may receive one as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/console/account/how-to/create-an-account/) and have a valid payment method. Voucher codes are unique and valid only for a defined period. +A Scaleway voucher provides you with a discount or credits to use on our services. You may receive one as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/account/how-to/create-an-account/) and have a valid payment method. Voucher codes are unique and valid only for a defined period. diff --git a/console/billing/how-to/add-billing-contact.mdx b/console/billing/how-to/add-billing-contact.mdx index 4bd781b3ed..02c90649ab 100644 --- a/console/billing/how-to/add-billing-contact.mdx +++ b/console/billing/how-to/add-billing-contact.mdx @@ -18,7 +18,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page. diff --git a/console/billing/how-to/add-payment-method.mdx b/console/billing/how-to/add-payment-method.mdx index c94a88b069..ccee5a42bd 100644 --- a/console/billing/how-to/add-payment-method.mdx +++ b/console/billing/how-to/add-payment-method.mdx @@ -18,7 +18,7 @@ Before you can order Scaleway resources, you must add a payment method to your a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to add a credit card @@ -58,7 +58,7 @@ Before you can order Scaleway resources, you must add a payment method to your a ## How to add a SEPA mandate - * This method requires a successful [KYC verification](/console/account/how-to/verify-identity/). + * This method requires a successful [KYC verification](/account/how-to/verify-identity/). * To add a SEPA mandate, both your postal and bank addresses must be part of the [SEPA zone](https://www.ecb.europa.eu/paym/integration/retail/sepa/html/index.en.html). diff --git a/console/billing/how-to/change-billing-information.mdx b/console/billing/how-to/change-billing-information.mdx index 1a7eedd68f..dee9d98013 100644 --- a/console/billing/how-to/change-billing-information.mdx +++ b/console/billing/how-to/change-billing-information.mdx @@ -16,7 +16,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page. diff --git a/console/billing/how-to/change-payment-method.mdx b/console/billing/how-to/change-payment-method.mdx index ecf2b176d0..42fbe2748a 100644 --- a/console/billing/how-to/change-payment-method.mdx +++ b/console/billing/how-to/change-payment-method.mdx @@ -18,7 +18,7 @@ If you have registered both a **credit card** and a **SEPA mandate**, you can ch - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A valid credit card added to your account, even if you have set up SEPA as the default payment method. diff --git a/console/billing/how-to/download-an-invoice.mdx b/console/billing/how-to/download-an-invoice.mdx index 904dec1d2a..f7cf2bd7d3 100644 --- a/console/billing/how-to/download-an-invoice.mdx +++ b/console/billing/how-to/download-an-invoice.mdx @@ -16,7 +16,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) that allow you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) that allow you to perform actions in the intended Organization 1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page. diff --git a/console/billing/how-to/purchase-savings-plan.mdx b/console/billing/how-to/purchase-savings-plan.mdx index c045ff2c52..35b871d7bf 100644 --- a/console/billing/how-to/purchase-savings-plan.mdx +++ b/console/billing/how-to/purchase-savings-plan.mdx @@ -15,14 +15,14 @@ categories: Savings Plans provide a flexible pricing structure designed to optimize costs. By committing to consistent usage, you unlock substantial discounts compared to pay-as-you-go models, resulting in significant long-term savings. Savings plans are available for Compute resources. -For more details about how Savings Plans work, how they are billed and which resources are covered, refer to the [Understanding Savings Plans](/console/billing/additional-content/understanding-savings-plans/) documentation page. +For more details about how Savings Plans work, how they are billed and which resources are covered, refer to the [Understanding Savings Plans](/billing/additional-content/understanding-savings-plans/) documentation page. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [valid payment method](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) added to your account. -- A [validated identity](/console/account/how-to/verify-identity/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [valid payment method](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) added to your account. +- A [validated identity](/account/how-to/verify-identity/) 1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page. diff --git a/console/billing/how-to/redeem-voucher-code.mdx b/console/billing/how-to/redeem-voucher-code.mdx index 2fe9d3af39..178fa7af93 100644 --- a/console/billing/how-to/redeem-voucher-code.mdx +++ b/console/billing/how-to/redeem-voucher-code.mdx @@ -13,14 +13,14 @@ categories: - billing --- -A Scaleway voucher provides you with a discount or credit to use on our services. You can receive it as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/console/account/how-to/create-an-account/). +A Scaleway voucher provides you with a discount or credit to use on our services. You can receive it as part of a promotional campaign or from your account manager. To redeem a voucher, you need to [create a Scaleway account](/account/how-to/create-an-account/). Voucher codes are unique and valid only for a defined period. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) that allow you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) that allow you to perform actions in the intended Organization - A valid payment method added to your account. diff --git a/console/billing/how-to/use-billing-alerts.mdx b/console/billing/how-to/use-billing-alerts.mdx index f3052821e3..d00d91d6b5 100644 --- a/console/billing/how-to/use-billing-alerts.mdx +++ b/console/billing/how-to/use-billing-alerts.mdx @@ -24,7 +24,7 @@ Your budget, denominated in euros, represents the limit for your expenses. Simul - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a billing alert diff --git a/console/billing/how-to/use-the-cost-manager.mdx b/console/billing/how-to/use-the-cost-manager.mdx index a6da192415..eb92d2c1c5 100644 --- a/console/billing/how-to/use-the-cost-manager.mdx +++ b/console/billing/how-to/use-the-cost-manager.mdx @@ -18,7 +18,7 @@ The Scaleway cost manager is a comprehensive tool to monitor and analyze cloud r - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Billing** in the Organization drop-down menu to go to the **Billing Overview** page. @@ -63,5 +63,5 @@ The Scaleway cost manager is a comprehensive tool to monitor and analyze cloud r You can click **Reset** to clear all filters and start over. - You can retrieve your monthly consumption via the [Billing API](https://www.scaleway.com/en/developers/api/billing/#path-consumption-get-monthly-consumption). Refer to the [Retrieving your monthly consumption](/console/billing/api-cli/retrieve-monthly-consumption/) documentation page for more information. + You can retrieve your monthly consumption via the [Billing API](https://www.scaleway.com/en/developers/api/billing/#path-consumption-get-monthly-consumption). Refer to the [Retrieving your monthly consumption](/billing/api-cli/retrieve-monthly-consumption/) documentation page for more information. \ No newline at end of file diff --git a/console/billing/index.mdx b/console/billing/index.mdx index 6d7ced992b..7815846b6a 100644 --- a/console/billing/index.mdx +++ b/console/billing/index.mdx @@ -8,7 +8,7 @@ meta: productName="Billing" productLogo="accountBilling" description="Billing management features provide a comprehensive overview of our billing features that help you monitor and understand your Scaleway cloud expenditure, pay your invoice, and effectively manage your budget." - url="/console/billing/quickstart" + url="/billing/quickstart" label="Billing Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to add and manage your billing information in a few steps." label="View Quickstart" - url="/console/billing/quickstart" + url="/billing/quickstart" /> diff --git a/console/billing/quickstart.mdx b/console/billing/quickstart.mdx index a97bc40952..afda701bd6 100644 --- a/console/billing/quickstart.mdx +++ b/console/billing/quickstart.mdx @@ -23,7 +23,7 @@ Before you can order Scaleway resources, you must add your payment method to you - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to add a payment method @@ -57,7 +57,7 @@ You can choose between two payment methods: **credit card** or **SEPA mandate**. ### How to add a SEPA mandate - This method requires a successful [KYC verification](/console/account/how-to/verify-identity/). + This method requires a successful [KYC verification](/account/how-to/verify-identity/). 1. Click **SEPA Direct Debit** under **Payment Methods**. diff --git a/containers/container-registry/concepts.mdx b/containers/container-registry/concepts.mdx index e4fdaa9de6..eaca615f06 100644 --- a/containers/container-registry/concepts.mdx +++ b/containers/container-registry/concepts.mdx @@ -18,23 +18,23 @@ Scaleway Container Registry is a fully-managed mutualized Container Registry, de ## Container image -A container image is a file that includes all the requirements and instructions of a complete and executable version of an application. When running, it becomes one or multiple instances of that application. You can [pull the image](/containers/container-registry/how-to/pull-images/), [edit its settings](/containers/container-registry/how-to/manage-image-privacy-settings/), [view its versions](/containers/container-registry/how-to/display-image-versions/) or [delete it](/containers/container-registry/how-to/delete-image/). +A container image is a file that includes all the requirements and instructions of a complete and executable version of an application. When running, it becomes one or multiple instances of that application. You can [pull the image](/container-registry/how-to/pull-images/), [edit its settings](/container-registry/how-to/manage-image-privacy-settings/), [view its versions](/container-registry/how-to/display-image-versions/) or [delete it](/container-registry/how-to/delete-image/). ## Docker -Docker is a tool that makes it easy to manage container images. You can [use Docker from your local computer](/containers/container-registry/how-to/connect-docker-cli/) to [push and pull images to and from your Scaleway Container Registry](/containers/container-registry/how-to/push-images/). +Docker is a tool that makes it easy to manage container images. You can [use Docker from your local computer](/container-registry/how-to/connect-docker-cli/) to [push and pull images to and from your Scaleway Container Registry](/container-registry/how-to/push-images/). ## Image privacy policies -Image privacy policies specify whether everyone has the right to pull the image or not. When an image is set to public, anyone is able to pull it. [Set your image to private](/containers/container-registry/how-to/manage-image-privacy-settings/) if you want to restrict access. You can also specify that an image should inherit its privacy policy from its namespace. +Image privacy policies specify whether everyone has the right to pull the image or not. When an image is set to public, anyone is able to pull it. [Set your image to private](/container-registry/how-to/manage-image-privacy-settings/) if you want to restrict access. You can also specify that an image should inherit its privacy policy from its namespace. ## Namespace -Namespaces allow you to [manage your Container Registry](/containers/container-registry/how-to/create-namespace/) in a simple, clear and human-readable way. A namespace is a collection of container images, each bearing the unique identifier of that namespace (each namespace must have a globally unique name). A namespace belongs to a user, who is responsible for configuring the push and pull permissions with [privacy policies](#namespace-privacy-policies). +Namespaces allow you to [manage your Container Registry](/container-registry/how-to/create-namespace/) in a simple, clear and human-readable way. A namespace is a collection of container images, each bearing the unique identifier of that namespace (each namespace must have a globally unique name). A namespace belongs to a user, who is responsible for configuring the push and pull permissions with [privacy policies](#namespace-privacy-policies). ## Namespace privacy policies -Namespace privacy policies specify whether everyone has the right to pull an image from the namespace or not. When an image is in a public namespace, anyone is able to pull it. [Set your namespace to private](/containers/container-registry/how-to/manage-namespace-privacy-policies/) if you want to restrict access. +Namespace privacy policies specify whether everyone has the right to pull an image from the namespace or not. When an image is in a public namespace, anyone is able to pull it. [Set your namespace to private](/container-registry/how-to/manage-namespace-privacy-policies/) if you want to restrict access. ## Registry diff --git a/containers/container-registry/how-to/connect-docker-cli.mdx b/containers/container-registry/how-to/connect-docker-cli.mdx index 876b0f67da..190f8d59be 100644 --- a/containers/container-registry/how-to/connect-docker-cli.mdx +++ b/containers/container-registry/how-to/connect-docker-cli.mdx @@ -18,8 +18,8 @@ Docker is a tool that makes it easy to manage container images. You can use Dock - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - [Docker](https://www.docker.com/) installed on your local computer @@ -32,7 +32,7 @@ Docker is a tool that makes it easy to manage container images. You can use Dock docker login rg.fr-par.scw.cloud/mynamespace -u nologin --password-stdin <<< "$SCW_SECRET_KEY" ``` - Replace `"$SCW_SECRET_KEY"` with your [API secret key](/identity-and-access-management/iam/how-to/create-api-keys/) and `mynamespace` with the name of your namespace. + Replace `"$SCW_SECRET_KEY"` with your [API secret key](/iam/how-to/create-api-keys/) and `mynamespace` with the name of your namespace. Once logged in, confirmation is displayed: diff --git a/containers/container-registry/how-to/create-namespace.mdx b/containers/container-registry/how-to/create-namespace.mdx index d7d2ba0e9b..eed2bf9957 100644 --- a/containers/container-registry/how-to/create-namespace.mdx +++ b/containers/container-registry/how-to/create-namespace.mdx @@ -13,14 +13,14 @@ categories: - container-registry --- -[Scaleway Container Registry](/containers/container-registry/concepts/#container-registry) is a fully-managed, mutualized container registry, designed to facilitate the storage, management, and deployment of container images. The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. +[Scaleway Container Registry](/container-registry/concepts/#container-registry) is a fully-managed, mutualized container registry, designed to facilitate the storage, management, and deployment of container images. The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. -Within your Container Registry, [namespaces](/containers/container-registry/concepts/#namespace) allow you to manage your registry in a clear, simple and human-readable way. A namespace is a collection of container images, each bearing the unique identifier of that namespace. To start using your Container Registry, you first need to create a namespace. +Within your Container Registry, [namespaces](/container-registry/concepts/#namespace) allow you to manage your registry in a clear, simple and human-readable way. A namespace is a collection of container images, each bearing the unique identifier of that namespace. To start using your Container Registry, you first need to create a namespace. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. If you do not have a Registry already created, the product creation page is displayed. @@ -32,7 +32,7 @@ Within your Container Registry, [namespaces](/containers/container-registry/conc * The namespace's **Privacy Policies** - A namespace can either be [public or private](/containers/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. + A namespace can either be [public or private](/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. 4. Click **Create namespace** to create the namespace. diff --git a/containers/container-registry/how-to/delete-image.mdx b/containers/container-registry/how-to/delete-image.mdx index 985b9e8083..c0e6bf7c25 100644 --- a/containers/container-registry/how-to/delete-image.mdx +++ b/containers/container-registry/how-to/delete-image.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) -- [Pushed an image](/containers/container-registry/how-to/push-images/) to your namespace +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) +- [Pushed an image](/container-registry/how-to/push-images/) to your namespace 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. diff --git a/containers/container-registry/how-to/delete-namespace.mdx b/containers/container-registry/how-to/delete-namespace.mdx index 30025dc49a..6bd739b680 100644 --- a/containers/container-registry/how-to/delete-namespace.mdx +++ b/containers/container-registry/how-to/delete-namespace.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. diff --git a/containers/container-registry/how-to/display-image-versions.mdx b/containers/container-registry/how-to/display-image-versions.mdx index dfffee5a33..0e377b20f3 100644 --- a/containers/container-registry/how-to/display-image-versions.mdx +++ b/containers/container-registry/how-to/display-image-versions.mdx @@ -18,8 +18,8 @@ Scaleway Container Registry supports image versioning. This allows you to track - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. diff --git a/containers/container-registry/how-to/manage-image-privacy-settings.mdx b/containers/container-registry/how-to/manage-image-privacy-settings.mdx index aa0780a6dd..2b5128bb6b 100644 --- a/containers/container-registry/how-to/manage-image-privacy-settings.mdx +++ b/containers/container-registry/how-to/manage-image-privacy-settings.mdx @@ -13,14 +13,14 @@ categories: - container-registry --- -The [image privacy policy](/containers/container-registry/concepts/#image-privacy-policies) specifies whether everyone is granted access to pull the image or not. +The [image privacy policy](/container-registry/concepts/#image-privacy-policies) specifies whether everyone is granted access to pull the image or not. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) -- An image [pushed](/containers/container-registry/how-to/push-images/) to your namespace +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) +- An image [pushed](/container-registry/how-to/push-images/) to your namespace 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. diff --git a/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx b/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx index 9be605e7ee..5b8765c0eb 100644 --- a/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx +++ b/containers/container-registry/how-to/manage-namespace-privacy-policies.mdx @@ -18,9 +18,9 @@ A namespace's privacy policy specifies whether everyone is granted access to pul - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) -- An image [pushed](/containers/container-registry/how-to/push-images/) to your namespace +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) +- An image [pushed](/container-registry/how-to/push-images/) to your namespace 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. @@ -28,7 +28,7 @@ A namespace's privacy policy specifies whether everyone is granted access to pul 3. Click the **Namespace settings** tab, then configure the policy by selecting either **Public** or **Private**. - Each container image may additionally have its [own privacy policies](/containers/container-registry/how-to/manage-image-privacy-settings/). + Each container image may additionally have its [own privacy policies](/container-registry/how-to/manage-image-privacy-settings/). diff --git a/containers/container-registry/how-to/pull-images.mdx b/containers/container-registry/how-to/pull-images.mdx index a7d6e4b8d9..6c1942d00b 100644 --- a/containers/container-registry/how-to/pull-images.mdx +++ b/containers/container-registry/how-to/pull-images.mdx @@ -13,15 +13,15 @@ categories: - container-registry --- -After [configuring Docker on your local machine](/containers/container-registry/how-to/connect-docker-cli/), you can use it to pull images from your Container Registry. +After [configuring Docker on your local machine](/container-registry/how-to/connect-docker-cli/), you can use it to pull images from your Container Registry. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) - [Docker](https://www.docker.com/) installed on your local computer -- Access to your [namespace](/containers/container-registry/how-to/connect-docker-cli/) +- Access to your [namespace](/container-registry/how-to/connect-docker-cli/) 1. Click **Container Registry** in the **Containers** section of the side menu. A list of your namespaces displays. diff --git a/containers/container-registry/how-to/push-images.mdx b/containers/container-registry/how-to/push-images.mdx index ace6fd770e..65ee43af82 100644 --- a/containers/container-registry/how-to/push-images.mdx +++ b/containers/container-registry/how-to/push-images.mdx @@ -13,15 +13,15 @@ categories: - container-registry --- -After [configuring Docker on your local machine](/containers/container-registry/how-to/connect-docker-cli/), you can use it to pull images from their library and push them to your Container Registry. This page shows you how to pull, tag, and push a first image to your Scaleway Container Registry namespace, using an Ubuntu image as an example. +After [configuring Docker on your local machine](/container-registry/how-to/connect-docker-cli/), you can use it to pull images from their library and push them to your Container Registry. This page shows you how to pull, tag, and push a first image to your Scaleway Container Registry namespace, using an Ubuntu image as an example. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) - [Docker](https://www.docker.com/) installed on your local computer -- Access to your [namespace](/containers/container-registry/how-to/connect-docker-cli/) +- Access to your [namespace](/container-registry/how-to/connect-docker-cli/) 1. Open a terminal window on your local computer. diff --git a/containers/container-registry/index.mdx b/containers/container-registry/index.mdx index 7ebd4595a0..509981fb1a 100644 --- a/containers/container-registry/index.mdx +++ b/containers/container-registry/index.mdx @@ -8,7 +8,7 @@ meta: productName="Container Registry" productLogo="containerRegistry" description="Container Registry is a fully-managed mutualized container registry designed to facilitate the storage, management, and deployment of container images." - url="/containers/container-registry/quickstart/" + url="/container-registry/quickstart/" label="Container Registry Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to create a Container Registry namespace and more, in a few steps." label="View Quickstart" - url="/containers/container-registry/quickstart/" + url="/container-registry/quickstart/" /> diff --git a/containers/container-registry/quickstart.mdx b/containers/container-registry/quickstart.mdx index 2105e4a50b..daac70c97d 100644 --- a/containers/container-registry/quickstart.mdx +++ b/containers/container-registry/quickstart.mdx @@ -13,12 +13,12 @@ categories: - container-registry --- -Scaleway [Container Registry](/containers/container-registry/concepts/#container-registry) is a fully-managed mutualized container registry, designed to facilitate the storage, management, and deployment of container images. The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. You can create your Container Registry namespace, connect it to the Docker CLI, then use Docker to push and pull images to and from your registry. When you no longer need an image, you can delete it from your Container Registry. +Scaleway [Container Registry](/container-registry/concepts/#container-registry) is a fully-managed mutualized container registry, designed to facilitate the storage, management, and deployment of container images. The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. You can create your Container Registry namespace, connect it to the Docker CLI, then use Docker to push and pull images to and from your registry. When you no longer need an image, you can delete it from your Container Registry. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Container Registry namespace @@ -31,7 +31,7 @@ Scaleway [Container Registry](/containers/container-registry/concepts/#container * The namespace's **Privacy Policies** - A namespace can either be [public or private](/containers/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. + A namespace can either be [public or private](/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. 4. Click **Create namespace** to create the namespace. @@ -40,7 +40,7 @@ Scaleway [Container Registry](/containers/container-registry/concepts/#container - Installed [Docker](https://www.docker.com/) on your local computer -- [Generated your API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Generated your API key](/iam/how-to/create-api-keys/) 1. Click **Container Registry** in the **Containers** section of the [Scaleway console](https://console.scaleway.com) side menu. The Container Registry namespaces dashboard displays. 2. Click , then **Push instructions** next to the namespace you want to push to. A pop-up displays. @@ -51,7 +51,7 @@ Scaleway [Container Registry](/containers/container-registry/concepts/#container ``` - Replace `` with your [API secret key](/identity-and-access-management/iam/how-to/create-api-keys/) and `` with the name of your namespace. + Replace `` with your [API secret key](/iam/how-to/create-api-keys/) and `` with the name of your namespace. Once logged in, a confirmation is displayed: diff --git a/containers/kubernetes/api-cli/changing-control-plane-offer.mdx b/containers/kubernetes/api-cli/changing-control-plane-offer.mdx index 784a6f3602..7ddb6bde5c 100644 --- a/containers/kubernetes/api-cli/changing-control-plane-offer.mdx +++ b/containers/kubernetes/api-cli/changing-control-plane-offer.mdx @@ -22,10 +22,10 @@ In this tutorial, we show you how to change your cluster type using the Scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the most recent version of the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) -- [Created a cluster](/containers/kubernetes/how-to/create-cluster/) +- [Created a cluster](/kubernetes/how-to/create-cluster/) 1. Run the following command to list the viable cluster types. ``` diff --git a/containers/kubernetes/api-cli/cluster-monitoring.mdx b/containers/kubernetes/api-cli/cluster-monitoring.mdx index da3d2ec5ff..bffd93d81c 100644 --- a/containers/kubernetes/api-cli/cluster-monitoring.mdx +++ b/containers/kubernetes/api-cli/cluster-monitoring.mdx @@ -14,16 +14,16 @@ categories: --- - Kubernetes Kapsule is fully integrated with Scaleway's [Observability Cockpit](/observability/cockpit/quickstart/). - You can [monitor your cluster](/containers/kubernetes/how-to/monitor-cluster/) directly from the cluster's dashboard, eliminating the need to set up your own monitoring solution. + Kubernetes Kapsule is fully integrated with Scaleway's [Observability Cockpit](/cockpit/quickstart/). + You can [monitor your cluster](/kubernetes/how-to/monitor-cluster/) directly from the cluster's dashboard, eliminating the need to set up your own monitoring solution. The following content is provided for informational purposes only. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster - Installed and configured `kubectl`, the [command line interface](https://kubernetes.io/docs/reference/kubectl/overview/) for Kubernetes, on your local machine - Installed `helm`, the Kubernetes [package manager](https://helm.sh/), on your local machine (version 3.2+) diff --git a/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx b/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx index e50e7df11e..697183b89b 100644 --- a/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx +++ b/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2.mdx @@ -15,7 +15,7 @@ categories: Scaleway's Kubernetes (K8s) Kapsule provides you with a managed environment to create, configure and run a cluster of pre-configured machines for containerized applications. You will be able to create clusters without the complexity of managing the infrastructure. -You can [create](/containers/kubernetes/how-to/create-cluster/) and [manage](/containers/kubernetes/how-to/edit-cluster/) your Kapsule clusters from the console, via the [API](https://www.scaleway.com/en/developers/api/kubernetes/) or via the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). +You can [create](/kubernetes/how-to/create-cluster/) and [manage](/kubernetes/how-to/edit-cluster/) your Kapsule clusters from the console, via the [API](https://www.scaleway.com/en/developers/api/kubernetes/) or via the [Scaleway Command Line Interface](https://github.com/scaleway/scaleway-cli). ## Scaleway command line interface overview @@ -24,8 +24,8 @@ You can [create](/containers/kubernetes/how-to/create-cluster/) and [manage](/co - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) ## Configuring the CLI @@ -54,7 +54,7 @@ You can [create](/containers/kubernetes/how-to/create-cluster/) and [manage](/co ``` Enter a valid secret-key or an email ``` -3. Enter either the email address for your account (you will then be asked for your password), or your [API secret key](/identity-and-access-management/iam/how-to/create-api-keys/): +3. Enter either the email address for your account (you will then be asked for your password), or your [API secret key](/iam/how-to/create-api-keys/): ``` To improve this tool we rely on diagnostic and usage data. Sending such data is optional and can be disabled at any time by running "scw config set send-telemetry=false". @@ -89,14 +89,14 @@ You can [create](/containers/kubernetes/how-to/create-cluster/) and [manage](/co ## Creating a Kubernetes Kapsule cluster -1. Type the following command in your terminal to create a [Kubernetes Kapsule cluster](/containers/kubernetes/concepts/#cluster): +1. Type the following command in your terminal to create a [Kubernetes Kapsule cluster](/kubernetes/concepts/#cluster): `scw k8s cluster create name=name-of-your-cluster` You can add the `type` argument to specify the cluster type. For an extensive list of the available cluster types, run the [list cluster types CLI command](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/k8s.md#list-available-cluster-types-for-a-cluster). If you do not specify a cluster type, a cluster of Kapsule type is created by default.

- It is possible to change the cluster type anytime. Depending on your current cluster type, the types you can change to vary. Refer to the [Changing the control plane offer](/containers/kubernetes/api-cli/changing-control-plane-offer/) documentation page for more information.

+ It is possible to change the cluster type anytime. Depending on your current cluster type, the types you can change to vary. Refer to the [Changing the control plane offer](/kubernetes/api-cli/changing-control-plane-offer/) documentation page for more information.

For more information about cluster types, refer to the [Kubernetes FAQ page](/faq/kubernetes/#can-i-choose-the-type-of-control-plane-for-my-cluster). diff --git a/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx b/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx index 68de0bd1f3..482feb2d6a 100644 --- a/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx +++ b/containers/kubernetes/api-cli/external-secrets-kubernetes.mdx @@ -17,15 +17,15 @@ dates: [External Secrets](https://external-secrets.io) is a Kubernetes operator that allows you to manage the lifecycle of your secrets from external providers. -In this tutorial you will learn how to deploy External Secrets and its services on [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule), the managed Kubernetes service from Scaleway. +In this tutorial you will learn how to deploy External Secrets and its services on [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule), the managed Kubernetes service from Scaleway. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Configured [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Configured [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) - Installed `helm`, the Kubernetes [package manager](https://helm.sh/), on your local machine (version 3.2 or latest) ## Preparing the Kubernetes Kapsule cluster @@ -61,7 +61,7 @@ kubectl create secret generic scwsm-secret --from-file=./access-key --from-file= ## Create your first SecretStore Define a `SecretStore` resource in Kubernetes to inform External Secrets where to fetch secrets from. -Secret Manager is a regionalized product, so you will need to specify the [region](/identity-and-access-management/secret-manager/concepts/#region) in which you want to create your secret. +Secret Manager is a regionalized product, so you will need to specify the [region](/secret-manager/concepts/#region) in which you want to create your secret. 1. Copy the template below and paste it into a file named `secret-store.yaml`. diff --git a/containers/kubernetes/api-cli/managing-storage.mdx b/containers/kubernetes/api-cli/managing-storage.mdx index 234e03e9b9..ff3752915c 100644 --- a/containers/kubernetes/api-cli/managing-storage.mdx +++ b/containers/kubernetes/api-cli/managing-storage.mdx @@ -18,13 +18,13 @@ The [Scaleway Block Storage volume](https://www.scaleway.com/en/block-storage/) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Your Scaleway Project or Organization ID -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes cluster running on Scaleway Instances (v1.21+) +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes cluster running on Scaleway Instances (v1.21+) - Refer to our video tutorial [Getting Started with Kubernetes Part 4 - Storage](/containers/kubernetes/videos/) to view a visual presentation and step-by-step guidance of how to manage Block Storage volumes on Kubernetes with the Scaleway CSI. + Refer to our video tutorial [Getting Started with Kubernetes Part 4 - Storage](/kubernetes/videos/) to view a visual presentation and step-by-step guidance of how to manage Block Storage volumes on Kubernetes with the Scaleway CSI. ## Verification of CSI driver status @@ -35,9 +35,9 @@ To verify if the driver is running, use the following command: kubectl get csidriver ``` -The output of this command provides a quick status update on the CSI plugin within your Kubernetes cluster. For the latest features and enhancements, consider upgrading to [release 0.3](https://github.com/scaleway/scaleway-csi/tree/release-0.3#block-storage-low-latency), which supports **[Block Storage low latency](/storage/block/quickstart/)** volumes. +The output of this command provides a quick status update on the CSI plugin within your Kubernetes cluster. For the latest features and enhancements, consider upgrading to [release 0.3](https://github.com/scaleway/scaleway-csi/tree/release-0.3#block-storage-low-latency), which supports **[Block Storage low latency](/block-storage/quickstart/)** volumes. -To identify your current CSI release version, navigate to the [Cockpit interface](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/), specifically the **Kubernetes Cluster - Overview** dashboard. +To identify your current CSI release version, navigate to the [Cockpit interface](/cockpit/how-to/access-grafana-and-managed-dashboards/), specifically the **Kubernetes Cluster - Overview** dashboard. ## Upgrading to CSI version 0.3 diff --git a/containers/kubernetes/api-cli/managing-tags.mdx b/containers/kubernetes/api-cli/managing-tags.mdx index c6e408ae6e..4974b92487 100644 --- a/containers/kubernetes/api-cli/managing-tags.mdx +++ b/containers/kubernetes/api-cli/managing-tags.mdx @@ -23,8 +23,8 @@ The Scaleway Cloud Controller Manager (CCM) will also synchronize the tags of Sc - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes cluster](/kubernetes/how-to/create-cluster/) ## Labels diff --git a/containers/kubernetes/concepts.mdx b/containers/kubernetes/concepts.mdx index ac967a8b9a..68fa5fc6c9 100644 --- a/containers/kubernetes/concepts.mdx +++ b/containers/kubernetes/concepts.mdx @@ -14,7 +14,7 @@ categories: ## Autoheal -[Autoheal](/containers/kubernetes/reference-content/using-kapsule-autoheal-feature/) allows you to keep the nodes in your pool in a healthy state. When enabled, periodic checks are performed to ensure all your nodes are running properly. +[Autoheal](/kubernetes/reference-content/using-kapsule-autoheal-feature/) allows you to keep the nodes in your pool in a healthy state. When enabled, periodic checks are performed to ensure all your nodes are running properly. ## Autoscale @@ -36,11 +36,11 @@ A single-zone cluster has its control plane operating in one zone, managing work ### Multi-AZ clusters -A Multi-AZ cluster features a single control plane in one zone but has nodes running across multiple zones. In case of a control plane outage or during cluster upgrades, workloads continue to run. However, the cluster and its workloads cannot be configured until the control plane is restored. Multi-zonal clusters offer a balance between availability and cost for stable workloads. During a zonal outage, workloads in that zone are disrupted, but they remain available in other zones. Multi AZ clusters have [technical limitations](/containers/kubernetes/reference-content/multi-az-clusters/#limitations). For maintaining high availability, consider using a regional cluster. +A Multi-AZ cluster features a single control plane in one zone but has nodes running across multiple zones. In case of a control plane outage or during cluster upgrades, workloads continue to run. However, the cluster and its workloads cannot be configured until the control plane is restored. Multi-zonal clusters offer a balance between availability and cost for stable workloads. During a zonal outage, workloads in that zone are disrupted, but they remain available in other zones. Multi AZ clusters have [technical limitations](/kubernetes/reference-content/multi-az-clusters/#limitations). For maintaining high availability, consider using a regional cluster. ### Regional clusters -A regional cluster has multiple replicas of the control plane distributed across multiple zones within a single region. Such cluster is only available with HA Dedicated Control Planes. Nodes can also be spread across multiple zones or restricted to a single zone, based on configuration. By default, Scaleway does not replicate each node pool across all zones of the control plane's region. You can customize this by specifying the zones for the cluster's nodes. Regional clusters are ideal for running production workloads due to their higher availability compared to zonal clusters. Regional clusters still have [technical limitations](/containers/kubernetes/reference-content/multi-az-clusters/#limitations). +A regional cluster has multiple replicas of the control plane distributed across multiple zones within a single region. Such cluster is only available with HA Dedicated Control Planes. Nodes can also be spread across multiple zones or restricted to a single zone, based on configuration. By default, Scaleway does not replicate each node pool across all zones of the control plane's region. You can customize this by specifying the zones for the cluster's nodes. Regional clusters are ideal for running production workloads due to their higher availability compared to zonal clusters. Regional clusters still have [technical limitations](/kubernetes/reference-content/multi-az-clusters/#limitations). ## Container Network Interface (CNI) @@ -60,7 +60,7 @@ The control plane manages the worker nodes and the pods in the cluster. In produ ## Easy Deploy -The Easy Deploy feature allows you to pull images directly from Scaleway Container Registry, instantly deploying containerized applications in your Kubernetes Kapsule cluster. With only the basic options to set, you can use Kubernetes Kapsule without needing to manage your `.yaml ` manifests. Check out our documentation on [creating containerized applications with the Easy Deploy feature](/containers/kubernetes/how-to/enable-easy-deploy/) for more information. +The Easy Deploy feature allows you to pull images directly from Scaleway Container Registry, instantly deploying containerized applications in your Kubernetes Kapsule cluster. With only the basic options to set, you can use Kubernetes Kapsule without needing to manage your `.yaml ` manifests. Check out our documentation on [creating containerized applications with the Easy Deploy feature](/kubernetes/how-to/enable-easy-deploy/) for more information. ## Image pull secret @@ -72,7 +72,7 @@ Ingress is an API object that manages external access to the services in a clust ## Ingress controller -Kubernetes supports a high-level abstraction called Ingress, which allows simple host or URL-based HTTP routing. Ingress is a core concept (in beta) of Kubernetes, but is always implemented by a third-party proxy. These implementations are known as ingress controllers. An ingress controller is responsible for reading the Ingress Resource information and processing that data accordingly. Different ingress controllers have extended the specification in different ways to support additional use cases. For more information, see our [dedicated how-to](/containers/kubernetes/how-to/deploy-ingress-controller/) on deploying ingress controllers. +Kubernetes supports a high-level abstraction called Ingress, which allows simple host or URL-based HTTP routing. Ingress is a core concept (in beta) of Kubernetes, but is always implemented by a third-party proxy. These implementations are known as ingress controllers. An ingress controller is responsible for reading the Ingress Resource information and processing that data accordingly. Different ingress controllers have extended the specification in different ways to support additional use cases. For more information, see our [dedicated how-to](/kubernetes/how-to/deploy-ingress-controller/) on deploying ingress controllers. ## Kubeconfig @@ -80,7 +80,7 @@ Kubernetes supports a high-level abstraction called Ingress, which allows simple ## Kubectl -Kubectl is the command line interface for running commands against Kubernetes clusters. You can [use kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) to connect to and manage your clusters from the command line. +Kubectl is the command line interface for running commands against Kubernetes clusters. You can [use kubectl](/kubernetes/how-to/connect-cluster-kubectl/) to connect to and manage your clusters from the command line. ## Kubernetes @@ -88,13 +88,13 @@ Kubernetes (K8s) is an open-source platform for managing containerized workloads ## Kubernetes Kapsule -Kubernetes Kapsule provides a managed environment for you to create, configure, and run a cluster of pre-configured machines for containerized applications. It allows you to create [Kubernetes](https://kubernetes.io) clusters without the complexity of managing the infrastructure. Kubernetes Kapsule clusters are composed uniquely of Scaleway Instances. Read our documentation on [how to create a Kubernetes Kapsule](/containers/kubernetes/how-to/create-cluster/). To create clusters including Instances from external cloud providers, see [Kubernetes Kosmos](#kubernetes-kosmos). +Kubernetes Kapsule provides a managed environment for you to create, configure, and run a cluster of pre-configured machines for containerized applications. It allows you to create [Kubernetes](https://kubernetes.io) clusters without the complexity of managing the infrastructure. Kubernetes Kapsule clusters are composed uniquely of Scaleway Instances. Read our documentation on [how to create a Kubernetes Kapsule](/kubernetes/how-to/create-cluster/). To create clusters including Instances from external cloud providers, see [Kubernetes Kosmos](#kubernetes-kosmos). ## Kubernetes Kosmos -Kubernetes Kosmos is the first-of-its-kind managed multi-cloud Kubernetes Engine. It allows the connection of Instances and servers from any Cloud provider to a single managed control plane hosted by Scaleway. Using Kubernetes in a multi-cloud cluster provides a high level of application redundancy by authorizing pod replication across different providers, regions, and Availability Zones. See our documentation to learn [how to create a Kubernetes Kosmos cluster](/containers/kubernetes/how-to/create-kosmos-cluster/). +Kubernetes Kosmos is the first-of-its-kind managed multi-cloud Kubernetes Engine. It allows the connection of Instances and servers from any Cloud provider to a single managed control plane hosted by Scaleway. Using Kubernetes in a multi-cloud cluster provides a high level of application redundancy by authorizing pod replication across different providers, regions, and Availability Zones. See our documentation to learn [how to create a Kubernetes Kosmos cluster](/kubernetes/how-to/create-kosmos-cluster/). -[Learn more about the differences between Kapsule and Kosmos](/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos/). +[Learn more about the differences between Kapsule and Kosmos](/kubernetes/reference-content/understanding-differences-kapsule-kosmos/). ## Load Balancer @@ -105,7 +105,7 @@ Load balancing efficiently distributes incoming network traffic across a group o Scaleway Kapsule and Kosmos are managed Kubernetes services. Scaleway's managed Kubernetes service abstracts away the complexities of managing and operating a Kubernetes cluster, enabling developers to focus on application development and deployment while ensuring a reliable and scalable environment for running containerized workloads. These services allow users to focus on deploying and running applications on Kubernetes without worrying about the underlying infrastructure and operational complexities. -For more information, refer to the [managed Kubernetes service definition](/containers/kubernetes/reference-content/managed-kubernetes-service-definition/). +For more information, refer to the [managed Kubernetes service definition](/kubernetes/reference-content/managed-kubernetes-service-definition/). ## Namespace diff --git a/containers/kubernetes/how-to/access-audit-logs.mdx b/containers/kubernetes/how-to/access-audit-logs.mdx index abfa0ab41c..b9836c764b 100644 --- a/containers/kubernetes/how-to/access-audit-logs.mdx +++ b/containers/kubernetes/how-to/access-audit-logs.mdx @@ -31,7 +31,7 @@ Auditing allows cluster administrators to answer the following questions: Audit logging in Kubernetes clusters is enabled by default for clusters with dedicated control planes. Use audit logging to keep a chronological record of calls made to the Kubernetes API server, investigate suspicious API requests, collect statistics, or create monitoring alerts for unwanted API calls. -All logs are centralized in [Cockpit](/observability/cockpit/quickstart/). +All logs are centralized in [Cockpit](/cockpit/quickstart/). Monitoring calls to the `kube-apiserver` is a matter of security compliance and perhaps a hard requirement for some of the certifications you are keen to obtain. @@ -40,8 +40,8 @@ All logs are centralized in [Cockpit](/observability/cockpit/quickstart/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule or Kosmos cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule or Kosmos cluster](/kubernetes/how-to/create-cluster/) - A cluster that uses a [dedicated control plane](https://www.scaleway.com/en/kubernetes-dedicated-control-plane/) ## How to enable audit logging for your clusters @@ -58,7 +58,7 @@ Audit logging is enabled by default for all new clusters. If your cluster predat 1. In the **Security and Compliance** section of your Kubernetes cluster's **Settings** tab, enable the **Audit logs** feature. -2. [Access Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) to view the logs on the **Kubernetes Cluster Audit Logs** dashboard in Cockpit and the **Explore** section of Cockpit/Grafana. +2. [Access Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) to view the logs on the **Kubernetes Cluster Audit Logs** dashboard in Cockpit and the **Explore** section of Cockpit/Grafana. If you are not sure whether audit logs for your cluster are enabled, you can verify the status of the feature from the clusters **Security** tab at any time. @@ -72,14 +72,14 @@ Audit logging is enabled by default for all new clusters. If your cluster predat ## How to access cluster audit logs for clusters having a dedicated control plane. -You can access your clusters audit logs in [Cockpit](/observability/cockpit/), Scaleway's monitoring solution. +You can access your clusters audit logs in [Cockpit](/cockpit/), Scaleway's monitoring solution. Audit logs are automatically enabled by default for all clusters using dedicated control planes. -1. [Retrieve](/observability/cockpit/how-to/retrieve-grafana-credentials/) your Grafana credentials. -2. [Access Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) to view the logs on the **Kubernetes Cluster Audit Logs** dashboard in Cockpit and the **Explore** section of Cockpit/Grafana. +1. [Retrieve](/cockpit/how-to/retrieve-grafana-credentials/) your Grafana credentials. +2. [Access Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) to view the logs on the **Kubernetes Cluster Audit Logs** dashboard in Cockpit and the **Explore** section of Cockpit/Grafana. ## How to use audit logging with mutualized control planes diff --git a/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx b/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx index b6d59988a9..d78ddaf2e1 100644 --- a/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx +++ b/containers/kubernetes/how-to/access-kubernetes-dashboard.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) ## How to access the Kubernetes dashboard diff --git a/containers/kubernetes/how-to/connect-cluster-kubectl.mdx b/containers/kubernetes/how-to/connect-cluster-kubectl.mdx index 8abf63d67f..33b6a7e7c2 100644 --- a/containers/kubernetes/how-to/connect-cluster-kubectl.mdx +++ b/containers/kubernetes/how-to/connect-cluster-kubectl.mdx @@ -13,13 +13,13 @@ categories: - kubernetes --- -Once your [cluster is created](/containers/kubernetes/how-to/create-cluster/), a `.kubeconfig` file is available for download to manage several Kubernetes clusters. You can use this with `kubectl`, the Kubernetes command line tool, allowing you to run commands against your Kubernetes clusters. You can use `kubectl` from a terminal on your local computer to deploy applications, inspect and manage cluster resources, and view logs. +Once your [cluster is created](/kubernetes/how-to/create-cluster/), a `.kubeconfig` file is available for download to manage several Kubernetes clusters. You can use this with `kubectl`, the Kubernetes command line tool, allowing you to run commands against your Kubernetes clusters. You can use `kubectl` from a terminal on your local computer to deploy applications, inspect and manage cluster resources, and view logs. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) 1. [Install kubectl](https://kubernetes.io/docs/tasks/tools/) on your local computer. 2. Download the `.kubeconfig` files from your cluster's **overview** page: diff --git a/containers/kubernetes/how-to/create-cluster.mdx b/containers/kubernetes/how-to/create-cluster.mdx index e070af562a..1b9fddbca9 100644 --- a/containers/kubernetes/how-to/create-cluster.mdx +++ b/containers/kubernetes/how-to/create-cluster.mdx @@ -25,12 +25,12 @@ To facilitate cluster administration, Scaleway provides a `.kubeconfig` file, en - A Scaleway account with access to the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Cluster configuration - This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/containers/kubernetes/how-to/create-kosmos-cluster/). + This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/kubernetes/how-to/create-kosmos-cluster/). 1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays. @@ -44,7 +44,7 @@ To facilitate cluster administration, Scaleway provides a `.kubeconfig` file, en * Choose the geographical **region** for the cluster. * Select the control plane offer for your cluster. Options include shared or dedicated control planes. - Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). + Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/kubernetes/reference-content/kubernetes-control-plane-offers/). * Specify the **Kubernetes version** for your cluster. 4. Enter the **cluster's details**. Provide a name for the cluster. Optionally, you can add a description and tags for better organization. @@ -64,17 +64,17 @@ This section outlines the settings for your cluster pools. You can configure as * Choose an **Availability Zone** for the pool's nodes. * Select the **node type** for the pool. - Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/containers/kubernetes/concepts/#node) + Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/kubernetes/concepts/#node) * Configure the **system volume**. This volume contains the operating system of the nodes in your pool. * Configure **pool options**, including node count and whether to enable autoscaling. Options also include enabling autoheal and linking to a placement group, or you can retain default settings. - - Unsure about the autoheal feature? [Learn more about autoheal.](/containers/kubernetes/concepts/#autoheal) - - Need more information about placement groups? [Learn more about placement groups.](/compute/instances/concepts/#placement-groups) + - Unsure about the autoheal feature? [Learn more about autoheal.](/kubernetes/concepts/#autoheal) + - Need more information about placement groups? [Learn more about placement groups.](/instances/concepts/#placement-groups) * Enable full isolation, if required. - Need more information on full isolation? [Learn more about full isolation.](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) + Need more information on full isolation? [Learn more about full isolation.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) 2. Click **Add pool** to integrate the pool into the cluster. 3. To add more pools, click **Expand** and repeat the steps above. diff --git a/containers/kubernetes/how-to/create-kosmos-cluster.mdx b/containers/kubernetes/how-to/create-kosmos-cluster.mdx index 148a2cac1a..5a0f377844 100644 --- a/containers/kubernetes/how-to/create-kosmos-cluster.mdx +++ b/containers/kubernetes/how-to/create-kosmos-cluster.mdx @@ -14,12 +14,12 @@ categories: - kubernetes --- -Kubernetes Kosmos provides an alternative to a classic [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule). With Kubernetes Kosmos, you can create a Kubernetes cluster comprising both managed Scaleway Instances (with autohealing and autoscaling) and external instances and servers from any other cloud provider. Scaleway ensures the high availability of your services globally, across different zones, regions, and providers. In addition to the Kubernetes Kapsule pricing, you are charged for the Kubernetes Kosmos control plane and an additional fee for managed external nodes. +Kubernetes Kosmos provides an alternative to a classic [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule). With Kubernetes Kosmos, you can create a Kubernetes cluster comprising both managed Scaleway Instances (with autohealing and autoscaling) and external instances and servers from any other cloud provider. Scaleway ensures the high availability of your services globally, across different zones, regions, and providers. In addition to the Kubernetes Kapsule pricing, you are charged for the Kubernetes Kosmos control plane and an additional fee for managed external nodes. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization Be aware that autoscaling and autohealing features are unavailable on external providers’ nodes within Kosmos clusters. Since Scaleway does not have access to your other providers’ accounts, it is not possible to carry out actions such as automatic deletion, creation, and reboot of external nodes. @@ -38,7 +38,7 @@ Kubernetes Kosmos provides an alternative to a classic [Kubernetes Kapsule](/con * Choose the geographical **region** for the cluster. * Select the control plane offer for your cluster. Options include shared or dedicated control planes. - Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). + Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/kubernetes/reference-content/kubernetes-control-plane-offers/). * Specify the Kubernetes **version** for your cluster. 4. Provide a **name** for the cluster. Optionally, you can add a description and tags for better organization. @@ -61,11 +61,11 @@ This section outlines the settings for your cluster pools. You can configure as * Select the **node type** for the pool. * Configure **pool options**, including node count and whether to enable autoscaling. Options also include enabling autoheal and linking to a placement group, or you can retain default settings. - Unsure about the autoheal feature? [Learn more about autoheal.](/containers/kubernetes/concepts/#autoheal) + Unsure about the autoheal feature? [Learn more about autoheal.](/kubernetes/concepts/#autoheal) * Enable full isolation, if required. - Need more information on full isolation? [Learn more about full isolation.](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) + Need more information on full isolation? [Learn more about full isolation.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) * For **multi-cloud** pools: * Specify the external nodes to be added to the pool. diff --git a/containers/kubernetes/how-to/delete-cluster.mdx b/containers/kubernetes/how-to/delete-cluster.mdx index 8ab9dc4b55..56d43bd548 100644 --- a/containers/kubernetes/how-to/delete-cluster.mdx +++ b/containers/kubernetes/how-to/delete-cluster.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) To refine the instructions for clarity and completeness: diff --git a/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx b/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx index a44ce186d5..84142484c4 100644 --- a/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx +++ b/containers/kubernetes/how-to/deploy-image-from-container-registry.mdx @@ -13,19 +13,19 @@ categories: - container-registry --- -In this how-to guide you learn how to create and push a container image to the Scaleway [Container Registry](/containers/container-registry/concepts/#container-registry) and how to use it on [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule). +In this how-to guide you learn how to create and push a container image to the Scaleway [Container Registry](/container-registry/concepts/#container-registry) and how to use it on [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule). -A container image consists of several bundled files, which encapsulate an application. This image can be built on a local machine, uploaded to the image registry, and then deployed on various Kubernetes pods with Kapsule. [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule) is the managed Kubernetes service provided by Scaleway. In this tutorial, we use [Docker](https://www.docker.com/) to build the containers. +A container image consists of several bundled files, which encapsulate an application. This image can be built on a local machine, uploaded to the image registry, and then deployed on various Kubernetes pods with Kapsule. [Kapsule](/kubernetes/concepts/#kubernetes-kapsule) is the managed Kubernetes service provided by Scaleway. In this tutorial, we use [Docker](https://www.docker.com/) to build the containers. -The generated Docker images are stored in a private Docker registry using the Scaleway [Container Registry](/containers/container-registry/concepts/#container-registry) product. +The generated Docker images are stored in a private Docker registry using the Scaleway [Container Registry](/container-registry/concepts/#container-registry) product. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) with a private privacy policy -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster and downloaded and [configured](/containers/kubernetes/how-to/connect-cluster-kubectl/) the corresponding `.kubeconfig` file +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a [Container Registry namespace](/container-registry/how-to/create-namespace/) with a private privacy policy +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster and downloaded and [configured](/kubernetes/how-to/connect-cluster-kubectl/) the corresponding `.kubeconfig` file - Installed [Docker](/tutorials/install-docker-ubuntu-bionic/) and [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) on your local computer ## How to push an image to the Scaleway Container Registry @@ -65,7 +65,7 @@ The generated Docker images are stored in a private Docker registry using the Sc REPOSITORY TAG IMAGE ID CREATED SIZE mycontainer latest c427b132b5fc 22 minutes ago 1.24GB ``` -5. [Log into your Container Registry](/containers/container-registry/how-to/connect-docker-cli/). The endpoint (for example: `rg.fr-par.scw.cloud/myregistry`) of your Container Registry is available from the [Scaleway console](https://console.scaleway.com/registry/namespaces) and depends on your configuration: +5. [Log into your Container Registry](/container-registry/how-to/connect-docker-cli/). The endpoint (for example: `rg.fr-par.scw.cloud/myregistry`) of your Container Registry is available from the [Scaleway console](https://console.scaleway.com/registry/namespaces) and depends on your configuration: ```bash docker login rg.fr-par.scw.cloud/myregistry -u nologin -p $SCW_SECRET_KEY ``` @@ -88,10 +88,10 @@ The generated Docker images are stored in a private Docker registry using the Sc ## How to create an Image Pull Secret -To deploy the previously created container image in a Kapsule cluster, you need to create an Image Pull Secret. This allows your Kapsule cluster to connect to your Container Registry and pull the image itself. For this, your [API secret key](/identity-and-access-management/iam/how-to/create-api-keys/) is required. +To deploy the previously created container image in a Kapsule cluster, you need to create an Image Pull Secret. This allows your Kapsule cluster to connect to your Container Registry and pull the image itself. For this, your [API secret key](/iam/how-to/create-api-keys/) is required. - - Make sure that your [Kapsule cluster](/containers/kubernetes/how-to/connect-cluster-kubectl/) is configured on your local computer before continuing. + - Make sure that your [Kapsule cluster](/kubernetes/how-to/connect-cluster-kubectl/) is configured on your local computer before continuing. - We suppose that all resources are living in the same [Kubernetes Namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/). The default namespace is named `default`. diff --git a/containers/kubernetes/how-to/deploy-ingress-controller.mdx b/containers/kubernetes/how-to/deploy-ingress-controller.mdx index 566575d304..6d0f88eba6 100644 --- a/containers/kubernetes/how-to/deploy-ingress-controller.mdx +++ b/containers/kubernetes/how-to/deploy-ingress-controller.mdx @@ -13,13 +13,13 @@ categories: - kubernetes --- -An [ingress controller](/containers/kubernetes/concepts/#ingress-controller) is an entry point that ingests your HTTP/HTTPS traffic and dispatches it to your services. More precisely, it is a reverse proxy that will dynamically configure itself and will forward HTTP/HTTPS traffic to your services. +An [ingress controller](/kubernetes/concepts/#ingress-controller) is an entry point that ingests your HTTP/HTTPS traffic and dispatches it to your services. More precisely, it is a reverse proxy that will dynamically configure itself and will forward HTTP/HTTPS traffic to your services. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) 1. Navigate to the **Containers** section within the [Scaleway console](https://console.scaleway.com) sidebar and select **Kubernetes**. The Kubernetes Kapsule dashboard displays. 2. Locate the cluster you want to modify and click on its name to access the **cluster dashboard**. diff --git a/containers/kubernetes/how-to/deploy-x86-arm-images.mdx b/containers/kubernetes/how-to/deploy-x86-arm-images.mdx index 7db719596c..001d32af7d 100644 --- a/containers/kubernetes/how-to/deploy-x86-arm-images.mdx +++ b/containers/kubernetes/how-to/deploy-x86-arm-images.mdx @@ -22,7 +22,7 @@ However, Kubernetes provides several mechanisms to manage architectural diversit - Kubernetes clusters may consist of nodes with different architectures, including x86 and ARM. - Deploying applications across these diverse architectures requires special consideration. -For a detailed comparison between ARM and x86 architectures, refer to our dedicated documentation [Understanding the differences between ARM and x86 Instances](/compute/instances/reference-content/understanding-differences-x86-arm/). +For a detailed comparison between ARM and x86 architectures, refer to our dedicated documentation [Understanding the differences between ARM and x86 Instances](/instances/reference-content/understanding-differences-x86-arm/). ## Using multi-arch images @@ -32,7 +32,7 @@ These images contain binaries for multiple architectures, allowing Kubernetes to ### How to deploy multi-arch images 1. Build multi-arch images. Docker supports multi-arch builds using `buildx`. -2. Push the built images to a container registry accessible by your Kubernetes cluster. For example, you can use the [Scaleway Container Registry](/containers/container-registry/quickstart/). +2. Push the built images to a container registry accessible by your Kubernetes cluster. For example, you can use the [Scaleway Container Registry](/container-registry/quickstart/). 3. Specify node selectors and affinity. Use either [node selectors](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) and [affinity rules](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) to ensure pods are scheduled on nodes with compatible architectures. Alternatively, use taints to mark nodes with specific architectures and tolerations to allow pods to run on those nodes. Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) for more information regarding taints and tolerations. diff --git a/containers/kubernetes/how-to/edit-cluster.mdx b/containers/kubernetes/how-to/edit-cluster.mdx index ec3142a976..0963cac777 100644 --- a/containers/kubernetes/how-to/edit-cluster.mdx +++ b/containers/kubernetes/how-to/edit-cluster.mdx @@ -18,8 +18,8 @@ You can manage and edit the parameters of your cluster from the [Scaleway consol - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) ## How to manage a Kubernetes Kapsule cluster diff --git a/containers/kubernetes/how-to/edit-kosmos-cluster.mdx b/containers/kubernetes/how-to/edit-kosmos-cluster.mdx index 7ed4d8dbd4..2fed6fcaff 100644 --- a/containers/kubernetes/how-to/edit-kosmos-cluster.mdx +++ b/containers/kubernetes/how-to/edit-kosmos-cluster.mdx @@ -16,7 +16,7 @@ categories: You can add nodes and pools to your Kosmos cluster from the [Scaleway console](https://console.scaleway.com) or by using the [API](https://www.scaleway.com/en/developers/). Here, we show you how to edit from the console. - This document concerns the management of a Kosmos cluster. For a Kapsule cluster, refer to the [corresponding documentation for Kapsule](/containers/kubernetes/how-to/edit-cluster/) + This document concerns the management of a Kosmos cluster. For a Kapsule cluster, refer to the [corresponding documentation for Kapsule](/kubernetes/how-to/edit-cluster/) @@ -26,8 +26,8 @@ You can add nodes and pools to your Kosmos cluster from the [Scaleway console](h - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes Kosmos cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kosmos cluster - External machines (`arm64` or `amd64`) you want to add to your cluster that are running on Ubuntu or Debian ## How to add a multi-cloud pool to your Kosmos cluster @@ -48,14 +48,14 @@ A multi-cloud pool allows you to attach external Instances and servers to your c In order to add external nodes to your multi-cloud cluster, you must first [create a multi-cloud pool](#how-to-add-a-multi-cloud-pool-to-your-kosmos-cluster). For security reasons, it is recommended to configure an API key with the `KubernetesExternalNodeRegister` IAM permission set. 1. Click **Identity and Access Management (IAM)** from the top-right of your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The [Identity and Access Management dashboard](https://console.scaleway.com/iam/) displays. -2. [Create an IAM Policy](/identity-and-access-management/iam/how-to/create-policy/) with the `KubernetesExternalNodeRegister` PermissionSet only. +2. [Create an IAM Policy](/iam/how-to/create-policy/) with the `KubernetesExternalNodeRegister` PermissionSet only. -3. [Create an IAM Application](/identity-and-access-management/iam/how-to/create-application/) linked with the policy created in the previous step. +3. [Create an IAM Application](/iam/how-to/create-application/) linked with the policy created in the previous step. -4. [Create a new API key](/identity-and-access-management/iam/how-to/create-api-keys/) linked to the IAM application created in the previous step. +4. [Create a new API key](/iam/how-to/create-api-keys/) linked to the IAM application created in the previous step. - Identity and Access Management (IAM) allows you to share access to the management of your Scaleway resources and Organization settings, in a controlled and secure manner. For more information, refer to our [dedicated IAM documentation](/identity-and-access-management/iam/quickstart/). + Identity and Access Management (IAM) allows you to share access to the management of your Scaleway resources and Organization settings, in a controlled and secure manner. For more information, refer to our [dedicated IAM documentation](/iam/quickstart/). 5. Click **Kubernetes** in the Compute section of the side menu. The Kubernetes creation page displays. 6. Click the cluster you want to add external nodes to. diff --git a/containers/kubernetes/how-to/enable-disable-ssh.mdx b/containers/kubernetes/how-to/enable-disable-ssh.mdx index 3fd5a3d5d0..0d90d0000c 100644 --- a/containers/kubernetes/how-to/enable-disable-ssh.mdx +++ b/containers/kubernetes/how-to/enable-disable-ssh.mdx @@ -15,13 +15,13 @@ categories: Kubernetes Kapsule clusters are provisioned with a default security group as standard. Clusters deployed prior to May 2023 allow inbound traffic to the nodes.

Since May 2023, each Kapsule cluster comes with a default security group implementing an inbound `DROP ALL` policy, effectively blocking all incoming connections by default.

-To activate the preinstalled SSH server for node access within the cluster, it is necessary to manually [configure a custom rule](/compute/instances/how-to/use-security-groups/#how-to-edit-a-security-group) in the cluster's security group to allow inbound traffic on TCP port 22. +To activate the preinstalled SSH server for node access within the cluster, it is necessary to manually [configure a custom rule](/instances/how-to/use-security-groups/#how-to-edit-a-security-group) in the cluster's security group to allow inbound traffic on TCP port 22. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule cluster 1. Click **Instances** in the side menu, then click **Security groups** to view the [security group](https://console.scaleway.com/instance/security-groups) section in your Scaleway console. 2. Click next to the security group you intend to configure and choose **More info**. The security group's overview displays. diff --git a/containers/kubernetes/how-to/enable-easy-deploy.mdx b/containers/kubernetes/how-to/enable-easy-deploy.mdx index 47eaf4310f..150d5c7d44 100644 --- a/containers/kubernetes/how-to/enable-easy-deploy.mdx +++ b/containers/kubernetes/how-to/enable-easy-deploy.mdx @@ -13,7 +13,7 @@ categories: - kubernetes --- -The Easy Deploy feature allows you to pull images directly from [Scaleway Container Registry](/containers/container-registry/concepts/#container-registry), instantly deploying containerized applications in your [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule) and [Kubernetes Kosmos](/containers/kubernetes/concepts/#kubernetes-kosmos) clusters. +The Easy Deploy feature allows you to pull images directly from [Scaleway Container Registry](/container-registry/concepts/#container-registry), instantly deploying containerized applications in your [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule) and [Kubernetes Kosmos](/kubernetes/concepts/#kubernetes-kosmos) clusters. You can also deploy off-the-shelf applications pre-configured for Scaleway products, such as Load Balancer and Block Storage. @@ -22,10 +22,10 @@ You can also deploy off-the-shelf applications pre-configured for Scaleway produ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster -- [Created a Scaleway Container Registry namespace](/containers/container-registry/how-to/create-namespace/) (not mandatory if deploying using the Application Library) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Created a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) (not mandatory if deploying using the Application Library) ## How to deploy an application diff --git a/containers/kubernetes/how-to/manage-allowed-ips.mdx b/containers/kubernetes/how-to/manage-allowed-ips.mdx index 2ec30d8fc9..39be028549 100644 --- a/containers/kubernetes/how-to/manage-allowed-ips.mdx +++ b/containers/kubernetes/how-to/manage-allowed-ips.mdx @@ -20,11 +20,11 @@ The default entry `0.0.0.0/0` enables any host to establish a connection. - A Scaleway account logged into the [Scaleway console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster) a Kubernetes Kapsule or Kosmos cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster) a Kubernetes Kapsule or Kosmos cluster - Allowed IP configuration is available for [fully isolated Kapsule clusters](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation), and Kosmos clusters. + Allowed IP configuration is available for [fully isolated Kapsule clusters](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation), and Kosmos clusters. ## How to add an IP address @@ -32,7 +32,7 @@ The default entry `0.0.0.0/0` enables any host to establish a connection. 1. Click **Kubernetes** in the **Containers** section of the [Scaleway console](https://console.scaleway.com). The **Kubernetes dashboard** appears. 2. Select the cluster you wish to configure. The **Cluster information** page opens. 3. Click the **Network** tab to display your cluster's network information. Your access control list appears in the **Allowed IPs for control plane** section. -4. Click **Add allowed IP**. Enter the IP address or IP block in [CIDR notation](/network/ipam/concepts/#cidr-notation) (e.g., `198.51.100.135/32` for a single IP, `198.51.100.0/24` for an IP block), then click **Add IP(s)**. +4. Click **Add allowed IP**. Enter the IP address or IP block in [CIDR notation](/ipam/concepts/#cidr-notation) (e.g., `198.51.100.135/32` for a single IP, `198.51.100.0/24` for an IP block), then click **Add IP(s)**. To restore default settings and allow connections from all IPs, add `0.0.0.0/0` to the list. diff --git a/containers/kubernetes/how-to/monitor-cluster.mdx b/containers/kubernetes/how-to/monitor-cluster.mdx index d85308f81c..cc5a1322f6 100644 --- a/containers/kubernetes/how-to/monitor-cluster.mdx +++ b/containers/kubernetes/how-to/monitor-cluster.mdx @@ -17,7 +17,7 @@ Scaleway's observability Cockpit provides automated monitoring of your Kubernete Grafana's rich visualizations and ease of use make it an ideal choice. Cockpit offers a hassle-free solution, providing real-time insights without extra infrastructure. -[Cockpit](/observability/cockpit/quickstart/) empowers you to monitor the clusters' control plane, nodes, managed resources and the cluster system applications. +[Cockpit](/cockpit/quickstart/) empowers you to monitor the clusters' control plane, nodes, managed resources and the cluster system applications. * Detect incidents and diagnose failures in the earliest stages * Get new insights on control plane and worker nodes usage such as CPU and memory to optimize your resource allocation @@ -26,19 +26,19 @@ Grafana's rich visualizations and ease of use make it an ideal choice. Cockpit o - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- [Created](/observability/cockpit/how-to/retrieve-grafana-credentials/) a Grafana user for Cockpit +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) +- [Created](/cockpit/how-to/retrieve-grafana-credentials/) a Grafana user for Cockpit ## How to access your Cockpit Grafana dashboard - Cockpit’s default retention duration is 31 days for metrics and 7 days for logs. Find out [how to change your data retention period](/observability/cockpit/how-to/change-data-retention/). + Cockpit’s default retention duration is 31 days for metrics and 7 days for logs. Find out [how to change your data retention period](/cockpit/how-to/change-data-retention/). 1. Open your Cockpit in the [Scaleway console](https://console.scaleway.com/cockpit/overview). 2. Click **Visualize Scaleway data**. The Grafana interface opens in a new browser tab. -3. Log into Grafana using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). The list of your Cockpit dashboards displays. +3. Log into Grafana using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). The list of your Cockpit dashboards displays. 4. Click **Kubernetes cluster overview** in the list of dashboards. A status overview of your cluster displays. This dashboard allows you to monitor multiple components of your Kubernetes cluster: control-plane, nodes, managed resources and cluster system applications. @@ -59,7 +59,7 @@ For scenarios where you require consistent and predictable performance, along wi 1. Open your Cockpit in the [Scaleway console](https://console.scaleway.com/cockpit/overview). 2. Click **Visualize Scaleway data**. The Grafana interface opens in a new browser tab. -3. Log into Grafana using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). The list of your Cockpit dashboards displays. +3. Log into Grafana using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). The list of your Cockpit dashboards displays. 4. Click **Kubernetes cluster logs** in the list of dashboards. A listing of your control plane logs displays. This dashboard allows you to view the logs of multiple components of your Kubernetes cluster, such as the `controller-manager`, `ccm`, `kapsule-autoscaler`, and more. Currently, no logs from the `kube-apiserver` are sent to your Cockpit. diff --git a/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx b/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx index f8007583a2..c5dcf25bb6 100644 --- a/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx +++ b/containers/kubernetes/how-to/upgrade-kubernetes-version.mdx @@ -20,8 +20,8 @@ You can either upgrade your Kubernetes Kapsule cluster [directly from the Scalew - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) running on a Kubernetes version older than the latest release +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) running on a Kubernetes version older than the latest release 1. Click **Kubernetes** under **Containers** on the side menu. A list of your Kubernetes Kapsule clusters displays. 2. Click the cluster name you wish to upgrade the Kubernetes version for. The cluster information page displays. @@ -49,7 +49,7 @@ You can either upgrade your Kubernetes Kapsule cluster [directly from the Scalew First, it is essential to verify that the most recent version of Kapsule adequately supports your workload. We maintain a compatibility matrix for various components, as your current cluster might use components that are deprecated or unavailable in the latest version. -For further details, consult our [version policy](/containers/kubernetes/reference-content/version-support-policy/). +For further details, consult our [version policy](/kubernetes/reference-content/version-support-policy/). We recommend you read the Kubernetes [changelog](https://kubernetes.io/releases/) to stay informed on the latest version upgrades. @@ -77,7 +77,7 @@ If your cluster currently uses a deprecated Container Network Interface (CNI) an Unfortunately, at present, there isn't a straightforward method to modify the CNI since it is tightly integrated within each cluster node, making the transition a complex process. For more help, check out the following resources: - The #k8s channel on our [Slack community](https://scaleway-community.slack.com) -- Our [support ticketing system](/console/account/how-to/open-a-support-ticket/) +- Our [support ticketing system](/account/how-to/open-a-support-ticket/) ### Container runtimes diff --git a/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx b/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx index 798771aedd..486b4c8f2d 100644 --- a/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx +++ b/containers/kubernetes/how-to/use-nvidia-gpu-operator.mdx @@ -22,8 +22,8 @@ The GPU operator is set up for all GPU pools created in Kubernetes Kapsule and K - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule or Kosmos cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule or Kosmos cluster](/kubernetes/how-to/create-cluster/) ## How to get the GPU operator for a new pool? diff --git a/containers/kubernetes/how-to/use-scratch-storage-h100.mdx b/containers/kubernetes/how-to/use-scratch-storage-h100.mdx index 88bdc56a8f..58bbc36fff 100644 --- a/containers/kubernetes/how-to/use-scratch-storage-h100.mdx +++ b/containers/kubernetes/how-to/use-scratch-storage-h100.mdx @@ -14,7 +14,7 @@ categories: - kubernetes --- -[Scratch storage](/compute/gpu/concepts/#scratch-storage) is ephemeral storage allocated to H100 and L40S GPU Instances (up to 6 TB) and crucial for handling temporary data in high-performance computing environments, especially when working with GPUs like the H100. Kubernetes, a powerful container orchestration platform, can be configured to make optimal use of scratch storage for improved performance. +[Scratch storage](/gpu/concepts/#scratch-storage) is ephemeral storage allocated to H100 and L40S GPU Instances (up to 6 TB) and crucial for handling temporary data in high-performance computing environments, especially when working with GPUs like the H100. Kubernetes, a powerful container orchestration platform, can be configured to make optimal use of scratch storage for improved performance. Its utility spans multiple use cases, including but not limited to: @@ -28,8 +28,8 @@ Design your workloads or applications to take advantage of the fast and temporar - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule or Kosmos cluster that uses [H100 and L40S GPU Instances](https://www.scaleway.com/en/h100-pcie-try-it-now/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster/) a Kubernetes Kapsule or Kosmos cluster that uses [H100 and L40S GPU Instances](https://www.scaleway.com/en/h100-pcie-try-it-now/) In Kubernetes, H100 and L40S scratch storage is implemented as a directory on the host node's file system. This scratch volume is made available to containers within a pod using the `hostPath` volume type, allowing direct integration with Kubernetes workloads. diff --git a/containers/kubernetes/index.mdx b/containers/kubernetes/index.mdx index 9cc5c3b06c..fc6d3eef10 100644 --- a/containers/kubernetes/index.mdx +++ b/containers/kubernetes/index.mdx @@ -8,7 +8,7 @@ meta: productName="Kubernetes" productLogo="k8sKapsule" description="Managed Kubernetes allows you to create and manage Kubernetes clusters in just a few clicks, scale effortlessly and focus on your applications." - url="/containers/kubernetes/quickstart/" + url="/kubernetes/quickstart/" label="Kubernetes Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, manage and delete a Kubernetes cluster in a few steps." label="View Quickstart" - url="/containers/kubernetes/quickstart/" + url="/kubernetes/quickstart/" /> diff --git a/containers/kubernetes/quickstart.mdx b/containers/kubernetes/quickstart.mdx index a1d10c5fbb..ef4e0c65cb 100644 --- a/containers/kubernetes/quickstart.mdx +++ b/containers/kubernetes/quickstart.mdx @@ -13,7 +13,7 @@ categories: - kubernetes --- -Scaleway Kubernetes [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule) and [Kosmos](/containers/kubernetes/concepts/#kubernetes-kosmos) provide a managed environment to create, configure, and run a cluster of preconfigured machines for containerized applications. This allows you to create Kubernetes clusters without the complexity of managing the infrastructure. You can create a Kapsule cluster to your required specifications, edit it after creation, and delete it all when you no longer need it. You might also want to check out our how-to on [deploying an image on your cluster](/containers/kubernetes/how-to/deploy-image-from-container-registry/). +Scaleway Kubernetes [Kapsule](/kubernetes/concepts/#kubernetes-kapsule) and [Kosmos](/kubernetes/concepts/#kubernetes-kosmos) provide a managed environment to create, configure, and run a cluster of preconfigured machines for containerized applications. This allows you to create Kubernetes clusters without the complexity of managing the infrastructure. You can create a Kapsule cluster to your required specifications, edit it after creation, and delete it all when you no longer need it. You might also want to check out our how-to on [deploying an image on your cluster](/kubernetes/how-to/deploy-image-from-container-registry/). ## Kubernetes decision tree @@ -22,32 +22,32 @@ Scaleway Kubernetes [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsul - - + + - - + + - + - - + + - - + + - - + + - - + +
[1 An Introduction To Kubernetes](/containers/kubernetes/reference-content/introduction-to-kubernetes/)[8 Let's learn how to create and push a container image to the Scaleway Container Registry and how to use it on Kubernetes Kapsule](/containers/kubernetes/how-to/deploy-image-from-container-registry/)[1 An Introduction To Kubernetes](/kubernetes/reference-content/introduction-to-kubernetes/)[8 Let's learn how to create and push a container image to the Scaleway Container Registry and how to use it on Kubernetes Kapsule](/kubernetes/how-to/deploy-image-from-container-registry/)
[2 Basics hands-on](/containers/kubernetes/quickstart/)[9 How to deploy containerized applications with the Easy Deploy Feature](/containers/kubernetes/how-to/enable-easy-deploy/)[2 Basics hands-on](/kubernetes/quickstart/)[9 How to deploy containerized applications with the Easy Deploy Feature](/kubernetes/how-to/enable-easy-deploy/)
[3 Concepts](/containers/kubernetes/concepts/)[3 Concepts](/kubernetes/concepts/) [10 Odoo on a Scaleway Kubernetes Kapsule using the Easy Deploy Feature](/tutorials/odoo-easy-deploy/)
[4 Introduction video to Kubernetes](/containers/kubernetes/videos/#introduction-to-kubernetes)[11 How does containerizing two simple applications with Docker sound](/containers/kubernetes/videos/#part-1-containers-and-docker)[4 Introduction video to Kubernetes](/kubernetes/videos/#introduction-to-kubernetes)[11 How does containerizing two simple applications with Docker sound](/kubernetes/videos/#part-1-containers-and-docker)
[5 Scaleway Instances](/compute/instances/reference-content/choosing-instance-type/)[12 Docker concepts](/containers/container-registry/concepts/#docker)[5 Scaleway Instances](/instances/reference-content/choosing-instance-type/)[12 Docker concepts](/container-registry/concepts/#docker)
[6 How to connect to a cluster with kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/)[13 How to deploy a containerized application with Kubernetes Kapsule](/containers/kubernetes/videos/#part-2-deploying-an-app-with-kapsule)[6 How to connect to a cluster with kubectl](/kubernetes/how-to/connect-cluster-kubectl/)[13 How to deploy a containerized application with Kubernetes Kapsule](/kubernetes/videos/#part-2-deploying-an-app-with-kapsule)
[7 kubectl definition](/containers/kubernetes/concepts/#kubectl)[14 How to add a load balancer service to your Scaleway Kubernetes Kapsule](/containers/kubernetes/videos/#part-3-load-balancers)[7 kubectl definition](/kubernetes/concepts/#kubectl)[14 How to add a load balancer service to your Scaleway Kubernetes Kapsule](/kubernetes/videos/#part-3-load-balancers)
@@ -61,14 +61,14 @@ Scaleway Kubernetes [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsul - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Kubernetes cluster ### Cluster configuration - This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/containers/kubernetes/how-to/create-kosmos-cluster/). + This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/kubernetes/how-to/create-kosmos-cluster/). 1. Navigate to **Kubernetes** under the **Containers** section of the [Scaleway console](https://console.scaleway.com/) side menu. The Kubernetes dashboard displays. @@ -80,12 +80,12 @@ Scaleway Kubernetes [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsul * Select **Kubernetes Kapsule** as the cluster type, which uses exclusively Scaleway Instances. - This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/containers/kubernetes/how-to/create-kosmos-cluster/). + This guide covers the creation of a **Kubernetes Kapsule** cluster. For Kubernetes Kosmos clusters, refer to the [Kubernetes Kosmos documentation](/kubernetes/how-to/create-kosmos-cluster/). * Choose the geographical **region** for the cluster. * Select the control plane offer for your cluster. Options include shared or dedicated control planes. - Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). + Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/kubernetes/reference-content/kubernetes-control-plane-offers/). * Specify the **Kubernetes version** for your cluster. 4. Enter the **cluster's details**. Provide a name for the cluster. Optionally, you can add a description and tags for better organization. @@ -105,17 +105,17 @@ This section outlines the settings for your cluster pools. You can configure as * Choose an **Availability Zone** for the pool's nodes. * Select the **node type** for the pool. - Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/containers/kubernetes/concepts/#node) + Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/kubernetes/concepts/#node) * Configure the **system volume**. This volume contains the operating system of the nodes in your pool. * Configure **pool options**, including node count and whether to enable autoscaling. Options also include enabling autoheal and linking to a placement group, or you can retain default settings. - - Unsure about the autoheal feature? [Learn more about autoheal.](/containers/kubernetes/concepts/#autoheal) - - Need more information about placement groups? [Learn more about placement groups.](/compute/instances/concepts/#placement-groups) + - Unsure about the autoheal feature? [Learn more about autoheal.](/kubernetes/concepts/#autoheal) + - Need more information about placement groups? [Learn more about placement groups.](/instances/concepts/#placement-groups) * Enable full isolation, if required. - Need more information on full isolation? [Learn more about full isolation.](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) + Need more information on full isolation? [Learn more about full isolation.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) 2. Click **Add pool** to integrate the pool into the cluster. 3. To add more pools, click **Expand** and repeat the steps above. @@ -156,13 +156,13 @@ This section outlines the settings for your cluster pools. You can configure as 3. Complete the following steps of the wizard: * Choose a **cluster type**. Select **Kubernetes Kosmos** to create a cluster, that allows you to attach a compute Instance or dedicated server from any Cloud provider to a Scaleway Kubernetes control plane. - This document concerns the creation and management of a **Kubernetes Kosmos** cluster. To create a Kubernetes Kapsule cluster, refer to the [Kubernetes Kapsule documentation](/containers/kubernetes/how-to/create-cluster/). + This document concerns the creation and management of a **Kubernetes Kosmos** cluster. To create a Kubernetes Kapsule cluster, refer to the [Kubernetes Kapsule documentation](/kubernetes/how-to/create-cluster/). * The geographical **region** of the cluster. * The Kubernetes **version** for the cluster. * A **name** for the cluster and, optionally, a description and tags. 4. Click **Create cluster** to create your cluster without any Scaleway pools. - If you choose this option, your cluster and its control plane are deployed, and you are taken to the cluster's overview tab. Continue to [How to manage your Kubernetes Kosmos cluster](/containers/kubernetes/how-to/edit-kosmos-cluster/) to find out how to add multi-cloud pools to your cluster. + If you choose this option, your cluster and its control plane are deployed, and you are taken to the cluster's overview tab. Continue to [How to manage your Kubernetes Kosmos cluster](/kubernetes/how-to/edit-kosmos-cluster/) to find out how to add multi-cloud pools to your cluster. Alternatively, click **Add and configure a pool** to add a pool of Scaleway nodes to your cluster. In this case, the second page of the cluster creation wizard displays. This concerns the settings for your pool. 5. Enter the following information to configure a Scaleway pool: @@ -173,10 +173,10 @@ This section outlines the settings for your cluster pools. You can configure as Make sure you have: * An `arm64` or `amd64` server running with Ubuntu or Debian, having a public IP assigned to it. - * A Scaleway [secret key](/identity-and-access-management/iam/how-to/create-api-keys/). + * A Scaleway [secret key](/iam/how-to/create-api-keys/). - For more information about adding external nodes to your Kosmos cluster, refer to our dedicated [How to manage a Kosmos cluster](/containers/kubernetes/how-to/edit-kosmos-cluster/) documentation. + For more information about adding external nodes to your Kosmos cluster, refer to our dedicated [How to manage a Kosmos cluster](/kubernetes/how-to/edit-kosmos-cluster/) documentation. ## How to edit a Kubernetes cluster diff --git a/containers/kubernetes/reference-content/exposing-services.mdx b/containers/kubernetes/reference-content/exposing-services.mdx index c03d343c3e..0e09bdba74 100644 --- a/containers/kubernetes/reference-content/exposing-services.mdx +++ b/containers/kubernetes/reference-content/exposing-services.mdx @@ -19,7 +19,7 @@ There are a number of different ways to expose your cluster to the internet. In ## Comparison of cluster exposure methods -In Kubernetes, you generally need to use a [Service](/containers/kubernetes/concepts/#services) to expose an application in your cluster to the internet. A service groups together pods performing the same function (e.g. running the same application) and defines how to access them. +In Kubernetes, you generally need to use a [Service](/kubernetes/concepts/#services) to expose an application in your cluster to the internet. A service groups together pods performing the same function (e.g. running the same application) and defines how to access them. The most basic type of service is **clusterIP**, but this only provides internal access, from within the cluster, to the defined pods. The **NodePort** and **LoadBalancer** services both provide external access. **Ingress** (which is not a service but an API object inside a cluster) combined with an explicitly-created **ingress controller** is another way to expose the cluster. @@ -52,7 +52,7 @@ For more information and practical help with creating a NodePort Service, check For more information and practical help with creating a LoadBalancer Service, check out the following resources: -- [Creating and configuring a Load Balancer service](/containers/kubernetes/reference-content/kubernetes-load-balancer/) +- [Creating and configuring a Load Balancer service](/kubernetes/reference-content/kubernetes-load-balancer/) - [Getting started with Kubernetes Load Balancers - Tutorial](/tutorials/get-started-kubernetes-loadbalancer/) - [Getting started with Kubernetes Load Balancers - Video demonstration](https://www.youtube.com/watch?v=R5CwAq1a0Og) @@ -62,8 +62,8 @@ For more information and practical help with creating a LoadBalancer Service, ch For more information and practical help with setting up ingress, check out the following resources: -- [How to deploy an ingress controller](/containers/kubernetes/how-to/deploy-ingress-controller/) -- [Using a Load Balancer to expose your ingress controller](/containers/kubernetes/reference-content/lb-ingress-controller/) +- [How to deploy an ingress controller](/kubernetes/how-to/deploy-ingress-controller/) +- [Using a Load Balancer to expose your ingress controller](/kubernetes/reference-content/lb-ingress-controller/) - [Configuring a Load Balancer for your Kubernetes applications - Webinar](https://www.youtube.com/watch?v=V0uKqYXJRF4) - Deep dive and practical demonstration of how to create an ingress controller with a Load Balancer for your cluster from the 14-minute mark to the 48-minute mark. ## Ingress or LoadBalancer? diff --git a/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx b/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx index 6d3f070bb5..e73edf5781 100644 --- a/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx +++ b/containers/kubernetes/reference-content/introduction-to-kubernetes.mdx @@ -171,6 +171,6 @@ Once a pod is being terminated, the reclamation policy of the volume determines ## Going further -* [Discover how to deploy your first Kapsule on Scaleway](/containers/kubernetes/how-to/create-cluster/) +* [Discover how to deploy your first Kapsule on Scaleway](/kubernetes/how-to/create-cluster/) * [Deploy your first Kapsule on Scaleway](https://console.scaleway.com/kapsule/) * Read the [official documentation](https://kubernetes.io/docs/home/) to learn more about Kubernetes. \ No newline at end of file diff --git a/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx b/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx index 7389e07faa..ac9db9f9d2 100644 --- a/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx +++ b/containers/kubernetes/reference-content/kubernetes-cheatsheet.mdx @@ -16,7 +16,7 @@ This page shows the most common `kubectl` commands for creating and managing Sca -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization diff --git a/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx b/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx index 8f5daf46f5..942aef4c34 100644 --- a/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx +++ b/containers/kubernetes/reference-content/kubernetes-control-plane-offers.mdx @@ -77,7 +77,7 @@ These limitations exist to ensure the stability and performance of your Kubernet For users running complex applications or managing large volumes of data, opting for a dedicated control plane is advisable. This not only provides a more substantial etcd quota but also enhances overall cluster performance and reliability. -You can monitor the size of your control plane’s etcd using [Cockpit](/observability/cockpit/quickstart/), Scaleway’s intuitive management interface. This visibility helps in proactive management and ensures you remain within the allotted limits, avoiding potential disruptions. +You can monitor the size of your control plane’s etcd using [Cockpit](/cockpit/quickstart/), Scaleway’s intuitive management interface. This visibility helps in proactive management and ensures you remain within the allotted limits, avoiding potential disruptions. You can not downgrade your cluster's control plane from a dedicated one to a mutualized control plane when your etcd quota exceeds the mutualized storage allowance. @@ -87,4 +87,4 @@ You can monitor the size of your control plane’s etcd using [Cockpit](/observa During the lifecycle of a Kubernetes cluster, you have the flexibility to transition its control plane to a different type, whether it involves [scaling up or scaling down](/faq/kubernetes/#can-i-change-the-offer-of-my-clusters-control-plane), to align with their specific workloads. -Refer to our dedicated documentation for more information regarding the [choice of control plane offers for clusters](/faq/kubernetes/#can-i-choose-the-type-of-control-plane-for-my-cluster), as well as instructions on how to manage a control plane through the [console](/containers/kubernetes/how-to/edit-cluster/) or [API](https://www.scaleway.com/en/developers/api/kubernetes/). \ No newline at end of file +Refer to our dedicated documentation for more information regarding the [choice of control plane offers for clusters](/faq/kubernetes/#can-i-choose-the-type-of-control-plane-for-my-cluster), as well as instructions on how to manage a control plane through the [console](/kubernetes/how-to/edit-cluster/) or [API](https://www.scaleway.com/en/developers/api/kubernetes/). \ No newline at end of file diff --git a/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx b/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx index 66ee566822..edb8b26563 100644 --- a/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx +++ b/containers/kubernetes/reference-content/kubernetes-load-balancer.mdx @@ -13,7 +13,7 @@ categories: - kubernetes --- -Creating a [Load Balancer](/containers/kubernetes/concepts/#load-balancer) for your Kubernetes cluster allows you to expose an application running inside your cluster to the internet. +Creating a [Load Balancer](/kubernetes/concepts/#load-balancer) for your Kubernetes cluster allows you to expose an application running inside your cluster to the internet. In this document, we summarize when to create a Load Balancer for your cluster (as opposed to a different solution for exposing your application), and take you through the basic steps to create and configure your Load Balancer. @@ -32,16 +32,16 @@ On the other hand, if you have multiple services running in a more complex clust - **Ingress** with an **ingress controller** and **Load Balancer** may be more suitable for exposing multiple services in your cluster, via a single external IP which forwards HTTP traffic to the right service in the cluster based on Ingress rules. -Read the [full documentation](/containers/kubernetes/reference-content/exposing-services/) on different ways to expose your services for full details, and links to the relevant documentation for each possibility. +Read the [full documentation](/kubernetes/reference-content/exposing-services/) on different ways to expose your services for full details, and links to the relevant documentation for each possibility. ## Creating a Load Balancer for your cluster: Overview Here is a quick overview of how to create a Load Balancer for your cluster: -- [Create a Scaleway Kubernetes Kapsule cluster](/network/load-balancer/how-to/create-load-balancer/) with an application running inside. -- Make sure you have [installed and configured kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) +- [Create a Scaleway Kubernetes Kapsule cluster](/load-balancer/how-to/create-load-balancer/) with an application running inside. +- Make sure you have [installed and configured kubectl](/kubernetes/how-to/connect-cluster-kubectl/) - Create a yaml manifest to describe the LoadBalancer service you want to create. You can use [Load Balancer annotations](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md) to fine-tune the Load Balancer's configuration in the manifest. -- Deploy the LoadBalancer service based on the manifest, using kubectl. The Cloud Controller Manager (CCM) will spin up the external [Scaleway Load Balancer](/network/load-balancer/quickstart/) with the correct configuration to forward traffic to the LoadBalancer service within your cluster. +- Deploy the LoadBalancer service based on the manifest, using kubectl. The Cloud Controller Manager (CCM) will spin up the external [Scaleway Load Balancer](/load-balancer/quickstart/) with the correct configuration to forward traffic to the LoadBalancer service within your cluster. - Modify your Load Balancer's configuration as necessary via the yaml manifest and [Load Balancer annotations](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md) , putting any new annotations into effect via kubectl, so the CCM can carry out the modifications as necessary. @@ -53,9 +53,9 @@ Load Balancers for Kubernetes clusters should **always** be provisioned via the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Kubernetes Kapsule cluster](/network/load-balancer/how-to/create-load-balancer/) -- [Installed and configured kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Kubernetes Kapsule cluster](/load-balancer/how-to/create-load-balancer/) +- [Installed and configured kubectl](/kubernetes/how-to/connect-cluster-kubectl/) - An application running in your cluster You can refer to the [following example of webserver application to run.](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-examples.md) @@ -98,7 +98,7 @@ You can refer to the [following example of webserver application to run.](https: By default, when you create a Load Balancer for your cluster, it will be assigned a public IP address at random. When you delete the Load Balancer, the IP address will also be deleted, and cannot be retrieved to transfer to another Load Balancer service in your cluster. -However, it is possible to use [flexible IP addresses](/network/load-balancer/concepts/#flexible-ip-address) with your cluster's Load Balancer, to give you more control over the IPs being used. Flexible IP addresses can be kept in your account even if/when their associated Load Balancer is deleted. They can then be assigned to a new Load Balancer in the future. +However, it is possible to use [flexible IP addresses](/load-balancer/concepts/#flexible-ip-address) with your cluster's Load Balancer, to give you more control over the IPs being used. Flexible IP addresses can be kept in your account even if/when their associated Load Balancer is deleted. They can then be assigned to a new Load Balancer in the future. To specify that an existing flexible IP address that you hold in your account should be used when creating your Load Balancer, add the `loadBalancerIP` field to your yaml manifest, as shown in the last line here: @@ -119,7 +119,7 @@ To specify that an existing flexible IP address that you hold in your account sh loadBalancerIP: 51.159.24.7 ``` -For full details and further examples of how to use flexible IPs with your Kubernetes Load Balancer, see our [dedicated documentation](/containers/kubernetes/reference-content/managing-load-balancer-ips/). +For full details and further examples of how to use flexible IPs with your Kubernetes Load Balancer, see our [dedicated documentation](/kubernetes/reference-content/managing-load-balancer-ips/). ## Defining your Load Balancer's configuration via annotations @@ -151,13 +151,13 @@ Add annotations to the `metadata` section of your LoadBalancer Service's yaml ma app: mydeployment ``` -For full details on how to use Load Balancer annotations when creating your Load Balancer, or how to modify your Load Balancer's annotations after creation, see our [dedicated documentation](/containers/kubernetes/reference-content/using-load-balancer-annotations/). For a full list of Load Balancer annotations, refer to the [Scaleway Cloud Controller documentation](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md). +For full details on how to use Load Balancer annotations when creating your Load Balancer, or how to modify your Load Balancer's annotations after creation, see our [dedicated documentation](/kubernetes/reference-content/using-load-balancer-annotations/). For a full list of Load Balancer annotations, refer to the [Scaleway Cloud Controller documentation](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md). ## Troubleshooting Kubernetes Load Balancers ### Load Balancer certificate error using SSL offload -If your Load Balancer is configured for [SSL offload](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-offloading), and you have several services behind the same Load Balancer, you will encounter an SSL error when trying to reach the other services using HTTPS. +If your Load Balancer is configured for [SSL offload](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-offloading), and you have several services behind the same Load Balancer, you will encounter an SSL error when trying to reach the other services using HTTPS. Example: - podA @@ -175,7 +175,7 @@ The Nginx Ingress must be configured with [use-proxy-protocol](https://kubernete #### Nginx Ingress Easy Deploy -The [Easy Deploy](/containers/kubernetes/how-to/enable-easy-deploy) Nginx Ingress can be configured to accept TCP Proxy: +The [Easy Deploy](/kubernetes/how-to/enable-easy-deploy) Nginx Ingress can be configured to accept TCP Proxy: ``` controller: service: @@ -192,11 +192,11 @@ controller: For more help and support using Scaleway Load Balancers with your Kubernetes cluster, check out the following resources: -- [Scaleway Load Balancers: full documentation](/network/load-balancer/) * +- [Scaleway Load Balancers: full documentation](/load-balancer/) * - [Getting Started with Kubernetes Load Balancers - Tutorial](/tutorials/get-started-kubernetes-loadbalancer/) - [Getting Started with Kubernetes Load Balancers - Video Demonstration](https://www.youtube.com/watch?v=W3gPUQ_ELEo) - [Configuring a Load Balancer for your Kubernetes applications - Webinar](https://www.youtube.com/watch?v=V0uKqYXJRF4) -- [Managing Kubernetes Load Balancer IPs](/containers/kubernetes/reference-content/managing-load-balancer-ips/) -- [Using annotations for Kubernetes Load Balancers](/containers/kubernetes/reference-content/using-load-balancer-annotations/) +- [Managing Kubernetes Load Balancer IPs](/kubernetes/reference-content/managing-load-balancer-ips/) +- [Using annotations for Kubernetes Load Balancers](/kubernetes/reference-content/using-load-balancer-annotations/) \* Though this documentation may be useful, bear in mind that it principally concerns Load Balancers outside a Kubernetes context. Remember to always create and configure Load Balancers for your Kubernetes cluster via the methods described on this page and **not** via the Scaleway console, API, or developer tools. \ No newline at end of file diff --git a/containers/kubernetes/reference-content/lb-ingress-controller.mdx b/containers/kubernetes/reference-content/lb-ingress-controller.mdx index d8136df85e..dfcf15f712 100644 --- a/containers/kubernetes/reference-content/lb-ingress-controller.mdx +++ b/containers/kubernetes/reference-content/lb-ingress-controller.mdx @@ -21,10 +21,10 @@ This document will guide you through deploying a test application on a Kubernete - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Set up a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/), deploying a TRAEFIK2 ingress controller via the application library using the [Easy Deploy function](/containers/kubernetes/how-to/enable-easy-deploy/) -- Obtained the [kubeconfig](/containers/kubernetes/how-to/edit-cluster/) file for the cluster -- Installed [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your local machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Set up a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/), deploying a TRAEFIK2 ingress controller via the application library using the [Easy Deploy function](/kubernetes/how-to/enable-easy-deploy/) +- Obtained the [kubeconfig](/kubernetes/how-to/edit-cluster/) file for the cluster +- Installed [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your local machine ## Exposing the ingress controller using a Scaleway Load Balancer @@ -93,7 +93,7 @@ By default, a new security group that blocks all incoming traffic on the nodes f ## Using a reserved IP with a Load Balancer -Reserve a flexible Load Balancer IP address [through the Scaleway API](/containers/kubernetes/reference-content/managing-load-balancer-ips/#reserve-a-load-balancer-flexible-ip-address-via-the-api). Take note of the IP address, referred to as `RESERVED_IP` from now on. +Reserve a flexible Load Balancer IP address [through the Scaleway API](/kubernetes/reference-content/managing-load-balancer-ips/#reserve-a-load-balancer-flexible-ip-address-via-the-api). Take note of the IP address, referred to as `RESERVED_IP` from now on. ### Using the reserved IP in Kubernetes @@ -119,4 +119,4 @@ Reserve a flexible Load Balancer IP address [through the Scaleway API](/containe - [Loki monitoring on Kubernetes](/tutorials/manage-k8s-logging-loki/) - [Monitoring a Kubernetes Kapsule cluster](/tutorials/monitor-k8s-grafana/) -- [Deploy an image from a private registry](/containers/kubernetes/how-to/deploy-image-from-container-registry/) \ No newline at end of file +- [Deploy an image from a private registry](/kubernetes/how-to/deploy-image-from-container-registry/) \ No newline at end of file diff --git a/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx b/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx index afef7d2683..2ab784f173 100644 --- a/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx +++ b/containers/kubernetes/reference-content/managing-load-balancer-ips.mdx @@ -13,9 +13,9 @@ categories: - kubernetes --- -By default, when you create a [Load Balancer](/containers/kubernetes/concepts/#load-balancer) for your cluster, it will be assigned a random public IP address. When you delete the Load Balancer, the IP address will also be deleted and cannot be retrieved to transfer to another Load Balancer service in your cluster. +By default, when you create a [Load Balancer](/kubernetes/concepts/#load-balancer) for your cluster, it will be assigned a random public IP address. When you delete the Load Balancer, the IP address will also be deleted and cannot be retrieved to transfer to another Load Balancer service in your cluster. -However, it is possible to use [flexible IP addresses](/network/load-balancer/concepts/#flexible-ip-address) with your cluster's Load Balancer, to give you more control over the IPs being used. Flexible IP addresses can be kept in your account even if/when their associated Load Balancer is deleted. They can then be assigned to a new Load Balancer in the future. +However, it is possible to use [flexible IP addresses](/load-balancer/concepts/#flexible-ip-address) with your cluster's Load Balancer, to give you more control over the IPs being used. Flexible IP addresses can be kept in your account even if/when their associated Load Balancer is deleted. They can then be assigned to a new Load Balancer in the future. You can view your existing Load Balancer flexible IP addresses, and create new ones, in the [Scaleway console](https://console.scaleway.com/load-balancer/ips). Alternatively, use the [API](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-ip-addresses-list-ip-addresses) or other development tools. @@ -28,14 +28,14 @@ Load Balancer flexible IPs have the following limitations: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes cluster](/kubernetes/how-to/create-cluster/) ## Reserve a Load Balancer flexible IP address via the API ### Using the API -Ensure that you have created an [API key](/identity-and-access-management/iam/how-to/create-api-keys/) and run this call: +Ensure that you have created an [API key](/iam/how-to/create-api-keys/) and run this call: ```sh curl -X POST \ diff --git a/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx b/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx index 82832bb82e..0c251b8eb0 100644 --- a/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx +++ b/containers/kubernetes/reference-content/modifying-kernel-parameters-kubernetes-cluster.mdx @@ -111,7 +111,7 @@ sysctl net.core.wmem_max ``` - On Scaleway Kapsule SSH access is blocked by default. You need to enable SSH in your security group before connecting to the node. Refer to [How to enable or disable SSH ports on Kubernetes Kapsule cluster nodes](/containers/kubernetes/how-to/enable-disable-ssh/) for further information. + On Scaleway Kapsule SSH access is blocked by default. You need to enable SSH in your security group before connecting to the node. Refer to [How to enable or disable SSH ports on Kubernetes Kapsule cluster nodes](/kubernetes/how-to/enable-disable-ssh/) for further information. ## Cleaning up (Optional) diff --git a/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx b/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx index 26060364f2..54cabae06f 100644 --- a/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx +++ b/containers/kubernetes/reference-content/move-kubernetes-nodes-routed-ip.mdx @@ -19,7 +19,7 @@ categories: As part of our ongoing efforts to enhance infrastructure capabilities and provide better services to our customers, Scaleway is [introducing routed IPs for all products](https://www.scaleway.com/en/news/routed-ips-are-coming-to-all-scaleway-products/), including Kubernetes (K8s) worker nodes. -One of the standout benefits of routed IPs is their support for [IP mobility](/compute/instances/concepts/#ip-mobility), streamlining IP management and movement within the Scaleway ecosystem. By simplifying the process of reallocating IPs across different products, routed IPs empower users with unprecedented flexibility and control over their network infrastructure. +One of the standout benefits of routed IPs is their support for [IP mobility](/instances/concepts/#ip-mobility), streamlining IP management and movement within the Scaleway ecosystem. By simplifying the process of reallocating IPs across different products, routed IPs empower users with unprecedented flexibility and control over their network infrastructure. Additionally, routed IPs unlock the ability to attach multiple IPv4 addresses to a single Instance, enabling specific functionalities such as IP failover. While this feature may have limited applicability within Kubernetes environments, it offers invaluable flexibility and resilience across other Scaleway products. @@ -41,8 +41,8 @@ Additionally, routed IPs unlock the ability to attach multiple IPv4 addresses to - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Set up a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Set up a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) Kapsule and Kosmos clusters created after April 11th 2024 are deployed with IP mobility enabled by default. For existing clusters, you can manually launch the migration to routed IPs. @@ -68,9 +68,9 @@ Additionally, routed IPs unlock the ability to attach multiple IPv4 addresses to - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes cluster](/containers/kubernetes/how-to/create-cluster/) that uses NAT IPs -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes cluster](/kubernetes/how-to/create-cluster/) that uses NAT IPs +- A valid [API key](/iam/how-to/create-api-keys/) 1. Configure the following variables for your Kubernetes cluster: ``` diff --git a/containers/kubernetes/reference-content/multi-az-clusters.mdx b/containers/kubernetes/reference-content/multi-az-clusters.mdx index e34905abfa..c7fd4a673f 100644 --- a/containers/kubernetes/reference-content/multi-az-clusters.mdx +++ b/containers/kubernetes/reference-content/multi-az-clusters.mdx @@ -13,7 +13,7 @@ categories: - kubernetes --- -Kubernetes Kapsule clusters can use [Private Networks](/faq/private-networks/#what-are-private-networks), providing a default security layer for worker nodes. Furthermore, these clusters can deploy node pools across various [Availability Zones (AZs)](/containers/kubernetes/concepts/#multi-az-clusters). +Kubernetes Kapsule clusters can use [Private Networks](/faq/private-networks/#what-are-private-networks), providing a default security layer for worker nodes. Furthermore, these clusters can deploy node pools across various [Availability Zones (AZs)](/kubernetes/concepts/#multi-az-clusters). @@ -57,7 +57,7 @@ It is important to note that the scalability and reliability of Kubernetes does ### Prerequisites for setting up a multi-AZ cluster -- Your cluster must be compatible with, and connected to a Private Network. If it is not, you will need to migrate your cluster following the [procedure through the console, API, or Terraform](/containers/kubernetes/reference-content/secure-cluster-with-private-network/). +- Your cluster must be compatible with, and connected to a Private Network. If it is not, you will need to migrate your cluster following the [procedure through the console, API, or Terraform](/kubernetes/reference-content/secure-cluster-with-private-network/). - Ensure the node types required for your pool are available in your chosen AZs, as not all node types are available in every AZ and stocks might be limited. diff --git a/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx b/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx index f416d6ed9d..8eb3a439be 100644 --- a/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx +++ b/containers/kubernetes/reference-content/secure-cluster-with-private-network.mdx @@ -15,13 +15,13 @@ categories: Scaleway Kubernetes Kapsule provides a managed environment to create, configure, and run a cluster of preconfigured machines for containerized applications. This allows you to create Kubernetes clusters without the complexity of managing the infrastructure. -All new Kubernetes clusters are deployed with a Scaleway [Private Network](/network/vpc/concepts/#private-networks) using [controlled isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation). +All new Kubernetes clusters are deployed with a Scaleway [Private Network](/vpc/concepts/#private-networks) using [controlled isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) By default, worker nodes are currently delivered with public IP addresses ([controlled isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation)). These IPs serve solely for outgoing traffic from your nodes to the internet; no default services are set to listen on them. @@ -42,7 +42,7 @@ Worker node pools with controlled isolation inside a Private Network have both p | Isolation | Controlled isolation
(default) | Full isolation
(optional) | None
(deprecated) | |-------------|-------------------------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------------------------|----------------------------------------------| -| Description | Worker nodes are assigned both private IPs and public IPs.
All inbound traffic on the public interface is dropped by default using Security Groups. | The control plane and worker nodes are set without public IPs (100% private network).
A [Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/) is required. | Clusters without a Private Network attached.
Nodes have public-only endpoints. | +| Description | Worker nodes are assigned both private IPs and public IPs.
All inbound traffic on the public interface is dropped by default using Security Groups. | The control plane and worker nodes are set without public IPs (100% private network).
A [Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) is required. | Clusters without a Private Network attached.
Nodes have public-only endpoints. | | Benefits | 1. Strong security
2. Dynamic public IPs to reach out to external providers while avoiding rate limiting | 1. Maximum security
2. A stable egress IP for secure connection to external providers | n/a | | Notice | Default choice for new clusters. Can be used in combination with pools using full isolation. | Requires a Public Gateway, which incurs additional costs. | Deprecated in October 2023. | @@ -54,15 +54,15 @@ Worker node pools with controlled isolation inside a Private Network have both p ### Can I use a Public Gateway with my Private Network to exit all outgoing traffic from the nodes? -Yes, you are required to attach a Private Gateway when setting up a node pool with [full isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation). This allows Kapsule nodes with private IPs to route their outgoing traffic through the Public Gateway. For detailed steps on setting up a Public Gateway, refer to our [Public Gateway documentation](/network/public-gateways/how-to/configure-a-public-gateway/). +Yes, you are required to attach a Private Gateway when setting up a node pool with [full isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation). This allows Kapsule nodes with private IPs to route their outgoing traffic through the Public Gateway. For detailed steps on setting up a Public Gateway, refer to our [Public Gateway documentation](/public-gateways/how-to/configure-a-public-gateway/). Keep in mind that removing or detaching the Public Gateway from the Private Network can cause a single point of failure in the cluster, preventing fully isolated node pools from accessing the control plane. To use a Public Gateway with a Private Network on a Kapsule cluster, make sure that * The Public Gateway is located in the same region as the Kapsule cluster. - * [Dynamic NAT must be activated](/network/public-gateways/concepts/#nat) (enabled by default). - * [Advertise DefaultRoute must be activated](/network/public-gateways/concepts/#default-route) (enabled by default). - * Your Public Gateway is [fully integrated with IPAM, and is not a legacy gateway](/network/public-gateways/concepts/#ipam). + * [Dynamic NAT must be activated](/public-gateways/concepts/#nat) (enabled by default). + * [Advertise DefaultRoute must be activated](/public-gateways/concepts/#default-route) (enabled by default). + * Your Public Gateway is [fully integrated with IPAM, and is not a legacy gateway](/public-gateways/concepts/#ipam). ### Is Kosmos compatible with Private Networks? @@ -73,11 +73,11 @@ Kosmos uses Kilo as a CNI, which uses WireGuard to create a VPN Mesh between nod ### Are Managed Databases compatible with Kubernetes Kapsule on Private Networks? -Yes, they are. Since July 2023, the automatic allocation of IP addresses via IPAM is available for Managed Databases. These IP addresses are compatible with Scaleway's VPC, which is now in General Availability. For more information about product compatibility, refer to the [VPC documentation](/network/vpc/troubleshooting/vpc-limitations/). +Yes, they are. Since July 2023, the automatic allocation of IP addresses via IPAM is available for Managed Databases. These IP addresses are compatible with Scaleway's VPC, which is now in General Availability. For more information about product compatibility, refer to the [VPC documentation](/vpc/troubleshooting/vpc-limitations/). For any new Private Networks you create and attach to Managed Databases after July 2023, your private IP addresses are automatically allocated. -If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old private network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API. +If you have set up Private Network endpoints for your Managed Databases before July 2023, and want to connect to Kapsule via a Private Network, you must first delete your old private network endpoint. Then, you can create a new one, either via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/#how-to-attach-a-database-instance-to-a-private-network) or API. In the example below, we show you how to do so via the API. We specify the automated configuration of your Private Network via IPAM using `"ipam_config": {},`. @@ -111,7 +111,7 @@ Refer to the [Managed Database for PostgreSQL and MySQL API documentation](https Managed Load Balancers support Private Networks with private backends and public frontends, meaning the traffic is forwarded to your worker nodes through your clusters' Private Network. -Additionally, [private Load Balancers](/network/load-balancer/concepts/#private-load-balancer) are supported. These Load Balancers have no public IPs in either their back or frontends. +Additionally, [private Load Balancers](/load-balancer/concepts/#private-load-balancer) are supported. These Load Balancers have no public IPs in either their back or frontends. If you have a trusted IP configured on your ingress controller, note that the request will come from a private IP. @@ -199,9 +199,9 @@ You can find a Terraform configuration example below: ## Is the control plane also located inside the Private Network? -The control plane and worker nodes are located in your cluster's Private Network. You can reach the control plane for nodes using [full isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation) by adding a [Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/) to the cluster. +The control plane and worker nodes are located in your cluster's Private Network. You can reach the control plane for nodes using [full isolation](#what-is-the-difference-between-controlled-isolation-and-full-isolation) by adding a [Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) to the cluster. ## Are there additional options for isolation? -- You can restrict and allow a range of IPs to control who can access the API server of your fully isolated clusters. [Learn how to manage allowed IPs](/containers/kubernetes/how-to/manage-allowed-ips) +- You can restrict and allow a range of IPs to control who can access the API server of your fully isolated clusters. [Learn how to manage allowed IPs](/kubernetes/how-to/manage-allowed-ips) - The CNI’s network policies will restrict/allow a range of IPs or ports to control who can access the API server. \ No newline at end of file diff --git a/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx b/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx index adf40c1084..26355ff712 100644 --- a/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx +++ b/containers/kubernetes/reference-content/using-load-balancer-annotations.mdx @@ -17,13 +17,13 @@ categories: In Kubernetes, annotations are a way to attach metadata to objects, like pods, services, and more. These annotations are key-value pairs that can be useful for tools and libraries interacting with these objects. These annotations are used to influence the behavior, settings, or configurations of the provisioned load balancer resource. -When you [create a Load Balancer](/containers/kubernetes/reference-content/kubernetes-load-balancer/) for your Kubernetes cluster, it will be created with a default configuration, unless you define its configuration parameters via **annotations**. Load Balancer annotations let you configure parameters such as the balancing method health check settings and more. +When you [create a Load Balancer](/kubernetes/reference-content/kubernetes-load-balancer/) for your Kubernetes cluster, it will be created with a default configuration, unless you define its configuration parameters via **annotations**. Load Balancer annotations let you configure parameters such as the balancing method health check settings and more. See the full list of available Load Balancer annotations [here](https://github.com/scaleway/scaleway-cloud-controller-manager/blob/master/docs/loadbalancer-annotations.md) as part of the Scaleway Cloud Controller Manager documentation. For help understanding any of these parameters, refer to the following documentation: -- [Load Balancer Concepts](/network/load-balancer/concepts/) -- [Configuring backends](/network/load-balancer/reference-content/configuring-backends/) -- [Configuring frontends](/network/load-balancer/reference-content/configuring-frontends/) -- [Configuring health checks](/network/load-balancer/reference-content/configuring-health-checks/) +- [Load Balancer Concepts](/load-balancer/concepts/) +- [Configuring backends](/load-balancer/reference-content/configuring-backends/) +- [Configuring frontends](/load-balancer/reference-content/configuring-frontends/) +- [Configuring health checks](/load-balancer/reference-content/configuring-health-checks/) You should **always** use annotations as described below to configure your cluster's Load Balancer. Any modifications made to the configuration of your Kubernetes cluster's Load Balancer via the Scaleway console, the API, or any other devtools, will be **overwritten by the cluster's CCM**. diff --git a/containers/kubernetes/reference-content/version-support-policy.mdx b/containers/kubernetes/reference-content/version-support-policy.mdx index 73ea52a320..ca70468bcf 100644 --- a/containers/kubernetes/reference-content/version-support-policy.mdx +++ b/containers/kubernetes/reference-content/version-support-policy.mdx @@ -33,7 +33,7 @@ The [Kubernetes Kapsule](https://www.scaleway.com/en/kubernetes-kapsule/) and [K This upgrade applies to both the control plane and the managed node versions of Kubernetes. You can activate this feature through the API, CLI, or the Scaleway console. Note, to ensure smooth operation of the auto-upgrade, the `kube-system` namespace should remain untouched and free from any user-initiated modifications that might cause issues with the upgrade process. -If you are looking to upgrade to the next minor version of Kubernetes, refer to our [documentation on upgrading to the next minor version](/containers/kubernetes/how-to/upgrade-kubernetes-version/). +If you are looking to upgrade to the next minor version of Kubernetes, refer to our [documentation on upgrading to the next minor version](/kubernetes/how-to/upgrade-kubernetes-version/). ## Support diff --git a/containers/kubernetes/reference-content/wildcard-dns.mdx b/containers/kubernetes/reference-content/wildcard-dns.mdx index d95d26db9e..fc519bba7b 100644 --- a/containers/kubernetes/reference-content/wildcard-dns.mdx +++ b/containers/kubernetes/reference-content/wildcard-dns.mdx @@ -26,8 +26,8 @@ In short, Kubernetes wildcard DNS, combined with an ingress controller, provides - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/containers/kubernetes/how-to/create-cluster/) a Scaleway Kubernetes cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/kubernetes/how-to/create-cluster/) a Scaleway Kubernetes cluster - Installed `helm` on your local computer - A domain name - A `TCP` or `HTTP` service you want to expose diff --git a/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx b/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx index 8a7df269ae..e07af74b17 100644 --- a/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx +++ b/containers/kubernetes/troubleshooting/configuring-sql-storage-backend-helm.mdx @@ -26,16 +26,16 @@ To resolve this issue, you can configure Helm to use an SQL storage backend such - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) ## Setting up a PostgreSQL database You can set up a PostgreSQL database using one of the two options below. ### Option A: Scaleway's managed PostgreSQL Service -1. [Create a PostgreSQL instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) using Scaleway's Managed Database service to create a PostgreSQL database. -2. [Whitelist your cluster's IPs](/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses/) to allow your Kubernetes cluster to connect to the database. +1. [Create a PostgreSQL instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) using Scaleway's Managed Database service to create a PostgreSQL database. +2. [Whitelist your cluster's IPs](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses/) to allow your Kubernetes cluster to connect to the database. 3. Note down the connection details. Save the host, port, database name, username, and password for later use. ### Option B: Deploy PostgreSQL in Kubernetes diff --git a/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx b/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx index c74085d6a5..d090c6628d 100644 --- a/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx +++ b/containers/kubernetes/troubleshooting/containers-not-starting-arm-instances.mdx @@ -61,4 +61,4 @@ docker manifest push : - Ensure that all dependencies and libraries used in your application are compatible with the ARM architecture. Tools like the `file` command can help identify the architecture of binary files. - Use Kubernetes node selectors or affinity rules to ensure that containers are scheduled on nodes with compatible architectures. This prevents scheduling x86 containers on ARM nodes and vice versa. -Refer to our documentation to find out [how to deploy both x86 and ARM images in Kubernetes](/containers/kubernetes/how-to/deploy-x86-arm-images/). \ No newline at end of file +Refer to our documentation to find out [how to deploy both x86 and ARM images in Kubernetes](/kubernetes/how-to/deploy-x86-arm-images/). \ No newline at end of file diff --git a/contribute.mdx b/contribute.mdx index 9af5f14522..e86fa709c6 100644 --- a/contribute.mdx +++ b/contribute.mdx @@ -65,7 +65,7 @@ Join the Scaleway **Write for the Community** program, an initiative for making Open a [new issue](https://github.com/scaleway/docs-content/issues/new?assignees=&labels=Documentation+Request&template=doc_request.yaml&title=%5B%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB+Documentation+Request%5D%3A+) in our GitHub repository using the documentation request template. - Do not forget to include your [Organization ID](/identity-and-access-management/iam/concepts/#organization-id) to receive your cloud credits. + Do not forget to include your [Organization ID](/iam/concepts/#organization-id) to receive your cloud credits. You can also create a pull request directly in the [docs-content GitHub repository](https://github.com/scaleway/docs-content/pulls) but remember that only content approved via a documentation request issue is eligible for rewards. @@ -74,7 +74,7 @@ Join the Scaleway **Write for the Community** program, an initiative for making If you write a tutorial that gets published on our website, you will receive a voucher of **up to €200 cloud credits** in your Scaleway account. Note that for receiving a reward, you must have: - - Submitted your tutorial idea via a [documentation request issue](https://github.com/scaleway/docs-content/issues/new?assignees=&labels=Documentation+Request&template=doc_request.yaml&title=%5B%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB+Documentation+Request%5D%3A+), which included your [Organization ID](https://www.scaleway.com/en/docs/identity-and-access-management/iam/how-to/accept-invitation-to-orga/) and was approved by our team. + - Submitted your tutorial idea via a [documentation request issue](https://github.com/scaleway/docs-content/issues/new?assignees=&labels=Documentation+Request&template=doc_request.yaml&title=%5B%F0%9F%91%A9%E2%80%8D%F0%9F%92%BB+Documentation+Request%5D%3A+), which included your [Organization ID](https://www.scaleway.com/en/docs/iam/how-to/accept-invitation-to-orga/) and was approved by our team. - Written the content yourself and followed our [contribution process](https://github.com/scaleway/docs-content/blob/main/docs/CONTRIBUTING.md). - Had your content merged and published by our team. diff --git a/dedibox-console/account/how-to/accept-outsourcing.mdx b/dedibox-console/account/how-to/accept-outsourcing.mdx index a2a9ae767f..4a90379d00 100644 --- a/dedibox-console/account/how-to/accept-outsourcing.mdx +++ b/dedibox-console/account/how-to/accept-outsourcing.mdx @@ -19,7 +19,7 @@ If you have a Scaleway Dedibox account, another user can grant you access to the - A Dedibox account logged into the [console](https://console.online.net) -1. When another user [sends you an outsourcing request](/dedibox-console/account/how-to/outsource-dedibox/), you will receive a notification. Click the link provided in the outsourcing request email to open the Scaleway Dedibox console. +1. When another user [sends you an outsourcing request](/dedibox-account/how-to/outsource-dedibox/), you will receive a notification. Click the link provided in the outsourcing request email to open the Scaleway Dedibox console. 2. The **Outsourcing** section of the Scaleway Dedibox console displays. 3. Review the services the user wants to outsource to you. diff --git a/dedibox-console/account/how-to/create-a-dedibox-account.mdx b/dedibox-console/account/how-to/create-a-dedibox-account.mdx index fd0267b913..65d6d7e4c2 100644 --- a/dedibox-console/account/how-to/create-a-dedibox-account.mdx +++ b/dedibox-console/account/how-to/create-a-dedibox-account.mdx @@ -26,4 +26,4 @@ Follow these steps to get started with Scaleway Dedibox: 3. Check your email inbox for a verification email. Click the verification link to activate your account. This will take you to the [Dedibox console](https://console.online.net/en/login) login page. 4. Enter the username and password you created during registration, then click **Sign in**. -You are now connected to the Scaleway Dedibox console. You must add [a payment method](/dedibox-console/account/how-to/add-payment-method/) before ordering your [first Dedibox dedicated server](/dedibox/dedicated-servers/how-to/order-a-server/). \ No newline at end of file +You are now connected to the Scaleway Dedibox console. You must add [a payment method](/dedibox-account/how-to/add-payment-method/) before ordering your [first Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/). \ No newline at end of file diff --git a/dedibox-console/account/how-to/resolve-abuse.mdx b/dedibox-console/account/how-to/resolve-abuse.mdx index cbfae5edb8..62b09130d1 100644 --- a/dedibox-console/account/how-to/resolve-abuse.mdx +++ b/dedibox-console/account/how-to/resolve-abuse.mdx @@ -30,7 +30,7 @@ If you encounter any issue with the resolution of an abuse, ensure that you cont 2. Click the **case ID** to view the specifics of the complaint. 3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue. - If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/compute/instances/reference-content/preventing-outgoing-ddos/). + If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/). If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly. * For other types of abuse, here are some suggestions to help you to correct them: @@ -75,7 +75,7 @@ If you encounter any issue with the resolution of your abuse tickets, please con 2. Click **Details** to view the specifics of the complaint. 3. Take note of the details provided and proceed with the necessary steps to address and resolve the issue. - If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/compute/instances/reference-content/preventing-outgoing-ddos/). + If you need guidance on resolving outgoing DDoS attacks from your server, refer to our documentation on [how to prevent outgoing DDoS](/instances/reference-content/preventing-outgoing-ddos/). If you are the subject of an abuse report for hosting illegal content (including copyright), we urge you to delete the content from the Scaleway infrastructure promptly. * For other types of abuse, here are some suggestions to help you to correct them: diff --git a/dedibox-console/account/how-to/upload-an-ssh-key.mdx b/dedibox-console/account/how-to/upload-an-ssh-key.mdx index a40ba5d2e6..927faa703b 100644 --- a/dedibox-console/account/how-to/upload-an-ssh-key.mdx +++ b/dedibox-console/account/how-to/upload-an-ssh-key.mdx @@ -26,7 +26,7 @@ SSH keys offer a more secure method of identity authentication on computer syste 3. Provide a description of your choice (e.g., your computer's name) and paste the public key into the designated field. 4. Click **Add SSH key** to upload the public key to your Scaleway Dedibox account. - With the SSH key now uploaded, you can select it during the [Dedibox installation process](/dedibox/dedicated-servers/how-to/install-a-server/) and use it for authentication on your server. + With the SSH key now uploaded, you can select it during the [Dedibox installation process](/dedicated-servers/how-to/install-a-server/) and use it for authentication on your server. If you upload another key or change the existing one, you must manually replace it on your Dedibox. The **keys are transferred from the console to your server solely during installation**. diff --git a/dedibox-console/account/index.mdx b/dedibox-console/account/index.mdx index 3b93f5888a..c7647a334f 100644 --- a/dedibox-console/account/index.mdx +++ b/dedibox-console/account/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox Account" productLogo="dedibox" description="Scaleway Dedibox account let you manage all services from the Dedibox console." - url="/dedibox-console/account/quickstart" + url="/dedibox-account/quickstart" label="Dedibox Account Quickstart" /> @@ -20,20 +20,20 @@ meta: icon="rocket" description="Learn how to create and add a payment method to your Dedibox account." label="View Quickstart" - url="/dedibox-console/account/quickstart/" + url="/dedibox-account/quickstart/" /> \ No newline at end of file diff --git a/dedibox-console/classic-hosting/concepts.mdx b/dedibox-console/classic-hosting/concepts.mdx index d250202cf4..1bec03c521 100644 --- a/dedibox-console/classic-hosting/concepts.mdx +++ b/dedibox-console/classic-hosting/concepts.mdx @@ -42,7 +42,7 @@ PHP is a server-side scripting language designed for web development, but also u ## php.ini -The `php.ini` file is the configuration file used for applications that require PHP. It contains the configuration of variables such as upload sizes, file timeouts, and resource limits. At Scaleway, we provide PHP with the most common values preconfigured for each webhosting. If required, you can [customize the configuration of PHP](/dedibox-console/classic-hosting/how-to/configure-php/) towards your needs. +The `php.ini` file is the configuration file used for applications that require PHP. It contains the configuration of variables such as upload sizes, file timeouts, and resource limits. At Scaleway, we provide PHP with the most common values preconfigured for each webhosting. If required, you can [customize the configuration of PHP](/classic-hosting/how-to/configure-php/) towards your needs. ## Redirection diff --git a/dedibox-console/classic-hosting/how-to/change-password-mysql-database.mdx b/dedibox-console/classic-hosting/how-to/change-password-mysql-database.mdx index 88127216e4..ebedc9950c 100644 --- a/dedibox-console/classic-hosting/how-to/change-password-mysql-database.mdx +++ b/dedibox-console/classic-hosting/how-to/change-password-mysql-database.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** plan -- [Created](/dedibox-console/classic-hosting/how-to/create-mysql-database/) a MySQL database +- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/change-password-postgresql-database.mdx b/dedibox-console/classic-hosting/how-to/change-password-postgresql-database.mdx index d9b22f1dc8..173dfbadcf 100644 --- a/dedibox-console/classic-hosting/how-to/change-password-postgresql-database.mdx +++ b/dedibox-console/classic-hosting/how-to/change-password-postgresql-database.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** plan -- [Created](/dedibox-console/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database +- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/configure-outlook.mdx b/dedibox-console/classic-hosting/how-to/configure-outlook.mdx index 0411daab24..22c4070a3b 100644 --- a/dedibox-console/classic-hosting/how-to/configure-outlook.mdx +++ b/dedibox-console/classic-hosting/how-to/configure-outlook.mdx @@ -21,13 +21,13 @@ You can read and send your emails using the Microsoft Outlook client. - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created an email account](/dedibox-console/classic-hosting/how-to/create-email-account/) +- [Created an email account](/classic-hosting/how-to/create-email-account/) We recommend using the IMAP protocol if you access your mailbox from different devices (PC, Mobile phone, Tablet, …). -You can [configure](https://support.microsoft.com/en-us/office/add-an-email-account-to-outlook-6e27792a-9267-4aa4-8bb6-c84ef146101b) Microsoft Outlook to [check your emails](/dedibox-console/classic-hosting/how-to/check-emails/). +You can [configure](https://support.microsoft.com/en-us/office/add-an-email-account-to-outlook-6e27792a-9267-4aa4-8bb6-c84ef146101b) Microsoft Outlook to [check your emails](/classic-hosting/how-to/check-emails/). 1. Set the following parameters in the configuration wizard to access your Webhosting Classic mailbox: * IMAP server (incoming mail): diff --git a/dedibox-console/classic-hosting/how-to/configure-php.mdx b/dedibox-console/classic-hosting/how-to/configure-php.mdx index 42a5049649..50e0ae22a3 100644 --- a/dedibox-console/classic-hosting/how-to/configure-php.mdx +++ b/dedibox-console/classic-hosting/how-to/configure-php.mdx @@ -108,7 +108,7 @@ As part of the creation of a large website, it is possible to centralize frequen - Persistent connections are not possible due to the architecture of the webhosting platform and are performed as a standard connection. -Refer to the [documentation](/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin/) on how to configure the connection to a database using PHP. +Refer to the [documentation](/classic-hosting/how-to/manage-mysql-database-phpmyadmin/) on how to configure the connection to a database using PHP. ## How to upload files diff --git a/dedibox-console/classic-hosting/how-to/connect-via-ftp.mdx b/dedibox-console/classic-hosting/how-to/connect-via-ftp.mdx index bd63400c2d..0baddf64ea 100644 --- a/dedibox-console/classic-hosting/how-to/connect-via-ftp.mdx +++ b/dedibox-console/classic-hosting/how-to/connect-via-ftp.mdx @@ -17,12 +17,12 @@ categories: **F**ile **T**ransfer **P**rotocol (FTP) is a standard method for transferring files between a client (e.g., your local computer) and a server (e.g., your Scaleway web hosting server) via the internet. This guide shows you how to configure the popular and free FTP client [FileZilla](https://filezilla-project.org/) to connect to your web hosting site using FTP. You will then be able to transfer files from your local computer to your Scaleway web hosting server. For additional help, refer to the [FileZilla Client Tutorial](https://wiki.filezilla-project.org/FileZilla_Client_Tutorial_(en)). -In this example, we assume your domain name is `example.com` and your FTP account is `webmaster@example.com`. Ensure you have [created an FTP account](/dedibox-console/classic-hosting/how-to/create-ftp-account/) before proceeding. +In this example, we assume your domain name is `example.com` and your FTP account is `webmaster@example.com`. Ensure you have [created an FTP account](/classic-hosting/how-to/create-ftp-account/) before proceeding. - A Dedibox account logged into the [console](https://console.online.net) - A **Web Hosting Classic** plan and a domain name -- An [FTP account created](/dedibox-console/classic-hosting/how-to/create-ftp-account/) +- An [FTP account created](/classic-hosting/how-to/create-ftp-account/) ### Installing FileZilla @@ -38,7 +38,7 @@ In this example, we assume your domain name is `example.com` and your FTP accoun 1. Open FileZilla on your local machine. 2. Click on **File** in the top menu, and select **Site Manager**. -3. Enter the following information in the form that displays. Remember to replace the **User** and **Password** values with [those of your FTP account](/dedibox-console/classic-hosting/how-to/create-ftp-account/). +3. Enter the following information in the form that displays. Remember to replace the **User** and **Password** values with [those of your FTP account](/classic-hosting/how-to/create-ftp-account/). - **Protocol**: FTP - File Transfer Protocol diff --git a/dedibox-console/classic-hosting/how-to/create-ftp-account.mdx b/dedibox-console/classic-hosting/how-to/create-ftp-account.mdx index a2039c0cc0..60fa0f9ffc 100644 --- a/dedibox-console/classic-hosting/how-to/create-ftp-account.mdx +++ b/dedibox-console/classic-hosting/how-to/create-ftp-account.mdx @@ -15,7 +15,7 @@ categories: -**F**ile **T**ransfer **P**rotocol is a standard way to transfer files between a client (such as your local computer) and a server (such as your Scaleway webhosting server) via the internet. In order to [use FTP](/dedibox-console/classic-hosting/how-to/connect-via-ftp/), you must first create an account. +**F**ile **T**ransfer **P**rotocol is a standard way to transfer files between a client (such as your local computer) and a server (such as your Scaleway webhosting server) via the internet. In order to [use FTP](/classic-hosting/how-to/connect-via-ftp/), you must first create an account. @@ -36,7 +36,7 @@ categories: Your FTP account appears in the account list with the status **Waiting to create**. Your account will be activated in approximately one hour. - When you [connect to your FTP account](/dedibox-console/classic-hosting/how-to/connect-via-ftp/), the following folders display: + When you [connect to your FTP account](/classic-hosting/how-to/connect-via-ftp/), the following folders display: * `awffull` (contains your old access statistics, if they were activated). * `www` (should contain your website). * `logs` (contains your old access statistics, if they were activated). diff --git a/dedibox-console/classic-hosting/how-to/create-postgresql-database.mdx b/dedibox-console/classic-hosting/how-to/create-postgresql-database.mdx index ee2ca94bd5..6547714f5f 100644 --- a/dedibox-console/classic-hosting/how-to/create-postgresql-database.mdx +++ b/dedibox-console/classic-hosting/how-to/create-postgresql-database.mdx @@ -37,7 +37,7 @@ However, it has the following limitations: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created](/dedibox-console/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database +- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/create-subdomain.mdx b/dedibox-console/classic-hosting/how-to/create-subdomain.mdx index 28751c96f1..9b70abc1da 100644 --- a/dedibox-console/classic-hosting/how-to/create-subdomain.mdx +++ b/dedibox-console/classic-hosting/how-to/create-subdomain.mdx @@ -32,7 +32,7 @@ Subdomains are an additional part to extend your main domain name. Mostly, they ## How to upload content to your subdomain -1. Connect to your webhosting using your [FTP account](/dedibox-console/classic-hosting/concepts/#ftp-account). A listing of your remote files and folders displays in the right part of the FTP client: +1. Connect to your webhosting using your [FTP account](/classic-hosting/concepts/#ftp-account). A listing of your remote files and folders displays in the right part of the FTP client: 2. Double-click on the folder named like your subdomain to enter it. Then upload your files into this directory. diff --git a/dedibox-console/classic-hosting/how-to/delete-ftp-account.mdx b/dedibox-console/classic-hosting/how-to/delete-ftp-account.mdx index 552ab301af..918a60b1ac 100644 --- a/dedibox-console/classic-hosting/how-to/delete-ftp-account.mdx +++ b/dedibox-console/classic-hosting/how-to/delete-ftp-account.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- An [FTP account](/dedibox-console/classic-hosting/how-to/create-ftp-account/) +- An [FTP account](/classic-hosting/how-to/create-ftp-account/) 1. Click **Hosting** then click **Manage**. 2. Click the **FTP accounts** tab. diff --git a/dedibox-console/classic-hosting/how-to/delete-mysql-database.mdx b/dedibox-console/classic-hosting/how-to/delete-mysql-database.mdx index 0da2d09103..4ae4625db8 100644 --- a/dedibox-console/classic-hosting/how-to/delete-mysql-database.mdx +++ b/dedibox-console/classic-hosting/how-to/delete-mysql-database.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created](/dedibox-console/classic-hosting/how-to/create-mysql-database/) a MySQL database +- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/delete-postgresql-database.mdx b/dedibox-console/classic-hosting/how-to/delete-postgresql-database.mdx index e51b285ba9..b074df6585 100644 --- a/dedibox-console/classic-hosting/how-to/delete-postgresql-database.mdx +++ b/dedibox-console/classic-hosting/how-to/delete-postgresql-database.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created](/dedibox-console/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database +- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx b/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx index 2c30b515ae..0c2ddcd7aa 100644 --- a/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx +++ b/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created](/dedibox-console/classic-hosting/how-to/create-mysql-database/) a MySQL database +- [Created](/classic-hosting/how-to/create-mysql-database/) a MySQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/manage-postgresql-database-adminer.mdx b/dedibox-console/classic-hosting/how-to/manage-postgresql-database-adminer.mdx index 29bd574eac..6641a367f3 100644 --- a/dedibox-console/classic-hosting/how-to/manage-postgresql-database-adminer.mdx +++ b/dedibox-console/classic-hosting/how-to/manage-postgresql-database-adminer.mdx @@ -19,7 +19,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- [Created](/dedibox-console/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database +- [Created](/classic-hosting/how-to/create-postgresql-database/) a PostgreSQL database 1. From your Dedibox console, click **Hosting**. A list of your webhosting accounts displays. 2. Click **Manage** next to the hosting you want to configure. The webhosting overview page displays. diff --git a/dedibox-console/classic-hosting/how-to/solve-email-account-connection-problems.mdx b/dedibox-console/classic-hosting/how-to/solve-email-account-connection-problems.mdx index 391d7324e1..8e004fc8fb 100644 --- a/dedibox-console/classic-hosting/how-to/solve-email-account-connection-problems.mdx +++ b/dedibox-console/classic-hosting/how-to/solve-email-account-connection-problems.mdx @@ -19,14 +19,14 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - Created a **Webhosting Classic** -- Created an [email account](/dedibox-console/classic-hosting/how-to/create-email-account/) +- Created an [email account](/classic-hosting/how-to/create-email-account/) 1. Log into the [Scaleway webmail interface](https://webmail.online.net/). 2. Verify if your emails are available from the Scaleway webmail interface. - If you can connect to your email account using the Scaleway webmail, the problem you are experiencing might come from the configuration of your computer. -3. Verify the [configuration of your client](/dedibox-console/classic-hosting/how-to/check-emails/). +3. Verify the [configuration of your client](/classic-hosting/how-to/check-emails/). - Some email clients cut the domain part of your email address in the username by default. For example, with the email address “[firstname.lastname@example.com](mailto:firstname.lastname@example.com)”, your client cuts it to “firstname.lastname”. Make sure to enter your complete email address as your username. diff --git a/dedibox-console/classic-hosting/index.mdx b/dedibox-console/classic-hosting/index.mdx index aead826906..34f1dd208c 100644 --- a/dedibox-console/classic-hosting/index.mdx +++ b/dedibox-console/classic-hosting/index.mdx @@ -8,7 +8,7 @@ meta: productName="Webhosting Classic" productLogo="dedibox" description="Webhosting Classic is a service provided by Scaleway which offers storage space and access for your websites." - url="/dedibox-console/classic-hosting/quickstart" + url="/classic-hosting/quickstart" label="Webhosting Classic Quickstart" /> @@ -20,20 +20,20 @@ meta: icon="rocket" description="Learn how to manage a Webhosting Classic in a few steps." label="View Quickstart" - url="/dedibox-console/classic-hosting/quickstart/" + url="/classic-hosting/quickstart/" /> diff --git a/dedibox-console/classic-hosting/quickstart.mdx b/dedibox-console/classic-hosting/quickstart.mdx index a2945fb115..ac27a96be3 100644 --- a/dedibox-console/classic-hosting/quickstart.mdx +++ b/dedibox-console/classic-hosting/quickstart.mdx @@ -99,5 +99,5 @@ Scaleway Webhosting Classic is our historical Webhosting service. It allows you Your database is being created and displays in the list of your MySQL databases. - For MySQL databases, [size limitations apply](/dedibox-console/classic-hosting/how-to/create-mysql-database/#limitations). + For MySQL databases, [size limitations apply](/classic-hosting/how-to/create-mysql-database/#limitations). \ No newline at end of file diff --git a/dedibox-console/cpanel-hosting/index.mdx b/dedibox-console/cpanel-hosting/index.mdx index 9f2a5ba851..426ead1d92 100644 --- a/dedibox-console/cpanel-hosting/index.mdx +++ b/dedibox-console/cpanel-hosting/index.mdx @@ -8,7 +8,7 @@ meta: productName="cPanel Webhosting" productLogo="dedibox" description="cPanel Webhosting is a service provided by Scaleway which offers storage space and access for your websites." - url="/dedibox-console/cpanel-hosting/quickstart" + url="/cpanel-hosting/quickstart" label="cPanel Webhosting Quickstart" /> @@ -20,13 +20,13 @@ meta: icon="rocket" description="Learn how to manage a cPanel Webhosting in a few steps." label="View Quickstart" - url="/dedibox-console/cpanel-hosting/quickstart/" + url="/cpanel-hosting/quickstart/" /> \ No newline at end of file diff --git a/dedibox-console/cpanel-hosting/reference-content.mdx b/dedibox-console/cpanel-hosting/reference-content.mdx index 93ce6af74a..b8309c2af9 100644 --- a/dedibox-console/cpanel-hosting/reference-content.mdx +++ b/dedibox-console/cpanel-hosting/reference-content.mdx @@ -17,7 +17,7 @@ categories: This documentation is for users who have a webhosting package powered by cPanel on [Scaleway Dedibox](https://www.scaleway.com/en/web-hosting/). -Refer to our [Quickstart](/dedibox-console/cpanel-hosting/quickstart/) which contains useful links that answer your frequently asked questions. +Refer to our [Quickstart](/cpanel-hosting/quickstart/) which contains useful links that answer your frequently asked questions. If you need additional help setting up your webhosting solution, or have any questions, refer to the index below: diff --git a/dedibox-network/dns/concepts.mdx b/dedibox-network/dns/concepts.mdx index e74c41f596..7b5a083501 100644 --- a/dedibox-network/dns/concepts.mdx +++ b/dedibox-network/dns/concepts.mdx @@ -14,11 +14,11 @@ categories: ## Domain Name / Domain -See [Domains](/dedibox-network/domains/concepts/#domain-name). +See [Domains](/dedibox-domains/concepts/#domain-name). ## DNS -The **D**omain **N**ame **S**ystem is a name management system for computing devices connected to a network, be it public (Internet) or private. It translates text-based [domain names](/dedibox-network/domains/concepts/#domain-name) to numerical [IP addresses](#ip-address). +The **D**omain **N**ame **S**ystem is a name management system for computing devices connected to a network, be it public (Internet) or private. It translates text-based [domain names](/dedibox-domains/concepts/#domain-name) to numerical [IP addresses](#ip-address). ## DNS Delegation @@ -70,7 +70,7 @@ Reverse DNS, or rDNS, is exactly the opposite of classic [forward DNS](#dns) as ## Root Server -Root Servers are a type of [DNS Name Server](#dns-name-servers) pertaining to [Top Level domains](/dedibox-network/domains/concepts/#tld). They are the first step in the resolution of any domain name, since they contain information about the authoritative DNS servers for each Top Level Domain. +Root Servers are a type of [DNS Name Server](#dns-name-servers) pertaining to [Top Level domains](/dedibox-domains/concepts/#tld). They are the first step in the resolution of any domain name, since they contain information about the authoritative DNS servers for each Top Level Domain. ## Secondary DNS diff --git a/dedibox-network/dns/how-to/configure-secondary-dns.mdx b/dedibox-network/dns/how-to/configure-secondary-dns.mdx index b4f4ed701b..1630209731 100644 --- a/dedibox-network/dns/how-to/configure-secondary-dns.mdx +++ b/dedibox-network/dns/how-to/configure-secondary-dns.mdx @@ -31,7 +31,7 @@ This how-to assumes that you want to manage your domains exclusively with BIND. ## How to configure BIND 1. If you use a management panel for your server, add the domain in your panel. -2. Log in to your server as root [via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). +2. Log in to your server as root [via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). 3. Use your favorite text editor to edit the general BIND configuration file, located at `/etc/bind/named.conf`. The configuration of your domain should be as follows (replace `domain.fr` with your domain): ``` zone "domain.fr" { diff --git a/dedibox-network/dns/index.mdx b/dedibox-network/dns/index.mdx index d82d2564ce..1bdf2512bd 100644 --- a/dedibox-network/dns/index.mdx +++ b/dedibox-network/dns/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox - DNS" productLogo="dedibox" description="Dedibox DNS allows you to configure the DNS settings of your Dedibox server." - url="/dedibox-network/dns/concepts/" + url="/dedibox-dns/concepts/" label="DNS Concepts" /> @@ -20,14 +20,14 @@ meta: icon="information-circle-outline" description="Core concepts that give you a better understanding of DNS." label="View Concepts" - url="/dedibox-network/dns/concepts/" + url="/dedibox-dns/concepts/" /> diff --git a/dedibox-network/domains/how-to/change-ownership.mdx b/dedibox-network/domains/how-to/change-ownership.mdx index 3a8e4c302f..551ece1775 100644 --- a/dedibox-network/domains/how-to/change-ownership.mdx +++ b/dedibox-network/domains/how-to/change-ownership.mdx @@ -11,10 +11,10 @@ dates: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. -You must always keep the contact details relating to the owner of your domain name accurate and up to date. This can be done by [following the instructions here](/dedibox-network/domains/how-to/file-contact-info/). If you wish to change details about the owner’s identity, such as full name(s) or corporate name, this must be done by the change of ownership process described below. +You must always keep the contact details relating to the owner of your domain name accurate and up to date. This can be done by [following the instructions here](/dedibox-domains/how-to/file-contact-info/). If you wish to change details about the owner’s identity, such as full name(s) or corporate name, this must be done by the change of ownership process described below. Before changing the ownership of the domain, you must [ensure that all contact email addresses of the domain are up to date](#how-to-check-and-update-the-contact-email). @@ -23,7 +23,7 @@ Before changing the ownership of the domain, you must [ensure that all contact e - A Dedibox account logged into the [console](https://console.online.net) -- A Scaleway domain you want to transfer to a new owner, who must have [created a Dedibox account](/dedibox-console/account/how-to/create-a-dedibox-account/) +- A Scaleway domain you want to transfer to a new owner, who must have [created a Dedibox account](/dedibox-account/how-to/create-a-dedibox-account/) ## How to check and update the contact email diff --git a/dedibox-network/domains/how-to/enable-dnssec.mdx b/dedibox-network/domains/how-to/enable-dnssec.mdx index 8cdbeb7b72..ad96698e71 100644 --- a/dedibox-network/domains/how-to/enable-dnssec.mdx +++ b/dedibox-network/domains/how-to/enable-dnssec.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. Since its design in 1983, DNS has been vulnerable to attacks. Attackers can falsify responses to DNS queries, which allows them to redirect end users to websites under their control. In response to these threats, [DNSSEC](https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en) was deployed. DNSSEC cryptographically ensures that DNS content cannot be modified from its source without being detected. It works by digitally signing each DNS record so that any tampering of that record can be detected. @@ -33,7 +33,7 @@ DNSSEC should only be used by experienced users, due to the propagation time of - Not all DNS servers (clients) verify DNSSEC, you can achieve responses on them despite bad DNSSEC configuration - This page shows you how to enable DNSSEC for **Online.net domains only**. Find out how to enable DNSSEC for Domains and DNS domains via [the API](https://www.scaleway.com/en/developers/api/domains-and-dns/registrar-api/#path-domains-update-domain-dnssec) or the [Scaleway console](/network/domains-and-dns/how-to/configure-dnssec-internal-domain/). + This page shows you how to enable DNSSEC for **Online.net domains only**. Find out how to enable DNSSEC for Domains and DNS domains via [the API](https://www.scaleway.com/en/developers/api/domains-and-dns/registrar-api/#path-domains-update-domain-dnssec) or the [Scaleway console](/domains-and-dns/how-to/configure-dnssec-internal-domain/). diff --git a/dedibox-network/domains/how-to/file-contact-info.mdx b/dedibox-network/domains/how-to/file-contact-info.mdx index 22f6fc9653..dbe6033e6d 100644 --- a/dedibox-network/domains/how-to/file-contact-info.mdx +++ b/dedibox-network/domains/how-to/file-contact-info.mdx @@ -14,13 +14,13 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. You must always ensure that the contact information for the domain owner is accurate and correct. You are prompted to provide and/or check contact details when you are ordering or renewing your domain. It is your responsibility to keep this information up-to-date after that. This document shows you how to check and modify this information. - If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-network/domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). + If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). diff --git a/dedibox-network/domains/how-to/manage-dns-servers.mdx b/dedibox-network/domains/how-to/manage-dns-servers.mdx index 796381840c..401f8355ec 100644 --- a/dedibox-network/domains/how-to/manage-dns-servers.mdx +++ b/dedibox-network/domains/how-to/manage-dns-servers.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. A DNS server is a program that responds to requests for DNS zones configured by the administrator. DNS servers typically operate in pairs, each consisting of a primary and secondary server. diff --git a/dedibox-network/domains/how-to/manage-dns-zones.mdx b/dedibox-network/domains/how-to/manage-dns-zones.mdx index 3a4a47fb4d..8684e7bef9 100644 --- a/dedibox-network/domains/how-to/manage-dns-zones.mdx +++ b/dedibox-network/domains/how-to/manage-dns-zones.mdx @@ -14,10 +14,10 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. -The [DNS zone](/dedibox-network/domains/concepts/#dns-zone) is the roadmap of the domain name and contains all the required information to operate it on the internet. +The [DNS zone](/dedibox-domains/concepts/#dns-zone) is the roadmap of the domain name and contains all the required information to operate it on the internet. For example, **A** records indicate where to find the website and **MX** records indicate where emails should be sent. diff --git a/dedibox-network/domains/how-to/purchase-domain.mdx b/dedibox-network/domains/how-to/purchase-domain.mdx index 60b5687c17..3c695068f1 100644 --- a/dedibox-network/domains/how-to/purchase-domain.mdx +++ b/dedibox-network/domains/how-to/purchase-domain.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. A domain name is the equivalent of your postal address on the web, and allows your users to find your website. Scaleway offers you the possibility of buying a domain name with or without web hosting. Depending on availability, you can buy the domain name and extension (.com, .fr, .net etc.) of your choice. @@ -27,11 +27,11 @@ A domain name is the equivalent of your postal address on the web, and allows yo 2. Enter the domain name of your choice in the search bar and click **search a domain**. The **Domain name choice** page displays, showing whether the domain is available and for which extensions. - If the domain name is not available because you are already the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-network/domains/how-to/transfer-domain/) for more information. + If the domain name is not available because you are already the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-domains/how-to/transfer-domain/) for more information. 3. Select an available domain-name/extension combination from the list by clicking the checkbox next to it. - Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-network/domains/concepts/#tld-specifications-at-scaleway). + Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-domains/concepts/#tld-specifications-at-scaleway). 4. Scroll to the bottom of the page and click **Order**. The **Hosting** page displays. 5. Select a web hosting package, or choose to proceed with no hosting. You can additionally choose to add a hosting backup if you wish. @@ -44,7 +44,7 @@ A domain name is the equivalent of your postal address on the web, and allows yo - You must always keep the contact details relating to the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-network/domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). + You must always keep the contact details relating to the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). 9. Scroll down to the bottom of the page and click **Confirm**. diff --git a/dedibox-network/domains/how-to/renew-domain.mdx b/dedibox-network/domains/how-to/renew-domain.mdx index 70b2e0bf53..af51781703 100644 --- a/dedibox-network/domains/how-to/renew-domain.mdx +++ b/dedibox-network/domains/how-to/renew-domain.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. When you buy a domain name, you can use it for the period of time you registered it for, which is typically from one to ten years. When this period is nearing its end, you must renew your domain if you wish to keep using it. diff --git a/dedibox-network/domains/how-to/transfer-domain.mdx b/dedibox-network/domains/how-to/transfer-domain.mdx index 31830dc44e..bda84135ed 100644 --- a/dedibox-network/domains/how-to/transfer-domain.mdx +++ b/dedibox-network/domains/how-to/transfer-domain.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. You can transfer any domain bought or renewed at another registrar to Scaleway as long as you meet the conditions shown below. @@ -48,7 +48,7 @@ You can transfer any domain bought or renewed at another registrar to Scaleway a 8. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays. 9. Complete the contact information for the domain name. - You must always keep the domain owner’s contact details accurate and up-to-date. If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-network/domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). + You must always keep the domain owner’s contact details accurate and up-to-date. If you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). 10. Scroll down to the bottom of the page and click **Confirm**. The **Summary** page displays. 11. Check the summary of your order and select a payment mode from the drop-down menu. You must also agree to the terms of service as well as the web hosting specific terms, and choose whether to activate automatic renewal of your domain. diff --git a/dedibox-network/domains/how-to/validate-waps-info.mdx b/dedibox-network/domains/how-to/validate-waps-info.mdx index 95654ce866..cdf78ea154 100644 --- a/dedibox-network/domains/how-to/validate-waps-info.mdx +++ b/dedibox-network/domains/how-to/validate-waps-info.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. WAPS, or **W**hois **A**ccuracy **P**rogram **S**pecification, is a system introduced by the [ICANN](https://www.icann.org/) to validate the contact information of a domain name. ICANN requires that all registrars validate the identity and the continuity of the information entered in the contact of a domain name in order to have up-to-date information about the owners. diff --git a/dedibox-network/domains/index.mdx b/dedibox-network/domains/index.mdx index 167725d529..67a6b658e9 100644 --- a/dedibox-network/domains/index.mdx +++ b/dedibox-network/domains/index.mdx @@ -10,7 +10,7 @@ meta: productName="Dedibox - Domains" productLogo="dedibox" description="Dedibox - Domains offers you the possibility of purchasing a domain name with or without web hosting." - url="/dedibox-network/domains/quickstart" + url="/dedibox-domains/quickstart" label="Domains Quickstart" /> @@ -24,21 +24,21 @@ meta: icon="rocket" description="Learn how to buy and manage a domain in a few steps." label="View Quickstart" - url="/dedibox-network/domains/quickstart/" + url="/dedibox-domains/quickstart/" /> diff --git a/dedibox-network/domains/quickstart.mdx b/dedibox-network/domains/quickstart.mdx index 0245783db1..566109a258 100644 --- a/dedibox-network/domains/quickstart.mdx +++ b/dedibox-network/domains/quickstart.mdx @@ -14,7 +14,7 @@ categories: --- - This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/network/domains-and-dns/quickstart/) service. + This documentation applies to the legacy domain product previously offered by Online.net. For managing your domain names with the latest features, we recommend using Scaleway's [Domains and DNS](/domains-and-dns/quickstart/) service. A domain name is the equivalent of your postal address on the web, and allows your users to find your website. Scaleway offers you the possibility of purchasing a domain name with or without web hosting. Depending on availability, you can buy the domain name and extension (`.com`, `.fr`, `.net`, etc.) of your choice. @@ -28,11 +28,11 @@ A domain name is the equivalent of your postal address on the web, and allows yo 1. Click **DNS** in the **Network** section of the console side menu to access the [domain name order page](https://www.scaleway.com/en/domain/). 2. Enter the domain name of your choice in the search bar, and click **search a domain**. The **Domain name choice** page displays, showing whether the domain is available, and for which extensions. - If the domain name is not available because you already are the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-network/domains/how-to/transfer-domain/) for more information. + If the domain name is not available because you already are the owner, you have the option to transfer the domain so that Scaleway becomes your new registrar, and you can manage your hosting and domain from the same location. See the [relevant documentation](/dedibox-domains/how-to/transfer-domain/) for more information. 3. Select an available domain-name/extension combination from the list by clicking the checkbox next to it. - Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-network/domains/concepts/#tld-specifications-at-scaleway). + Some Top Level Domain (TLD) extensions have special requirements that owners must comply with. You may be asked for verification if you order or renew one of these extensions. [Learn more about TLD specifications](/dedibox-domains/concepts/#tld-specifications-at-scaleway). 4. Scroll to the bottom of the page and click **Order**. The **Hosting** page displays. 5. Select a web hosting package, or choose to proceed with no hosting. You can additionally choose to add a hosting backup if you wish. @@ -43,7 +43,7 @@ A domain name is the equivalent of your postal address on the web, and allows yo 7. If you did not select hosting backup, a pop-up may display asking you to confirm your choice. Click **Continue without backup** or **Add backup**. The **Contact information** page displays. 8. Select the domain owner from your existing contacts, or choose to create a new contact. - You must always keep the contact details regarding the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-network/domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). + You must always keep the contact details regarding the owner of your domain name accurate and up-to-date. Once created, if you wish to change details about the owner’s identity, such as full name(s) or corporate name, you must complete the [change of owner/applicant](/dedibox-domains/how-to/change-ownership/) process via the [console](https://console.online.net/fr/domain/trade). 9. Scroll down to the bottom of the page and click **Confirm**. diff --git a/dedibox-network/ip-failover/concepts.mdx b/dedibox-network/ip-failover/concepts.mdx index 053bbf1a68..2bf98a3270 100644 --- a/dedibox-network/ip-failover/concepts.mdx +++ b/dedibox-network/ip-failover/concepts.mdx @@ -14,7 +14,7 @@ categories: ## Bridged network -A bridged network is a mode of networking for virtual machines, another being [NAT-ed networks](/dedibox-network/ip-failover/concepts/#nat-ed-network). In bridge mode, your server and your virtual machines are seen as different servers at the level of the network equipment. Setting up a bridged network requires a [Virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address). +A bridged network is a mode of networking for virtual machines, another being [NAT-ed networks](/dedibox-ip-failover/concepts/#nat-ed-network). In bridge mode, your server and your virtual machines are seen as different servers at the level of the network equipment. Setting up a bridged network requires a [Virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address). ## Failover IPs @@ -26,7 +26,7 @@ IP configuration refers to the assignment and management of IP addresses. Any se ## NAT-ed network -A NAT-ed network is a mode of networking for virtual machines, another being [bridged networks](/dedibox-network/ip-failover/concepts/#bridged-network). In NAT mode, your server and its virtual machines are seen as one single server. As only the MAC address of your physical network card is broadcasted on the network, you do not require virtual MAC addresses for this network mode. +A NAT-ed network is a mode of networking for virtual machines, another being [bridged networks](/dedibox-ip-failover/concepts/#bridged-network). In NAT mode, your server and its virtual machines are seen as one single server. As only the MAC address of your physical network card is broadcasted on the network, you do not require virtual MAC addresses for this network mode. ## Reverse DNS @@ -34,8 +34,8 @@ Reverse DNS, or rDNS, is exactly the opposite of classic forward DNS as we know ## Virtual MAC address -Virtual MAC addresses are associated with Failover IPs, and are virtual versions of MAC addresses that identify physical hardware. Virtual MAC addresses allow you to create a [bridged network](/dedibox-network/ip-failover/concepts/#bridged-network) of virtual machines from your server, where the physical server and its virtual machines are identified as different machines at the network level. The same virtual MAC can be associated with several Failover IPs. +Virtual MAC addresses are associated with Failover IPs, and are virtual versions of MAC addresses that identify physical hardware. Virtual MAC addresses allow you to create a [bridged network](/dedibox-ip-failover/concepts/#bridged-network) of virtual machines from your server, where the physical server and its virtual machines are identified as different machines at the network level. The same virtual MAC can be associated with several Failover IPs. ## Virtualization -Virtualization refers to the creation of one or multiple virtual machines on a physical server. This can be achieved via virtualization solutions such as VMware vSphere Hypervisor (ESXi) or Proxmox. Virtualization allows you to create separate environments for your different services (for example, keeping mail and web services on different VMs) or to launch several virtual machines to make better use of the performance of the server. To communicate on the Internet, each of your virtual machines needs an IP Address. You can use [Failover IPs](/dedibox-network/ip-failover/concepts/#failover-ips) for this purpose. If you want to create a bridged network for your virtual machines, you will also need to configure [Virtual MAC addresses](/dedibox-network/ip-failover/concepts/#virtual-mac-address). \ No newline at end of file +Virtualization refers to the creation of one or multiple virtual machines on a physical server. This can be achieved via virtualization solutions such as VMware vSphere Hypervisor (ESXi) or Proxmox. Virtualization allows you to create separate environments for your different services (for example, keeping mail and web services on different VMs) or to launch several virtual machines to make better use of the performance of the server. To communicate on the Internet, each of your virtual machines needs an IP Address. You can use [Failover IPs](/dedibox-ip-failover/concepts/#failover-ips) for this purpose. If you want to create a bridged network for your virtual machines, you will also need to configure [Virtual MAC addresses](/dedibox-ip-failover/concepts/#virtual-mac-address). \ No newline at end of file diff --git a/dedibox-network/ip-failover/how-to/assign-failover-ip.mdx b/dedibox-network/ip-failover/how-to/assign-failover-ip.mdx index cfcae73674..8349b50962 100644 --- a/dedibox-network/ip-failover/how-to/assign-failover-ip.mdx +++ b/dedibox-network/ip-failover/how-to/assign-failover-ip.mdx @@ -22,7 +22,7 @@ For each server, you can add failover IP addresses according to the offer and yo - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server diff --git a/dedibox-network/ip-failover/how-to/configure-centos.mdx b/dedibox-network/ip-failover/how-to/configure-centos.mdx index 11035c8144..d88f68e57e 100644 --- a/dedibox-network/ip-failover/how-to/configure-centos.mdx +++ b/dedibox-network/ip-failover/how-to/configure-centos.mdx @@ -13,12 +13,12 @@ categories: - dedibox-network --- -This page shows you how to configure a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) on Dedibox servers running on CentOS. +This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on CentOS. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server ## Failover IP configuration using the Network Manager diff --git a/dedibox-network/ip-failover/how-to/configure-debian-ubuntu.mdx b/dedibox-network/ip-failover/how-to/configure-debian-ubuntu.mdx index 7ae65867f2..f528688b98 100644 --- a/dedibox-network/ip-failover/how-to/configure-debian-ubuntu.mdx +++ b/dedibox-network/ip-failover/how-to/configure-debian-ubuntu.mdx @@ -13,17 +13,17 @@ categories: - dedibox-network --- -This page shows you how to configure a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) on Dedibox servers running on Debian or Ubuntu Linux. +This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on Debian or Ubuntu Linux. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server ## Failover IP configuration on Debian - If you are using Ubuntu 18.04 or later, you should configure the interfaces using [Netplan](/dedibox-network/network/how-to/configure-network-netplan/). + If you are using Ubuntu 18.04 or later, you should configure the interfaces using [Netplan](/dedibox-network/how-to/configure-network-netplan/). 1. Connect to your server using SSH. @@ -85,7 +85,7 @@ It is a YAML-based configuration system, which simplifies the configuration proc nameservers: addresses: - 51.159.47.28 - - 51.159.47.26 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + - 51.159.47.26 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) search: [] version: 2 ``` diff --git a/dedibox-network/ip-failover/how-to/configure-freebsd.mdx b/dedibox-network/ip-failover/how-to/configure-freebsd.mdx index eadb5f47fc..ea7c0c6c42 100644 --- a/dedibox-network/ip-failover/how-to/configure-freebsd.mdx +++ b/dedibox-network/ip-failover/how-to/configure-freebsd.mdx @@ -13,12 +13,12 @@ categories: - dedibox-network --- -This page shows you how to configure a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) on Dedibox servers running on FreeBSD. +This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on FreeBSD. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server ## Failover IP configuration on FreeBSD diff --git a/dedibox-network/ip-failover/how-to/configure-multiip-virtualmac.mdx b/dedibox-network/ip-failover/how-to/configure-multiip-virtualmac.mdx index 77822374b6..c5adc1bb5a 100644 --- a/dedibox-network/ip-failover/how-to/configure-multiip-virtualmac.mdx +++ b/dedibox-network/ip-failover/how-to/configure-multiip-virtualmac.mdx @@ -15,16 +15,16 @@ categories: You can use the same virtual MAC at several failover IPs pointing on the same dedicated server. -To do this, you need to have several [failover IPs](/dedibox-network/ip-failover/concepts/#failover-ips) at the same server and at least one [virtual MAC](/dedibox-network/ip-failover/concepts/#virtual-mac-address) associated with one of these failover IPs. +To do this, you need to have several [failover IPs](/dedibox-ip-failover/concepts/#failover-ips) at the same server and at least one [virtual MAC](/dedibox-ip-failover/concepts/#virtual-mac-address) associated with one of these failover IPs. As long as they share the same virtual MAC, your failover IPs must be moved in a group from one server to another. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server -- At least 2 [failover IPs](/dedibox-network/ip-failover/concepts/#failover-ips) -- Generated a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server +- At least 2 [failover IPs](/dedibox-ip-failover/concepts/#failover-ips) +- Generated a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) 1. Click **Server** > **Server list** to display a list of your physical machines. 2. Select the server you want to configure and click **Manage**. The servers' status page displays. diff --git a/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx b/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx index 550b08c1a5..a97bfc4f22 100644 --- a/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx +++ b/dedibox-network/ip-failover/how-to/configure-network-virtual-machine.mdx @@ -26,9 +26,9 @@ To communicate on the internet, each of your virtual machines needs an IP addres - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server and installed a hypervisor on it -- Ordered a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) -- Generated a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox dedicated server and installed a hypervisor on it +- Ordered a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) +- Generated a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) Find below examples of network interface configurations on different distributions inside a virtual machine: @@ -48,7 +48,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for addresses: - [ "fail.over.ip.address/32" ] nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) routes: - to: default via: 62.210.0.1 @@ -89,7 +89,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for nameserver 51.159.47.26 ``` - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) 6. Activate the network on your virtual machine by running: ``` @@ -114,7 +114,7 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for NETMASK=255.255.255.255 IPADDR=fail.over.ip.address GATEWAY=62.210.0.1 - DNS1=51.159.47.28 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + DNS1=51.159.47.28 # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) DNS2=51.159.47.26 ARP=yes HWADDR=virtual:mac:address @@ -141,5 +141,5 @@ Since the release of version 18.04 (Bionic Beaver), Ubuntu has used Netplan for * DNS 2: `51.159.47.26` - Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performance. [Check the IPs for each data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) \ No newline at end of file diff --git a/dedibox-network/ip-failover/how-to/configure-reverse-dns.mdx b/dedibox-network/ip-failover/how-to/configure-reverse-dns.mdx index 6f78e14742..df15d2a2d2 100644 --- a/dedibox-network/ip-failover/how-to/configure-reverse-dns.mdx +++ b/dedibox-network/ip-failover/how-to/configure-reverse-dns.mdx @@ -31,7 +31,7 @@ You can add a failover IP address(es) for each server according to the offer and - Make sure to have a valid **[A record](/dedibox-network/dns/concepts/#dns-record)** for forwarding DNS configured and pointing to your IP address before changing the reverse DNS of it. + Make sure to have a valid **[A record](/dedibox-dns/concepts/#dns-record)** for forwarding DNS configured and pointing to your IP address before changing the reverse DNS of it. diff --git a/dedibox-network/ip-failover/how-to/configure-windows.mdx b/dedibox-network/ip-failover/how-to/configure-windows.mdx index af1bb31a73..b454f3a644 100644 --- a/dedibox-network/ip-failover/how-to/configure-windows.mdx +++ b/dedibox-network/ip-failover/how-to/configure-windows.mdx @@ -13,7 +13,7 @@ categories: - dedibox-network --- -This page shows you how to configure a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) on Dedibox servers running on Windows Server 2019. +This page shows you how to configure a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) on Dedibox servers running on Windows Server 2019. diff --git a/dedibox-network/ip-failover/how-to/create-virtual-mac.mdx b/dedibox-network/ip-failover/how-to/create-virtual-mac.mdx index 0fd0593929..5eda8824b0 100644 --- a/dedibox-network/ip-failover/how-to/create-virtual-mac.mdx +++ b/dedibox-network/ip-failover/how-to/create-virtual-mac.mdx @@ -19,7 +19,7 @@ Virtualization requires, in most cases, that you configure additional IP address - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -- Ordered a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) +- Ordered a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) diff --git a/dedibox-network/ip-failover/how-to/order-failover-ip.mdx b/dedibox-network/ip-failover/how-to/order-failover-ip.mdx index de6b6e20d6..94c4ff9d4e 100644 --- a/dedibox-network/ip-failover/how-to/order-failover-ip.mdx +++ b/dedibox-network/ip-failover/how-to/order-failover-ip.mdx @@ -39,4 +39,4 @@ By switching a failover IP addresses from one server to another, your hosted ser Failover IPs and failover IP blocks are paid options. They come with a **monthly** service charge and a **one-time** setup fee. -The failover IP is now available in your account, and you can [assign it to your Dedibox server](/dedibox-network/ip-failover/how-to/assign-failover-ip/). \ No newline at end of file +The failover IP is now available in your account, and you can [assign it to your Dedibox server](/dedibox-ip-failover/how-to/assign-failover-ip/). \ No newline at end of file diff --git a/dedibox-network/ip-failover/index.mdx b/dedibox-network/ip-failover/index.mdx index 007a5d1e41..69e4f13b58 100644 --- a/dedibox-network/ip-failover/index.mdx +++ b/dedibox-network/ip-failover/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox - Failover IP" productLogo="dedibox" description="Failover IPs are IP addresses that you can order and move from one server to another (even across data centers), without changing your whole configuration." - url="/dedibox-network/ip-failover/quickstart" + url="/dedibox-ip-failover/quickstart" label="Failover IP Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to create, and manage a Dedibox failover IP in a few steps." label="View Quickstart" - url="/dedibox-network/ip-failover/quickstart/" + url="/dedibox-ip-failover/quickstart/" /> diff --git a/dedibox-network/ip-failover/quickstart.mdx b/dedibox-network/ip-failover/quickstart.mdx index acac39591e..eaf67f3c01 100644 --- a/dedibox-network/ip-failover/quickstart.mdx +++ b/dedibox-network/ip-failover/quickstart.mdx @@ -39,8 +39,8 @@ Failover IPs are IP addresses you can order and move from one server to another We provide a series of dedicated how-to's about the configuration of failover IPs on your Dedibox server: -* [How to configure a failover IP on CentOS](/dedibox-network/ip-failover/how-to/configure-centos/) -* [How to configure a failover IP on Debian/Ubuntu](/dedibox-network/ip-failover/how-to/configure-debian-ubuntu/) -* [How to configure a failover IP on FreeBSD](/dedibox-network/ip-failover/how-to/configure-freebsd/) -* [How to configure a failover IP on Windows Server](/dedibox-network/ip-failover/how-to/configure-windows/) -* [How to configure the network of a virtual machine](/dedibox-network/ip-failover/how-to/configure-network-virtual-machine/). \ No newline at end of file +* [How to configure a failover IP on CentOS](/dedibox-ip-failover/how-to/configure-centos/) +* [How to configure a failover IP on Debian/Ubuntu](/dedibox-ip-failover/how-to/configure-debian-ubuntu/) +* [How to configure a failover IP on FreeBSD](/dedibox-ip-failover/how-to/configure-freebsd/) +* [How to configure a failover IP on Windows Server](/dedibox-ip-failover/how-to/configure-windows/) +* [How to configure the network of a virtual machine](/dedibox-ip-failover/how-to/configure-network-virtual-machine/). \ No newline at end of file diff --git a/dedibox-network/ipv6/concepts.mdx b/dedibox-network/ipv6/concepts.mdx index 15a63d037e..2bca16045f 100644 --- a/dedibox-network/ipv6/concepts.mdx +++ b/dedibox-network/ipv6/concepts.mdx @@ -34,7 +34,7 @@ An **I**nternet **P**rotocol address is a unique address that identifies a devic ## IPv6 -**I**nternet **P**rotocol **V**ersion **6** is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. Alternatively, `2001:DB8::3:0:1FF:0:2E`. Dedibox network is wholly IPv6 compatible. IPv6 can be used as the main IP of your server, and also as an [IP failover](/dedibox-network/ip-failover/concepts/#failover-ips) using the principle of [virtual MAC](/dedibox-network/ip-failover/concepts/#virtual-mac-address). +**I**nternet **P**rotocol **V**ersion **6** is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. Alternatively, `2001:DB8::3:0:1FF:0:2E`. Dedibox network is wholly IPv6 compatible. IPv6 can be used as the main IP of your server, and also as an [IP failover](/dedibox-ip-failover/concepts/#failover-ips) using the principle of [virtual MAC](/dedibox-ip-failover/concepts/#virtual-mac-address). ## Neighbor Discovery Protocol @@ -42,12 +42,12 @@ The Neighbour Discovery Protocol (NDP) allows devices to discover neighbors, rou ## SLAAC -**S**tateless **A**uto **A**ddress **C**onfiguration is the simplest way to assign IP addresses in an IPv6 network. Using the [Neighbor Discovery Protocol](/dedibox-network/ipv6/concepts/#neighbor-discovery-protocol), devices request the network prefix from the router, and then use this prefix and their own MAC address to create an IPv6 address. +**S**tateless **A**uto **A**ddress **C**onfiguration is the simplest way to assign IP addresses in an IPv6 network. Using the [Neighbor Discovery Protocol](/dedibox-ipv6/concepts/#neighbor-discovery-protocol), devices request the network prefix from the router, and then use this prefix and their own MAC address to create an IPv6 address. ## Stateful DHCPv6 -With [stateful DHCPv6](/dedibox-network/ipv6/concepts/#stateful-dhcpv6), it is the DHCPv6 server that chooses and assigns IPv6 addresses to clients, unlike with [SLAAC](/dedibox-network/ipv6/concepts/#slaac) or [Stateless DHCPv6](/dedibox-network/ipv6/concepts/#stateless-dhcpv6) where the client creates their own IPv6 address. Stateful DHCPv6 is so-called because the DHCPv6 server keeps track of the state of IPv6 addresses on the network. +With [stateful DHCPv6](/dedibox-ipv6/concepts/#stateful-dhcpv6), it is the DHCPv6 server that chooses and assigns IPv6 addresses to clients, unlike with [SLAAC](/dedibox-ipv6/concepts/#slaac) or [Stateless DHCPv6](/dedibox-ipv6/concepts/#stateless-dhcpv6) where the client creates their own IPv6 address. Stateful DHCPv6 is so-called because the DHCPv6 server keeps track of the state of IPv6 addresses on the network. ## Stateless DHCPv6 -[Stateless DHCPv6](/dedibox-network/ipv6/concepts/#stateless-dhcpv6) involves the initial use of [SLAAC](/dedibox-network/ipv6/concepts/#slaac) by a client to create its own IPv6 address, followed by an extra DHCPv6 request to get extra details from the DHCPv6 server, such as DNS server or domain name information. Stateful DHCPv6 is so-called because no server or client is keeping track of the overall state of IPv6 addresses on the network. \ No newline at end of file +[Stateless DHCPv6](/dedibox-ipv6/concepts/#stateless-dhcpv6) involves the initial use of [SLAAC](/dedibox-ipv6/concepts/#slaac) by a client to create its own IPv6 address, followed by an extra DHCPv6 request to get extra details from the DHCPv6 server, such as DNS server or domain name information. Stateful DHCPv6 is so-called because no server or client is keeping track of the overall state of IPv6 addresses on the network. \ No newline at end of file diff --git a/dedibox-network/ipv6/how-to/configure-ipv6-linux.mdx b/dedibox-network/ipv6/how-to/configure-ipv6-linux.mdx index 1836de8483..391b92dd73 100644 --- a/dedibox-network/ipv6/how-to/configure-ipv6-linux.mdx +++ b/dedibox-network/ipv6/how-to/configure-ipv6-linux.mdx @@ -17,7 +17,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -- [Requested](/dedibox-network/ipv6/how-to/request-prefix/) a /48 IPv6 prefix +- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix Follow the IPv6 on Ubuntu configuration if you are on Ubuntu and use Netplan as your default network manager. @@ -45,7 +45,7 @@ It replaces the classical network configuration with new configuration files, wr - "2001:bc8:xxxx:xxx::x/64" # An IP address from your IPv6 block and its subnet mask /64, replace placeholder values gateway4: aaa.bbb.ccc.1 # The gateway is the IPv4 address of your Dedibox, ending on .1 nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) routes: - to: 0.0.0.0 via: aaa.bbb.ccc.1 @@ -55,7 +55,7 @@ It replaces the classical network configuration with new configuration files, wr Remember to replace `enp1s0` with the proper name of your internet interface. - The configuration example above is valid for the main IP address of your Dedibox server. If you want to use IPv6 on a [virtual machine](/dedibox-network/network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), remember to use the unique gateway for the failover IPv4. + The configuration example above is valid for the main IP address of your Dedibox server. If you want to use IPv6 on a [virtual machine](/dedibox-network/how-to/configure-network-netplan/#configuring-a-failover-ip-for-virtual-machines), remember to use the unique gateway for the failover IPv4. 2. Check and validate your configuration file. ``` diff --git a/dedibox-network/ipv6/how-to/configure-ipv6-windows.mdx b/dedibox-network/ipv6/how-to/configure-ipv6-windows.mdx index 06626236af..19c1b1608f 100644 --- a/dedibox-network/ipv6/how-to/configure-ipv6-windows.mdx +++ b/dedibox-network/ipv6/how-to/configure-ipv6-windows.mdx @@ -17,10 +17,10 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -- [Requested](/dedibox-network/ipv6/how-to/request-prefix/) a /48 IPv6 prefix +- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix - * On servers supporting [IPv6 SLAAC](/dedibox-network/ipv6/how-to/enable-ipv6-slaac/), SLAAC has to be enabled in order to ensure that DHCPv6 works correctly. + * On servers supporting [IPv6 SLAAC](/dedibox-ipv6/how-to/enable-ipv6-slaac/), SLAAC has to be enabled in order to ensure that DHCPv6 works correctly. * This documentation addresses the setup of a /48 IPv6 network on your Dedibox. If you intend to use only the SLAAC IP address, no additional configuration is necessary, and your machine can acquire its IP address automatically. diff --git a/dedibox-network/ipv6/how-to/create-subnet.mdx b/dedibox-network/ipv6/how-to/create-subnet.mdx index 08722d8490..a4e0e67092 100644 --- a/dedibox-network/ipv6/how-to/create-subnet.mdx +++ b/dedibox-network/ipv6/how-to/create-subnet.mdx @@ -13,7 +13,7 @@ categories: - dedibox-network --- -You can split your IPv6 prefix into several subnets and use them on your Dedibox servers both in Paris and Amsterdam. Each subnet has its own [DUID](/dedibox-network/ipv6/concepts/#duid) and can be configured individually. +You can split your IPv6 prefix into several subnets and use them on your Dedibox servers both in Paris and Amsterdam. Each subnet has its own [DUID](/dedibox-ipv6/concepts/#duid) and can be configured individually. * You can create as many /56 subnets as you have servers. @@ -24,7 +24,7 @@ You can split your IPv6 prefix into several subnets and use them on your Dedibox - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) -- [Requested](/dedibox-network/ipv6/how-to/request-prefix/) a /48 IPv6 prefix +- [Requested](/dedibox-ipv6/how-to/request-prefix/) a /48 IPv6 prefix 1. Click **Server** > **Network configuration** in the Dedibox console. The network configuration pages displays. Scroll down to the IPv6 network configuration section. 2. Click the settings icon (cogwheel) next to your `/48` prefix. Then click **Create subnet**. diff --git a/dedibox-network/ipv6/how-to/debug-ipv6.mdx b/dedibox-network/ipv6/how-to/debug-ipv6.mdx index cc912dfd32..8a882cc51d 100644 --- a/dedibox-network/ipv6/how-to/debug-ipv6.mdx +++ b/dedibox-network/ipv6/how-to/debug-ipv6.mdx @@ -18,13 +18,13 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) - A [Dedibox dedicated server](https://www.scaleway.com/en/dedibox) - An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/) -- A [requested /48 IPv6 prefix](/dedibox-network/ipv6/how-to/request-prefix/) -- Configured the `systemd-networkd` [DHCPv6 client](/dedibox-network/ipv6/how-to/configure-ipv6-linux/) +- A [requested /48 IPv6 prefix](/dedibox-ipv6/how-to/request-prefix/) +- Configured the `systemd-networkd` [DHCPv6 client](/dedibox-ipv6/how-to/configure-ipv6-linux/) ## How to debug IPv6 connection issues from rescue mode -If you experience IPv6 connection issues, you can test the network connectivity from [rescue mode](/dedibox/dedicated-servers/how-to/use-rescue-mode/). +If you experience IPv6 connection issues, you can test the network connectivity from [rescue mode](/dedicated-servers/how-to/use-rescue-mode/). To test IPv6 connectivity on your server in rescue mode, reboot the server into "Ubuntu rescue" mode. The `dhclient` is preinstalled in these images. diff --git a/dedibox-network/ipv6/index.mdx b/dedibox-network/ipv6/index.mdx index 22ee7c8df0..396d983308 100644 --- a/dedibox-network/ipv6/index.mdx +++ b/dedibox-network/ipv6/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox - IPv6" productLogo="dedibox" description="IPv6s is supported on all Scaleway Dedibox dedicated servers. You can request a free /48 IPv6 prefix for your account." - url="/dedibox-network/ipv6/quickstart" + url="/dedibox-ipv6/quickstart" label="IPv6 Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to create, and manage a IPv6 in a few steps." label="View Quickstart" - url="/dedibox-network/ipv6/quickstart/" + url="/dedibox-ipv6/quickstart/" /> diff --git a/dedibox-network/ipv6/quickstart.mdx b/dedibox-network/ipv6/quickstart.mdx index eaaf1b3014..3eadf6f1cf 100644 --- a/dedibox-network/ipv6/quickstart.mdx +++ b/dedibox-network/ipv6/quickstart.mdx @@ -13,7 +13,7 @@ categories: - dedibox-network --- -IPv6 stands as the latest iteration of the Internet Protocol (IP) used to allocate addresses across the web. Each IPv6 address is composed of 128 bits. When expressed in a human-friendly format, an IPv6 address takes the form of eight sets of four hexadecimal digits, with each set accounting for 16 bits. These sets are separated by colons, such as in `2001:0DB8:0000:0003:0000:01FF:0000:002E`. An alternate representation could be `2001:DB8::3:0:1FF:0:2E`. The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server's primary IP and also as a [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) utilizing the concept of a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address). +IPv6 stands as the latest iteration of the Internet Protocol (IP) used to allocate addresses across the web. Each IPv6 address is composed of 128 bits. When expressed in a human-friendly format, an IPv6 address takes the form of eight sets of four hexadecimal digits, with each set accounting for 16 bits. These sets are separated by colons, such as in `2001:0DB8:0000:0003:0000:01FF:0000:002E`. An alternate representation could be `2001:DB8::3:0:1FF:0:2E`. The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server's primary IP and also as a [failover IP](/dedibox-ip-failover/concepts/#failover-ips) utilizing the concept of a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address). @@ -100,5 +100,5 @@ Activation of IPv6 SLAAC assigns **one** `/128` IPv6 subnet to your server (one You can find information regarding the configuration of IPv6 on your Dedibox dedicated server at the following links: -* [How to configure IPv6 on Linux using `systemd-networkd`](/dedibox-network/ipv6/how-to/configure-ipv6-linux/) -* [How to configure IPv6 on Windows Server](/dedibox-network/ipv6/how-to/configure-ipv6-windows/) \ No newline at end of file +* [How to configure IPv6 on Linux using `systemd-networkd`](/dedibox-ipv6/how-to/configure-ipv6-linux/) +* [How to configure IPv6 on Windows Server](/dedibox-ipv6/how-to/configure-ipv6-windows/) \ No newline at end of file diff --git a/dedibox-network/network/how-to/configure-network-netplan.mdx b/dedibox-network/network/how-to/configure-network-netplan.mdx index 0990ef2299..2f393f99c7 100644 --- a/dedibox-network/network/how-to/configure-network-netplan.mdx +++ b/dedibox-network/network/how-to/configure-network-netplan.mdx @@ -18,7 +18,7 @@ Since the release of its version 18.04, Bionic Beaver, [Ubuntu](http://www.ubunt - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server ## Configuration files @@ -73,7 +73,7 @@ network: ``` - Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. + Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. Once you have edited and saved the file, you can reload the configuration with the following command: @@ -93,7 +93,7 @@ When configuring a failover IP in a virtual machine, you must specify which rout addresses: - [ "fail.over.ip.address/32" ] nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers/) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers/) routes: - to: default via: 62.210.0.1 @@ -104,5 +104,5 @@ When configuring a failover IP in a virtual machine, you must specify which rout ``` - Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/console/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. + Replace the DNS cache servers in the example above (`51.159.47.28` and `51.159.47.26`) with the nameservers [available in the same data center](/account/reference-content/scaleway-network-information/#dns-cache-servers) as your server for optimal latency. \ No newline at end of file diff --git a/dedibox-network/network/how-to/subscribe-to-jmrp.mdx b/dedibox-network/network/how-to/subscribe-to-jmrp.mdx index 0e52310e76..002e243acb 100644 --- a/dedibox-network/network/how-to/subscribe-to-jmrp.mdx +++ b/dedibox-network/network/how-to/subscribe-to-jmrp.mdx @@ -15,15 +15,15 @@ categories: Subscribing to the Junk Mail Reporting Program (JMRP) allows you to register your IP addresses with Microsoft's mail delivery system. This registration helps you proactively manage your IP reputation by enabling you to take appropriate actions if your IP is flagged as a source of spam, thus reducing the risk of blacklisting. -By default, the IP owner’s information (e.g., Scaleway/Online.net) is used to identify the association of an email address with a specific IP. However, if you have [properly configured the reverse DNS for your IP](/dedibox-network/ip-failover/how-to/configure-reverse-dns/), you can use an email address from your own domain for these notifications. +By default, the IP owner’s information (e.g., Scaleway/Online.net) is used to identify the association of an email address with a specific IP. However, if you have [properly configured the reverse DNS for your IP](/dedibox-ip-failover/how-to/configure-reverse-dns/), you can use an email address from your own domain for these notifications. Following these steps will help you maintain a clean email delivery system and protect your IP reputation. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server -- [Configured the reverse DNS of your IP](/dedibox-network/ip-failover/how-to/configure-reverse-dns/) +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Configured the reverse DNS of your IP](/dedibox-ip-failover/how-to/configure-reverse-dns/) - [Created](https://signup.live.com/signup) a Microsoft account 1. Open the [JMRP website](https://sendersupport.olc.protection.outlook.com/snds/JMRP.aspx) in your web browser. diff --git a/dedibox-network/network/index.mdx b/dedibox-network/network/index.mdx index 4748005577..6e6e468a0a 100644 --- a/dedibox-network/network/index.mdx +++ b/dedibox-network/network/index.mdx @@ -20,14 +20,14 @@ meta: icon="help-circle-outline" description="Check our guides helping you to configure the network of your Dedibox dedicated server." label="View How-tos" - url="/dedibox-network/network/how-to/" + url="/dedibox-network/how-to/" /> diff --git a/dedibox-network/rpn/how-to/configure-rpnv2.mdx b/dedibox-network/rpn/how-to/configure-rpnv2.mdx index 13de233cfd..47767ad92b 100644 --- a/dedibox-network/rpn/how-to/configure-rpnv2.mdx +++ b/dedibox-network/rpn/how-to/configure-rpnv2.mdx @@ -13,7 +13,7 @@ categories: - dedibox-network --- -[RPNv2](/dedibox-network/rpn/concepts/#rpn-v2) can be configured on any operating system supporting VLANs. The feature is available for selected Dedibox servers. +[RPNv2](/dedibox-rpn/concepts/#rpn-v2) can be configured on any operating system supporting VLANs. The feature is available for selected Dedibox servers. ## How to configure RPNv2 on Debian diff --git a/dedibox-network/rpn/how-to/connect-rpn-san-windows.mdx b/dedibox-network/rpn/how-to/connect-rpn-san-windows.mdx index a44ad3e6be..257ae7390b 100644 --- a/dedibox-network/rpn/how-to/connect-rpn-san-windows.mdx +++ b/dedibox-network/rpn/how-to/connect-rpn-san-windows.mdx @@ -13,7 +13,7 @@ categories: - dedibox-network --- -The [RPN SAN](/dedibox-network/rpn/concepts/#rpn-san) is an iSCSI target, it is possible to mount it in Windows Server 2012 or later to use it as a normal disk in the system. +The [RPN SAN](/dedibox-rpn/concepts/#rpn-san) is an iSCSI target, it is possible to mount it in Windows Server 2012 or later to use it as a normal disk in the system. diff --git a/dedibox-network/rpn/how-to/connect-rpn-san.mdx b/dedibox-network/rpn/how-to/connect-rpn-san.mdx index 375fa8ecdb..b6abdfd2d1 100644 --- a/dedibox-network/rpn/how-to/connect-rpn-san.mdx +++ b/dedibox-network/rpn/how-to/connect-rpn-san.mdx @@ -22,7 +22,7 @@ categories: - An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/) - - RPN SAN does not support RPNv2. To use RPNv2, you either need a server with an RPNv1 connection **or** to [enable the RPNv1 gateway](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/). + - RPN SAN does not support RPNv2. To use RPNv2, you either need a server with an RPNv1 connection **or** to [enable the RPNv1 gateway](/dedibox-rpn/how-to/configure-rpnv1-gateway/). - You must authorize the server(s) to connect to your RPN SAN. @@ -37,7 +37,7 @@ categories: The allowed server(s) are listed on the SAN overview page. - Some SAN endpoints may not be reachable directly from the RPNv2, and it is required to configure an [RPNv1 gateway](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/) to use them with RPNv2. + Some SAN endpoints may not be reachable directly from the RPNv2, and it is required to configure an [RPNv1 gateway](/dedibox-rpn/how-to/configure-rpnv1-gateway/) to use them with RPNv2. ## How to add a SAN to an RPN group diff --git a/dedibox-network/rpn/how-to/use-rpn-san-esxi-v7.mdx b/dedibox-network/rpn/how-to/use-rpn-san-esxi-v7.mdx index cbf2c5c92b..ef238e5271 100644 --- a/dedibox-network/rpn/how-to/use-rpn-san-esxi-v7.mdx +++ b/dedibox-network/rpn/how-to/use-rpn-san-esxi-v7.mdx @@ -25,7 +25,7 @@ We suggest considering alternative hypervisors such as Proxmox. You can learn ho - An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/) - This documentation covers **VMware ESXi version 7** and later. Follow [this link](/dedibox-network/rpn/how-to/use-rpn-san-esxi/) to see the documentation for ESXi 5.0/5.1/5.5 and 6.0. + This documentation covers **VMware ESXi version 7** and later. Follow [this link](/dedibox-rpn/how-to/use-rpn-san-esxi/) to see the documentation for ESXi 5.0/5.1/5.5 and 6.0. ## How to configure VMware ESXi to use RPN @@ -74,7 +74,7 @@ We suggest considering alternative hypervisors such as Proxmox. You can learn ho ``` vi vmknics.json ``` -9. Replace the MAC address of your RPN VMkernel NIC with your [virtual MAC](/dedibox-network/ip-failover/how-to/create-virtual-mac/). +9. Replace the MAC address of your RPN VMkernel NIC with your [virtual MAC](/dedibox-ip-failover/how-to/create-virtual-mac/). 10. Import the new configuration: ``` @@ -92,7 +92,7 @@ We suggest considering alternative hypervisors such as Proxmox. You can learn ho ``` - You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-network/rpn/how-to/find-rpn-gateway/). + You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-rpn/how-to/find-rpn-gateway/). 4. Ping the RPN-SAN to check if the RPN connection is working properly: ``` @@ -112,7 +112,7 @@ To be able to communicate with the RPN-SAN, you need to allow your servers to ac 2. Select the SAN you want to configure and click **Manage**. 3. Add the server(s) you want to access your SAN services to the list. Optionally you can add RPN subnet IPs. - If you use RPNv2, an [additional configuration](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. + If you use RPNv2, an [additional configuration](/dedibox-rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. diff --git a/dedibox-network/rpn/how-to/use-rpn-san-esxi.mdx b/dedibox-network/rpn/how-to/use-rpn-san-esxi.mdx index 15ab185c06..e1dd7e5b02 100644 --- a/dedibox-network/rpn/how-to/use-rpn-san-esxi.mdx +++ b/dedibox-network/rpn/how-to/use-rpn-san-esxi.mdx @@ -25,7 +25,7 @@ We suggest considering alternative hypervisors such as Proxmox. You can learn ho - An [RPN SAN](https://www.scaleway.com/en/dedibox/storage/) - This documentation covers **VMware ESXi version ESXi 5.0/5.1/5.5 and 6.0** and later. Follow [this link](/dedibox-network/rpn/how-to/use-rpn-san-esxi-v7/) to see the Documentation for ESXi 7 and later. + This documentation covers **VMware ESXi version ESXi 5.0/5.1/5.5 and 6.0** and later. Follow [this link](/dedibox-rpn/how-to/use-rpn-san-esxi-v7/) to see the Documentation for ESXi 7 and later. ## How to configure VMware ESXi to use RPN diff --git a/dedibox-network/rpn/how-to/use-rpn-vpn.mdx b/dedibox-network/rpn/how-to/use-rpn-vpn.mdx index cd034ae8bd..1b3f8a1134 100644 --- a/dedibox-network/rpn/how-to/use-rpn-vpn.mdx +++ b/dedibox-network/rpn/how-to/use-rpn-vpn.mdx @@ -42,7 +42,7 @@ The RPN VPN service allows you to: - To use your RPN VPN in your RPNv1 group, you must add it to your group as an RPN server. For more information, follow our [RPN documentation](/dedibox-network/rpn/quickstart/). + To use your RPN VPN in your RPNv1 group, you must add it to your group as an RPN server. For more information, follow our [RPN documentation](/dedibox-rpn/quickstart/). ## How to configure the RPN VPN client @@ -117,6 +117,6 @@ The RPN VPN service allows you to: 10.90.250.26 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 ``` - Now you can [configure your server](/dedibox-network/rpn/quickstart/) in your RPN group. + Now you can [configure your server](/dedibox-rpn/quickstart/) in your RPN group. diff --git a/dedibox-network/rpn/index.mdx b/dedibox-network/rpn/index.mdx index 541f06923a..e5dab6dccb 100644 --- a/dedibox-network/rpn/index.mdx +++ b/dedibox-network/rpn/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox - RPN" productLogo="dedibox" description="RPN (Real Private Network) is a dedicated private network connected to the second network interface of a Dedibox server." - url="/dedibox-network/rpn/quickstart" + url="/dedibox-rpn/quickstart" label="RPN Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to create, configure, and manage a RPN connection in a few steps." label="View Quickstart" - url="/dedibox-network/rpn/quickstart/" + url="/dedibox-rpn/quickstart/" /> diff --git a/dedibox-network/rpn/quickstart.mdx b/dedibox-network/rpn/quickstart.mdx index 15c2fd60a4..4263deb039 100644 --- a/dedibox-network/rpn/quickstart.mdx +++ b/dedibox-network/rpn/quickstart.mdx @@ -30,14 +30,14 @@ Furthermore, RPN v2 facilitates the configuration of robust security measures to 1. Click on **RPN** > **RPN groups** in the menu on top of the console. Then click **Local RPNv2 groups** in the menu on the left. The RPNv2 groups page displays. 2. Click **Add group**. The add RPNv2 groups form displays. -3. Select the type of the group. It can either be **Standard** or **[Q-in-Q](/dedibox-network/rpn/concepts/#q-in-q-mode)**. Then enter the name of the group and select the servers to add to the group. Click **Submit** to confirm. +3. Select the type of the group. It can either be **Standard** or **[Q-in-Q](/dedibox-rpn/concepts/#q-in-q-mode)**. Then enter the name of the group and select the servers to add to the group. Click **Submit** to confirm. A VLAN ID is assigned automatically during the group creation. It is possible to modify the VLAN ID with values between 1 and 3967. ## How to configure the RPN interface -Below you find configuration instructions for the most common operating systems. For more information, refer to our how-to about [RPNv2 interface configuration](/dedibox-network/rpn/how-to/configure-rpnv2/). +Below you find configuration instructions for the most common operating systems. For more information, refer to our how-to about [RPNv2 interface configuration](/dedibox-rpn/how-to/configure-rpnv2/). ### How to configure RPNv2 on Debian @@ -104,7 +104,7 @@ In the following 'how to' we assume your RPN NIC is `eth1`. ## How to configure Jumboframes -The RPN supports Jumboframes with a maximum payload of 9000 bytes. You need to configure your RPN interface to send pacekets with an MTU 9000. For more information, refer to our how-to: [Configuration of Jumboframes](/dedibox-network/rpn/how-to/configure-jumboframes/). +The RPN supports Jumboframes with a maximum payload of 9000 bytes. You need to configure your RPN interface to send pacekets with an MTU 9000. For more information, refer to our how-to: [Configuration of Jumboframes](/dedibox-rpn/how-to/configure-jumboframes/). #### CentOS diff --git a/dedibox-network/rpn/reference-content/private-networks-overview.mdx b/dedibox-network/rpn/reference-content/private-networks-overview.mdx index 7621f518ca..01417fd59f 100644 --- a/dedibox-network/rpn/reference-content/private-networks-overview.mdx +++ b/dedibox-network/rpn/reference-content/private-networks-overview.mdx @@ -65,4 +65,4 @@ For example, a Dedibox server could serve as a load balancer, routing traffic vi ### Conclusion -Scaleway provides a range of options for secure networking between Dedibox servers, Scaleway Instances, or both. Explore our [documentation](/compute/instances/how-to/use-private-networks/) to learn more about Dedibox RPNs, Scaleway Private Networks, and VPN solutions. +Scaleway provides a range of options for secure networking between Dedibox servers, Scaleway Instances, or both. Explore our [documentation](/instances/how-to/use-private-networks/) to learn more about Dedibox RPNs, Scaleway Private Networks, and VPN solutions. diff --git a/dedibox/dedicated-servers/how-to/change-root-password.mdx b/dedibox/dedicated-servers/how-to/change-root-password.mdx index c491fc5bff..eb51ac2bf7 100644 --- a/dedibox/dedicated-servers/how-to/change-root-password.mdx +++ b/dedibox/dedicated-servers/how-to/change-root-password.mdx @@ -13,14 +13,14 @@ categories: - dedibox-servers --- -This document shows you how to change your password using the [rescue system](/dedibox/dedicated-servers/how-to/use-rescue-mode/). If you try to use the usual `passwd` command to change your password, it will only change the password of the rescue system. Your modifications are reset after a reboot. We will show you how to access your real files to change your password. +This document shows you how to change your password using the [rescue system](/dedicated-servers/how-to/use-rescue-mode/). If you try to use the usual `passwd` command to change your password, it will only change the password of the rescue system. Your modifications are reset after a reboot. We will show you how to access your real files to change your password. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server -1. From the console, [launch rescue mode](/dedibox/dedicated-servers/how-to/use-rescue-mode/). +1. From the console, [launch rescue mode](/dedicated-servers/how-to/use-rescue-mode/). 2. Mount your partitions: ``` sudo mountall.sh @@ -35,7 +35,7 @@ This document shows you how to change your password using the [rescue system](/d ``` - - If you [installed your server](/dedibox/dedicated-servers/how-to/install-a-server/) with the default partition layout, the root partition will be mounted on sda2. + - If you [installed your server](/dedicated-servers/how-to/install-a-server/) with the default partition layout, the root partition will be mounted on sda2. - If you configured custom partitioning, your root partition may be mounted elsewhere. 4. Use the following command to change the password: diff --git a/dedibox/dedicated-servers/how-to/change-win-server-language.mdx b/dedibox/dedicated-servers/how-to/change-win-server-language.mdx index 192a3ac1ee..55b81ee940 100644 --- a/dedibox/dedicated-servers/how-to/change-win-server-language.mdx +++ b/dedibox/dedicated-servers/how-to/change-win-server-language.mdx @@ -18,7 +18,7 @@ This guide provides step-by-step instructions to change the display language of - A Dedibox account logged into the [console](https://console.online.net) -- A [Dedibox server](/dedibox/dedicated-servers/how-to/order-a-server/) with Windows Server 2019 [installed](/dedibox/dedicated-servers/how-to/install-a-server/) +- A [Dedibox server](/dedicated-servers/how-to/order-a-server/) with Windows Server 2019 [installed](/dedicated-servers/how-to/install-a-server/) 1. Log in to your Windows Server's graphical interface using Remote Desktop or a similar tool. 2. Open the **Start** menu and click the settings icon to access the **Settings** interface. diff --git a/dedibox/dedicated-servers/how-to/connect-to-server.mdx b/dedibox/dedicated-servers/how-to/connect-to-server.mdx index adfd0a903f..b5653e81bd 100644 --- a/dedibox/dedicated-servers/how-to/connect-to-server.mdx +++ b/dedibox/dedicated-servers/how-to/connect-to-server.mdx @@ -18,8 +18,8 @@ This guide provides instructions on connecting to your Scaleway Dedibox server u - A Dedibox account logged into the [console](https://console.online.net) -- [Created and uploaded your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation +- [Created and uploaded your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation ## Connecting via SSH @@ -73,7 +73,7 @@ If you have installed Windows Server on your Dedibox, follow these steps to conn 4. Click **Connect** and enter the password set during the server installation. 5. Confirm the connection if prompted. -You are now connected to the Windows Server graphical interface. For language settings, refer to the [Windows Server language change guide](/dedibox/dedicated-servers/how-to/change-win-server-language/). +You are now connected to the Windows Server graphical interface. For language settings, refer to the [Windows Server language change guide](/dedicated-servers/how-to/change-win-server-language/). ## Transferring data to your server diff --git a/dedibox/dedicated-servers/how-to/get-started-with-server.mdx b/dedibox/dedicated-servers/how-to/get-started-with-server.mdx index ce0b9161a0..27994774d5 100644 --- a/dedibox/dedicated-servers/how-to/get-started-with-server.mdx +++ b/dedibox/dedicated-servers/how-to/get-started-with-server.mdx @@ -18,7 +18,7 @@ Once you have set up your Dedibox server, installed an operating system, and con - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server ## Using the shell @@ -28,17 +28,17 @@ Dedibox servers do not come with a graphical interface by default. Instead, all - Create, edit, and delete files and directories - Configure server settings -You can [connect to the shell via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). For essential commands, refer to our [basic Linux commands guide](/dedibox/dedicated-servers/reference-content/basic-linux-commands/). +You can [connect to the shell via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). For essential commands, refer to our [basic Linux commands guide](/dedicated-servers/reference-content/basic-linux-commands/). ## Using a graphical desktop -If you prefer a graphical interface, you can install a desktop-oriented distribution and connect using the X2Go Client. For more information, refer to our [guide on connecting via Windows Remote Desktop](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-remote-desktop). +If you prefer a graphical interface, you can install a desktop-oriented distribution and connect using the X2Go Client. For more information, refer to our [guide on connecting via Windows Remote Desktop](/dedicated-servers/how-to/connect-to-server/#connecting-via-remote-desktop). ## Installing software on Linux OSes After setting up your Dedibox, only the operating system and an SSH server are installed. To add software, use a package manager specific to your distribution: -- **Debian/Ubuntu**: Use the APT package manager. See our guide on [getting started with APT](/dedibox/dedicated-servers/how-to/manage-packages/). +- **Debian/Ubuntu**: Use the APT package manager. See our guide on [getting started with APT](/dedicated-servers/how-to/manage-packages/). - **CentOS/RHEL**: Use [DNF](https://dnf.readthedocs.io/en/latest/) (previously YUM for CentOS 7 and older). - **SuSE Linux**: Use [YAST](https://documentation.suse.com/sles/15-SP2/html/SLES-all/cha-yast-software.html). diff --git a/dedibox/dedicated-servers/how-to/install-a-server.mdx b/dedibox/dedicated-servers/how-to/install-a-server.mdx index 806d376355..fff7bb7cd4 100644 --- a/dedibox/dedicated-servers/how-to/install-a-server.mdx +++ b/dedibox/dedicated-servers/how-to/install-a-server.mdx @@ -18,20 +18,20 @@ After your Scaleway Dedibox server has been delivered, you can proceed with the - A Dedibox account logged into the [console](https://console.online.net) -- A [Dedibox server](/dedibox/dedicated-servers/how-to/order-a-server/) +- A [Dedibox server](/dedicated-servers/how-to/order-a-server/) 1. In the [Dedibox console](https://console.online.net/), navigate to **Server** > **Server list** in the top menu. A list of your servers will be displayed. 2. Click **Manage** next to the server you want to install. The server installation wizard will appear. 3. Select the operating system type to be installed. - For detailed information about OS types, refer to the [dedicated servers concepts page](/dedibox/dedicated-servers/concepts/#os-type). + For detailed information about OS types, refer to the [dedicated servers concepts page](/dedicated-servers/concepts/#os-type). - If you prefer to complete the installation using [KVM Over IP](/dedibox/kvm-over-ip/), click **Install over KVM** on this page. + If you prefer to complete the installation using [KVM Over IP](/dedibox-kvm-over-ip/), click **Install over KVM** on this page. 4. Choose the specific operating system and version you wish to install, then click **Install**. -5. Customize the [partitioning](/dedibox/dedicated-servers/concepts/#partitioning) configuration: +5. Customize the [partitioning](/dedicated-servers/concepts/#partitioning) configuration: - Select the **File system**, **RAID level**, and specify the **mount point** and **partition size** in MB. - If the server has two disks, you can choose between **RAID 0**, **RAID 1**, or **No RAID**. For servers with more than two disks, **RAID 5** is also available. Configure the RAID and partitioning according to your needs. Ensure identical partitioning across all disks in a software RAID setup. @@ -52,7 +52,7 @@ After your Scaleway Dedibox server has been delivered, you can proceed with the 8. Configure the system parameters, such as server name, username, password, SSH key, monitoring alerts, and updates. - To connect via SSH, we recommend [creating and uploading your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) at this stage for transfer during installation. + To connect via SSH, we recommend [creating and uploading your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage for transfer during installation. 9. Verify all details on the installation summary tab. Once installation is complete, your server will automatically reboot from its hard disk. diff --git a/dedibox/dedicated-servers/how-to/manage-packages.mdx b/dedibox/dedicated-servers/how-to/manage-packages.mdx index bad902f147..abd44c2410 100644 --- a/dedibox/dedicated-servers/how-to/manage-packages.mdx +++ b/dedibox/dedicated-servers/how-to/manage-packages.mdx @@ -23,7 +23,7 @@ This guide covers package management on the following distributions: - A Dedibox account logged into the [console](https://console.online.net) -- A [created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) Dedibox server +- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) Dedibox server ## Debian and Ubuntu: Using APT diff --git a/dedibox/dedicated-servers/how-to/migrate-server.mdx b/dedibox/dedicated-servers/how-to/migrate-server.mdx index 9f1d7df349..7d8cb2af60 100644 --- a/dedibox/dedicated-servers/how-to/migrate-server.mdx +++ b/dedibox/dedicated-servers/how-to/migrate-server.mdx @@ -22,14 +22,14 @@ Rest assured, this guide will walk you through the steps to seamlessly migrate y - A Dedibox account logged into the [console](https://console.online.net) -- A [created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) dedicated server +- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) dedicated server ## How to migrate your data Transferring data from one server to another is straightforward. Here are some methods you can use: -- [Use FTP](/dedibox/dedicated-servers/how-to/connect-to-server/#using-sftp-with-filezilla) -- [Use SCP](/dedibox/dedicated-servers/how-to/connect-to-server/#using-scp-in-a-terminal) +- [Use FTP](/dedicated-servers/how-to/connect-to-server/#using-sftp-with-filezilla) +- [Use SCP](/dedicated-servers/how-to/connect-to-server/#using-scp-in-a-terminal) - [Use Rsync](https://manpages.ubuntu.com/manpages/noble/en/man1/rsync.1.html) ## How to migrate your services diff --git a/dedibox/dedicated-servers/how-to/monitor-server.mdx b/dedibox/dedicated-servers/how-to/monitor-server.mdx index 2481b815d2..62a69bdb37 100644 --- a/dedibox/dedicated-servers/how-to/monitor-server.mdx +++ b/dedibox/dedicated-servers/how-to/monitor-server.mdx @@ -22,7 +22,7 @@ Your management console includes a monitoring system that can notify you by e-ma - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server ## How to use the monitoring page diff --git a/dedibox/dedicated-servers/how-to/order-a-server.mdx b/dedibox/dedicated-servers/how-to/order-a-server.mdx index 23a5ec18a7..36eabc649e 100644 --- a/dedibox/dedicated-servers/how-to/order-a-server.mdx +++ b/dedibox/dedicated-servers/how-to/order-a-server.mdx @@ -18,7 +18,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) -- Added [a payment method](/dedibox-console/account/how-to/add-payment-method/) to your account +- Added [a payment method](/dedibox-account/how-to/add-payment-method/) to your account 1. Click **Order** on your Dedibox console homepage. 2. Click **Server**. The server offers page displays. diff --git a/dedibox/dedicated-servers/how-to/rescue-your-data.mdx b/dedibox/dedicated-servers/how-to/rescue-your-data.mdx index 28b3934db2..4ca48b51f7 100644 --- a/dedibox/dedicated-servers/how-to/rescue-your-data.mdx +++ b/dedibox/dedicated-servers/how-to/rescue-your-data.mdx @@ -18,14 +18,14 @@ If your server encounters issues but does not have a hardware failure, you can s - A Dedibox account logged into the [console](https://console.online.net) -- A [created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) dedicated server +- A [created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) dedicated server ## Booting into rescue mode -1. Follow [these instructions](/dedibox/dedicated-servers/how-to/use-rescue-mode/) to start your server in rescue mode (emergency system) via the Dedibox console. +1. Follow [these instructions](/dedicated-servers/how-to/use-rescue-mode/) to start your server in rescue mode (emergency system) via the Dedibox console. 2. Log into your server using one of the following methods: - - [PuTTY](http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe) on [Windows](/dedibox/dedicated-servers/how-to/connect-to-server/#for-windows-users) - - `ssh` from a terminal on [Linux or macOS](/dedibox/dedicated-servers/how-to/connect-to-server/#for-macos-and-linux-users). + - [PuTTY](http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe) on [Windows](/dedicated-servers/how-to/connect-to-server/#for-windows-users) + - `ssh` from a terminal on [Linux or macOS](/dedicated-servers/how-to/connect-to-server/#for-macos-and-linux-users). The rescue mode credentials (username and password) are displayed in your Dedibox console. diff --git a/dedibox/dedicated-servers/how-to/restart-server.mdx b/dedibox/dedicated-servers/how-to/restart-server.mdx index e574a25035..c760a508e1 100644 --- a/dedibox/dedicated-servers/how-to/restart-server.mdx +++ b/dedibox/dedicated-servers/how-to/restart-server.mdx @@ -18,7 +18,7 @@ Your Dedibox server includes a remote reboot system, which we show you how to us - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server 1. From the console, click **Server** > **Server list**. A list of your servers displays. 2. Click **Manage** next to the server you want to restart. @@ -28,8 +28,8 @@ Your Dedibox server includes a remote reboot system, which we show you how to us You are returned to your main server page, where you see the message **Reboot in progress**. - - You can also reboot your server via [KVM](/dedibox/kvm-over-ip/). In the iDRAC and iLO KVM interfaces, you can switch your server OFF and ON again. This allows you to check what happens during its boot sequence and intervene if necessary. - - If it stops responding, you can try [rebooting your server in Rescue Mode](/dedibox/dedicated-servers/how-to/use-rescue-mode/). In the case the problem persists, [open a support ticket](https://console.online.net/en/assistance/ticket) to ask for a hardware check of your server. + - You can also reboot your server via [KVM](/dedibox-kvm-over-ip/). In the iDRAC and iLO KVM interfaces, you can switch your server OFF and ON again. This allows you to check what happens during its boot sequence and intervene if necessary. + - If it stops responding, you can try [rebooting your server in Rescue Mode](/dedicated-servers/how-to/use-rescue-mode/). In the case the problem persists, [open a support ticket](https://console.online.net/en/assistance/ticket) to ask for a hardware check of your server. diff --git a/dedibox/dedicated-servers/how-to/use-dedibackup-ftp-backup.mdx b/dedibox/dedicated-servers/how-to/use-dedibackup-ftp-backup.mdx index 6b97033d73..c4c1bf144c 100644 --- a/dedibox/dedicated-servers/how-to/use-dedibackup-ftp-backup.mdx +++ b/dedibox/dedicated-servers/how-to/use-dedibackup-ftp-backup.mdx @@ -29,7 +29,7 @@ The storage system is backed by our [Object Storage](https://www.scaleway.com/en - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server ## How to activate the Dedibackup service diff --git a/dedibox/dedicated-servers/how-to/use-ipmi-on-server.mdx b/dedibox/dedicated-servers/how-to/use-ipmi-on-server.mdx index 58a82c30a5..43fae707f3 100644 --- a/dedibox/dedicated-servers/how-to/use-ipmi-on-server.mdx +++ b/dedibox/dedicated-servers/how-to/use-ipmi-on-server.mdx @@ -30,12 +30,12 @@ Actions that can be carried out via IPMI include: - Viewing of logs from the BIOS, - Accessing the serial port and BIOS over the network via serial console. -In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox/kvm-over-ip/) documentation for information about other server models. +In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox-kvm-over-ip/) documentation for information about other server models. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a Dedibox server with a dedicated KVM over IP device +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a Dedibox server with a dedicated KVM over IP device ## How to use IPMI via Dell iDRAC diff --git a/dedibox/dedicated-servers/how-to/use-rescue-mode.mdx b/dedibox/dedicated-servers/how-to/use-rescue-mode.mdx index 04a2f3f20b..721a78384c 100644 --- a/dedibox/dedicated-servers/how-to/use-rescue-mode.mdx +++ b/dedibox/dedicated-servers/how-to/use-rescue-mode.mdx @@ -31,7 +31,7 @@ We offer three types of rescue modes: - A Dedibox account logged into the [console](https://console.online.net) -- A [Dedibox server](/dedibox/dedicated-servers/how-to/order-a-server/) +- A [Dedibox server](/dedicated-servers/how-to/order-a-server/) ## Launching rescue mode @@ -46,7 +46,7 @@ We offer three types of rescue modes: To access your server in Linux/FreeBSD rescue mode: -1. [Connect to your server via SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). +1. [Connect to your server via SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). 2. Use the login credentials provided on the server’s status page in the console. Note that it may take approximately two minutes for rescue mode to fully initialize. Once connected, you can operate rescue mode like a standard distribution, installing tools such as text editors or FTP clients as needed. Keep in mind that the size of the ramdisk is limited. @@ -56,4 +56,4 @@ To access your server in Linux/FreeBSD rescue mode: To access your server in Windows PE rescue mode: 1. Use the KVM/IP feature of your server, as it is the only way to connect in this mode. -2. Refer to the [KVM/IP documentation](/dedibox/kvm-over-ip/quickstart/) for instructions specific to your server model. +2. Refer to the [KVM/IP documentation](/dedibox-kvm-over-ip/quickstart/) for instructions specific to your server model. diff --git a/dedibox/dedicated-servers/how-to/use-serial-console.mdx b/dedibox/dedicated-servers/how-to/use-serial-console.mdx index 618113403a..32c13eac1a 100644 --- a/dedibox/dedicated-servers/how-to/use-serial-console.mdx +++ b/dedibox/dedicated-servers/how-to/use-serial-console.mdx @@ -18,7 +18,7 @@ Some Dedibox server models do not have KVM over IP, but allow the visualization - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server ## How to access the serial console diff --git a/dedibox/dedicated-servers/index.mdx b/dedibox/dedicated-servers/index.mdx index a434042878..d447baacea 100644 --- a/dedibox/dedicated-servers/index.mdx +++ b/dedibox/dedicated-servers/index.mdx @@ -10,7 +10,7 @@ meta: productName="Dedibox Dedicated Servers" productLogo="dedibox" description="Dedibox dedicated servers are high-quality servers that benefit from extreme reliability and best-in-class redundancy for any workload requirement." - url="/dedibox/dedicated-servers/quickstart" + url="/dedicated-servers/quickstart" label="Dedicated Servers Quickstart" /> @@ -22,28 +22,28 @@ meta: icon="rocket" description="Learn how to create, connect to, and manage a Dedibox dedicated server in a few steps." label="View Quickstart" - url="/dedibox/dedicated-servers/quickstart/" + url="/dedicated-servers/quickstart/" /> diff --git a/dedibox/dedicated-servers/quickstart.mdx b/dedibox/dedicated-servers/quickstart.mdx index e6d9dc36c4..d18d74ed44 100644 --- a/dedibox/dedicated-servers/quickstart.mdx +++ b/dedibox/dedicated-servers/quickstart.mdx @@ -18,7 +18,7 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) -- [Added a payment method](/dedibox-console/account/how-to/add-payment-method/) to your account +- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account ## How to order a server @@ -71,14 +71,14 @@ After the delivery of your server, you can begin installing it. 2. Click **Manage** next to the server you want to install. The server installation wizard displays. 3. Select the type of operating system you want to install. - For more information about OS types, refer to the [dedicated servers concepts page](/dedibox/dedicated-servers/concepts/#os-type). + For more information about OS types, refer to the [dedicated servers concepts page](/dedicated-servers/concepts/#os-type). If you wish to complete your installation using KVM Over IP, click **Install over KVM** on this page. 4. Choose the operating system and OS version. Then, click **Install**. -5. Personalize the following [partitioning](/dedibox/dedicated-servers/concepts/#partitioning) parameters: +5. Personalize the following [partitioning](/dedicated-servers/concepts/#partitioning) parameters: - the file system (ext4, ext3, ext2, xfs, reiserfs, nfts, swap) - the mount point of the partition - the partition size @@ -90,7 +90,7 @@ After the delivery of your server, you can begin installing it. 6. Click **Validate**. 7. Configure the system parameters. You can edit parameters such as the name of the server, add a username, password, and SSH key, and configure monitoring alerts and updates. - To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. + To connect to your server via SSH, it is recommended that you [create and upload your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) at this stage so that it can be transferred to your server during installation. 8. Check that all information you entered is correct on the installation summary tab. @@ -111,8 +111,8 @@ You can also use FTP, SFTP, or SCP to transfer data to and from your server. - A Dedibox account logged into the [console](https://console.online.net) -- [Created and uploaded your SSH key](/dedibox-console/account/how-to/upload-an-ssh-key/) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation +- [Created and uploaded your SSH key](/dedibox-account/how-to/upload-an-ssh-key/) +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server and transferred your SSH key to the server during installation ## How to connect via SSH @@ -146,7 +146,7 @@ To connect to your Instance from Windows, you will need to use a small applicati 4. Use the side menu to navigate to the **Auth** sub-category by expanding **Connection**, then **SSH**, and finally clicking on **Auth**. -5. Click the **Browse** button and select the private key file you [generated previously](/dedibox-console/account/how-to/upload-an-ssh-key/). +5. Click the **Browse** button and select the private key file you [generated previously](/dedibox-account/how-to/upload-an-ssh-key/). 6. Click **Open** at the bottom of the screen to open a connection to the server. Upon the first connection, PuTTY asks you to allow the connection to the host. 7. Click **OK** to confirm. The terminal window displays. 8. Enter your username and password to authenticate against the server with your SSH key. @@ -166,4 +166,4 @@ The following steps show you how to connect to your Dedibox on which you have in 5. Enter the password that you set during installation of your Dedibox Windows Server machine, and click **OK**. 6. You may be asked to confirm that you want to connect. Click **Yes**. - You are connected to the graphical interface of your Windows Server. If you need to change the language, refer to the [How to change the language of Windows Server](/dedibox/dedicated-servers/how-to/change-win-server-language/) page. \ No newline at end of file + You are connected to the graphical interface of your Windows Server. If you need to change the language, refer to the [How to change the language of Windows Server](/dedicated-servers/how-to/change-win-server-language/) page. \ No newline at end of file diff --git a/dedibox/hardware/how-to/configure-dell-perc-h200.mdx b/dedibox/hardware/how-to/configure-dell-perc-h200.mdx index c85cffb254..526bc5e633 100644 --- a/dedibox/hardware/how-to/configure-dell-perc-h200.mdx +++ b/dedibox/hardware/how-to/configure-dell-perc-h200.mdx @@ -133,7 +133,7 @@ For maximum performance, you can activate the cache of your SATA disks. After cr This step can be performed on Dedibox servers equipped with a DELL PERC H200 RAID controller and SATA hard disk drives. -1. Boot your server into [rescue mode](/dedibox/dedicated-servers/how-to/use-rescue-mode/) using a 64-bit Ubuntu operating system. +1. Boot your server into [rescue mode](/dedicated-servers/how-to/use-rescue-mode/) using a 64-bit Ubuntu operating system. 2. Log into the server using the provided SSH credentials and run the following commands to re-enable the disk cache: ```sh sudo su diff --git a/dedibox/hardware/how-to/configure-hardware-raid-console.mdx b/dedibox/hardware/how-to/configure-hardware-raid-console.mdx index 48a89c7395..6df164b6d0 100644 --- a/dedibox/hardware/how-to/configure-hardware-raid-console.mdx +++ b/dedibox/hardware/how-to/configure-hardware-raid-console.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -A hardware RAID is a type of [RAID](/dedibox/hardware/concepts/#raid) implementation where construction and management of the RAID is performed on dedicated hardware, independently of the operating system. +A hardware RAID is a type of [RAID](/hardware/concepts/#raid) implementation where construction and management of the RAID is performed on dedicated hardware, independently of the operating system. The logical disks of the RAID array are managed by a physical controller, sitting on the PCI bus, which presents only the logical volumes to the operating system. The RAID controller manages the RAID using its own CPU and RAM, without delegating tasks to the main CPU of the machine. diff --git a/dedibox/hardware/index.mdx b/dedibox/hardware/index.mdx index bfbe71b28c..14e3a83d8b 100644 --- a/dedibox/hardware/index.mdx +++ b/dedibox/hardware/index.mdx @@ -20,13 +20,13 @@ meta: icon="information-circle-outline" description="Core concepts about the hardware of our dedicated servers." label="View Concepts" - url="/dedibox/hardware/concepts/" + url="/hardware/concepts/" /> \ No newline at end of file diff --git a/dedibox/hardware/troubleshooting/diagnose-defective-disk.mdx b/dedibox/hardware/troubleshooting/diagnose-defective-disk.mdx index 142a7fbe72..29a9213759 100644 --- a/dedibox/hardware/troubleshooting/diagnose-defective-disk.mdx +++ b/dedibox/hardware/troubleshooting/diagnose-defective-disk.mdx @@ -177,7 +177,7 @@ smartctl -l selftest /dev/sda ## How to report disk failures -If you notice any errors when running a SMART diagnosis on your disk, open a [support ticket](/console/account/how-to/open-a-support-ticket/) and ask for the disk to be replaced, indicating the serial number with the result of the `smartctl` command: +If you notice any errors when running a SMART diagnosis on your disk, open a [support ticket](/account/how-to/open-a-support-ticket/) and ask for the disk to be replaced, indicating the serial number with the result of the `smartctl` command: ``` === START OF INFORMATION SECTION === diff --git a/dedibox/kvm-over-ip/concepts.mdx b/dedibox/kvm-over-ip/concepts.mdx index 742b7c1ec8..ca42d1bf73 100644 --- a/dedibox/kvm-over-ip/concepts.mdx +++ b/dedibox/kvm-over-ip/concepts.mdx @@ -29,5 +29,5 @@ The **I**ntegrated **L**ights-**O**ut card is the hardware allowing KVM Over IP An ISO file, also called ISO image, is an archive file that contains an identical copy of data usually stored on a physical optical disk, such as a CD or DVD. The name ISO file comes from the file system type used by optical media (typically ISO 9660). The ISO file can be distributed to be burned on a physical disc or can be read directly by most operating systems or [KVM over IP](#kvm-over-ip) devices to install an operating system on a remote machine. - Scaleway provides a wide range of operating systems for installation on Dedibox servers equipped with a KVM over IP device. You can find a list of all available images at [http://virtualmedia.online.net/](http://virtualmedia.online.net). For more information on how to install an operating system using the KVM device, refer to our [dedicated documentation](/dedibox/kvm-over-ip/quickstart/). + Scaleway provides a wide range of operating systems for installation on Dedibox servers equipped with a KVM over IP device. You can find a list of all available images at [http://virtualmedia.online.net/](http://virtualmedia.online.net). For more information on how to install an operating system using the KVM device, refer to our [dedicated documentation](/dedibox-kvm-over-ip/quickstart/). \ No newline at end of file diff --git a/dedibox/kvm-over-ip/how-to/dell-idrac6.mdx b/dedibox/kvm-over-ip/how-to/dell-idrac6.mdx index 5df16c6f06..0cc00c277b 100644 --- a/dedibox/kvm-over-ip/how-to/dell-idrac6.mdx +++ b/dedibox/kvm-over-ip/how-to/dell-idrac6.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 6. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 6. diff --git a/dedibox/kvm-over-ip/how-to/dell-idrac7.mdx b/dedibox/kvm-over-ip/how-to/dell-idrac7.mdx index 3be76a91ac..ef9f1bce60 100644 --- a/dedibox/kvm-over-ip/how-to/dell-idrac7.mdx +++ b/dedibox/kvm-over-ip/how-to/dell-idrac7.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 7. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 7. diff --git a/dedibox/kvm-over-ip/how-to/dell-idrac8.mdx b/dedibox/kvm-over-ip/how-to/dell-idrac8.mdx index d4a3469d95..bedd171e54 100644 --- a/dedibox/kvm-over-ip/how-to/dell-idrac8.mdx +++ b/dedibox/kvm-over-ip/how-to/dell-idrac8.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 8. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 8. diff --git a/dedibox/kvm-over-ip/how-to/dell-idrac9.mdx b/dedibox/kvm-over-ip/how-to/dell-idrac9.mdx index 0d4672c9d3..dbe5deaf6c 100644 --- a/dedibox/kvm-over-ip/how-to/dell-idrac9.mdx +++ b/dedibox/kvm-over-ip/how-to/dell-idrac9.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 9. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with DELL iDRAC 9. diff --git a/dedibox/kvm-over-ip/how-to/disable-boot-errors-idrac.mdx b/dedibox/kvm-over-ip/how-to/disable-boot-errors-idrac.mdx index 0121d223d5..2ffc9b0642 100644 --- a/dedibox/kvm-over-ip/how-to/disable-boot-errors-idrac.mdx +++ b/dedibox/kvm-over-ip/how-to/disable-boot-errors-idrac.mdx @@ -18,9 +18,9 @@ This document shows you how to disable boot errors, where your server gets "stuc - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server with a Dell iDRAC controller +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server with a Dell iDRAC controller -1. [Connect to your server's iDRAC](/dedibox/dedicated-servers/how-to/use-ipmi-on-server/#how-to-use-ipmi-via-dell-idrac). +1. [Connect to your server's iDRAC](/dedicated-servers/how-to/use-ipmi-on-server/#how-to-use-ipmi-via-dell-idrac). 2. Click **System**, on the side menu. 3. Click the **Console/Media** tab, then **Launch virtual console**. diff --git a/dedibox/kvm-over-ip/how-to/hp-ilo.mdx b/dedibox/kvm-over-ip/how-to/hp-ilo.mdx index 793d42621c..157ea3dce0 100644 --- a/dedibox/kvm-over-ip/how-to/hp-ilo.mdx +++ b/dedibox/kvm-over-ip/how-to/hp-ilo.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with HP iLO. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with HP iLO. diff --git a/dedibox/kvm-over-ip/how-to/quanta-computer.mdx b/dedibox/kvm-over-ip/how-to/quanta-computer.mdx index 4807de2ab4..f675cd2153 100644 --- a/dedibox/kvm-over-ip/how-to/quanta-computer.mdx +++ b/dedibox/kvm-over-ip/how-to/quanta-computer.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Quanta Computer KVM. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Quanta Computer KVM. diff --git a/dedibox/kvm-over-ip/how-to/quantaplex.mdx b/dedibox/kvm-over-ip/how-to/quantaplex.mdx index d53c06fe51..5f4cff9cd2 100644 --- a/dedibox/kvm-over-ip/how-to/quantaplex.mdx +++ b/dedibox/kvm-over-ip/how-to/quantaplex.mdx @@ -13,12 +13,12 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a QuantaPlex Dedibox. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a QuantaPlex Dedibox. - A Dedibox account logged into the [console](https://console.online.net) -- A [Dedibox server](/dedibox/dedicated-servers/how-to/install-a-server/) with a [Quanta Computer QuantaPlex](https://www.qct.io) KVM-over-IP device +- A [Dedibox server](/dedicated-servers/how-to/install-a-server/) with a [Quanta Computer QuantaPlex](https://www.qct.io) KVM-over-IP device ## Creating a KVM session diff --git a/dedibox/kvm-over-ip/how-to/supermicro.mdx b/dedibox/kvm-over-ip/how-to/supermicro.mdx index 4a4b64beb8..1a2c8cf183 100644 --- a/dedibox/kvm-over-ip/how-to/supermicro.mdx +++ b/dedibox/kvm-over-ip/how-to/supermicro.mdx @@ -13,7 +13,7 @@ categories: - dedibox-servers --- -This page shows you how to use [KVM](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Supermicro KVM. +This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) on a Dedibox with Supermicro KVM. diff --git a/dedibox/kvm-over-ip/index.mdx b/dedibox/kvm-over-ip/index.mdx index ea19c6367d..0df7c3efc8 100644 --- a/dedibox/kvm-over-ip/index.mdx +++ b/dedibox/kvm-over-ip/index.mdx @@ -8,7 +8,7 @@ meta: productName="Dedibox - KVM-over-IP" productLogo="dedibox" description="KVM-over-IP allows you to manage and monitor a server using a network connection to the hardware, even if it is powered off or unresponsive." - url="/dedibox/kvm-over-ip/quickstart" + url="/dedibox-kvm-over-ip/quickstart" label="KVM-over-IP Quickstart" /> @@ -20,20 +20,20 @@ meta: icon="rocket" description="Learn how to create and connect to a Dedibox dedicated server using KVM-over-IP." label="View Quickstart" - url="/dedibox/kvm-over-ip/quickstart/" + url="/dedibox-kvm-over-ip/quickstart/" /> diff --git a/dedibox/kvm-over-ip/quickstart.mdx b/dedibox/kvm-over-ip/quickstart.mdx index 3bcf9211f8..eb8185859b 100644 --- a/dedibox/kvm-over-ip/quickstart.mdx +++ b/dedibox/kvm-over-ip/quickstart.mdx @@ -29,12 +29,12 @@ Actions that can be carried out via IPMI include: - Viewing of logs from the BIOS, - Accessing the serial port and BIOS over the network via serial console. -In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox/kvm-over-ip/) documentation for information about other server models. +In this document, we show you how to access the IPMI for a Dell or HP server. See the [KVM-over-IP](/dedibox-kvm-over-ip/) documentation for information about other server models. - A Dedibox account logged into the [console](https://console.online.net) -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a dedicated server with a dedicated KVM over IP device +- [Created](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a dedicated server with a dedicated KVM over IP device ## How to use IPMI via Dell iDRAC diff --git a/dedibox/vps/how-to/connect-vps.mdx b/dedibox/vps/how-to/connect-vps.mdx index d8e2c4b5c5..e18818b1e4 100644 --- a/dedibox/vps/how-to/connect-vps.mdx +++ b/dedibox/vps/how-to/connect-vps.mdx @@ -18,7 +18,7 @@ You can manage your Dedibox VPS by accessing it through SSH. - A Dedibox account logged into the [console](https://console.online.net) -- [Created a Dedibox VPS](/dedibox/vps/how-to/create-vps/) +- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/) ## Connecting from Linux and OSX (Mac) To connect to your Dedibox VPS from Linux or Mac OSX, follow these steps: diff --git a/dedibox/vps/how-to/create-vps.mdx b/dedibox/vps/how-to/create-vps.mdx index b9d5e3ccb9..2ab5cafba4 100644 --- a/dedibox/vps/how-to/create-vps.mdx +++ b/dedibox/vps/how-to/create-vps.mdx @@ -21,7 +21,7 @@ VPS are suitable for various use cases, including hosting websites, web applicat - A Dedibox account logged into the [console](https://console.online.net) -- [Added a payment method](/dedibox-console/account/how-to/add-payment-method/) to your account +- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account 1. Log in to your [Dedibox console](https://console.online.net) account and click **Order** in the navigation at the top of the page. 2. From the drop-down menu, select **Dedibox VPS** to access the Dedibox VPS offers page. @@ -30,7 +30,7 @@ VPS are suitable for various use cases, including hosting websites, web applicat 5. Select your preferred location for the virtual machine deployment, then click **Order** to proceed. 6. Choose your virtual machine's desired Operating System (OS) and select the appropriate OS version. 7. Enter a hostname for your VPS, ensuring it contains at least eight (8) alphanumeric characters. -8. Optionally paste an [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) that can be used for authentication when connecting to the Dedibox VPS using SSH, then click **Order**. An order summary displays. +8. Optionally paste an [SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) that can be used for authentication when connecting to the Dedibox VPS using SSH, then click **Order**. An order summary displays. 9. Review all the parameters for your virtual machine and check the message boxes to indicate you have read the terms of service and specific VPS conditions. 10. Click **Confirm my order** to confirm your purchase and initiate the deployment of your VPS. diff --git a/dedibox/vps/how-to/delete-vps.mdx b/dedibox/vps/how-to/delete-vps.mdx index 2035cd7d0c..3d2d50a0fd 100644 --- a/dedibox/vps/how-to/delete-vps.mdx +++ b/dedibox/vps/how-to/delete-vps.mdx @@ -18,7 +18,7 @@ You can delete your VPS by requesting termination from the Dedibox console. To d - A Dedibox account logged into the [console](https://console.online.net) -- [Created a Dedibox VPS](/dedibox/vps/how-to/create-vps/) +- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/) 1. Log in to your [Dedibox console](https://console.online.net/) account and locate **Dedibox VPS** in the top navigation menu. Click it to access the list of your Dedibox VPS. 2. Select the Dedibox VPS you want to delete and click **Manage**. This action will direct you to the VPS information dashboard. diff --git a/dedibox/vps/how-to/manage-vps.mdx b/dedibox/vps/how-to/manage-vps.mdx index fd896190c0..207473f343 100644 --- a/dedibox/vps/how-to/manage-vps.mdx +++ b/dedibox/vps/how-to/manage-vps.mdx @@ -18,7 +18,7 @@ You can manage your Dedibox VPS directly from the Dedibox console. - A Dedibox account logged into the [console](https://console.online.net) -- [Created a Dedibox VPS](/dedibox/vps/how-to/create-vps/) +- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/) ## How to manage a Dedibox VPS from its information dashboard diff --git a/dedibox/vps/how-to/reinstall-vps.mdx b/dedibox/vps/how-to/reinstall-vps.mdx index b57ebbfc82..af7715207f 100644 --- a/dedibox/vps/how-to/reinstall-vps.mdx +++ b/dedibox/vps/how-to/reinstall-vps.mdx @@ -18,7 +18,7 @@ You can reinstall your VPS at any time from your Dedibox console. - A Dedibox account logged into the [console](https://console.online.net) -- [Created a Dedibox VPS](/dedibox/vps/how-to/create-vps/) +- [Created a Dedibox VPS](/dedibox-vps/how-to/create-vps/) 1. Log in to your [Dedibox console](https://console.online.net/) account and locate **Dedibox VPS** in the top navigation menu. Click it to access the list of your Dedibox VPS. 2. Select the Dedibox VPS you want to reinstall and click **Manage** next to it. This action will direct you to the VPS information dashboard. diff --git a/dedibox/vps/index.mdx b/dedibox/vps/index.mdx index 6db89dfe16..8e27175ccb 100644 --- a/dedibox/vps/index.mdx +++ b/dedibox/vps/index.mdx @@ -11,7 +11,7 @@ meta: productLogo="dediboxVps" description="Dedibox VPS (Virtual Private Server) are virtualized server environments that provide directly accessible computing resources and full control of your virtual machine. " - url="/dedibox/vps/quickstart" + url="/dedibox-vps/quickstart" label="Dedibox VPS Quickstart" /> @@ -23,20 +23,20 @@ meta: icon="rocket" description="Learn how to create, connect to, and manage a Dedibox VPS in a few steps." label="View Quickstart" - url="/dedibox/vps/quickstart/" + url="/dedibox-vps/quickstart/" /> diff --git a/dedibox/vps/quickstart.mdx b/dedibox/vps/quickstart.mdx index 68ae80eb95..23f6c9a419 100644 --- a/dedibox/vps/quickstart.mdx +++ b/dedibox/vps/quickstart.mdx @@ -23,7 +23,7 @@ They offer a balance of performance, control, and affordability for businesses a - A Dedibox account logged into the [console](https://console.online.net) -- [Added a payment method](/dedibox-console/account/how-to/add-payment-method/) to your account +- [Added a payment method](/dedibox-account/how-to/add-payment-method/) to your account 1. Navigate to your [Dedibox console](https://console.online.net) home page and select **Order** from the top navigation. 2. Choose **Dedibox VPS** from the drop-down menu to access available offers. @@ -31,7 +31,7 @@ They offer a balance of performance, control, and affordability for businesses a 4. Specify the geographical region for deployment and confirm your choice. 5. Choose the operating system (OS) and version for your virtual machine. 6. Enter a hostname containing at least eight alphanumeric characters. -7. Optionally, paste an [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) for authentication. +7. Optionally, paste an [SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-upload-the-public-ssh-key-to-the-scaleway-interface) for authentication. 8. Review your order details and confirm by clicking **Confirm my order**. It may take a few minutes for your VPS to be delivered and visible in your account. diff --git a/developer-tools/scaleway-cli/quickstart.mdx b/developer-tools/scaleway-cli/quickstart.mdx index 4d9f7f57a2..657b3d3815 100644 --- a/developer-tools/scaleway-cli/quickstart.mdx +++ b/developer-tools/scaleway-cli/quickstart.mdx @@ -26,8 +26,8 @@ You can also use the integrated Scaleway console CLI by clicking the button at t - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## How to install the Scaleway CLI locally @@ -101,7 +101,7 @@ Refer to the [Scaleway CLI repository](https://github.com/scaleway/scaleway-cli) Enter a valid secret-key: ``` - Enter your [API secret Key](/identity-and-access-management/iam/how-to/create-api-keys/). + Enter your [API secret Key](/iam/how-to/create-api-keys/). 3. The following message displays: @@ -109,7 +109,7 @@ Refer to the [Scaleway CLI repository](https://github.com/scaleway/scaleway-cli) Enter a valid access-key: ``` - Enter your [API access key](/identity-and-access-management/iam/how-to/create-api-keys/). + Enter your [API access key](/iam/how-to/create-api-keys/). 4. The following message displays: @@ -162,7 +162,7 @@ Refer to the [Scaleway CLI repository](https://github.com/scaleway/scaleway-cli) If a key is present, but not associated with the default Scaleway Project, the Scaleway CLI will add this key to the Project defined previously. - Otherwise, the Scaleway CLI will either confirm that the key is already present in your Scaleway Project, or warn you that no key were found. Refer to the [dedicated documentation](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) to create an SSH key. + Otherwise, the Scaleway CLI will either confirm that the key is already present in your Scaleway Project, or warn you that no key were found. Refer to the [dedicated documentation](/organizations-and-projects/how-to/create-ssh-key/) to create an SSH key. 10. The configuration is complete, and the message below displays: diff --git a/developer-tools/scaleway-cli/reference-content/cli-reference.mdx b/developer-tools/scaleway-cli/reference-content/cli-reference.mdx index 1bb559ade4..bf967aa818 100644 --- a/developer-tools/scaleway-cli/reference-content/cli-reference.mdx +++ b/developer-tools/scaleway-cli/reference-content/cli-reference.mdx @@ -17,12 +17,12 @@ The [Scaleway command line interface (CLI)](https://github.com/scaleway/scaleway | Product | Page | | ------------------------------- | --------------------- | -| Instances | [Scaleway Instances CLI cheatsheet](/compute/instances/api-cli/cli-cheatsheet/) | -| Instances | [Using cloud-init with Scaleway API and CLI](/compute/instances/api-cli/using-cloud-init/) | -| Instances | [Creating and managing an Instance with the CLI (v2)](/compute/instances/api-cli/creating-managing-instances-with-cliv2/) | -| Instances | [Managing Instance snapshots with the CLI (v2)](/compute/instances/api-cli/managing-instance-snapshot-via-cli/) | -| Elastic Metal | [Creating and Managing Elastic Metal servers with the CLI](/bare-metal/elastic-metal/api-cli/elastic-metal-with-cli/) | -| NATS | [Using the NATS CLI](/serverless/messaging/api-cli/nats-cli/) | -| Kubernetes | [Creating and managing a Kubernetes Kapsule with the CLI (v2)](/containers/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2/) | -| Iot Hub | [Getting started with the IoT Hub CLI](/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli/) | +| Instances | [Scaleway Instances CLI cheatsheet](/instances/api-cli/cli-cheatsheet/) | +| Instances | [Using cloud-init with Scaleway API and CLI](/instances/api-cli/using-cloud-init/) | +| Instances | [Creating and managing an Instance with the CLI (v2)](/instances/api-cli/creating-managing-instances-with-cliv2/) | +| Instances | [Managing Instance snapshots with the CLI (v2)](/instances/api-cli/managing-instance-snapshot-via-cli/) | +| Elastic Metal | [Creating and Managing Elastic Metal servers with the CLI](/elastic-metal/api-cli/elastic-metal-with-cli/) | +| NATS | [Using the NATS CLI](/messaging/api-cli/nats-cli/) | +| Kubernetes | [Creating and managing a Kubernetes Kapsule with the CLI (v2)](/kubernetes/api-cli/creating-managing-kubernetes-lifecycle-cliv2/) | +| Iot Hub | [Getting started with the IoT Hub CLI](/iot-hub/api-cli/getting-started-with-iot-hub-cli/) | diff --git a/developer-tools/scaleway-sdk/go-sdk.mdx b/developer-tools/scaleway-sdk/go-sdk.mdx index e55634ae76..306bc5b2d7 100644 --- a/developer-tools/scaleway-sdk/go-sdk.mdx +++ b/developer-tools/scaleway-sdk/go-sdk.mdx @@ -30,7 +30,7 @@ The process involves creating a Scaleway client, and then using SDK objects for ## Initialization -You need a pair of access and secret keys to connect to Scaleway API. Check out the documentation to find out [how to retrieve them](/identity-and-access-management/iam/how-to/create-api-keys/). +You need a pair of access and secret keys to connect to Scaleway API. Check out the documentation to find out [how to retrieve them](/iam/how-to/create-api-keys/). A minimal setup, allowing you to list servers using the Instance API, would look like this: @@ -53,7 +53,7 @@ func main() { scw.WithDefaultOrganizationID("SCW_DEFAULT_ORGANIZATION_ID"), // Get your credentials at https://console.scaleway.com/iam/api-keys scw.WithAuth("SCW_ACCESS_KEY", "SCW_SECRET_KEY"), - // Get more about our availability zones at https://www.scaleway.com/en/docs/console/account/reference-content/products-availability/ + // Get more about our availability zones at https://www.scaleway.com/en/docs/account/reference-content/products-availability/ scw.WithDefaultRegion("SCW_REGION"), ) if err != nil { diff --git a/developer-tools/scaleway-sdk/js-sdk.mdx b/developer-tools/scaleway-sdk/js-sdk.mdx index d40c2d4ade..c869b57364 100644 --- a/developer-tools/scaleway-sdk/js-sdk.mdx +++ b/developer-tools/scaleway-sdk/js-sdk.mdx @@ -21,7 +21,7 @@ The Scaleway JS SDK is a dynamic tool for developers who use JavaScript to inter ## Installing the JS SDK -To use the SDK, you need an access key and a secret key for the Scaleway API. Refer to Scaleway's [documentation on API keys](/identity-and-access-management/iam/how-to/create-api-keys/) for instructions on creating and retrieving these keys. +To use the SDK, you need an access key and a secret key for the Scaleway API. Refer to Scaleway's [documentation on API keys](/iam/how-to/create-api-keys/) for instructions on creating and retrieving these keys. Below is a basic setup example: diff --git a/developer-tools/scaleway-sdk/python-sdk.mdx b/developer-tools/scaleway-sdk/python-sdk.mdx index 396f2bc46c..d55162746f 100644 --- a/developer-tools/scaleway-sdk/python-sdk.mdx +++ b/developer-tools/scaleway-sdk/python-sdk.mdx @@ -38,7 +38,7 @@ The SDK caters to different programming needs by offering both synchronous and a ## Initialization -You need a pair of access and secret keys to connect to Scaleway API. Check out the documentation to find out [how to retrieve them](/identity-and-access-management/iam/how-to/create-api-keys/). +You need a pair of access and secret keys to connect to Scaleway API. Check out the documentation to find out [how to retrieve them](/iam/how-to/create-api-keys/). `scaleway` APIs must be initialized with `scaleway.Client`. diff --git a/developer-tools/terraform/quickstart.mdx b/developer-tools/terraform/quickstart.mdx index 5ee9cc7d5f..355a0825c3 100644 --- a/developer-tools/terraform/quickstart.mdx +++ b/developer-tools/terraform/quickstart.mdx @@ -20,7 +20,7 @@ Check out the [Scaleway Terraform registry](https://registry.terraform.io/provid - A Scaleway account logged into the [console](https://console.scaleway.com) -- initialized the [Scaleway configuration file](/developer-tools/terraform/reference-content/scaleway-configuration-file/) +- initialized the [Scaleway configuration file](/terraform/reference-content/scaleway-configuration-file/) - [Installed Terraform](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli#install-terraform) ## Creating and Deploying Scaleway resources using Terraform @@ -51,7 +51,7 @@ For the sake of this example, we are going to create a Kubernetes Kapsule cluste ``` - If you do not specify a Project ID, Terraform will use the default Project specified in the [Scaleway configuration file](/developer-tools/terraform/reference-content/scaleway-configuration-file/). + If you do not specify a Project ID, Terraform will use the default Project specified in the [Scaleway configuration file](/terraform/reference-content/scaleway-configuration-file/). 4. Add the following blocks to create a Private Network, a Kubernetes cluster and its associated pool: diff --git a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx index 48ace9149c..2c89a18b37 100644 --- a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx +++ b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator-estimation.mdx @@ -16,13 +16,13 @@ categories: The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).

-This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. +This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. -When you [order an Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/), you can see the estimated impact of your Elastic Metal server of choice before you order. In this page, we explain how the estimation is measured. +When you [order an Elastic Metal server](/elastic-metal/how-to/create-server/), you can see the estimated impact of your Elastic Metal server of choice before you order. In this page, we explain how the estimation is measured. - The estimation described on this page is based on the calculation methodology detailed in the [Environmental Footprint calculation breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + The estimation described on this page is based on the calculation methodology detailed in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. ## Availability Zone footprint estimation @@ -31,7 +31,7 @@ When you select your Elastic Metal server's Availability Zone, you can see the q -This data is determined by the [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness) of the data center and the [energy mix](/environmental-footprint/environmental-footprint/concepts/#energy-mix) of the country in which the data center is located. +This data is determined by the [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts/#pue-power-usage-effectiveness) of the data center and the [energy mix](/environmental-footprint/concepts/#energy-mix) of the country in which the data center is located. We use [Ember's](https://ember-climate.org/) Electricity Data Explorer to determine the impact linked to the energy mix. The energy mix can be very different from one country to another depending on the origin of the electricity used. We can see on [Electricity Maps' Environmental Impact by Zone map](https://app.electricitymaps.com/map) the significant differences that there can be between countries. @@ -50,7 +50,7 @@ The estimation is represented by three green leaf icons: The AZ footprint estimation is a straightforward calculation of CO₂ emissions per kW of electricity consumed, based on the energy mix and the data center’s Power Usage Effectiveness (PUE) specific to that AZ. For example, in an AZ like PAR-2, each kW consumed may have an impact of 0.065 kgCO₂e.

- Meanwhile, the offer footprint estimation is a more complex calculation that combines the AZ-specific data with additional factors relevant to the specific offer. This calculation considers not just energy consumption but also other elements, which are outlined in the [Environmental Footprint calculation breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page, to reflect a comprehensive impact specific to the offer rather than just adding up kW-based impacts. + Meanwhile, the offer footprint estimation is a more complex calculation that combines the AZ-specific data with additional factors relevant to the specific offer. This calculation considers not just energy consumption but also other elements, which are outlined in the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page, to reflect a comprehensive impact specific to the offer rather than just adding up kW-based impacts. ## Elastic Metal offers footprint estimation @@ -58,7 +58,7 @@ The estimation is represented by three green leaf icons: For Elastic Metal offers, the environmental footprint estimation considers the impact of the **manufacturing** and **use** of all the elements that allow the service to work, such as network, cross-IT equipment and stock, and non-IT elements in addition to the manufacturing and use of the server itself. The AZ you chose in the previous step will impact the **use** by multiplying each kw consumed by each of these elements by the value indicated. - For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + For a detailed report of how the environmental impact of Scaleway services is calculated, refer to the [Environmental Footprint calculator breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. For usage, we rely on an estimate of electricity consumption. This estimation is based on tests carried out by the Hardware team at Scaleway. Each range of offers was tested using different compute configurations, to ensure coverage of a variety of possible power consumption set ups. diff --git a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx index 37bc83f6f0..64d4693336 100644 --- a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx +++ b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator.mdx @@ -16,7 +16,7 @@ categories: The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).

-This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. +This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. This page details the methodology used to calculate the environmental footprint of Scaleway cloud services, and Bare Metal offers. This methodology ensures transparency and precision, as it provides reliable estimations covering a full lifecycle analysis. @@ -31,7 +31,7 @@ Our calculation methodology was developed in collaboration with the green IT spe Our Methodology is based on the [ADEME (French Government Agency for Ecological Transition) Product Category Rules (PCR) for Datacenter and Cloud services](https://librairie.ademe.fr/produire-autrement/6105-methodological-standard-for-the-environmental-assessment-of-datacenter-it-hosting-services-and-cloud-services.html), which provide a standardized framework for calculating and reporting the environmental impact of data centers and cloud services. These rules are designed to ensure consistency, transparency, and comparability in the assessment of environmental footprints across the industry. -The ADEME PCR specifies the methodology for conducting [Life Cycle Analysis (LCA)](/environmental-footprint/environmental-footprint/concepts/#life-cycle-analysis-lca) for data center operations, which includes the evaluation of energy consumption, greenhouse gas emissions, resource usage, and other environmental impacts associated with the lifecycle of data center infrastructures and cloud services. This lifecycle covers all stages from raw material extraction, manufacturing, and transportation, to the use and end-of-life disposal of data center equipment. +The ADEME PCR specifies the methodology for conducting [Life Cycle Analysis (LCA)](/environmental-footprint/concepts/#life-cycle-analysis-lca) for data center operations, which includes the evaluation of energy consumption, greenhouse gas emissions, resource usage, and other environmental impacts associated with the lifecycle of data center infrastructures and cloud services. This lifecycle covers all stages from raw material extraction, manufacturing, and transportation, to the use and end-of-life disposal of data center equipment. The stages of the lifecycle that are really significant in the total impact of a server are its manufacturing and its use. We will therefore focus on these two stages in the rest of this documentation. By adhering to PCR guidelines, we provide reliable and standardized environmental impact data. This facilitates better decision-making for both providers and consumers of data center and cloud services, as it allows for clear comparisons and informed choices regarding sustainability. @@ -57,7 +57,7 @@ By integrating these additional factors into the PCR Data center and cloud metho The final calculation of the environmental impact considers several critical factors to provide a thorough and accurate assessment. This includes considering the manufacturing processes for data centers and related technical components, network machines, and servers directly used by customers. Additionally, the assessment accounts for servers dedicated to IT tools and those maintained in stock. -The usage phase also includes every data center [Power Usage Effectiveness (PUE)](/environmental-footprint/environmental-footprint/concepts/#pue-power-usage-effectiveness), which is multiplied by the impact related to electricity consumption of network servers, customer-used servers, and servers used for transversal IT tools. This approach ensures that both the direct and indirect energy consumption associated with data center operations is accurately represented. +The usage phase also includes every data center [Power Usage Effectiveness (PUE)](/environmental-footprint/concepts/#pue-power-usage-effectiveness), which is multiplied by the impact related to electricity consumption of network servers, customer-used servers, and servers used for transversal IT tools. This approach ensures that both the direct and indirect energy consumption associated with data center operations is accurately represented. Our calculations of the impact of electricity consumption are based on a 'location-based' approach, although we have PPA (Power Purchase Agreements) type contracts for each of our data centers, we have chosen not to take them into account in accordance with ADEME guidelines. @@ -75,15 +75,15 @@ All calculations will use the following variables: The acronyms used below are based on the French phrases for these terms. -- [dU](/environmental-footprint/environmental-footprint/concepts/#du-duration-of-use): duration of use of the equipment included in the study -- [DDV](/environmental-footprint/environmental-footprint/concepts/#ddvdc-data-center-lifespan): lifespan -- [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power): rated power of the equipment -- [PuissCommDC](/environmental-footprint/environmental-footprint/concepts/#puisscommdc): proportion of the data center's installed power reserved by customers -- [FE](/environmental-footprint/environmental-footprint/concepts/#emission-factor): emission factor -- [%mutualization](/environmental-footprint/environmental-footprint/concepts/#mutualization): mutualization factor +- [dU](/environmental-footprint/concepts/#du-duration-of-use): duration of use of the equipment included in the study +- [DDV](/environmental-footprint/concepts/#ddvdc-data-center-lifespan): lifespan +- [PuissEqt](/environmental-footprint/concepts/#puisseqt-rated-power): rated power of the equipment +- [PuissCommDC](/environmental-footprint/concepts/#puisscommdc): proportion of the data center's installed power reserved by customers +- [FE](/environmental-footprint/concepts/#emission-factor): emission factor +- [%mutualization](/environmental-footprint/concepts/#mutualization): mutualization factor - Refer to the [Environmental Footprint concepts page](/environmental-footprint/environmental-footprint/concepts/) for more information about each of the concepts above. + Refer to the [Environmental Footprint concepts page](/environmental-footprint/concepts/) for more information about each of the concepts above. ### Data center and technical environment @@ -173,7 +173,7 @@ This data is availlable for: For each Scaleway product or service in these Availability Zones, we calculate the water consumption based on its energy consumption. -To estimate the water consumption by multiplying the total energy consumption for each service by the [Water Usage Effectiveness (WUE)](/environmental-footprint/environmental-footprint/concepts/#water-usage-effectiveness), as such: +To estimate the water consumption by multiplying the total energy consumption for each service by the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness), as such: ```math Water Consumption (liters) = Energy Consumption (kWh) × WUE (liters/kWh) diff --git a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration.mdx b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration.mdx index 7bd4a94825..53db45290e 100644 --- a/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration.mdx +++ b/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration.mdx @@ -13,7 +13,7 @@ categories: - environmental-footprint --- -The following tables provide details about the Scaleway products that currently integrate the [environmental footprint calculator](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) and the products that will integrate it in the future, by order of integration. +The following tables provide details about the Scaleway products that currently integrate the [environmental footprint calculator](/environmental-footprint/additional-content/environmental-footprint-calculator) and the products that will integrate it in the future, by order of integration. ## Product integration available diff --git a/environmental-footprint/environmental-footprint/concepts.mdx b/environmental-footprint/environmental-footprint/concepts.mdx index a53926a497..5251a8162c 100644 --- a/environmental-footprint/environmental-footprint/concepts.mdx +++ b/environmental-footprint/environmental-footprint/concepts.mdx @@ -55,7 +55,7 @@ In the context of Scaleway, the LCA can be used to assess the environmental impa ## Mutualization -This factor is equivalent to [PuissEqt](/environmental-footprint/environmental-footprint/concepts/#puisseqt-rated-power) and PuissDisponibleDC, which is the nominal power available for Scaleway at the data center. For shared equipment, such as management servers and network equipment of the data center, this factor is applied. +This factor is equivalent to [PuissEqt](/environmental-footprint/concepts/#puisseqt-rated-power) and PuissDisponibleDC, which is the nominal power available for Scaleway at the data center. For shared equipment, such as management servers and network equipment of the data center, this factor is applied. ## PuissCommDC diff --git a/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx b/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx index 048b982bdd..a8f1d9a6b9 100644 --- a/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx +++ b/environmental-footprint/environmental-footprint/how-to/track-monthly-footprint.mdx @@ -20,7 +20,7 @@ The environmental footprint estimation tool is currently in private beta. Sign u - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization The monthly report shows the total environmental footprint of your Scaleway Organization. However, Elastic Metal servers are currently the only product considered in the calculation. Therefore, **only results related to Elastic Metal servers are shown in the report**. @@ -39,11 +39,11 @@ The environmental footprint estimation tool is currently in private beta. Sign u - **2.** The name of your Organization. - **3.** The total carbon footprint of your Organization per month, which takes into account the impact of the **manufacture** and **use** of all the components that run your active Scaleway products in relation to each service's useful life. - For a detailed description of how the carbon emissions are calculated, refer to the [Environmental Footprint calculation breakdown](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. + For a detailed description of how the carbon emissions are calculated, refer to the [Environmental Footprint calculation breakdown](/environmental-footprint/additional-content/environmental-footprint-calculator) documentation page. - - **4.** The total water consumption of your Organization per month, which is calculated on the basis of the [Water Usage Effectiveness (WUE)](/environmental-footprint/environmental-footprint/concepts/#water-usage-effectiveness) of the data centers in which each of your services are located, as well as the services' electricity consumption. + - **4.** The total water consumption of your Organization per month, which is calculated on the basis of the [Water Usage Effectiveness (WUE)](/environmental-footprint/concepts/#water-usage-effectiveness) of the data centers in which each of your services are located, as well as the services' electricity consumption. - For a detailed description of how the water consumption is calculated, refer to the [Water Consumption section](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator/#water-consumption) of the Environmental Footprint calculation breakdown documentation page. + For a detailed description of how the water consumption is calculated, refer to the [Water Consumption section](/environmental-footprint/additional-content/environmental-footprint-calculator/#water-consumption) of the Environmental Footprint calculation breakdown documentation page. - **5.** The total water consumption and carbon footprint of each of your Projects. - **6.** The total water consumption and carbon footprint per geographical location (Region and Availability Zone) diff --git a/environmental-footprint/environmental-footprint/index.mdx b/environmental-footprint/environmental-footprint/index.mdx index 2bb44a25db..8da702d8c2 100644 --- a/environmental-footprint/environmental-footprint/index.mdx +++ b/environmental-footprint/environmental-footprint/index.mdx @@ -8,14 +8,14 @@ meta: productName="Environmental Footprint" productLogo="iam" description="Scaleway's Environmental footprint calculator Allows you to measure your environmental impact to your use of Scaleway cloud and bare metal services." - url="/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-calculator" + url="/environmental-footprint/additional-content/environmental-footprint-calculator" label="Environmental Footprint calculator breakdown" /> The environmental footprint estimation tool is currently in private beta. Sign up for the beta via [the Scaleway betas page](https://www.scaleway.com/fr/betas/#environmental-footprint-calculator).

-This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. +This feature is currently only available for Elastic Metal servers. Refer to the [Environmental footprint calculator product integration](/environmental-footprint/additional-content/environmental-footprint-integration) index to see which products will integrate the calculator next. ## Getting Started @@ -26,13 +26,13 @@ This feature is currently only available for Elastic Metal servers. Refer to the icon="information-circle-outline" description="Core concepts that give you a better understanding of the Environmental Footprint calculator." label="View Concepts" - url="/environmental-footprint/environmental-footprint/concepts" + url="/environmental-footprint/concepts" /> diff --git a/faq/account.mdx b/faq/account.mdx index 27ad2e6e37..2616c92a63 100644 --- a/faq/account.mdx +++ b/faq/account.mdx @@ -26,7 +26,7 @@ At this moment, it is not possible to move a Project from one account to another ## How do I delete my Organization? -[Closing your account](/console/account/how-to/close-account/#how-to-close-your-account) permanently deletes your Organization, along with its servers, resources, services, and backups. +[Closing your account](/account/how-to/close-account/#how-to-close-your-account) permanently deletes your Organization, along with its servers, resources, services, and backups. We recommend that you delete all resources before closing your account. Otherwise, the remaining resources will be billed for usage before their manual deletion, which can take up to 10 days. @@ -34,7 +34,7 @@ At this moment, it is not possible to move a Project from one account to another ## Can I reopen a closed account? -Yes, you can [reopen a closed account](/console/account/how-to/close-account/#how-to-reopen-your-account). However, a closed account's resources are permanently deleted, and you cannot retrieve them. +Yes, you can [reopen a closed account](/account/how-to/close-account/#how-to-reopen-your-account). However, a closed account's resources are permanently deleted, and you cannot retrieve them. ## How do I change my email address? @@ -49,21 +49,21 @@ Your email address is now updated. ## How can I get more quotas? -You can get more quotas by adding and verifying your [payment method](/console/billing/how-to/add-payment-method/) and [identity](/console/account/how-to/verify-identity/). +You can get more quotas by adding and verifying your [payment method](/billing/how-to/add-payment-method/) and [identity](/account/how-to/verify-identity/). If you have already completed these two steps and still need an increase in quotas, contact our [support team](https://console.scaleway.com/support/tickets/create) and inform them which product you need more quotas for. ## I don’t seem to have access to my Organization's resources -If you do not have access to certain Organization resources, you might not have the necessary [IAM](/identity-and-access-management/iam/concepts/#iam) **permission set**. +If you do not have access to certain Organization resources, you might not have the necessary [IAM](/iam/concepts/#iam) **permission set**. -[Read the documentation on permission sets](/identity-and-access-management/iam/reference-content/permission-sets/)​ to learn more about the different access levels. +[Read the documentation on permission sets](/iam/reference-content/permission-sets/)​ to learn more about the different access levels. Contact an Organization owner or a member with the necessary permissions to request rights to the resources you require access to. ## I would like to delete my Scaleway account and data -Refer to the [How to delete your account and personal data](/console/account/how-to/close-account/) documentation. +Refer to the [How to delete your account and personal data](/account/how-to/close-account/) documentation. Once you request the deletion of your account and personal data, you will no longer be able to access your account or invoices. The request will take at least 72 hours to be processed. You must make sure all your bills are paid, and that you have not used any resources since the beginning of the current calendar month. diff --git a/faq/apple-silicon.mdx b/faq/apple-silicon.mdx index 2f8aca99e6..eaf42900e6 100644 --- a/faq/apple-silicon.mdx +++ b/faq/apple-silicon.mdx @@ -27,7 +27,7 @@ You can back up your Mac mini using a backup solution of your choice. Examples i - [Restic](/tutorials/restic-s3-backup/) for command-line backups. - [Arq Backup](/tutorials/arqbackup-pc-mac/) for graphical interface backups. -Both solutions allow you to store backups on our [Object Storage](/storage/object/quickstart/). +Both solutions allow you to store backups on our [Object Storage](/object-storage/quickstart/). ## What is preinstalled on the Mac mini? When you rent a Mac mini, it comes with a bare environment. The pre-installed tools include: @@ -42,5 +42,5 @@ Certain operations are restricted by default MDM configuration profiles: - Certain admin actions, like system Time Machine restoration and boot system policies, are not possible. ## Do I pay for my Mac mini when I am not using it? -Yes, you pay for your Mac mini as long as it is assigned to your account. You must explicitly delete it in the console or via the CLI to stop charges. For deletion instructions, see [How to delete Mac mini](/bare-metal/apple-silicon/how-to/delete-mac-mini/). +Yes, you pay for your Mac mini as long as it is assigned to your account. You must explicitly delete it in the console or via the CLI to stop charges. For deletion instructions, see [How to delete Mac mini](/apple-silicon/how-to/delete-mac-mini/). diff --git a/faq/audit-trail.mdx b/faq/audit-trail.mdx index e1ef226403..ae417e336a 100644 --- a/faq/audit-trail.mdx +++ b/faq/audit-trail.mdx @@ -26,7 +26,7 @@ Audit Trail is free of charge. ## Which Scaleway products are integrated with Audit Trail? -During Beta, only Secret Manager is integrated with Audit Trail. Refer to the [dedicated documentation](/identity-and-access-management/audit-trail/reference-content/resource-integration-with-adt/) to find out more about product integration with Audit Trail. +During Beta, only Secret Manager is integrated with Audit Trail. Refer to the [dedicated documentation](/audit-trail/reference-content/resource-integration-with-adt/) to find out more about product integration with Audit Trail. ## Where are my Audit Trail events stored? diff --git a/faq/billing.mdx b/faq/billing.mdx index cbce1b226b..fccfe19769 100644 --- a/faq/billing.mdx +++ b/faq/billing.mdx @@ -54,7 +54,7 @@ This billing model ensures that you pay for the service based on your actual usa ## How to read my invoice? -Refer to the [Reading an invoice](/console/billing/additional-content/reading-an-invoice/) documentation page for a detailed description of your invoices. +Refer to the [Reading an invoice](/billing/additional-content/reading-an-invoice/) documentation page for a detailed description of your invoices. ## When are invoices issued? @@ -126,7 +126,7 @@ You can add a billing contact directly from the User Account section of your Sca ## How can I obtain a SEPA Mandate? -Refer to the [How to add a payment method](/console/billing/how-to/add-payment-method#how-to-add-a-sepa-mandate) documentation page for a complete guide on how to add a SEPA mandate. +Refer to the [How to add a payment method](/billing/how-to/add-payment-method#how-to-add-a-sepa-mandate) documentation page for a complete guide on how to add a SEPA mandate. ## My credit card validation code expired. What should I do? @@ -177,12 +177,12 @@ No. Virtual or prepaid cards are **not** accepted as payment methods. When using ## Why is my Savings Plan charge lower than expected? When you commit to an amount and purchase a Savings Plan, you receive a monthly discount based on your committed rate and the duration of your plan. If you find that the rate you pay monthly is smaller than the committed rate, this is because your discount was applied. -Refer to the [Understanding Savings Plan](/console/billing/additional-content/understanding-savings-plans/) documentation page for more information. +Refer to the [Understanding Savings Plan](/billing/additional-content/understanding-savings-plans/) documentation page for more information. ## Why am I incurring charges while my Savings Plan utilization is less than 100%? When you purchase a Savings Plan, you commit to a monthly rate in resource consumption. This means that even if you do not consume enough resources, you are still billed for the full committed rate with discounts. -Refer to the [Understanding Savings Plan](/console/billing/additional-content/understanding-savings-plans/) documentation page for more information. +Refer to the [Understanding Savings Plan](/billing/additional-content/understanding-savings-plans/) documentation page for more information. ## I deleted my account, but still received an invoice. Why? diff --git a/faq/blockstorage.mdx b/faq/blockstorage.mdx index 80180953ea..1d2ad53fe4 100644 --- a/faq/blockstorage.mdx +++ b/faq/blockstorage.mdx @@ -52,7 +52,7 @@ The Block Storage billing scheme is not the same as for Object Storage. You are ## What other Scaleway resources are compatible with Block Storage? -Block Storage volumes are compatible with [Scaleway Instances](/compute/instances/), [Managed Dabatase for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/), and [Kubernetes](/containers/kubernetes/) Kapsule clusters. +Block Storage volumes are compatible with [Scaleway Instances](/instances/), [Managed Dabatase for PostgreSQL and MySQL](/managed-databases-for-postgresql-and-mysql/), and [Kubernetes](/kubernetes/) Kapsule clusters. ## How can I convert a Block Storage legacy volume into a Block Storage Low Latency volume? @@ -65,10 +65,10 @@ Although there is no direct way to change the storage class of a volume while pr While this approach allows you to transition to a Block Storage Low Latency volume, it is only a workaround. -1. [Create a snapshot of your Block Storage legacy volume](/compute/instances/how-to/create-a-snapshot/). -2. [Export the snapshot](/compute/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). +1. [Create a snapshot of your Block Storage legacy volume](/instances/how-to/create-a-snapshot/). +2. [Export the snapshot](/instances/api-cli/snapshot-import-export-feature/#exporting-snapshots). 3. [Import the snapshot into a new Low Latency volume](https://www.scaleway.com/en/developers/api/block/#path-snapshot-import-a-snapshot-from-a-scaleway-object-storage-bucket). -Find out how to [migrate your Block Storage volumes and snapshots](/compute/instances/how-to/migrate-volumes-snapshots-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. -Find out about the [advantages of migrating the management of your volumes and snapshots](/storage/block/reference-content/advantages-migrating-to-sbs) from the Instance API to the Block Storage API. +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. diff --git a/faq/cockpit.mdx b/faq/cockpit.mdx index 35f7e95635..fc1c6b1deb 100644 --- a/faq/cockpit.mdx +++ b/faq/cockpit.mdx @@ -15,25 +15,25 @@ productIcon: CockpitProductIcon ## What is Cockpit? Cockpit is a monitoring and alerting solution designed for multi-source observability. Cockpit allows you to collect, store, and analyze metrics and logs from your infrastructure and applications, giving you insights into your system's performance and behavior. -Cockpits are scoped per [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). +Cockpits are scoped per [Project](/organizations-and-projects/concepts/#project). ## How does Cockpit integrate with other Scaleway products? Cockpit integrates seamlessly with Scaleway’s ecosystem. It provides pre-built dashboards in Grafana, and alerts to monitor other Scaleway resources' performance. -Refer to the [dedicated documentation page](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) for the whole list of Scaleway resources integrated with Cockpit. +Refer to the [dedicated documentation page](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) for the whole list of Scaleway resources integrated with Cockpit. ## How am I billed for using Cockpit with my Scaleway data? Using Cockpit with your Scaleway data is free of charge. -During the beta phase of the retention period edition feature, the retention period you set for your data - whether from [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) or custom data - will be free of charge. +During the beta phase of the retention period edition feature, the retention period you set for your data - whether from [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) or custom data - will be free of charge. Additional costs apply for sending custom data to Cockpit. This means that you will be billed for sending **data from Scaleway resources that are not integrated with Cockpit**, or data from any other external resources. ## How am I billed for using Cockpit with custom data? -Custom data is any data that is external to Scaleway, or **data from Scaleway resources not integrated with Cockpit**. Refer to the [dedicated documentation page](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which resources are integrated with Cockpit. +Custom data is any data that is external to Scaleway, or **data from Scaleway resources not integrated with Cockpit**. Refer to the [dedicated documentation page](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) to find out which resources are integrated with Cockpit. During the beta of the retention period edition feature, the retention period you set for your custom data is free of charge. @@ -69,25 +69,25 @@ Here is an example of how you would be billed for sending 52 billion custom metr ## Why are Cockpit pricing plans being deprecated? -From January 1st 2025, Cockpit is transitioning away from fixed pricing plans to offer you more flexibility and granularity for managing data [retention](/observability/cockpit/concepts/#retention). +From January 1st 2025, Cockpit is transitioning away from fixed pricing plans to offer you more flexibility and granularity for managing data [retention](/cockpit/concepts/#retention). This change allows you to tailor retention settings to your specific needs. We hope to enhance your experience by providing more customizable options without immediate cost impact, as changing data retention period will be free during Beta. -Find out [how to change data retention period](/observability/cockpit/how-to/change-data-retention/) in the dedicated documentation. +Find out [how to change data retention period](/cockpit/how-to/change-data-retention/) in the dedicated documentation. ## How do I send my own data to my Cockpit? -If you have set up an agent, you can send your data using our [dedicated documentation](/observability/cockpit/how-to/send-metrics-logs-to-cockpit/). +If you have set up an agent, you can send your data using our [dedicated documentation](/cockpit/how-to/send-metrics-logs-to-cockpit/). -If you have not set up an agent, check out our [documentation](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to +If you have not set up an agent, check out our [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure the Grafana Alloy agent, push your data, and visualize it in Grafana. ## Which Scaleway products are integrated into Cockpit? -Find out which Scaleway products are integrated into Cockpit in our [capabilities and limits documentation page](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Find out which Scaleway products are integrated into Cockpit in our [capabilities and limits documentation page](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). -Refer to our [documentation on understanding Cockpit usage and pricing](/observability/cockpit/reference-content/understanding-cockpit-usage/) for more information on how to reduce extra costs. +Refer to our [documentation on understanding Cockpit usage and pricing](/cockpit/reference-content/understanding-cockpit-usage/) for more information on how to reduce extra costs. Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information. diff --git a/faq/databases-for-postgresql-and-mysql.mdx b/faq/databases-for-postgresql-and-mysql.mdx index 730909055b..8a7bbc946b 100644 --- a/faq/databases-for-postgresql-and-mysql.mdx +++ b/faq/databases-for-postgresql-and-mysql.mdx @@ -41,7 +41,7 @@ You will be prompted to enter your password to log in. ## How can I manage my databases? -You can [create a MySQL database](/dedibox-console/classic-hosting/how-to/create-mysql-database/), [manage your MySQL database with phpMyAdmin](/dedibox-console/classic-hosting/how-to/manage-mysql-database-phpmyadmin/) or [delete your MySQL database](/dedibox-console/classic-hosting/how-to/delete-mysql-database/). You can also [create](/dedibox-console/classic-hosting/how-to/create-postgresql-database/), [manage](/dedibox-console/classic-hosting/how-to/manage-postgresql-database-adminer/) or [delete](/dedibox-console/classic-hosting/how-to/delete-postgresql-database/) PostgreSQL databases. +You can [create a MySQL database](/classic-hosting/how-to/create-mysql-database/), [manage your MySQL database with phpMyAdmin](/classic-hosting/how-to/manage-mysql-database-phpmyadmin/) or [delete your MySQL database](/classic-hosting/how-to/delete-mysql-database/). You can also [create](/classic-hosting/how-to/create-postgresql-database/), [manage](/classic-hosting/how-to/manage-postgresql-database-adminer/) or [delete](/classic-hosting/how-to/delete-postgresql-database/) PostgreSQL databases. See our documentation on [upgrading a Database for PostgreSQL](/tutorials/upgrade-managed-postgresql-database/). @@ -79,7 +79,7 @@ Then import the backup into your Scaleway Databases for `MySQL`: ## Which PostgreSQL extensions are available? -Refer to our dedicated [PostgreSQL extentions reference page](/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions) for a list of all available extensions and more details about each one. +Refer to our dedicated [PostgreSQL extentions reference page](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) for a list of all available extensions and more details about each one. ## How do I back up my database? @@ -96,7 +96,7 @@ The idea is to offer the best performance to our users by reducing latency betwe ## What is the Private Networks feature for Database Instances? -[Private Networks](/network/public-gateways/quickstart/) allow you to enhance the security of your system architecture by isolating it from the internet. +[Private Networks](/public-gateways/quickstart/) allow you to enhance the security of your system architecture by isolating it from the internet. This feature introduces a significant change in the architecture of Scaleway's Databases: when using Private Networks, your application connects directly to your Database nodes, without going through a Load Balancer. This improves performance by reducing the latency between your nodes. It also increases the security of your databases, since Instances in your Private Network can connect directly to your Database Instance, without passing through the public internet. @@ -131,8 +131,8 @@ Database Instances supports IP provisioning using IPAM. With this mode, a privat No, the second node created when you activate the HA on your Managed Database Instance is a hot standby. This node allows a fast failover in case of issues on the primary node. -You can use the [Read Replica feature](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/). +You can use the [Read Replica feature](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/). ## If my main node becomes unavailable, is my Read Replica automatically promoted to the main node? -No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure. \ No newline at end of file +No. To promote a Read Replica to the main node, follow the [How to promote a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) procedure. \ No newline at end of file diff --git a/faq/databases-for-redis.mdx b/faq/databases-for-redis.mdx index 07c6b4ff96..7d14e28198 100644 --- a/faq/databases-for-redis.mdx +++ b/faq/databases-for-redis.mdx @@ -14,7 +14,7 @@ productIcon: RedisProductIcon Managed Database for Redis™* is a low-latency caching solution. It allows you to easily set up a secure cache and lighten the load on your main database. Based on the in-memory data storage, Managed Database for Redis™ improves your application response time and helps you provide a better experience to your users. -Using Managed Database for Redis™ as a cache optimizes the speed of your requests as copies of the most frequently used data are stored in memory, making them accessible in milliseconds. [Learn more about Managed Database for Redis™](/managed-databases/redis/how-to/create-a-database-for-redis/). +Using Managed Database for Redis™ as a cache optimizes the speed of your requests as copies of the most frequently used data are stored in memory, making them accessible in milliseconds. [Learn more about Managed Database for Redis™](/managed-databases-for-redis/how-to/create-a-database-for-redis/). ## Why is it ideal for Cache usage? @@ -37,7 +37,7 @@ You can connect to your Managed Database for Redis™ using the IP address(es) a ## What is the Private Networks feature for Redis™ Database Instances? -[Private Networks](/network/public-gateways/quickstart/) allow you to increase the security of your databases since Instances in your Private Networks can directly be connected to your Redis™ Database Instance without passing through the public internet. +[Private Networks](/public-gateways/quickstart/) allow you to increase the security of your databases since Instances in your Private Networks can directly be connected to your Redis™ Database Instance without passing through the public internet. In standalone mode, you can attach Private Networks to your Redis™ Database Instances at the creation level or add a Private Networks endpoint to your existing Redis™ Database Instance from the console. @@ -95,9 +95,9 @@ The HA standby node is linked to the main node, using asynchronous replication. Yes. You can change the default username and password anytime via the Scaleway API or the CLI. -Refer to the [Managing the default user's username and password](/managed-databases/redis/api-cli/managing-username-and-password/) documentation page to learn how. +Refer to the [Managing the default user's username and password](/managed-databases-for-redis/api-cli/managing-username-and-password/) documentation page to learn how. -For more information, refer to the [Understanding default user permissions](/managed-databases/redis/reference-content/default-user-permissions/) documentation page. +For more information, refer to the [Understanding default user permissions](/managed-databases-for-redis/reference-content/default-user-permissions/) documentation page.
diff --git a/faq/dedibox-in-scaleway-console.mdx b/faq/dedibox-in-scaleway-console.mdx index 2f19574592..47e9aa4cd2 100644 --- a/faq/dedibox-in-scaleway-console.mdx +++ b/faq/dedibox-in-scaleway-console.mdx @@ -44,7 +44,7 @@ The account linking process takes about 5 minutes. This is the time required to ### To which Scaleway Organization can I link my Dedibox? -If you already have a Scaleway account, you must be the Owner of the [Organization](/identity-and-access-management/iam/concepts/#organization) you would like to link your Dedibox account to. You should also make sure that this Organization is based in the same country as your Dedibox account. If it is not the case, you should either create a new account, or [contact our support team](/console/account/how-to/open-a-support-ticket/) to change the country. +If you already have a Scaleway account, you must be the Owner of the [Organization](/iam/concepts/#organization) you would like to link your Dedibox account to. You should also make sure that this Organization is based in the same country as your Dedibox account. If it is not the case, you should either create a new account, or [contact our support team](/account/how-to/open-a-support-ticket/) to change the country. ## Functional coverage and console usage diff --git a/faq/domains-and-dns.mdx b/faq/domains-and-dns.mdx index a36be5bdc5..4116116c3d 100644 --- a/faq/domains-and-dns.mdx +++ b/faq/domains-and-dns.mdx @@ -51,7 +51,7 @@ If a domain name is unavailable, you can test a light variation of the desired n ## Is domain renewal automatic? No. You must renew your domain name before the end of its validity period. -If you enable the [auto-renew feature](/network/domains-and-dns/how-to/configure-autorenew/), your domain name will be automatically renewed. +If you enable the [auto-renew feature](/domains-and-dns/how-to/configure-autorenew/), your domain name will be automatically renewed. You will be notified by email 60 days before your domain name expires. Your domain name will then switch to the `late renew` status. diff --git a/faq/edge-services.mdx b/faq/edge-services.mdx index bfde116da4..b6505acccf 100644 --- a/faq/edge-services.mdx +++ b/faq/edge-services.mdx @@ -12,22 +12,22 @@ productIcon: EdgeServicesProductIcon ## What is Edge Services? -Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets. Creating Edge Services [pipelines](/network/edge-services/concepts/#pipeline) towards your Load Balancers or Object Storage buckets provides: --A [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and +Edge Services is a feature for Scaleway Load Balancers and Object Storage buckets. Creating Edge Services [pipelines](/edge-services/concepts/#pipeline) towards your Load Balancers or Object Storage buckets provides: +-A [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/edge-services/concepts/#origin), and - A customizable and secure endpoint for accessing content via Edge Services, which can be set to a subdomain of your choice and secured with an SSL/TLS certificate. ## Which products are compatible with Edge Services? -Edge Services is currently available for Scaleway [Object Storage buckets](/storage/object/) and Scaleway [Load Balancers](/network/load-balancer/). +Edge Services is currently available for Scaleway [Object Storage buckets](/object-storage/) and Scaleway [Load Balancers](/load-balancer/). ## How much does Edge Services cost? On November 1st 2024, Edge Services transitioned from Public Beta to General Availability, and became billable. Pricing is based on [monthly subscription plans](https://www.scaleway.com/en/pricing/network/#edge-services): three plans are available, each allowing a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate. -Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page. ## If I customize my Edge Services endpoint with my own domain, can it serve content over HTTPS? -Yes, if you choose to [customize your Edge Services endpoint with your own subdomain](/network/edge-services/how-to/configure-custom-domain/), you are prompted to generate or upload an SSL/TLS certificate for that subdomain so that Edge Services can serve content over HTTPS. This certificate can either be a Let's Encrypt certificate generated and managed by Scaleway, or you can import your own certificate. If you import your own certificate, it will be stored in Scaleway Secret Manager, and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/). \ No newline at end of file +Yes, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), you are prompted to generate or upload an SSL/TLS certificate for that subdomain so that Edge Services can serve content over HTTPS. This certificate can either be a Let's Encrypt certificate generated and managed by Scaleway, or you can import your own certificate. If you import your own certificate, it will be stored in Scaleway Secret Manager, and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/). \ No newline at end of file diff --git a/faq/elastic-metal.mdx b/faq/elastic-metal.mdx index 53248f4a46..425b3d9013 100644 --- a/faq/elastic-metal.mdx +++ b/faq/elastic-metal.mdx @@ -19,7 +19,7 @@ An Elastic Metal server is a 100%-dedicated machine without a hypervisor, availa With Elastic Metal, you get full control of the resources and applications installed on the server, for maximum performance and security. -Several operating systems are available for [automatic installation from the console](/bare-metal/elastic-metal/how-to/install-server/). +Several operating systems are available for [automatic installation from the console](/elastic-metal/how-to/install-server/). ### What is the difference between an Elastic Metal server and a Dedibox dedicated server? @@ -60,7 +60,7 @@ An hourly-billed dedicated server allows you to take advantage of both the flexi If you need a powerful server on a frequent and continual basis, you may find that monthly billing is more suitable for you. In this case, you will get a more advantageous price, while still benefiting from full integration with our public cloud to manage sporadic exceptional workloads or peak periods. - You must [create](/bare-metal/elastic-metal/how-to/create-server/) and [reinstall](/bare-metal/elastic-metal/how-to/reinstall-server/) a new Elastic Metal server to switch from monthly to hourly billing, and vice versa. + You must [create](/elastic-metal/how-to/create-server/) and [reinstall](/elastic-metal/how-to/reinstall-server/) a new Elastic Metal server to switch from monthly to hourly billing, and vice versa. ### What is the loyalty reward and how do I use it? @@ -69,7 +69,7 @@ The loyalty reward is a cloud service voucher in the sum of the commitment fees You are entitled to it if you have a monthly Elastic Metal server that is up and running for 12 consecutive months without termination. You have the right to one voucher per physical server, and it can be used for all Scaleway Cloud products, apart from Elastic Metal servers and their associated options. -The loyalty reward voucher is valid for six months and automatically added to your Scaleway account. [Learn more about how to get and use a loyalty reward](/bare-metal/elastic-metal/how-to/get-use-loyalty-reward/). +The loyalty reward voucher is valid for six months and automatically added to your Scaleway account. [Learn more about how to get and use a loyalty reward](/elastic-metal/how-to/get-use-loyalty-reward/). ### Can I get a refund of the commitment fees after 12 months of keeping the server? @@ -112,7 +112,7 @@ Yes, you have the flexibility to modify the bandwidth available for your Elastic Each Elastic Metal dedicated server comes with an allocated bandwidth allowance. However, you can easily increase or decrease this bandwidth through your Scaleway console at any time. Scaleway offers high-performance bandwidth options of up to 25Gbps per server, all of which include unlimited traffic. -For step-by-step instructions on how to modify the available bandwidth for your Elastic Metal server, refer to our documentation on [how to modify the available bandwidth for an Elastic Metal server](/bare-metal/elastic-metal/how-to/adjust-available-bandwidth/). +For step-by-step instructions on how to modify the available bandwidth for your Elastic Metal server, refer to our documentation on [how to modify the available bandwidth for an Elastic Metal server](/elastic-metal/how-to/adjust-available-bandwidth/). The maximum available bandwidth for each Elastic Metal server is determined by the physical conditions of the network card installed, as specified in the offer description. @@ -120,13 +120,13 @@ For step-by-step instructions on how to modify the available bandwidth for your ### How can I reinstall an Elastic Metal server? -You can reinstall an Elastic Metal server with a few clicks at any time, [directly from your Scaleway console](/bare-metal/elastic-metal/how-to/install-server/). +You can reinstall an Elastic Metal server with a few clicks at any time, [directly from your Scaleway console](/elastic-metal/how-to/install-server/). ### How do I back up an Elastic Metal server? Elastic Metal servers must be backed up differently from Instances, which have the snapshot feature. -The first level is to back up your Elastic Metal server's data and configuration. This can be done by exporting it to an [Object Storage bucket](/storage/object/quickstart/). You can check our tutorial on [backing up servers to Object Storage](/tutorials/backup-dedicated-server-s3-duplicity/) for more information. +The first level is to back up your Elastic Metal server's data and configuration. This can be done by exporting it to an [Object Storage bucket](/object-storage/quickstart/). You can check our tutorial on [backing up servers to Object Storage](/tutorials/backup-dedicated-server-s3-duplicity/) for more information. The security and redundancy of your data can also be ensured by a cluster configuration of your application. @@ -146,7 +146,7 @@ Make sure to back up your data before deleting a server, as it cannot be recover ### How many flexible IPs can I have per Elastic Metal server? -You can have up to 64 [flexible IPs](/bare-metal/elastic-metal/how-to/order-flexible-ip/) per Elastic Metal server. +You can have up to 64 [flexible IPs](/elastic-metal/how-to/order-flexible-ip/) per Elastic Metal server. ### Can I move flexible IPs between my Elastic Metal servers and Instances? diff --git a/faq/iam.mdx b/faq/iam.mdx index c7fa642577..4341396643 100644 --- a/faq/iam.mdx +++ b/faq/iam.mdx @@ -24,13 +24,13 @@ With IAM you can manage access for each Scaleway product, but at the Project lev ## Which products work with IAM? IAM enables you to manage access control to all Scaleway products. -You may decide yourself whether to leave these automatically-created IAM applications and policies in place, [edit the policies](/identity-and-access-management/iam/how-to/manage-policies/) to change permissions as required, or [generate new API keys for individual users](/identity-and-access-management/iam/how-to/create-api-keys/) to define rights per-user via the creation of [new policies](/identity-and-access-management/iam/how-to/create-policy/) for those users. +You may decide yourself whether to leave these automatically-created IAM applications and policies in place, [edit the policies](/iam/how-to/manage-policies/) to change permissions as required, or [generate new API keys for individual users](/iam/how-to/create-api-keys/) to define rights per-user via the creation of [new policies](/iam/how-to/create-policy/) for those users. ## What are applications, and why do I need them? Applications represent the identity of non-human users (such as a CI pipeline, a custom script, or a Terraform provider). They are used to attach permissions and API keys to these operations - without being linked to specific users and their own rights. ## Why do I have to select a preferred Project for Object Storage when I create an API key? -Due to limitations on the Object Storage API, API keys cannot perform Object Storage actions on several projects at the same time. Whenever you generate an API key that will be used on Object Storage, you must specify a preferred project where the API key will be able to perform actions. For more information, refer to the [Using IAM API keys with Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) documentation page. +Due to limitations on the Object Storage API, API keys cannot perform Object Storage actions on several projects at the same time. Whenever you generate an API key that will be used on Object Storage, you must specify a preferred project where the API key will be able to perform actions. For more information, refer to the [Using IAM API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) documentation page. ## Why and how should I rotate API keys? API keys are credentials that grant access to resources in Scaleway Organizations. It is good practice to change your credentials on a regular basis to reduce the risk of security breaches. diff --git a/faq/instances.mdx b/faq/instances.mdx index 8e60475145..1c88aa53be 100644 --- a/faq/instances.mdx +++ b/faq/instances.mdx @@ -15,9 +15,9 @@ productIcon: InstanceProductIcon ### How can I create an image? -You must [create at least one snapshot](/compute/instances/how-to/create-a-snapshot/) before creating an image. +You must [create at least one snapshot](/instances/how-to/create-a-snapshot/) before creating an image. -See the documentation on [creating an image from scratch](/compute/instances/how-to/create-image-from-snapshot/). +See the documentation on [creating an image from scratch](/instances/how-to/create-image-from-snapshot/). ### What is ImageHub? @@ -59,7 +59,7 @@ You can change the storage type and flexible IP after the Instance creation, whi * Prices indicated below do not include storage or IP. - * *All regions refer to `PAR1`, `PAR2`, `AMS1`, `AMS2`, `AMS3`, `WAW1`, `WAW2`, and `WAW3`. Some ranges might not be available in some of these regions. Check the [Instances availability guide](/console/account/reference-content/products-availability/) to discover where each Instance type is available. + * *All regions refer to `PAR1`, `PAR2`, `AMS1`, `AMS2`, `AMS3`, `WAW1`, `WAW2`, and `WAW3`. Some ranges might not be available in some of these regions. Check the [Instances availability guide](/account/reference-content/products-availability/) to discover where each Instance type is available. * PAR3 prices are shown separately. @@ -164,7 +164,7 @@ You can change the storage type and flexible IP after the Instance creation, whi ¹= Billed per minute. - `PLAY2-PICO` and `DEV1-S` Instances are not available for [Kubernetes Kapsule](/containers/kubernetes/quickstart/) due to RAM constraints. + `PLAY2-PICO` and `DEV1-S` Instances are not available for [Kubernetes Kapsule](/kubernetes/quickstart/) due to RAM constraints. @@ -227,24 +227,24 @@ Yes, each Instance has two DNS hostnames associated with it: * A **public DNS hostname**: `.pub.instances.scw.cloud` * A **private DNS hostname**: `.priv.instances.scw.cloud` -Both are automatically updated when the Instance moves to another hypervisor, also changing its IPv6 and private IPv4. You can either use these hostnames directly or configure a [CNAME record](/dedibox-network/dns/concepts/#resource-records) linking to it. +Both are automatically updated when the Instance moves to another hypervisor, also changing its IPv6 and private IPv4. You can either use these hostnames directly or configure a [CNAME record](/dedibox-dns/concepts/#resource-records) linking to it. ### Can I migrate from a first-generation DEV1 Instance to a PLAY2 Instance? -Yes. Refer to the [changing the commercial type of an Instance](/compute/instances/api-cli/migrating-instances/) documentation. +Yes. Refer to the [changing the commercial type of an Instance](/instances/api-cli/migrating-instances/) documentation. ### Can I migrate from my first-generation GP1 Instance to a PRO2 Instance? -Yes. Refer to the [changing the commercial type of an Instance](/compute/instances/api-cli/migrating-instances/) documentation. +Yes. Refer to the [changing the commercial type of an Instance](/instances/api-cli/migrating-instances/) documentation. ### Can I boot my Instance from a Block Storage volume? Yes. When creating an Instance, you can select Block Storage as a system volume type. This allows you to reboot Instances from the block volume on which your OS is stored. -You can also add a Block volume after creating an Instance and [choosing it as the boot volume](/compute/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). +You can also add a Block volume after creating an Instance and [choosing it as the boot volume](/instances/how-to/use-boot-modes/#how-to-change-the-boot-volume). ## Offers and availability @@ -258,7 +258,7 @@ You are free to bootstrap your own distribution. ### Which Linux distributions are available for Enterprise Instances? -We provide a wide range of different Linux distributions and InstantApps for Instances. Refer to [Scaleway Instance OS images and InstantApps](/compute/instances/reference-content/images-and-instantapps/) for a complete list of all available OSes and InstantApps. +We provide a wide range of different Linux distributions and InstantApps for Instances. Refer to [Scaleway Instance OS images and InstantApps](/instances/reference-content/images-and-instantapps/) for a complete list of all available OSes and InstantApps. ### What are the differences between ENT1 and POP2 Instances? @@ -276,7 +276,7 @@ We recommend choosing POP2 Instances for most general workloads unless your spec Scaleway offers different Instance ranges in all regions: Paris (France), Amsterdam (Netherlands), and Warsaw (Poland). -Check the [Instances availability guide](/console/account/reference-content/products-availability/) to discover where each Instance type is available. +Check the [Instances availability guide](/account/reference-content/products-availability/) to discover where each Instance type is available. ### What makes FR-PAR-2 a sustainable Region? @@ -289,11 +289,11 @@ This Region is entirely powered by renewable (hydraulic) energy. It also has an ### Which Instances support IP Mobility? -All ranges are compatible except for Instances using the “bootscript” feature, which has [reached its end of life (EOL)](/compute/instances/troubleshooting/bootscript-eol/). +All ranges are compatible except for Instances using the “bootscript” feature, which has [reached its end of life (EOL)](/instances/troubleshooting/bootscript-eol/). ### Can I enable “Routed IP” on my bootscript Instance? -Instances using a bootscript are not compatible with Routed IPs. As the bootscript feature has reached its end of life (EOL), refer to [this tutorial](/compute/instances/troubleshooting/bootscript-eol/) for migration instructions. +Instances using a bootscript are not compatible with Routed IPs. As the bootscript feature has reached its end of life (EOL), refer to [this tutorial](/instances/troubleshooting/bootscript-eol/) for migration instructions. ### Can I revert the migration to “Routed IP”? @@ -323,4 +323,4 @@ Yes, they can communicate with each other using their public IPs. Currently, additional routed IPv6 addresses do not autoconfigure on CentOS 7, 8, 9, Alma 8, 9, Rocky 8, 9 after migration. Additional routed IPv4 and IPv6 addresses are not autoconfigured post-migration on Ubuntu 20.04 Focal. However, the primary IPv6 continues to be configured via SLAAC. These limitations are currently being addressed. -For detailed migration steps, refer to our [migration guide](/compute/instances/how-to/migrate-routed-ips/). If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our [troubleshooting guide](/compute/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). +For detailed migration steps, refer to our [migration guide](/instances/how-to/migrate-routed-ips/). If you encounter connectivity issues with Ubuntu Focal Instances having multiple public IPs, consult our [troubleshooting guide](/instances/troubleshooting/fix-unreachable-focal-with-two-public-ips/). diff --git a/faq/iothub.mdx b/faq/iothub.mdx index 8db61f5607..b1c4e5ee79 100644 --- a/faq/iothub.mdx +++ b/faq/iothub.mdx @@ -19,10 +19,10 @@ Connected devices is the common name for all devices able to communicate over th All kinds of connected devices supporting the MQTT protocol can be connected to IoT Hub. MQTT through WebSockets is also supported. There is no limitation to specific vendors. To learn more about what is a **Hub**, what is a **Device** and what is a **Route**, head over to our dedicated pages: -* [Scaleway IoT Hub Overview](/managed-services/iot-hub/quickstart/) -* [Hub](/managed-services/iot-hub/reference-content/hubs/) -* [Device](/managed-services/iot-hub/concepts/#device) -* [Route](/managed-services/iot-hub/concepts/#routes) +* [Scaleway IoT Hub Overview](/iot-hub/quickstart/) +* [Hub](/iot-hub/reference-content/hubs/) +* [Device](/iot-hub/concepts/#device) +* [Route](/iot-hub/concepts/#routes) IoT Hub is only available at PAR1 (Paris, France) for the moment, other regions are planned. diff --git a/faq/ipam.mdx b/faq/ipam.mdx index 29dd7a016b..824de30b48 100644 --- a/faq/ipam.mdx +++ b/faq/ipam.mdx @@ -16,9 +16,9 @@ productIcon: IpamProductIcon ## What can I do with IPAM? -**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/network/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources. +**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources. -The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging and filtering all your [private IP addresses](/network/ipam/concepts/#private-ip-address). You can also [reserve](/network/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach a specified resource to the network. +The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging and filtering all your [private IP addresses](/ipam/concepts/#private-ip-address). You can also [reserve](/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach a specified resource to the network. Management of public (flexible) IP addresses with IPAM is planned for the future. @@ -28,4 +28,4 @@ Currently, the Scaleway console only supports attachment with a reserved IP for ## Can I use a reserved private IP with a virtual machine hosted on my Elastic Metal server? -Yes, this functionality is now available via the Scaleway console and API. See [how to reserve a private IP address with an attached MAC address](/network/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file +Yes, this functionality is now available via the Scaleway console and API. See [how to reserve a private IP address with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file diff --git a/faq/kubernetes.mdx b/faq/kubernetes.mdx index 67129297d6..d487230db6 100644 --- a/faq/kubernetes.mdx +++ b/faq/kubernetes.mdx @@ -20,13 +20,13 @@ With Scaleway, you can choose between Kubernetes Kapsule and Kosmos, and profit ### What is a managed Kubernetes service? In the context of Scaleway, a managed Kubernetes service refers to the Kapsule and Kosmos products, with Scaleway handling the management and maintenance of the Kubernetes control plane, along with all the crucial core components required for the proper operation of the Kubernetes cluster. -For more information, refer to the [managed Kubernetes service definition](/containers/kubernetes/reference-content/managed-kubernetes-service-definition/). +For more information, refer to the [managed Kubernetes service definition](/kubernetes/reference-content/managed-kubernetes-service-definition/). ### What is the difference between Kubernetes Kapsule and Kosmos? The primary difference between them is that **Kapsule** clusters are composed solely of Scaleway Instances. On the other hand, a **Kosmos** cluster is a managed multi-cloud Kubernetes engine that allows you to connect Instances and virtual or dedicated servers from any cloud provider to a single managed Control-Plane. -For more information, refer to our dedicated documentation [Understanding differences between the Kapsule and Kosmos managed Kubernetes services](/containers/kubernetes/reference-content/understanding-differences-kapsule-kosmos/). +For more information, refer to our dedicated documentation [Understanding differences between the Kapsule and Kosmos managed Kubernetes services](/kubernetes/reference-content/understanding-differences-kapsule-kosmos/). ## Billing and pricing @@ -93,4 +93,4 @@ Depending on the type of node selected for your pool, one or two types of volume ### How do I connect to my nodes using SSH? By default, an SSH server is installed and configured on the nodes of your Kubernetes Kapsule cluster. To ensure the correct behavior of your cluster, it is not recommended to perform actions directly on the nodes. SSH access is provided for debugging only and all actions and configurations should be done using Kubernetes (from the Scaleway console, `kubectl` command, or Scaleway Kapsule `APIs`). -To improve the security of your Kapsule cluster, you can disable this SSH server on your nodes by following the documentation on [how to enable or disable SSH on Kubernetes Kapsule nodes](/containers/kubernetes/how-to/enable-disable-ssh/). \ No newline at end of file +To improve the security of your Kapsule cluster, you can disable this SSH server on your nodes by following the documentation on [how to enable or disable SSH on Kubernetes Kapsule nodes](/kubernetes/how-to/enable-disable-ssh/). \ No newline at end of file diff --git a/faq/loadbalancer.mdx b/faq/loadbalancer.mdx index 652f5cb321..084cb38e57 100644 --- a/faq/loadbalancer.mdx +++ b/faq/loadbalancer.mdx @@ -20,12 +20,12 @@ A Load Balancer can be used as frontend for any Instance type, even if it is not ## Can I use Load Balancers with other products? Yes: Check out our documentation on: -- [Using a Load Balancer to expose a Kubernetes Kapsule](/containers/kubernetes/reference-content/kubernetes-load-balancer/). -- [Setting up caching for your Load Balancer via Edge Services](/network/edge-services/quickstart/) +- [Using a Load Balancer to expose a Kubernetes Kapsule](/kubernetes/reference-content/kubernetes-load-balancer/). +- [Setting up caching for your Load Balancer via Edge Services](/edge-services/quickstart/) ## What is a flexible IP address? -By default, each [public](/network/load-balancer/concepts/#accessibility) Load Balancer is created automatically with a flexible IPv4 address. This is a public IP that can be held in your account even after you delete your Load Balancer. You can optionally also add an IPv6 address. +By default, each [public](/load-balancer/concepts/#accessibility) Load Balancer is created automatically with a flexible IPv4 address. This is a public IP that can be held in your account even after you delete your Load Balancer. You can optionally also add an IPv6 address. Your frontend listens to your Load Balancer's public flexible IP address. In case of a failure of the Load Balancer, a replica Load Balancer is immediately spawned and deployed, and the IP address is automatically rerouted to this replica. This is done automatically, by the Load Balancer control subsystems. @@ -54,7 +54,7 @@ Multi-cloud means that you can backend servers that are neither Instances, nor E Unlike the multi-cloud offers, non-multi-cloud offers allow you to add only backend servers part of the Scaleway ecosystems which include Instances, Elastic Metal servers, and Dedibox dedicated servers. -To take advantage of multi-cloud, you must choose a compatible Load Balancer offer type when creating your Load Balancer, or [resize](/network/load-balancer/how-to/resize-lb/) to such an offer afterwards. +To take advantage of multi-cloud, you must choose a compatible Load Balancer offer type when creating your Load Balancer, or [resize](/load-balancer/how-to/resize-lb/) to such an offer afterwards. ## What are the communication protocols currently supported? @@ -62,11 +62,11 @@ All protocols based on `TCP` are supported. This includes `database`, `HTTP`, `L ## Is it possible to add security to restrict access to a URL or port on the Load Balancer? -Yes, you can restrict the use of a `TCP` port or `HTTP` URL using ACLs. Find more information in our [ACL documentation](/network/load-balancer/how-to/create-manage-acls/). +Yes, you can restrict the use of a `TCP` port or `HTTP` URL using ACLs. Find more information in our [ACL documentation](/load-balancer/how-to/create-manage-acls/). ## What is a route? -Once you have created one or more Load Balancers, you can create routes. Routes indicate how to direct incoming connections to certain backends based on various parameters such as IP addresses, path, host, etc. You can choose the frontend to which the rule should apply, and the backend it should direct to. Routes can be based on **Server Name Indication** (SNI) for TCP Load Balancers, or the **HTTP Host header** for HTTP Load Balancers. Check out our [dedicated documentation](/network/load-balancer/how-to/create-manage-routes/) for more information. +Once you have created one or more Load Balancers, you can create routes. Routes indicate how to direct incoming connections to certain backends based on various parameters such as IP addresses, path, host, etc. You can choose the frontend to which the rule should apply, and the backend it should direct to. Routes can be based on **Server Name Indication** (SNI) for TCP Load Balancers, or the **HTTP Host header** for HTTP Load Balancers. Check out our [dedicated documentation](/load-balancer/how-to/create-manage-routes/) for more information. ## Can I add multiple backends to a frontend? @@ -74,8 +74,8 @@ Yes, this is possible using routes. When you create a frontend, you must select ## What is a health check? -A health check is one of the core concepts for a well-functioning Load Balancer. It is a predefined request which periodically checks whether the server is in a healthy state or an unhealthy state. Only servers that respond correctly to the health check receive client requests. When the Load Balancer determines that an Instance is unhealthy, it stops routing requests to that Instance. Currently, our Load Balancer supports `TCP` and `TCP-based` health checks such as `HTTP(S)`, `LDAP`, `REDIS`, etc. [Find out more about health checks](/network/load-balancer/reference-content/configuring-health-checks/). +A health check is one of the core concepts for a well-functioning Load Balancer. It is a predefined request which periodically checks whether the server is in a healthy state or an unhealthy state. Only servers that respond correctly to the health check receive client requests. When the Load Balancer determines that an Instance is unhealthy, it stops routing requests to that Instance. Currently, our Load Balancer supports `TCP` and `TCP-based` health checks such as `HTTP(S)`, `LDAP`, `REDIS`, etc. [Find out more about health checks](/load-balancer/reference-content/configuring-health-checks/). ## Can I set up a caching service for my load balanced application? -Yes, this is possible with Scaleway's [Edge Services](/network/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin. \ No newline at end of file +Yes, this is possible with Scaleway's [Edge Services](/edge-services/) product, currently in Public Beta. By creating an Edge Services pipeline for your Load Balancer, you can access Edge Services caching service reduce load on your origin. \ No newline at end of file diff --git a/faq/messaging-and-queuing.mdx b/faq/messaging-and-queuing.mdx index b6bfee9f12..3fb2f5f958 100644 --- a/faq/messaging-and-queuing.mdx +++ b/faq/messaging-and-queuing.mdx @@ -16,11 +16,11 @@ These are three distinct managed message broker tools offered by Scaleway, based ## What are NATS, SNS and SQS? -NATS, SNS and SQS are all messaging protocols used by the Scaleway NATS, Queues, and Topics and Events products. You can find out more about these protocols, and other essential concepts, on our dedicated [concepts page](/serverless/messaging/concepts/). +NATS, SNS and SQS are all messaging protocols used by the Scaleway NATS, Queues, and Topics and Events products. You can find out more about these protocols, and other essential concepts, on our dedicated [concepts page](/messaging/concepts/). ## Is the Scaleway Queues gateway compatible with my application, framework or tool? -We currently implement the API endpoints listed [here](/serverless/messaging/reference-content/sqs-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including KEDA and Symfony. Note that you need to specify both Regions and URL to ensure compatibility. +We currently implement the API endpoints listed [here](/messaging/reference-content/sqs-support/), which makes Scaleway Queues compatible with the AWS SDK as well as many other tools and frameworks including KEDA and Symfony. Note that you need to specify both Regions and URL to ensure compatibility. ## Does Scaleway Topics and Events support all SNS features? @@ -29,7 +29,7 @@ The following subscriber types are supported: - Serverless Functions and Containers - Scaleway Queues queues -For more details on supported and unsupported Topics and Events features, see our [dedicated page](/serverless/messaging/reference-content/sns-support/). +For more details on supported and unsupported Topics and Events features, see our [dedicated page](/messaging/reference-content/sns-support/). ## Can I configure Scaleway NATS via Terraform? @@ -39,8 +39,8 @@ Yes, check out our [tutorial](https://registry.terraform.io/providers/scaleway/s Billing is based on: -- For NATS: [Stream volume](/serverless/messaging/concepts/#stream-volume) (the total sum of each message's size going through the stream) and [stream persistence](/serverless/messaging/concepts/#stream-persistence) (the total amount of data stored * duration) -- For Queues: [Queue volume](/serverless/messaging/concepts/#queue-volume) (the total sum of each message's size going through the queue) -- For Topics and Events : [Topic Volume](/serverless/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions) +- For NATS: [Stream volume](/messaging/concepts/#stream-volume) (the total sum of each message's size going through the stream) and [stream persistence](/messaging/concepts/#stream-persistence) (the total amount of data stored * duration) +- For Queues: [Queue volume](/messaging/concepts/#queue-volume) (the total sum of each message's size going through the queue) +- For Topics and Events : [Topic Volume](/messaging/concepts/#queue-volume)(the total sum of each message's size going out from the topic to the subscriptions) For full pricing details, see our [dedicated pricing page](https://www.scaleway.com/en/pricing/). \ No newline at end of file diff --git a/faq/objectstorage.mdx b/faq/objectstorage.mdx index d32608e67d..111cecaff8 100644 --- a/faq/objectstorage.mdx +++ b/faq/objectstorage.mdx @@ -43,7 +43,7 @@ Refer to our [Cold Storage FAQ](/faq/objectstorage/#cold-storage) for more infor ## How can I benefit from the Object Storage free trial? -As a new user, you benefit from 750 GB of free [Multi-AZ class storage](/storage/object/concepts/#storage-class) for buckets in your Organization, across all [regions](/storage/object/concepts/#region-and-availability-zone), for 90 days. +As a new user, you benefit from 750 GB of free [Multi-AZ class storage](/object-storage/concepts/#storage-class) for buckets in your Organization, across all [regions](/object-storage/concepts/#region-and-availability-zone), for 90 days. If you exceed 750 GB of Multi-AZ storage during the free trial period, you will only be billed for the excess data. @@ -57,7 +57,7 @@ To be eligible for this offer, you must have never used the Standard Multi-AZ cl ## How can I monitor my Object Storage consumption? -You can monitor your Object Storage metrics and logs using [Scaleway Cockpit](/observability/cockpit/quickstart/). Cockpit is available in all [regions](/storage/object/concepts/#region-and-availability-zone) for Object Storage. Refer to our dedicated [documentation](/storage/object/how-to/monitor-consumption/) for more information. +You can monitor your Object Storage metrics and logs using [Scaleway Cockpit](/cockpit/quickstart/). Cockpit is available in all [regions](/object-storage/concepts/#region-and-availability-zone) for Object Storage. Refer to our dedicated [documentation](/object-storage/how-to/monitor-consumption/) for more information. ## Is there a limitation in the bucket name? @@ -84,11 +84,11 @@ The `“Bucket already exists”` error message is triggered when the name you i The Object Storage product delivers content for your applications and users from a single point in the region of your choice. Our platform is designed to deliver very high performance, up to 100 Gbit/sec per bucket per region without performance loss. -If you want to deliver your content to several geographic locations with minimal latency, you can use Scaleway's [Edge Services](/storage/object/how-to/get-started-edge-services/) directly from your bucket. +If you want to deliver your content to several geographic locations with minimal latency, you can use Scaleway's [Edge Services](/object-storage/how-to/get-started-edge-services/) directly from your bucket. ## Can I access my files via HTTPS? -Yes, you can access your files via HTTPS by creating a public link from the Scaleway console. Follow the [How to access my files via HTTPS](/storage/object/how-to/access-objects-via-https/) documentation to do so. +Yes, you can access your files via HTTPS by creating a public link from the Scaleway console. Follow the [How to access my files via HTTPS](/object-storage/how-to/access-objects-via-https/) documentation to do so. ## Can I change HTTP headers during upload? @@ -101,7 +101,7 @@ aws s3 cp s3://BUCKET/ s3://BUCKET/ --recursive --acl public-read --metadata-dir ## Can I make an object public? -Yes. All objects are private by default, but you can change their visibility to public any time. Follow the [How to manage object visibility](/storage/object/how-to/manage-object-visibility/) documentation to do so. +Yes. All objects are private by default, but you can change their visibility to public any time. Follow the [How to manage object visibility](/object-storage/how-to/manage-object-visibility/) documentation to do so. ## How can I upload large objects? @@ -113,7 +113,7 @@ The following technical specifications apply to multipart uploads: - 5 MB to 5 GB per part (except for the last one) - Each object stores up to 5 TB -For more information, refer to the [documentation](/storage/object/api-cli/multipart-uploads/). +For more information, refer to the [documentation](/object-storage/api-cli/multipart-uploads/). ## Does my bucket remain available after deletion? @@ -135,7 +135,7 @@ Examples: ## Will closing my web browser after requesting to delete a bucket stop the deletion process? -No. After you click the button to delete a bucket in the Scaleway console, the request is processed in our backend, and does not depend on your web browser. For more information on how to delete a bucket, refer to the [dedicated documentation](/storage/object/how-to/delete-a-bucket/). +No. After you click the button to delete a bucket in the Scaleway console, the request is processed in our backend, and does not depend on your web browser. For more information on how to delete a bucket, refer to the [dedicated documentation](/object-storage/how-to/delete-a-bucket/). ## Can I create a bucket with the same name as a previously deleted one? @@ -151,11 +151,11 @@ Each Scaleway Project can use up to 250 TB of Object Storage resources. If you w Scaleway offers three storage classes: -- `Standard (Multi-AZ)`: your data is secured by distributing it across three different [Availability Zones (AZ)](/storage/object/concepts/#region-and-availability-zone). In the event of a complete data center failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one data center per AZ, three AZs per region). The Standard class is available in [all regions](/storage/object/concepts/#region-and-availability-zone). +- `Standard (Multi-AZ)`: your data is secured by distributing it across three different [Availability Zones (AZ)](/object-storage/concepts/#region-and-availability-zone). In the event of a complete data center failure in an AZ, we are still able to rebuild your data and make it accessible. This is the system we call Multi-AZ (one data center per AZ, three AZs per region). The Standard class is available in [all regions](/object-storage/concepts/#region-and-availability-zone). -- `One Zone - Infrequent Access`: your data is stored across three different racks in a single [Availability Zone (AZ)](/storage/object/concepts/#region-and-availability-zone). This storage class is best suited for secondary backups and recreatable data. The One Zone - IA class is available in [all regions](/storage/object/concepts/#region-and-availability-zone). +- `One Zone - Infrequent Access`: your data is stored across three different racks in a single [Availability Zone (AZ)](/object-storage/concepts/#region-and-availability-zone). This storage class is best suited for secondary backups and recreatable data. The One Zone - IA class is available in [all regions](/object-storage/concepts/#region-and-availability-zone). -- `Glacier`: your data is archived and must be restored before being used. The Glacier storage class is only available in `fr-par` and `nl-ams` [regions](/storage/object/concepts/#region-and-availability-zone). Refer to our [Cold storage FAQ](/faq/objectstorage/#cold-storage) for more information. +- `Glacier`: your data is archived and must be restored before being used. The Glacier storage class is only available in `fr-par` and `nl-ams` [regions](/object-storage/concepts/#region-and-availability-zone). Refer to our [Cold storage FAQ](/faq/objectstorage/#cold-storage) for more information. ## What happens when Multi-AZ is launched in a region? @@ -165,11 +165,11 @@ New objects created after the Multi-AZ launch can have the `Standard (Multi-AZ)` ## Will these new storage classes affect how I use my buckets? -No, any objects you upload into your buckets are added as Standard class objects by default, just as before. If you want to transfer your objects to One Zone - IA or Glacier you can do so manually or set up [lifecycle rules](/storage/object/api-cli/lifecycle-rules-api/). +No, any objects you upload into your buckets are added as Standard class objects by default, just as before. If you want to transfer your objects to One Zone - IA or Glacier you can do so manually or set up [lifecycle rules](/object-storage/api-cli/lifecycle-rules-api/). ## I do not want to use the new Standard (Multi-AZ) class. Can I still use the old class? -No, you cannot use the old `Standard` class. You must use the [One Zone - IA class](/storage/object/concepts/#storage-class), which has the same behavior as the old Standard class. +No, you cannot use the old `Standard` class. You must use the [One Zone - IA class](/object-storage/concepts/#storage-class), which has the same behavior as the old Standard class. ## Can I create a lifecycle rule to restore objects from Glacier class to One Zone - IA? @@ -185,7 +185,7 @@ No, the rules for using Glacier class remain the same and your data is still hos ## Can I migrate my existing data to the new Multi-AZ Standard class? -Yes, you simply need to [edit the storage class](/storage/object/how-to/edit-storage-class/) of your objects. +Yes, you simply need to [edit the storage class](/object-storage/how-to/edit-storage-class/) of your objects. ### Cold storage @@ -222,17 +222,17 @@ An object stored in Glacier class is listed but cannot be downloaded instantly. We recommend that you use Glacier to archive data that you may need only once or twice within a decade. - The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). + The time it takes to restore an object depends on the size of the object and if [multipart](/object-storage/concepts/#multipart-uploads) is configured. It can take anywhere from a few minutes to 24 hours for restore to start (for objects larger than 1 MB). Unfortunately, we are unable to provide estimates of how long data retrieval takes for each use case. To facilitate restoration and ensure the fast restitution of your data, we recommend you use average-sized files (larger than 1 MB). -Find out [how to restore an object from Glacier](/storage/object/how-to/restore-an-object-from-glacier/) on our dedicated page. +Find out [how to restore an object from Glacier](/object-storage/how-to/restore-an-object-from-glacier/) on our dedicated page. ## Can I upload an object directly to Glacier? -Yes, you can select the storage class (`Standard`, `One Zone IA`, or `GLACIER`) when uploading objects using the Scaleway console. It is also possible to do so using the API. For more information, refer to our [dedicated documentation](/storage/object/how-to/edit-storage-class/). +Yes, you can select the storage class (`Standard`, `One Zone IA`, or `GLACIER`) when uploading objects using the Scaleway console. It is also possible to do so using the API. For more information, refer to our [dedicated documentation](/object-storage/how-to/edit-storage-class/). ## Why are Glacier objects stored in Paris DC4? Is it accessible from buckets in all locations? @@ -277,10 +277,10 @@ Lifecycle management features meet both of these requirements by allowing you to ## What is the maximum data volume and object size supported by Scaleway Glacier? There is no maximum data size, Glacier accepts an unlimited number of objects up to 5 TB each. -Large objects can be uploaded using [multipart uploads](/storage/object/api-cli/multipart-uploads/). +Large objects can be uploaded using [multipart uploads](/object-storage/api-cli/multipart-uploads/). ## Can I change the storage class of an entire bucket from Standard to Glacier? -Yes, a best practice is to create a [lifecycle rule](/storage/object/how-to/manage-lifecycle-rules/) targeting all objects in the bucket, or using a filter with an empty prefix. +Yes, a best practice is to create a [lifecycle rule](/object-storage/how-to/manage-lifecycle-rules/) targeting all objects in the bucket, or using a filter with an empty prefix. In this case, all files contained within the selected bucket will have their storage class altered automatically on the dates stipulated by you. However, due to some restrictions on Amazon's S3 protocol, a lifecycle rule cannot be created to modify the storage class from Glacier to Standard. \ No newline at end of file diff --git a/faq/private-networks.mdx b/faq/private-networks.mdx index c31f32ed0f..f5f7687375 100644 --- a/faq/private-networks.mdx +++ b/faq/private-networks.mdx @@ -22,7 +22,7 @@ Scaleway VPC offers layer 3 network isolation, while layer 2 Private Networks ar ## Can I connect multiple Private Networks to the same Scaleway resource? -Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, you can connect up to 8 Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. For Elastic Metal, some additional configuration is required: check out our documentation on [configuring the network interface](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). +Yes, you can configure multiple Private Networks on the same Scaleway resource. For example, you can connect up to 8 Private Networks to the same Instance. A virtual network interface is created for each Private Network the Instance is attached to. For Elastic Metal, some additional configuration is required: check out our documentation on [configuring the network interface](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). You can configure: - Up to 8 Private Networks per Scaleway resource @@ -45,7 +45,7 @@ No, they do not require a public IPv4 address. ## Can resources in a Private Network access the internet without a public IPv4 address? -Yes. You can attach a [Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) to your Private Network to provide internet access to your Instances, Elastic Metal servers, and other attached Scaleway resources. +Yes. You can attach a [Public Gateway](/public-gateways/how-to/create-a-public-gateway/) to your Private Network to provide internet access to your Instances, Elastic Metal servers, and other attached Scaleway resources. ## Do non-IP protocols work over Private Networks? @@ -53,4 +53,4 @@ Technically, any ethernet payload should work over Private Networks. However, on ## Do Private Networks support IP autoconfiguration? -Yes, DHCP is an inbuilt function of Private Networks and provides IP autoconfiguration for your attached resources. Alternatively, you can use Scaleway IPAM to [reserve specific IP addresses](/network/ipam/how-to/reserve-ip/) on a Private Network and use these to attach resources. \ No newline at end of file +Yes, DHCP is an inbuilt function of Private Networks and provides IP autoconfiguration for your attached resources. Alternatively, you can use Scaleway IPAM to [reserve specific IP addresses](/ipam/how-to/reserve-ip/) on a Private Network and use these to attach resources. \ No newline at end of file diff --git a/faq/public-gateways.mdx b/faq/public-gateways.mdx index 87c28fae3c..d9c6da2e35 100644 --- a/faq/public-gateways.mdx +++ b/faq/public-gateways.mdx @@ -12,7 +12,7 @@ productIcon: PublicGatewayProductIcon ## What is a Public Gateway? -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](/identity-and-access-management/organizations-and-projects/concepts/#organization). +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/). @@ -22,24 +22,24 @@ No. A public IPv4 address (aka. flexible IP) must be assigned to the Public Gate ## Can my Instances and other resources access the internet via a Public Gateway without a public IP address? -Yes. The Public Gateway can advertize itself as the [default route to the internet](/network/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources on the same Private Network, can access the internet via the gateway. -Moreover, the Public Gateway supports [static NAT](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (aka. port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the Private Network. +Yes. The Public Gateway can advertize itself as the [default route to the internet](/public-gateways/concepts/#default-route) over the Private Network it is attached to, so that Instances and other resources on the same Private Network, can access the internet via the gateway. +Moreover, the Public Gateway supports [static NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) (aka. port forwarding), so that ingress traffic from the public internet can reach Instances on the Private Network. This works by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the Private Network. ## What happened to static leases (DHCP reservations) when DHCP moved from the Public Gateway to Private Networks? -On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our [dedicated migration documentation](/network/vpc/reference-content/vpc-migration/) for full details. +On 12 July 2023, DHCP functionality moved from Public Gateways to Private Networks. See our [dedicated migration documentation](/vpc/reference-content/vpc-migration/) for full details. -Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API and other devtools, but is no longer available via the Scaleway console. We recommend that you use [Scaleway IPAM](/network/ipam/) to reserve private IP addresses on specific Private Networks, which you can then use when attaching resources. +Pre-existing static leases created via the Public Gateway were fully migrated and still work for your attached resources on a Private Network. Manual static lease configuration is still available via the API and other devtools, but is no longer available via the Scaleway console. We recommend that you use [Scaleway IPAM](/ipam/) to reserve private IP addresses on specific Private Networks, which you can then use when attaching resources. ## Why is my Public Gateway labelled as Legacy? -**Legacy** Public Gateways use a [workaround](/network/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatiblity with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources +**Legacy** Public Gateways use a [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure compatiblity with Scaleway's IPAM (**I** **P** **A**ddress **M**anagement) tool. IPAM acts as a single source of truth for the IP addresses of Scaleway resources -Your gateway is probably a legacy gateway if you created it prior to 17 October 2023. These gateways will continue to function, but are not natively integrated with IPAM, and you cannot take advantage of features such as IP management via Scaleway [IPAM](/network/ipam/), or fully-isolated Kubernetes Kapsules. You should create a new gateway if you want to benefit from such features. +Your gateway is probably a legacy gateway if you created it prior to 17 October 2023. These gateways will continue to function, but are not natively integrated with IPAM, and you cannot take advantage of features such as IP management via Scaleway [IPAM](/ipam/), or fully-isolated Kubernetes Kapsules. You should create a new gateway if you want to benefit from such features. ## Do I need a Public Gateway for each Availability Zone (AZ)? -VPC and Private Networks are both [regional](/network/public-gateways/concepts/#region-and-availability-zone), meaning they span all AZs across a given region. Even though Public Gateways are zoned and not regional, one Public Gateway attached to a regional Private Network is functionally enough, and will cover the whole region. That is to say a Public Gateway created in PAR-1 can serve Instances in PAR-2 and PAR-3, as long as they are all attached to the same PAR-region Private Network. +VPC and Private Networks are both [regional](/public-gateways/concepts/#region-and-availability-zone), meaning they span all AZs across a given region. Even though Public Gateways are zoned and not regional, one Public Gateway attached to a regional Private Network is functionally enough, and will cover the whole region. That is to say a Public Gateway created in PAR-1 can serve Instances in PAR-2 and PAR-3, as long as they are all attached to the same PAR-region Private Network. ## How can I achieve truly High Availability (HA) networking when the Public Gateway is a zoned resource? @@ -49,4 +49,4 @@ In the meantime, if this is a concern, you could consider attaching several Publ ## I need more than 1Gbps bandwidth for my Public Gateway, what can I do? -We have introduced a `VPC-GW-L` offer with 3Gbps bandwidth, and a `VPC-GW-XL` offer with 10Gbps 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](/network/public-gateways/how-to/upgrade-public-gateway/). \ No newline at end of file +We have introduced a `VPC-GW-L` offer with 3Gbps bandwidth, and a `VPC-GW-XL` offer with 10Gbps 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 diff --git a/faq/secret-manager.mdx b/faq/secret-manager.mdx index b146889c4d..eb958957a7 100644 --- a/faq/secret-manager.mdx +++ b/faq/secret-manager.mdx @@ -20,7 +20,7 @@ You can manage different types of secrets, such as identifiers for databases, Sa ## How can my applications access these secrets? -To access the secrets stored in Secret Manager, you must create an Identity and Access Management (IAM) policy for your application. Then, you can replace the plain text secrets with code to retrieve the stored secrets through the Secret Manager API. For more information, see the [related documentation](/identity-and-access-management/secret-manager/quickstart/). +To access the secrets stored in Secret Manager, you must create an Identity and Access Management (IAM) policy for your application. Then, you can replace the plain text secrets with code to retrieve the stored secrets through the Secret Manager API. For more information, see the [related documentation](/secret-manager/quickstart/). ## In which regions is Secret Manager available? @@ -33,7 +33,7 @@ Secret Manager allows you to control access to secrets through IAM policies. Whe ## How does Secret Manager encrypt my secrets? Secret Manager uses envelope encryption (AES-256 encryption algorithm) to encrypt your secrets with an internal key management service. -To understand the secrets encryption process, refer to our [related documentation](/identity-and-access-management/secret-manager/reference-content/data-encryption-with-secret-manager/). +To understand the secrets encryption process, refer to our [related documentation](/secret-manager/reference-content/data-encryption-with-secret-manager/). ## How is Scaleway Secret Manager billed? diff --git a/faq/serverless-containers.mdx b/faq/serverless-containers.mdx index 07d0684b66..a29654a712 100644 --- a/faq/serverless-containers.mdx +++ b/faq/serverless-containers.mdx @@ -47,7 +47,7 @@ Scaling in Serverless Containers and Serverless Functions is handled automatical ## How do I integrate my serverless solutions with other Scaleway services? -Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. +Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. ## Can I migrate existing applications to Serverless Containers? @@ -123,7 +123,7 @@ Serverless Containers are billed on a pay-as-you-go basis, strictly on resource Insufficient vCPU, RAM or ephemeral storage can lead to containers going to error status. Make sure to provision enough resources for your container. -We recommend you set high values, [use metrics to monitor](/serverless/containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly. +We recommend you set high values, [use metrics to monitor](/serverless-containers/how-to/monitor-container/) the resource usage of your container, then adjust the values accordingly. ## How can I reduce the cold-starts of Serverless Containers ? @@ -138,7 +138,7 @@ Ensure that your code avoids heavy computations or long-running initialization a ## What are the limitations of Serverless Containers? -Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless/containers/reference-content/containers-limitations/) for more information. +Refer to our dedicated page about [Serverless Containers limitations and configuration restrictions](/serverless-containers/reference-content/containers-limitations/) for more information. ## Where should I host my container images for deployment ? @@ -146,7 +146,7 @@ Refer to our dedicated page about [Serverless Containers limitations and configu ## How can I copy an image from an external registry to Scaleway Container Registry? -You can copy an image from an external registry using the Docker CLI, or open source third-party tools such as Skopeo. Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information. +You can copy an image from an external registry using the Docker CLI, or open source third-party tools such as Skopeo. Refer to the [dedicated documentation](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information. ## Can I whitelist the IPs of my containers? @@ -154,7 +154,7 @@ Serverless Containers does not yet support Private Networks. However, you can us ## How can I deploy my Containers? -There are several ways to deploy containers. Refer to the [dedicated documentation](/serverless/containers/reference-content/deploy-container/) to determine the best method for your use case. +There are several ways to deploy containers. Refer to the [dedicated documentation](/serverless-containers/reference-content/deploy-container/) to determine the best method for your use case. ## Which protocols are supported by Serverless Containers? @@ -190,26 +190,26 @@ scale is set to 0. This behavior is not configurable at this time. ## How can I store data in my Serverless resource? -Serverless resources are by default [stateless](/serverless/containers/concepts/#stateless), local storage is ephemeral. +Serverless resources are by default [stateless](/serverless-containers/concepts/#stateless), local storage is ephemeral. For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose: ### Databases -* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. -* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. -* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds. -* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database. +* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. +* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. +* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds. +* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database. ### Storage -* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data. -* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. +* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data. +* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. Explore all Scaleway products in the console and select the right product for your use case. -Further integrations are also possible even if not listed above, for example, [Secret Manager](/identity-and-access-management/secret-manager/) can help you to store information that requires versioning. +Further integrations are also possible even if not listed above, for example, [Secret Manager](/secret-manager/) can help you to store information that requires versioning. ## Can I use Serverless Containers with Edge Services? diff --git a/faq/serverless-functions.mdx b/faq/serverless-functions.mdx index 04d0697f9f..ef095ac9b9 100644 --- a/faq/serverless-functions.mdx +++ b/faq/serverless-functions.mdx @@ -43,7 +43,7 @@ Yes, Serverless Functions resources can be changed at any time without causing d ## How do I integrate my serverless solutions with other Scaleway services? -Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. +Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. ## How am I billed for Serverless Functions? @@ -150,7 +150,7 @@ The scheme below illustrates our billing model: Insufficient vCPU and RAM resources can lead to functions going to error status. Make sure to provision enough resources for your function. -We recommend you set high values, [use metrics to monitor](/serverless/functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly. +We recommend you set high values, [use metrics to monitor](/serverless-functions/how-to/monitor-function/) the resource usage of your function, then adjust the value accordingly. ## How to reduce cold-start of Serverless Functions ? @@ -165,13 +165,13 @@ Ensure that your code avoid heavy computations or long-running initialization at ## What are the limitations of Serverless Functions? -Refer to our dedicated page about [Serverless Functions limitations and configuration restrictions](/serverless/functions/reference-content/functions-limitations/) for more information. +Refer to our dedicated page about [Serverless Functions limitations and configuration restrictions](/serverless-functions/reference-content/functions-limitations/) for more information. ## What runtimes are available on Serverless Functions? Serverless Functions enables you to deploy functions using popular languages: `Go`, `Node`, `Python`, `PHP`, `Rust`... -Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless/functions/reference-content/functions-lifecycle/) +Refer to our dedicated page about [Serverless Functions Runtimes Lifecycle](/serverless-functions/reference-content/functions-lifecycle/) ## How can I check build errors? @@ -188,11 +188,11 @@ Serverless Functions does not yet support Private Networks. However, you can use ## How can I deploy my Functions? -Serverless Functions use cases are wide so [several ways to deploy functions](/serverless/functions/reference-content/deploy-function/) are available. +Serverless Functions use cases are wide so [several ways to deploy functions](/serverless-functions/reference-content/deploy-function/) are available. ## How can I test my functions locally? - Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless/functions/reference-content/local-testing/) for more information. + Scaleway provides libraries to run your functions locally, for debugging, profiling, and testing purposes. Refer to the [dedicated documentation](/serverless-functions/reference-content/local-testing/) for more information. ## Where can I find some advanced code examples for functions? @@ -201,7 +201,7 @@ Check out our [serverless-examples repository](https://github.com/scaleway/serve ## How to migrate runtimes? There are no constraints when changing a function runtime, you simply need to choose the runtime version you want. -Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless/functions/reference-content/functions-lifecycle/) for more information. +Upgrading a runtime is highly recommended in case of deprecation, and for runtimes that have reached end-of-support or end-of-life. See the [functions runtimes lifecycle documentation](/serverless-functions/reference-content/functions-lifecycle/) for more information. ## How do I configure access to a Private Network? @@ -222,21 +222,21 @@ scale is set to 0. This behavior is not configurable at this time. ## How can I store data in my Serverless resource? -Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral. +Serverless resources are by default [stateless](/serverless-functions/concepts/#stateless), local storage is ephemeral. For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose: ### Databases -* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. -* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. -* [Managed Database for Redis®](/managed-databases/redis/): Fully managed Redis®* in seconds. -* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database. +* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. +* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. +* [Managed Database for Redis®](/managed-databases-for-redis/): Fully managed Redis®* in seconds. +* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database. ### Storage -* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data. -* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. +* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data. +* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. Explore all Scaleway products in the console and select the right product for your use case. diff --git a/faq/serverless-jobs.mdx b/faq/serverless-jobs.mdx index c902940bee..2ae6938291 100644 --- a/faq/serverless-jobs.mdx +++ b/faq/serverless-jobs.mdx @@ -24,7 +24,7 @@ Serverless Jobs allows you to run large-scale batch processing and computational ## How do I integrate my serverless solutions with other Scaleway services? -Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/serverless/messaging/concepts/#queues) and [Topics and Events](/serverless/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless/sql-databases/). [Serverless Jobs](/serverless/jobs/) can pull data from [Object Storage](/storage/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. +Integration is straightforward. Serverless Functions and Containers can be triggered by events from [Queues](/messaging/concepts/#queues) and [Topics and Events](/messaging/concepts/#topics-and-events), and can easily communicate with services like [Managed Databases](/managed-databases/) or [Serverless databases](/serverless-sql-databases/). [Serverless Jobs](/serverless-jobs/) can pull data from [Object Storage](/object), or output processed results into a database. With managed connectors, APIs, and built-in integrations, linking to the broader Scaleway ecosystem is seamless. ## Can I update Serverless Jobs resources (vCPU and RAM) at any time? @@ -98,19 +98,19 @@ Serverless Jobs is ideal for tasks such as data processing, analysis and various ## How can I monitor the activity of my Serverless Jobs? -Serverless Jobs are integrated with [Cockpit](/observability/cockpit/quickstart/), Scaleway's Observability service. Cockpit allows you to [see all the logs and metrics associated with your job runs](/serverless/jobs/concepts/#job-run). Additionally, each job run has a status that provides you with real-time information on your job's execution. +Serverless Jobs are integrated with [Cockpit](/cockpit/quickstart/), Scaleway's Observability service. Cockpit allows you to [see all the logs and metrics associated with your job runs](/serverless-jobs/concepts/#job-run). Additionally, each job run has a status that provides you with real-time information on your job's execution. ## Can I cancel or modify a Serverless Job after it has started? -An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab. Refer to the [dedicated docmentation](/serverless/jobs/how-to/stop-job/) for more information. +An ongoing Serverless Job can be interrupted during its execution from the **Job runs** section of a job's **Overview** tab. Refer to the [dedicated docmentation](/serverless-jobs/how-to/stop-job/) for more information. ## How can I automate the deployment and management of Scaleway Serverless Jobs? -Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be driven using the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), and other [developer tools](https://www.scaleway.com/en/developers/). Our serverless ecosystem offers a lot of possibilities with event-driven architectures, and integrations with more products of the Scaleway ecosystem are under active development. +Scaleway Serverless Jobs is part of the Scaleway ecosystem, it can therefore be driven using the [Scaleway CLI](/scaleway-cli/quickstart/), the [Scaleway API](https://www.scaleway.com/en/developers/api/), and other [developer tools](https://www.scaleway.com/en/developers/). Our serverless ecosystem offers a lot of possibilities with event-driven architectures, and integrations with more products of the Scaleway ecosystem are under active development. ## Can I run multiple Serverless Jobs at the same time? -When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless/jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information. +When starting a job, you can use contextual options to define the number of jobs to execute at the same time. Refer to the [dedicated documentation](/serverless-jobs/how-to/run-job/#how-to-run-a-job-with-contextual-options) for more information. ## Where should I host my jobs images for deployment ? @@ -118,7 +118,7 @@ When starting a job, you can use contextual options to define the number of jobs ## How can I copy an image from an external registry to Scaleway Container Registry? -You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/containers/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below: +You can copy an image from an external registry by [logging in to the Scaleway Container Registry](/container-registry/how-to/connect-docker-cli/) using the Docker CLI, and by copying the image as shown below: ```sh docker pull alpine:latest @@ -141,24 +141,24 @@ To add network restrictions on your resource, consult the [list of prefixes used ## Can I securely use sensitive information with Serverless Jobs? -Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless/jobs/how-to/reference-secret-in-job/) for more information. +Yes, you can use sensitive data such as API secret keys, passwords, TLS/SSL certificates, or tokens. Serverless Jobs seamlessly integrates with [Secret Manager](/secret-manager/), which allows you to securely reference sensitive information within your jobs. Refer to the [dedicated documentation](/serverless-jobs/how-to/reference-secret-in-job/) for more information. ## How can I store data in my Serverless resource? -Serverless resources are by default [stateless](/serverless/functions/concepts/#stateless), local storage is ephemeral. +Serverless resources are by default [stateless](/serverless-functions/concepts/#stateless), local storage is ephemeral. For some use cases, such as saving analysis results, exporting data etc., it can be important to save data. Serverless resources can be connected to other resources from the Scaleway ecosystem for this purpose: ### Databases -* [Serverless Databases](/serverless/sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. -* [Managed MySQL / PostgreSQL](/managed-databases/postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. -* [Managed MongoDB®](/managed-databases/mongodb/): Get the best of MongoDB® and Scaleway in one database. +* [Serverless Databases](/serverless-sql-databases/): Go full serverless and take the complexity out of PostgreSQL database operations. +* [Managed MySQL / PostgreSQL](/managed-databases-for-postgresql-and-mysql/): Ensure scalability of your infrastructure and storage with our new generation of Managed Databases designed to scale on-demand according to your needs. +* [Managed MongoDB®](/managed-mongodb-databases/): Get the best of MongoDB® and Scaleway in one database. ### Storage -* [Object Storage](/storage/object/): Multi-AZ resilient object storage service ensuring high availability for your data. -* [Scaleway Glacier](/storage/object/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. +* [Object Storage](/object-storage/): Multi-AZ resilient object storage service ensuring high availability for your data. +* [Scaleway Glacier](/object-storage/): Our outstanding Cold Storage class to secure long-term object storage. Ideal for deep archived data. Explore all Scaleway products in the console and select the right product for your use case. diff --git a/faq/serverless-sql-databases.mdx b/faq/serverless-sql-databases.mdx index 659f2f673b..b58f70b129 100644 --- a/faq/serverless-sql-databases.mdx +++ b/faq/serverless-sql-databases.mdx @@ -14,7 +14,7 @@ productIcon: ServerlessDbProductIcon You are billed both for the compute resources provisioned and the storage used. You can see the cost estimate in the Database creation wizard. - - **Compute**: You are billed based on compute resources (vCPU and RAM) provisioned to handle your workload. Provisioned resources evolve according to the [autoscaling](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/#autoscaling) parameter, and stay between the minimum and maximum thresholds defined for your database. For each vCPU provisioned, 4 GB of RAM will be allocated. + - **Compute**: You are billed based on compute resources (vCPU and RAM) provisioned to handle your workload. Provisioned resources evolve according to the [autoscaling](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/#autoscaling) parameter, and stay between the minimum and maximum thresholds defined for your database. For each vCPU provisioned, 4 GB of RAM will be allocated. - **Storage**: You are billed for the storage consumed by your database. Storage price is based on the size of your database (in GB) and includes 7 days of automated backups at no additional costs. Storage is always billed even if your database is in an active state or idle state. @@ -34,11 +34,11 @@ Backup and restore operations for databases that are less than 10 GB usually las ## What are the differences between Serverless SQL Databases and PostgreSQL databases? -Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features are disabled or will not work as expected. Refer to the [Known differences](/serverless/sql-databases/reference-content/known-differences/) for more information. +Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features are disabled or will not work as expected. Refer to the [Known differences](/serverless-sql-databases/reference-content/known-differences/) for more information. ## How many simultaneous connections can my database receive? -Serverless SQL Database handles connection pooling seamlessly. The number of maximum simultaneous connections will scale with CPU and RAM. Refer to the [Serverless SQL Databases overview](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) for more information on technical specifications. +Serverless SQL Database handles connection pooling seamlessly. The number of maximum simultaneous connections will scale with CPU and RAM. Refer to the [Serverless SQL Databases overview](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) for more information on technical specifications. Refer to [How am I billed?](/faq/serverless-sql-databases/#how-am-i-billed-for-serverless-sql-databases) for more information. @@ -53,8 +53,8 @@ You can avoid cold starts by provisioning a minimum of 1 vCPU or more. The following features are currently not supported and will be implemented at a later time: - Manual backups (you can still perform manual backups using SQL queries or via SQL administration tools such as pgAdmin) - - Several SQL commands detailed in the [Known differences with default PostgreSQL](/serverless/sql-databases/reference-content/known-differences/) documentation + - Several SQL commands detailed in the [Known differences with default PostgreSQL](/serverless-sql-databases/reference-content/known-differences/) documentation ## Which PostgreSQL extensions are available? -Refer to our dedicated [PostgreSQL extentions reference page](/serverless/sql-databases/reference-content/supported-postgresql-extensions/) for a list of all available extensions and more details about each one. \ No newline at end of file +Refer to our dedicated [PostgreSQL extentions reference page](/serverless-sql-databases/reference-content/supported-postgresql-extensions/) for a list of all available extensions and more details about each one. \ No newline at end of file diff --git a/faq/support.mdx b/faq/support.mdx index 067c499697..92922a93de 100644 --- a/faq/support.mdx +++ b/faq/support.mdx @@ -14,7 +14,7 @@ productIcon: SupportProductIcon You can find your support plan on [the support plan page within the Scaleway console](https://console.scaleway.com/support/plans). The free Basic support plan is included for all Scaleway customers automatically. ## How can I change my current support plan? -You can [change your support plan](/console/account/how-to/configure-support-plans/) on the support plan page via the Scaleway console. +You can [change your support plan](/account/how-to/configure-support-plans/) on the support plan page via the Scaleway console. ## How frequently can I change my plan? You can switch plans once a month. @@ -35,7 +35,7 @@ For the Gold plan, we will charge you whichever is greater, either €499 (exclu Our support team can assist you in English and French, via ticket and/or phone, depending on your support plan level. ## How do I create a support ticket? -You can create and track your support tickets from the Scaleway console. [Follow this how to](/console/account/how-to/open-a-support-ticket/) for more details. +You can create and track your support tickets from the Scaleway console. [Follow this how to](/account/how-to/open-a-support-ticket/) for more details. ## How do I report abuse or suspected abuse coming from the Scaleway network? To report abuse or suspicion of abuse from our network, open a new abuse report via [abuse.scaleway.com](https://abuse.scaleway.com). Include as many details as possible in your report such as logs, header, URL and any information you might find relevant in your report. @@ -75,4 +75,4 @@ Your plan remains unchanged until January 1st, 2023. Past this date, the new mod ## How frequently can I benefit from an architecture review? -You can benefit from an architecture review every 6 months (maximum). Architecture reviews are available only after the third month of subscription to the Gold Plan. If you would like to benefit from an architecture review right away after subscribing, you can reach out to your Customer Success Manager or [contact the support team](/console/account/how-to/open-a-support-ticket/). \ No newline at end of file +You can benefit from an architecture review every 6 months (maximum). Architecture reviews are available only after the third month of subscription to the Gold Plan. If you would like to benefit from an architecture review right away after subscribing, you can reach out to your Customer Success Manager or [contact the support team](/account/how-to/open-a-support-ticket/). \ No newline at end of file diff --git a/faq/transactional-email.mdx b/faq/transactional-email.mdx index e672634aec..f35b30d8dc 100644 --- a/faq/transactional-email.mdx +++ b/faq/transactional-email.mdx @@ -25,7 +25,7 @@ Scaleway's Transactional Email platform is dedicated to sending transactional em ## How can I configure DNS records to send emails? -You need to [add SPF and DKIM records](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to be able to send emails. Find out [how to set up your DNS records for other DNS providers](/tutorials/set-up-spf-dkim-for-dns-providers/). +You need to [add SPF and DKIM records](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to be able to send emails. Find out [how to set up your DNS records for other DNS providers](/tutorials/set-up-spf-dkim-for-dns-providers/). ## How do I know if my domain is valid for sending emails? @@ -33,19 +33,19 @@ After configuring your SPF and DKIM records, you must launch a verification of t ## Do I have to set up an MX record for better email deliverability? -Setting up an [MX record](/managed-services/transactional-email/concepts#mx-record) is highly recommended to ensure your email deliverability. Find out [how to add an MX record to your domain](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-your-own-mx-record). You can also [use Scaleway's blackhole MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-scaleways-mx-record) if you do not have your own MX. +Setting up an [MX record](/transactional-email/concepts#mx-record) is highly recommended to ensure your email deliverability. Find out [how to add an MX record to your domain](/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-your-own-mx-record). You can also [use Scaleway's blackhole MX](/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-scaleways-mx-record) if you do not have your own MX. ## What happens to automatically configured DNS records when I delete a domain in the Transactional Email service? -When a domain is removed from Scalway's Transactional Email platform, [autoconfigured DNS records](/managed-services/transactional-email/how-to/autoconfigure-domain/) are not automatically deleted in the Domains & DNS section. If you no longer use the domain for sending emails, you must manually delete or modify these records. It is recommended to verify the associated DNS records to ensure they are correctly configured or removed. +When a domain is removed from Scalway's Transactional Email platform, [autoconfigured DNS records](/transactional-email/how-to/autoconfigure-domain/) are not automatically deleted in the Domains & DNS section. If you no longer use the domain for sending emails, you must manually delete or modify these records. It is recommended to verify the associated DNS records to ensure they are correctly configured or removed. ## What is the impact on the Transactional Email service if a DNS zone is deleted in Scaleway Domains & DNS? -If a DNS zone is deleted while [autoconfig is enabled](/managed-services/transactional-email/how-to/autoconfigure-domain/), the DNS records will be added to the parent zone. This ensures that the domain remains validated on the Transactional Email platform, allowing continued use of the service without interruption. +If a DNS zone is deleted while [autoconfig is enabled](/transactional-email/how-to/autoconfigure-domain/), the DNS records will be added to the parent zone. This ensures that the domain remains validated on the Transactional Email platform, allowing continued use of the service without interruption. ## What are the limitations and restrictions when using Transactional Email? -Find out about [limits and quotas](/managed-services/transactional-email/reference-content/tem-capabilities-and-limits/) available for Transactional Email. If you want to increase your quota beyond the values shown on this page, [contact our support team](https://console.scaleway.com/support/create). +Find out about [limits and quotas](/transactional-email/reference-content/tem-capabilities-and-limits/) available for Transactional Email. If you want to increase your quota beyond the values shown on this page, [contact our support team](https://console.scaleway.com/support/create). ## How is Scaleway's Transactional Email service billed? diff --git a/faq/vpc.mdx b/faq/vpc.mdx index 77dda9fd28..f5a594a265 100644 --- a/faq/vpc.mdx +++ b/faq/vpc.mdx @@ -12,7 +12,7 @@ productIcon: VpcProductIcon ## What is the difference between VPC and a Private Network? -One default VPC (**V**irtual **P**rivate **C**loud) for every available region is automatically created in each Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). A VPC offers layer 3 network isolation. +One default VPC (**V**irtual **P**rivate **C**loud) for every available region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project). A VPC offers layer 3 network isolation. Within each VPC, you can create multiple **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet. @@ -20,7 +20,7 @@ In the future, VPC will allow you to interconnect your VPC with other networks, ## Can I route traffic between different Private Networks on the same VPC? -Yes, [VPC routing](/network/vpc/concepts#routing) allows you to automize the routing of traffic between resources in different Private Networks within the same VPC. +Yes, [VPC routing](/vpc/concepts#routing) allows you to automize the routing of traffic between resources in different Private Networks within the same VPC. ## Can I route traffic between different Private Networks in different VPCs or different Scaleway Projects? @@ -28,14 +28,14 @@ This is not currently possible. You may consider using a VPN tunnel to achieve t ## What happened to my classic, mono-AZ Private Network? -When VPC and regional Private Networks moved from Public Beta to General Availability, all mono-AZ Private Networks were automatically migrated to be regional. [Read the documentation](/network/vpc/reference-content/vpc-migration/) to find out more about the migration process. +When VPC and regional Private Networks moved from Public Beta to General Availability, all mono-AZ Private Networks were automatically migrated to be regional. [Read the documentation](/vpc/reference-content/vpc-migration/) to find out more about the migration process. ## Do resources' IP addresses on a Private Network risk changing when allocated by managed DHCP? With managed DHCP, the IP is allocated when the resource is attached to a Private Network, and released only when the resource is detached or deleted. The IP address remains stable across reboots and long power offs, and will not change except upon deletion or detachment from the Private Network. -Nonetheless, you can also reserve specific IPs from a Private Network's CIDR block, and use these IPs to attach specific resources, if you prefer. See our documentation on [how to reserve IPs](/network/ipam/how-to/reserve-ip/). +Nonetheless, you can also reserve specific IPs from a Private Network's CIDR block, and use these IPs to attach specific resources, if you prefer. See our documentation on [how to reserve IPs](/ipam/how-to/reserve-ip/). ## How can I manage IP addresses for my Proxmox Virtual Machines (VMs) on Elastic Metal servers? -We recommend that you use our IPAM product for this purpose. See [how to reserve a private IP address with an attached MAC address](/network/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file +We recommend that you use our IPAM product for this purpose. See [how to reserve a private IP address with an attached MAC address](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file diff --git a/guidelines.mdx b/guidelines.mdx index 2acbd99fe0..b40767c682 100644 --- a/guidelines.mdx +++ b/guidelines.mdx @@ -58,12 +58,12 @@ All documentation pages must fall into one of the following categories: | PAGE TYPE | DESCRIPTION | | -------------------| ---------------------------------------------------------------------------------------- | -| How to | Shows how to do a core action (e.g. create, configure, delete, use features) for a Scaleway product via the console, e.g. [How to create a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) | -| Quickstart | Shows how to do the main series of actions necessary to start using a Scaleway product via the console, e.g. [Instances Quickstart](/compute/instances/quickstart/) | -| Concepts | Defines and briefly explains the main terminology associated with a Scaleway product, e.g. [Kubernetes Concepts](/containers/kubernetes/concepts/) | -| Troubleshooting | Gives solutions to help resolve a common issue with a Scaleway product, e.g. [VPC auto-config is not working](/network/vpc/troubleshooting/autoconfig-not-working/) | -| API/CLI | Presents information and tips for creating and configuring a Scaleway product via both official and third-party APIs, CLIs, SDKs and other developer tools, e.g. Terraform, e.g. [Using Object Storage with the AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/). These pages complement the [main developer reference documentation](https://www.scaleway.com/en/developers/). | -| Additional Content | Provides detailed information on specific subjects and features associated with a Scaleway product, e.g. [Optimize your Object Storage performance](/storage/object/reference-content/optimize-object-storage-performance/) | +| How to | Shows how to do a core action (e.g. create, configure, delete, use features) for a Scaleway product via the console, e.g. [How to create a Load Balancer](/load-balancer/how-to/create-load-balancer/) | +| Quickstart | Shows how to do the main series of actions necessary to start using a Scaleway product via the console, e.g. [Instances Quickstart](/instances/quickstart/) | +| Concepts | Defines and briefly explains the main terminology associated with a Scaleway product, e.g. [Kubernetes Concepts](/kubernetes/concepts/) | +| Troubleshooting | Gives solutions to help resolve a common issue with a Scaleway product, e.g. [VPC auto-config is not working](/vpc/troubleshooting/autoconfig-not-working/) | +| API/CLI | Presents information and tips for creating and configuring a Scaleway product via both official and third-party APIs, CLIs, SDKs and other developer tools, e.g. Terraform, e.g. [Using Object Storage with the AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/). These pages complement the [main developer reference documentation](https://www.scaleway.com/en/developers/). | +| Additional Content | Provides detailed information on specific subjects and features associated with a Scaleway product, e.g. [Optimize your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/) | | Tutorial | Explains how to use a Scaleway product with a third-party tool, or how to use multiple Scaleway products together for a specific use-case, e.g. [Deploying Strapi on an Instance](/tutorials/strapi/) | | FAQ | Gives answers to the most frequently asked questions about Scaleway products, e.g. [Cockpit FAQ](/faq/cockpit/) | @@ -203,14 +203,14 @@ When linking to other Scaleway Documentation pages, use relative links. Include | ✅ GOOD INTERNAL LINK | ❌ BAD INTERNAL LINK | | ------------------------------------------ | ----------------------------------------------- | -| ````Refer to the [VPC Quickstart](/network/vpc/quickstart/)```` | ````Refer to the [VPC Quickstart](https://www.scaleway.com/en/docs/network/vpc/quickstart/)````

````Refer to the [VPC Quickstart](/en/docs/network/vpc/quickstart/)````

````Refer to the [VPC Quickstart](network/vpc/quickstart)```` | +| ````Refer to the [VPC Quickstart](/vpc/quickstart/)```` | ````Refer to the [VPC Quickstart](https://www.scaleway.com/en/docs/vpc/quickstart/)````

````Refer to the [VPC Quickstart](/en/docs/network/vpc/quickstart/)````

````Refer to the [VPC Quickstart](network/vpc/quickstart)```` | When linking to a Scaleway Documentation page anchor, include a leading slash, **but no trailing slash** | ✅ GOOD INTERNAL ANCHOR LINK | ❌ BAD INTERNAL LINK | | ------------------------------------------ | ----------------------------------------------- | -| Anchor is on same page as link: ````Learn more about [InstantApps](#instantapp)```` | ````Learn more about [InstantApps](https://www.scaleway.com/en/docs/compute/instances/concepts/#instantapp/)```` | -| Anchor is on different page : ````Learn more about [InstantApps](/compute/instances/concepts/#instantapp)```` | ````Learn more about [InstantApps](/#instantapp/)```` | +| Anchor is on same page as link: ````Learn more about [InstantApps](#instantapp)```` | ````Learn more about [InstantApps](https://www.scaleway.com/en/docs/instances/concepts/#instantapp/)```` | +| Anchor is on different page : ````Learn more about [InstantApps](/instances/concepts/#instantapp)```` | ````Learn more about [InstantApps](/#instantapp/)```` | When linking to an external page, copy and paste the full link exactly as it appears in the browser (including any slashes as shown). @@ -258,7 +258,7 @@ You can use the tabs component to: - Give instructions for multiple operating systems, environments, platforms or similar - Show conditional instructions, where the user must follow one set or the other depending on a condition -See an example of the tabs component in action on the [How to connect to an Instance](/compute/instances/how-to/connect-to-instance/) page. +See an example of the tabs component in action on the [How to connect to an Instance](/instances/how-to/connect-to-instance/) page. Tabs syntax: @@ -477,7 +477,7 @@ The `meta: title` and `content: title` should be the same, other than in excepti ### Introduction ``` -In this tutorial, you will learn how to use **Loki** and **Grafana** to collect your Kubernetes logs on a [Kapsule cluster](/containers/kubernetes/how-to/create-cluster/). +In this tutorial, you will learn how to use **Loki** and **Grafana** to collect your Kubernetes logs on a [Kapsule cluster](/kubernetes/how-to/create-cluster/). Loki is a log aggregation system inspired by **Prometheus**. It is easy to operate, as it does not index the content of the Kubernetes logs but sets labels for log streams. Your metadata (object labels) can be used in Loki for scraping Kubernetes logs. If you use Grafana for metrics, Loki will allow you to have a single point of management for both logging and monitoring. ``` @@ -490,9 +490,9 @@ The introduction should be a few sentences, or a few short paragraphs, which exp - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Configured [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Configured [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your machine - Installed `helm` (version 3.2+), the Kubernetes [packet manager](https://helm.sh/), on your local machine --- @@ -506,15 +506,15 @@ Continue by listing the necessary products, resources or items users must have. | DO WRITE ✅ | DO NOT WRITE ❌| |-------------|----------------| -| ## Before you start

To complete the actions presented below, you must have:

- A Scaleway account logged in to the [console](https://console.scaleway.com)
- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)
- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) | To complete the actions presented below, you must have:

- You have a Scaleway account
- Have an SSH key
-SSH key | +| ## Before you start

To complete the actions presented below, you must have:

- A Scaleway account logged in to the [console](https://console.scaleway.com)
- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)
- A valid [API key](/iam/how-to/create-api-keys/) | To complete the actions presented below, you must have:

- You have a Scaleway account
- Have an SSH key
-SSH key | **Frequently used requirements** | MDX formatting | What users see | |----------------|----------------| |`- A Scaleway account logged in to the [console](https://console.scaleway.com)` | - A Scaleway account logged in to the [console](https://console.scaleway.com) | -|`- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization` | - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization | -|`- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/)` | - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) | -|`- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/)` | - A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) | +|`- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization` | - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization | +|`- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/)` | - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) | +|`- A valid [API key](/iam/how-to/create-api-keys/)` | - A valid [API key](/iam/how-to/create-api-keys/) | |`- Downloaded and installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) ` | - Downloaded and installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) | -|`- An [Instance](/compute/instances/how-to/create-an-instance) ` | - An [Instance](/compute/instances/how-to/create-an-instance) | \ No newline at end of file +|`- An [Instance](/instances/how-to/create-an-instance) ` | - An [Instance](/instances/how-to/create-an-instance) | \ No newline at end of file diff --git a/identity-and-access-management/audit-trail/concepts.mdx b/identity-and-access-management/audit-trail/concepts.mdx index 9bf731f80e..aaa396088b 100644 --- a/identity-and-access-management/audit-trail/concepts.mdx +++ b/identity-and-access-management/audit-trail/concepts.mdx @@ -14,7 +14,7 @@ dates: Audit Trail is a tool that holds a record of events and changes performed within a Scaleway Organization. Audit Trail allows you to keep track of all actions, whether successful, attempted, or failed, perfomed on your Scaleway resources. -With Audit Trail you can view actions taken by any [principal](/identity-and-access-management/iam/concepts/#principal) in any Project and on any of your Scaleway resources. You can also see the API methods used, the outcome of the action performed (status), and the IP address from which a principal performed an action. +With Audit Trail you can view actions taken by any [principal](/iam/concepts/#principal) in any Project and on any of your Scaleway resources. You can also see the API methods used, the outcome of the action performed (status), and the IP address from which a principal performed an action. Audit Trail allows you to view the metadata of the API method used, allowing you to investigate incidents and troubleshoot issues. diff --git a/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx b/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx index f55df7dfc6..e9585c4d14 100644 --- a/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx +++ b/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions.mdx @@ -13,19 +13,19 @@ categories: - identity-and-access-management --- -This page teaches you how to configure the necessary permission set to access [Audit Trail](/identity-and-access-management/audit-trail/concepts/#audit-trail). +This page teaches you how to configure the necessary permission set to access [Audit Trail](/audit-trail/concepts/#audit-trail). ## Configure the Audit Trail permission set -To start using Audit Trail you need to configure the `AuditTrailReadOnly` or the `OrganizationManager` permission sets in [IAM](/identity-and-access-management/iam/concepts/#iam). +To start using Audit Trail you need to configure the `AuditTrailReadOnly` or the `OrganizationManager` permission sets in [IAM](/iam/concepts/#iam). The `OrganizationManager` permission set is included in the `Administrators` group which is created by default whenever a new Organization is created. -The [scope](/identity-and-access-management/iam/concepts/#scope) of these permission sets is at [Organization](/identity-and-access-management/iam/concepts/#organization) level. +The [scope](/iam/concepts/#scope) of these permission sets is at [Organization](/iam/concepts/#organization) level. 1. Click **Identity and Access Management (IAM)** from the top-right of your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. -2. [Create an IAM policy](/identity-and-access-management/iam/how-to/create-policy/) and perform steps one to five. +2. [Create an IAM policy](/iam/how-to/create-policy/) and perform steps one to five. 3. Select the **Access to Organization features** scope and click **Validate** to move on to the next step. - The **Access to Organization features** scope allows you to give the [principal](/identity-and-access-management/iam/concepts/#principal) permissions to Organization-level features such as IAM, Audit Trail, billing, support and abuse tickets, and project management. + The **Access to Organization features** scope allows you to give the [principal](/iam/concepts/#principal) permissions to Organization-level features such as IAM, Audit Trail, billing, support and abuse tickets, and project management. 4. Click the **Security and Identity** category in the **Products** section, then choose the **AuditTrailReadOnly** permission set. 5. Click **Validate**. @@ -33,9 +33,9 @@ The [scope](/identity-and-access-management/iam/concepts/#scope) of these permis ## Configure Audit Trail access via the IAM Administrators group -You can also use Audit Trail if you are part of the IAM `Administrators` [group](/identity-and-access-management/iam/concepts/#group). +You can also use Audit Trail if you are part of the IAM `Administrators` [group](/iam/concepts/#group). -1. Follow the [following procedure](/identity-and-access-management/iam/how-to/invite-user-to-orga/) until step 3. +1. Follow the [following procedure](/iam/how-to/invite-user-to-orga/) until step 3. 2. Click the drop-down under **Add to an existing group** and add the users to the **Administrators** group. -3. Click **Invite** to send the invitation. The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/console/account/how-to/create-an-account/) first. +3. Click **Invite** to send the invitation. The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/account/how-to/create-an-account/) first. 4. The user will appear in the **Users** tab** once they have accepted the invitation. diff --git a/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx b/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx index f7545ae0fd..798233b5c2 100644 --- a/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx +++ b/identity-and-access-management/audit-trail/how-to/use-audit-trail.mdx @@ -26,5 +26,5 @@ This page shows you how to see and filter events for your Scaleway resources in 7. Optionally, click **Reset** to reset the filter. - If no events display after you use the filter, check the [dedicated troubleshooting page](/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events/) to solve the issue. + If no events display after you use the filter, check the [dedicated troubleshooting page](/audit-trail/troubleshooting/cannot-see-events/) to solve the issue. diff --git a/identity-and-access-management/audit-trail/index.mdx b/identity-and-access-management/audit-trail/index.mdx index 58ebd576d0..801677a263 100644 --- a/identity-and-access-management/audit-trail/index.mdx +++ b/identity-and-access-management/audit-trail/index.mdx @@ -8,7 +8,7 @@ meta: productName="Audit Trail" productLogo="auditTrail" description="Audit Trail allows you to keep track of the activity of your Scaleway resources." - url="/identity-and-access-management/audit-trail/quickstart/" + url="/audit-trail/quickstart/" label="Audit Trail Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to track user activity, access events, and system changes in a few steps." label="View Quickstart" - url="/identity-and-access-management/audit-trail/quickstart/" + url="/audit-trail/quickstart/" /> diff --git a/identity-and-access-management/audit-trail/quickstart.mdx b/identity-and-access-management/audit-trail/quickstart.mdx index 4ee71cc278..d296ff5b33 100644 --- a/identity-and-access-management/audit-trail/quickstart.mdx +++ b/identity-and-access-management/audit-trail/quickstart.mdx @@ -10,19 +10,19 @@ dates: posted: 2024-11-28 --- -In this quickstart, we show you how to start using [Audit Trail](/identity-and-access-management/audit-trail/concepts/#audit-trail). +In this quickstart, we show you how to start using [Audit Trail](/audit-trail/concepts/#audit-trail). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created [resources integrated with Audit Trail](/identity-and-access-management/audit-trail/reference-content/resource-integration-with-adt/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created [resources integrated with Audit Trail](/audit-trail/reference-content/resource-integration-with-adt/) ## How to configure the Audit Trail permission set -To start using Audit Trail you need to configure permission sets in [IAM](/identity-and-access-management/iam/concepts/#iam). +To start using Audit Trail you need to configure permission sets in [IAM](/iam/concepts/#iam). -Refer to the [dedicated documentation page](/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions/) to find out how. +Refer to the [dedicated documentation page](/audit-trail/how-to/configure-audit-trail-permissions/) to find out how. ## How to use Audit Trail @@ -38,7 +38,7 @@ Refer to the [dedicated documentation page](/identity-and-access-management/audi 7. Optionally, click **Reset** to reset the filter. - If no events display after you use the filter, try switching the region from the **Region** drop-down, or adjusting your search. Find out how to troubleshoot event issues in our [dedicated documentation](/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events/). + If no events display after you use the filter, try switching the region from the **Region** drop-down, or adjusting your search. Find out how to troubleshoot event issues in our [dedicated documentation](/audit-trail/troubleshooting/cannot-see-events/). diff --git a/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx b/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx index 3702754154..b87a8a454d 100644 --- a/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx +++ b/identity-and-access-management/audit-trail/troubleshooting/cannot-see-events.mdx @@ -21,7 +21,7 @@ I cannot see any events in Audit Trail. ## Possible solutions -- Make sure that you have the [permision set necessary to access Audit Trail](/identity-and-access-management/audit-trail/how-to/configure-audit-trail-permissions). If you are not an IAM manager, contact your IAM manager to ask for Audit Trail access. +- Make sure that you have the [permision set necessary to access Audit Trail](/audit-trail/how-to/configure-audit-trail-permissions). If you are not an IAM manager, contact your IAM manager to ask for Audit Trail access. - Make sure you have created Scaleway resources to see events in Audit Trail. diff --git a/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx b/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx index fb5719ceea..4b3b058597 100644 --- a/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx +++ b/identity-and-access-management/iam/api-cli/using-api-key-object-storage.mdx @@ -13,7 +13,7 @@ categories: - IAM --- -You can carry out actions on Scaleway Object Storage resources either via the [Scaleway console](https://console.scaleway.com/), or via a third-party API or CLI, such as [the AWS CLI](/storage/object/api-cli/object-storage-aws-cli/), [MinIOClient](/storage/object/api-cli/installing-minio-client/) or [Rclone](/storage/object/api-cli/installing-rclone/). +You can carry out actions on Scaleway Object Storage resources either via the [Scaleway console](https://console.scaleway.com/), or via a third-party API or CLI, such as [the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIOClient](/object-storage/api-cli/installing-minio-client/) or [Rclone](/object-storage/api-cli/installing-rclone/). While the Scaleway console gives you the option to specify the [Scaleway Project](#what-is-a-project) to carry out your Object Storage actions in, this option is not available via third-party API/CLI tools. These tools are based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services), which does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. @@ -31,14 +31,14 @@ When you create new Projects, you can choose the Project in which you want to ad You need an API key if you want to carry out actions on Scaleway products and resources via the Scaleway [API](https://www.scaleway.com/en/developers/api/) or other Scaleway developer tools like the [CLI](https://github.com/scaleway/scaleway-cli) and [Terraform](https://github.com/scaleway/terraform-provider-scaleway), or any third-party API/CLI compatible with Scaleway products. An API key is not necessary if you only use the [console](https://console.scaleway.com/) to create and manage your Scaleway resources. -When you generate an API key with IAM, the key is associated with a specific [IAM user](/identity-and-access-management/iam/concepts/#user) or [IAM application](/identity-and-access-management/iam/concepts/#application). The API key inherits the permissions of its bearer (the user or application it is associated with). The user/application may have permissions on one or several Scaleway Projects, accorded to them via [policies](/identity-and-access-management/iam/concepts/#policy). +When you generate an API key with IAM, the key is associated with a specific [IAM user](/iam/concepts/#user) or [IAM application](/iam/concepts/#application). The API key inherits the permissions of its bearer (the user or application it is associated with). The user/application may have permissions on one or several Scaleway Projects, accorded to them via [policies](/iam/concepts/#policy). ## The impact of preferred Projects -When you perform an action on Scaleway Object Storage resources using a third-party API or CLI, such as [the AWS CLI](/storage/object/api-cli/object-storage-aws-cli/), [MinIOClient](/storage/object/api-cli/installing-minio-client/) or [Rclone](/storage/object/api-cli/installing-rclone/), you are using tools based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services). This standard interface does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. The preferred Project is specified when creating the API key (or can be edited at a later date). +When you perform an action on Scaleway Object Storage resources using a third-party API or CLI, such as [the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIOClient](/object-storage/api-cli/installing-minio-client/) or [Rclone](/object-storage/api-cli/installing-rclone/), you are using tools based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services). This standard interface does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. The preferred Project is specified when creating the API key (or can be edited at a later date). -Setting the preferred Project does not automatically give the API key bearer permissions for Object Storage in this Project. Ensure that the user/application is either the Owner of the Organization, or has a [policy](/identity-and-access-management/iam/concepts/#policy) giving them appropriate permissions for Object Storage in this Project. Note that the application of Object Storage permissions can take up to 5 minutes after creating a new rule or policy. +Setting the preferred Project does not automatically give the API key bearer permissions for Object Storage in this Project. Ensure that the user/application is either the Owner of the Organization, or has a [policy](/iam/concepts/#policy) giving them appropriate permissions for Object Storage in this Project. Note that the application of Object Storage permissions can take up to 5 minutes after creating a new rule or policy. When using the AWS S3 CLI: @@ -53,16 +53,16 @@ Therefore, whenever you perform an action on Object Storage via the API, check t ## How to create an API key via the Scaleway console -To create an API key via the Scaleway console, follow the steps detailed in [how to create an API key](/identity-and-access-management/iam/how-to/create-api-keys/). +To create an API key via the Scaleway console, follow the steps detailed in [how to create an API key](/iam/how-to/create-api-keys/). During creation, you are asked to select a preferred Project for the API key. A list of your current Projects displays. Choose the required Project for this API key. In the example below, the default project has been chosen: - While creating an API key, you have the option to skip the step of selecting a preferred Project. Note that if you select this option, the Project that you are currently navigating in the console (i.e. the one that is selected in your [Project dashboard](/identity-and-access-management/organizations-and-projects/concepts/#project-dashboard)) will be automatically selected as the preferred Project for Object Storage. This can still be edited later. + While creating an API key, you have the option to skip the step of selecting a preferred Project. Note that if you select this option, the Project that you are currently navigating in the console (i.e. the one that is selected in your [Project dashboard](/organizations-and-projects/concepts/#project-dashboard)) will be automatically selected as the preferred Project for Object Storage. This can still be edited later. -It is also essential to make sure the API key [has permissions to carry out Object Storage actions within this Project](/identity-and-access-management/iam/reference-content/permission-sets/). Ensure that a suitable policy is attached to the IAM user/application associated with this API key. +It is also essential to make sure the API key [has permissions to carry out Object Storage actions within this Project](/iam/reference-content/permission-sets/). Ensure that a suitable policy is attached to the IAM user/application associated with this API key. ## How to edit the preferred Project of an API key via the Scaleway console @@ -93,15 +93,15 @@ In the first part of this example, we create an IAM application, create an API k - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to create an IAM application. +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to create an IAM application. -1. [Create a new IAM application](/identity-and-access-management/iam/how-to/create-application/) called `my-test-app` without attaching any policies. +1. [Create a new IAM application](/iam/how-to/create-application/) called `my-test-app` without attaching any policies. -2. [Create an API key](/identity-and-access-management/iam/how-to/create-api-keys/) for the `my-test-app` application. Select the preferred Project for the API key as `default`. +2. [Create an API key](/iam/how-to/create-api-keys/) for the `my-test-app` application. Select the preferred Project for the API key as `default`. -3. [Install the AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) on your machine, using the API key you created in step 2 to complete the fields of the `.aws/credentials` file. +3. [Install the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) on your machine, using the API key you created in step 2 to complete the fields of the `.aws/credentials` file. 4. Run the following command to list all buckets: @@ -117,7 +117,7 @@ In the first part of this example, we create an IAM application, create an API k This is because the IAM application that bears this API key does not have permissions to view or create Object Storage resources. -5. [Create a policy](/identity-and-access-management/iam/how-to/create-policy/) with the name `object-storage-full-access` and the IAM application you created in step 1 as the principal. When adding rules, create a rule giving `Access to resources` > `default` Project, and the `Storage` permission set `ObjectStorageFullAccess`. +5. [Create a policy](/iam/how-to/create-policy/) with the name `object-storage-full-access` and the IAM application you created in step 1 as the principal. When adding rules, create a rule giving `Access to resources` > `default` Project, and the `Storage` permission set `ObjectStorageFullAccess`. 6. Repeat the command from step 4: @@ -142,9 +142,9 @@ In the first part of this example, we create an IAM application, create an API k In the second part of this example, we create a new Project, give `my-test-app` Object Storage permissions in this Project, and see how we can override the API key's preferred Project of `default` to create a new bucket in `my-second-project`. -1. [Create a new Project](/identity-and-access-management/organizations-and-projects/how-to/create-a-project/) in the Organization, with the name `my-second-project`. +1. [Create a new Project](/organizations-and-projects/how-to/create-a-project/) in the Organization, with the name `my-second-project`. - You must be Owner of the Organization, or have the `ProjectManager`, `IAMManager` or `OrganizationManager` [permissions](/identity-and-access-management/iam/reference-content/permission-sets/) to create a Project. + You must be Owner of the Organization, or have the `ProjectManager`, `IAMManager` or `OrganizationManager` [permissions](/iam/reference-content/permission-sets/) to create a Project. @@ -162,7 +162,7 @@ In the second part of this example, we create a new Project, give `my-test-app` Save and exit the file. -4. [Edit](/identity-and-access-management/iam/how-to/create-policy/) the `object-storage-full-access` policy you created in part 1 step 5 to add a second rule with `Access to resources` > `test-project` as scope, and the `Storage` permission set `ObjectStorageFullAccess`. Alternatively, edit the existing rule to change the scope to `All current projects`. +4. [Edit](/iam/how-to/create-policy/) the `object-storage-full-access` policy you created in part 1 step 5 to add a second rule with `Access to resources` > `test-project` as scope, and the `Storage` permission set `ObjectStorageFullAccess`. Alternatively, edit the existing rule to change the scope to `All current projects`. 5. Run the following command on your machine to create a new bucket called `bucket-for-second-project`: diff --git a/identity-and-access-management/iam/concepts.mdx b/identity-and-access-management/iam/concepts.mdx index 4425a81272..b5370cc7d2 100644 --- a/identity-and-access-management/iam/concepts.mdx +++ b/identity-and-access-management/iam/concepts.mdx @@ -95,7 +95,7 @@ For each policy rule, you specify one or more permission sets (e.g. "list all In ## Preferred Project -You can carry out actions on Scaleway Object Storage resources either via the [Scaleway console](https://console.scaleway.com), or via a third-party API or CLI, such as [the AWS CLI](/storage/object/api-cli/object-storage-aws-cli/), [MinIOClient](/storage/object/api-cli/installing-minio-client/) or [Rclone](/storage/object/api-cli/installing-rclone/). While the Scaleway console gives you the option to specify the [Scaleway Project](/identity-and-access-management/organizations-and-projects/concepts/#project) to carry out your Object Storage actions in, this option is not available via third-party API/CLI tools. These tools are based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services), which does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. See our page on [using API keys with Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) for more information. +You can carry out actions on Scaleway Object Storage resources either via the [Scaleway console](https://console.scaleway.com), or via a third-party API or CLI, such as [the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIOClient](/object-storage/api-cli/installing-minio-client/) or [Rclone](/object-storage/api-cli/installing-rclone/). While the Scaleway console gives you the option to specify the [Scaleway Project](/organizations-and-projects/concepts/#project) to carry out your Object Storage actions in, this option is not available via third-party API/CLI tools. These tools are based on a [standard Amazon S3 programming interface](https://en.wikipedia.org/wiki/Amazon_S3#S3_API_and_competing_services), which does not accept Project ID as a parameter. Therefore, when you create a Scaleway API key with IAM, you are prompted to specify the API key's **preferred Project for Object Storage**. This API key will always use this Project when carrying out Object Storage actions via any API/CLI. See our page on [using API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) for more information. ## Principal diff --git a/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx b/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx index 461453bb48..87005ce933 100644 --- a/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx +++ b/identity-and-access-management/iam/how-to/accept-invitation-to-orga.mdx @@ -10,19 +10,19 @@ dates: posted: 2022-06-20 --- -When you [create a Scaleway account](/console/account/how-to/create-an-account/), an Organization is automatically created, of which you are the [Owner](/identity-and-access-management/iam/concepts/#owner). If you are invited to someone else's Organization, you will simultaneously be the Owner of your own Organization and a guest in the other Organization, where you will have the rights and permissions granted to you via [policies](/identity-and-access-management/iam/concepts/#policy). +When you [create a Scaleway account](/account/how-to/create-an-account/), an Organization is automatically created, of which you are the [Owner](/iam/concepts/#owner). If you are invited to someone else's Organization, you will simultaneously be the Owner of your own Organization and a guest in the other Organization, where you will have the rights and permissions granted to you via [policies](/iam/concepts/#policy). - A Scaleway account logged into the [console](https://console.scaleway.com) -- Received an invitation to join an [Organization](/identity-and-access-management/iam/concepts/#organization) +- Received an invitation to join an [Organization](/iam/concepts/#organization) When someone invites you to join their Organization, you receive an email to inform you. - If the Organization you were invited to [enforces MFA](/console/account/how-to/enforce-mfa/), make sure you have [activated MFA](/console/account/how-to/use-2fa/) before accepting the invitation. + If the Organization you were invited to [enforces MFA](/account/how-to/enforce-mfa/), make sure you have [activated MFA](/account/how-to/use-2fa/) before accepting the invitation. ## If you already have a Scaleway account @@ -36,12 +36,12 @@ When someone invites you to join their Organization, you receive an email to inf - If you click **Decline**, your invitation will be rescinded. If you want to be invited again, you must ask the [IAM Manager](/identity-and-access-management/iam/reference-content/permission-sets/) or [Owner](/identity-and-access-management/iam/concepts/#owner) of the Organization. + If you click **Decline**, your invitation will be rescinded. If you want to be invited again, you must ask the [IAM Manager](/iam/reference-content/permission-sets/) or [Owner](/iam/concepts/#owner) of the Organization. You are redirected to the overview page of the Organization to which you were invited. - As an [IAM user](/identity-and-access-management/iam/concepts/#user) of an Organization, you must always ensure that you are in the desired Organization by checking the Organization name that displays in the top right corner of your console. + As an [IAM user](/iam/concepts/#user) of an Organization, you must always ensure that you are in the desired Organization by checking the Organization name that displays in the top right corner of your console. In the image below, we are currently in the Marion Créange Organization (highlighted in red). Use the drop-down menu to navigate to a different Organization, for example below we could switch to the Documentation Team Organization. @@ -50,17 +50,17 @@ When someone invites you to join their Organization, you receive an email to inf ## If you do not have a Scaleway account 1. Click **Create your account** from your email invitation. The Scaleway console opens in a browser window. -2. Create a Scaleway account. Follow the [How to create a Scaleway account](/console/account/how-to/create-an-account/) documentation page to do so. Your Organization overview page displays. +2. Create a Scaleway account. Follow the [How to create a Scaleway account](/account/how-to/create-an-account/) documentation page to do so. Your Organization overview page displays. 3. Click **Accept** in the top right pop-up. - If you click **Decline**, your invitation will be rescinded. If you want to be invited again, you must ask the [IAM Manager](/identity-and-access-management/iam/reference-content/permission-sets/) or [Owner](/identity-and-access-management/iam/concepts/#owner) of the Organization. + If you click **Decline**, your invitation will be rescinded. If you want to be invited again, you must ask the [IAM Manager](/iam/reference-content/permission-sets/) or [Owner](/iam/concepts/#owner) of the Organization. You are redirected to the overview page of the Organization to which you were invited. - As an [IAM user](/identity-and-access-management/iam/concepts/#user) of an Organization, you must always ensure that you are in the desired Organization by checking the Organization name that displays in the top right corner of your console. + As an [IAM user](/iam/concepts/#user) of an Organization, you must always ensure that you are in the desired Organization by checking the Organization name that displays in the top right corner of your console. In the image below, we are currently in the Marion Créange Organization (highlighted in red). Use the drop-down menu to navigate to a different Organization. For example, below, we could switch to the Documentation Team Organization. diff --git a/identity-and-access-management/iam/how-to/create-api-keys.mdx b/identity-and-access-management/iam/how-to/create-api-keys.mdx index afa32e47db..0fb25cebd1 100644 --- a/identity-and-access-management/iam/how-to/create-api-keys.mdx +++ b/identity-and-access-management/iam/how-to/create-api-keys.mdx @@ -11,17 +11,17 @@ dates: posted: 2022-06-20 --- -API keys are unique identifiers necessary to use the [Scaleway API](https://www.scaleway.com/en/developers/api/). You can generate API keys for yourself or for an [IAM application](/identity-and-access-management/iam/concepts/#application) via the Scaleway console. Each API key is scoped to one [Organization](/identity-and-access-management/iam/concepts/#organization) only (so if you are part of multiple Organizations, you will need a different API key for each one). Each user and application can have multiple API keys in each Organization. +API keys are unique identifiers necessary to use the [Scaleway API](https://www.scaleway.com/en/developers/api/). You can generate API keys for yourself or for an [IAM application](/iam/concepts/#application) via the Scaleway console. Each API key is scoped to one [Organization](/iam/concepts/#organization) only (so if you are part of multiple Organizations, you will need a different API key for each one). Each user and application can have multiple API keys in each Organization. -API keys always inherit the permissions of their bearer (the IAM user or IAM application with which they are associated), giving that bearer the exact rights and permissions that have been defined for them in the Organization via [policies](/identity-and-access-management/iam/concepts/#policy). +API keys always inherit the permissions of their bearer (the IAM user or IAM application with which they are associated), giving that bearer the exact rights and permissions that have been defined for them in the Organization via [policies](/iam/concepts/#policy). - - You can only generate API keys for yourself and, if you are the Organization Owner or have [IAMManager permissions](/identity-and-access-management/iam/reference-content/permission-sets/), for IAM applications. You cannot generate API keys for other IAM users, regardless of your permissions. + - You can only generate API keys for yourself and, if you are the Organization Owner or have [IAMManager permissions](/iam/reference-content/permission-sets/), for IAM applications. You cannot generate API keys for other IAM users, regardless of your permissions. - You can attach API keys to your own user to test and access your infrastructure, but we do not recommend this for all use cases. - If you plan to create API keys that will be used for a long period of time, in production for example, we recommend that you use [applications](/identity-and-access-management/iam/concepts/#application) as the bearers of these API keys. This way, the API keys are linked to non-human users, and are under no risk of leaving or being removed from the Organization. + If you plan to create API keys that will be used for a long period of time, in production for example, we recommend that you use [applications](/iam/concepts/#application) as the bearers of these API keys. This way, the API keys are linked to non-human users, and are under no risk of leaving or being removed from the Organization. @@ -35,7 +35,7 @@ API keys always inherit the permissions of their bearer (the IAM user or IAM app 3. Click **+ Generate API key**. The following screen pops up: -4. Select the **bearer** of the API key. Choose between yourself (as an IAM user), or an [IAM application](/identity-and-access-management/iam/concepts/#application) associated with the Organization. +4. Select the **bearer** of the API key. Choose between yourself (as an IAM user), or an [IAM application](/iam/concepts/#application) associated with the Organization. 5. Enter an optional **description** for the API key. 6. Enter the desired **expiration**. Choose from: - **Never**: the API key will never expire, @@ -43,15 +43,15 @@ API keys always inherit the permissions of their bearer (the IAM user or IAM app - **Custom**: you are prompted to enter a **date** on which the API key will expire. 7. Select whether the API key will be used for Object Storage. Choose from: - - **Yes, set up preferred Project**: you are prompted to select a [Project](/identity-and-access-management/iam/concepts/#project) that the API key will always use for Object Storage operations. - - **No, skip for now**: the Project that you are currently navigating in the console (i.e. the one that is selected in your [Project dashboard](/identity-and-access-management/organizations-and-projects/concepts/#project-dashboard)) will be automatically selected as the preferred Project for Object Storage. + - **Yes, set up preferred Project**: you are prompted to select a [Project](/iam/concepts/#project) that the API key will always use for Object Storage operations. + - **No, skip for now**: the Project that you are currently navigating in the console (i.e. the one that is selected in your [Project dashboard](/organizations-and-projects/concepts/#project-dashboard)) will be automatically selected as the preferred Project for Object Storage. Preferred Projects for Object Storage - When creating and/or listing Object Storage buckets via the API, there is no available parameter to specify the Project in which you wish to list or create buckets. All buckets you create via the API will therefore be created in the preferred Project you choose when creating the API key. Similarly, when listing buckets, buckets from your preferred Project will be listed. Note that: - This only applies to the creation and/or listing of Object Storage buckets, and no other products or resources. - You can still create and/or list buckets in your Project of choice via the Scaleway console. - See our [dedicated documentation](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) for more information. + See our [dedicated documentation](/iam/api-cli/using-api-key-object-storage/) for more information. 8. Click **Generate API key**. A screen displays showing the access key and secret key for your new API key and reminding you that this is your only chance to securely save the secret key: diff --git a/identity-and-access-management/iam/how-to/create-application.mdx b/identity-and-access-management/iam/how-to/create-application.mdx index cfc7e21e00..7c32c09440 100644 --- a/identity-and-access-management/iam/how-to/create-application.mdx +++ b/identity-and-access-management/iam/how-to/create-application.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -An IAM application is a non-human user in an [Organization](/identity-and-access-management/iam/concepts/#organization). This feature lets you create API keys that are not linked to a specific user, to give programmatic access to resources and make your production code more robust. As with users, you can define permissions and access rights for each IAM application via policies. +An IAM application is a non-human user in an [Organization](/iam/concepts/#organization). This feature lets you create API keys that are not linked to a specific user, to give programmatic access to resources and make your production code more robust. As with users, you can define permissions and access rights for each IAM application via policies. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. diff --git a/identity-and-access-management/iam/how-to/create-group.mdx b/identity-and-access-management/iam/how-to/create-group.mdx index 8e9f91ceee..f6d852323e 100644 --- a/identity-and-access-management/iam/how-to/create-group.mdx +++ b/identity-and-access-management/iam/how-to/create-group.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -An IAM group is a grouping of users and/or applications. Groups allow you to attach [policies](/identity-and-access-management/iam/concepts/#policy) to multiple users at the same time. +An IAM group is a grouping of users and/or applications. Groups allow you to attach [policies](/iam/concepts/#policy) to multiple users at the same time. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. diff --git a/identity-and-access-management/iam/how-to/create-policy.mdx b/identity-and-access-management/iam/how-to/create-policy.mdx index 17aa85126e..ee01eae581 100644 --- a/identity-and-access-management/iam/how-to/create-policy.mdx +++ b/identity-and-access-management/iam/how-to/create-policy.mdx @@ -10,14 +10,14 @@ dates: posted: 2022-06-20 --- -An IAM [policy](/identity-and-access-management/iam/reference-content/policy/) is used to define the permissions of users, groups, and applications in a given [Organization](/identity-and-access-management/iam/concepts/#organization). A policy is composed of a **principal** (the user, group, or application to which it applies) and one or more **IAM rules** (which describe the permission sets the principal should have, and the scope of those permission sets). +An IAM [policy](/iam/reference-content/policy/) is used to define the permissions of users, groups, and applications in a given [Organization](/iam/concepts/#organization). A policy is composed of a **principal** (the user, group, or application to which it applies) and one or more **IAM rules** (which describe the permission sets the principal should have, and the scope of those permission sets). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from the top-right of your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. @@ -35,20 +35,20 @@ An IAM [policy](/identity-and-access-management/iam/reference-content/policy/) i - The same tag cannot be used twice - Enter a **description** (optional), - - Select a **principal**, who will be the target of your policy. The [principal](/identity-and-access-management/iam/concepts/#principal) should be the user, application, or group who you want to grant specific permissions to through this policy. + - Select a **principal**, who will be the target of your policy. The [principal](/iam/concepts/#principal) should be the user, application, or group who you want to grant specific permissions to through this policy. You can choose to create a policy without a principal for now, and attach the principal later. Be aware that the policy will have no effect until a principal is attached. A policy can only be attached to one principal at a time. 5. Click **Add rules** to progress to the next part of the policy creation wizard. - Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/identity-and-access-management/iam/reference-content/policy/). + Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/iam/reference-content/policy/). 6. Select a **scope** for the rule: - - To give the principal permissions to view, create, edit and/or delete [resources](/identity-and-access-management/iam/concepts/#resource), select the **Access to resources** scope. Then, select the [Project](/identity-and-access-management/iam/concepts/#project) in which you want the permissions to apply. You can select from **all current and future Projects**, **all current Projects** or select specific Projects. - - To give the principal permissions to [Organization](/identity-and-access-management/iam/concepts/#organization)-level features such as IAM, billing, support & abuse tickets and project management, select the **Access to Organization features** scope. + - To give the principal permissions to view, create, edit and/or delete [resources](/iam/concepts/#resource), select the **Access to resources** scope. Then, select the [Project](/iam/concepts/#project) in which you want the permissions to apply. You can select from **all current and future Projects**, **all current Projects** or select specific Projects. + - To give the principal permissions to [Organization](/iam/concepts/#organization)-level features such as IAM, billing, support & abuse tickets and project management, select the **Access to Organization features** scope. 7. Click **Validate** to continue. -8. Choose the **permission sets** for the rule by selecting the required boxes. You can select as many permission sets as you like. The principal will have the rights defined in these permission sets within the scope you set in **step 6**. See our dedicated documentation for [more help with permission sets](/identity-and-access-management/iam/reference-content/permission-sets/). +8. Choose the **permission sets** for the rule by selecting the required boxes. You can select as many permission sets as you like. The principal will have the rights defined in these permission sets within the scope you set in **step 6**. See our dedicated documentation for [more help with permission sets](/iam/reference-content/permission-sets/). 9. Click **Validate**. The rule, with its scope and permission sets, is added to the list of the policy's rules. 10. Click **Add new rule** and repeat steps 6-8 as many times as required to add multiple rules to your policy. diff --git a/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx b/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx index 39f94d8122..f2dd2eab49 100644 --- a/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx +++ b/identity-and-access-management/iam/how-to/invite-user-to-orga.mdx @@ -10,24 +10,24 @@ dates: posted: 2022-06-20 --- -When you [create a Scaleway account](/console/account/how-to/create-an-account/), you are the [Owner](/identity-and-access-management/iam/concepts/#owner) of your Organization. You can invite other people to join your Organization: they will create their own Scaleway account (if they do not already have one) and then become [IAM users](/identity-and-access-management/iam/concepts/#user) of your Organization. +When you [create a Scaleway account](/account/how-to/create-an-account/), you are the [Owner](/iam/concepts/#owner) of your Organization. You can invite other people to join your Organization: they will create their own Scaleway account (if they do not already have one) and then become [IAM users](/iam/concepts/#user) of your Organization. -You can define the rights and permissions you want guests to have in your Organization via [policies](/identity-and-access-management/iam/concepts/#policy). +You can define the rights and permissions you want guests to have in your Organization via [policies](/iam/concepts/#policy). -You can invite people to be IAM users of an Organization in which you are not the Owner, if you have sufficient permissions (via policies) to do so. See our documentation on [permission sets](/identity-and-access-management/iam/reference-content/permission-sets/) for more information. +You can invite people to be IAM users of an Organization in which you are not the Owner, if you have sufficient permissions (via policies) to do so. See our documentation on [permission sets](/iam/reference-content/permission-sets/) for more information. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from the top-right of your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. 2. Click **+ Add user**. The following screen displays: -3. Enter the email address of the person you want to invite. If you want to invite more than one user, enter multiple email addresses separated by commas. Optionally, you can also select a [group](/identity-and-access-management/iam/concepts/#group) to add the user to. +3. Enter the email address of the person you want to invite. If you want to invite more than one user, enter multiple email addresses separated by commas. Optionally, you can also select a [group](/iam/concepts/#group) to add the user to. 4. Optionally, add one or more tags. @@ -37,10 +37,10 @@ You can invite people to be IAM users of an Organization in which you are not th - The same tag cannot be used twice 5. Click **Invite** to send the invitation. - The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/console/account/how-to/create-an-account/) first. + The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/account/how-to/create-an-account/) first. 6. The user will appear in the list of your Organization's users once they have accepted the invitation. Invitations have a validity period of 7 days. - Once an invitation expires, or if it is rejected, an [IAM log](/identity-and-access-management/iam/how-to/view-logs) is created indicating the user was "deleted". + Once an invitation expires, or if it is rejected, an [IAM log](/iam/how-to/view-logs) is created indicating the user was "deleted". diff --git a/identity-and-access-management/iam/how-to/manage-api-keys.mdx b/identity-and-access-management/iam/how-to/manage-api-keys.mdx index 5c5b278576..9ecf0638c4 100644 --- a/identity-and-access-management/iam/how-to/manage-api-keys.mdx +++ b/identity-and-access-management/iam/how-to/manage-api-keys.mdx @@ -10,7 +10,7 @@ dates: posted: 2022-06-20 --- -All users are able to view and delete their own API keys as necessary. API keys can also be edited, to change the description or [preferred Project](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/). Instructions for these actions are given below. If you are the Owner of your Organization, or have [sufficient permissions](/identity-and-access-management/iam/reference-content/permission-sets/) to do so, you can also view, edit and delete the API keys of other IAM users / applications. +All users are able to view and delete their own API keys as necessary. API keys can also be edited, to change the description or [preferred Project](/iam/api-cli/using-api-key-object-storage/). Instructions for these actions are given below. If you are the Owner of your Organization, or have [sufficient permissions](/iam/reference-content/permission-sets/) to do so, you can also view, edit and delete the API keys of other IAM users / applications. @@ -27,7 +27,7 @@ All users are able to view and delete their own API keys as necessary. API keys 4. Edit the API key as required: - Edit the **description**, and/or - - Change the [preferred Project](/identity-and-access-management/iam/concepts/#preferred-project) for Object Storage + - Change the [preferred Project](/iam/concepts/#preferred-project) for Object Storage 5. Click **Validate** to finish. The API key is edited, and you are returned to the list of API keys. ## How to delete an API key diff --git a/identity-and-access-management/iam/how-to/manage-applications.mdx b/identity-and-access-management/iam/how-to/manage-applications.mdx index c5b0fb26c2..9f6dedb384 100644 --- a/identity-and-access-management/iam/how-to/manage-applications.mdx +++ b/identity-and-access-management/iam/how-to/manage-applications.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -You can manage IAM applications in an Organization if you are the [Owner](/identity-and-access-management/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/identity-and-access-management/iam/concepts/#policy)) to do so. Management actions including adding and removing IAM applications to/from groups, attaching and detaching policies to/from applications, generating, viewing and deleting applications' API keys and deleting applications from the Organization. +You can manage IAM applications in an Organization if you are the [Owner](/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/iam/concepts/#policy)) to do so. Management actions including adding and removing IAM applications to/from groups, attaching and detaching policies to/from applications, generating, viewing and deleting applications' API keys and deleting applications from the Organization. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to access the application overview @@ -54,7 +54,7 @@ An application may be part of multiple groups at the same time. 3. Click **Validate** to finish. The application is added to the selected group, and you are returned to the **Overview** tab. - Learn [how to create a new IAM group](/identity-and-access-management/iam/how-to/create-group/). + Learn [how to create a new IAM group](/iam/how-to/create-group/). ## How to manage an application's policies @@ -66,7 +66,7 @@ From the application's [**Overview** tab](#how-to-access-the-application-overvie 1. Click the **X** button next to the policy you want to detach from the application. A pop-up displays asking you to confirm the action. 2. Click **Detach policy** to confirm. - Since policies can only be attached to one [principal](/identity-and-access-management/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. ### Attach another policy to an application @@ -78,7 +78,7 @@ An application may be attached to multiple policies. 3. Click **Validate** to finish. The selected policy is attached to the application, and you are returned to the **Overview** tab. - Learn [how to create a new policy](/identity-and-access-management/iam/how-to/create-policy/). + Learn [how to create a new policy](/iam/how-to/create-policy/). ## How to manage an application's API keys @@ -86,17 +86,17 @@ An application may be attached to multiple policies. ### View and create API keys 1. From the application's [Overview tab](#how-to-access-the-application-overview), click the **API keys** tab. - Here, you can view details of the application's [API keys](/identity-and-access-management/iam/how-to/create-api-keys/). + Here, you can view details of the application's [API keys](/iam/how-to/create-api-keys/). If you want to create a new API key for an application, proceed to the following steps: 2. Click **+ Generate an API key** to generate a new API key. The creation wizard displays. -3. Complete the information in the wizard. See our [dedicated documentation](/identity-and-access-management/iam/how-to/create-api-keys/) if you need any help with this step. +3. Complete the information in the wizard. See our [dedicated documentation](/iam/how-to/create-api-keys/) if you need any help with this step. 4. Ensure you have securely saved the secret key, then close the window. You are returned to the **API keys** tab, where the new API key now appears in the list. ### Edit API keys 1. From the application's [Overview tab](#how-to-access-the-application-overview), click the **API keys** tab. 2. Click > **Edit** next to the API key you wish to edit. -3. Edit the description and/or [preferred Project](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) of the API key as required, and click **Validate**. +3. Edit the description and/or [preferred Project](/iam/api-cli/using-api-key-object-storage/) of the API key as required, and click **Validate**. The API key is edited, and you are returned to the list of API keys. diff --git a/identity-and-access-management/iam/how-to/manage-groups.mdx b/identity-and-access-management/iam/how-to/manage-groups.mdx index 26fe9a960f..2b8a0e7078 100644 --- a/identity-and-access-management/iam/how-to/manage-groups.mdx +++ b/identity-and-access-management/iam/how-to/manage-groups.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -You can manage IAM groups in an Organization if you are the [Owner](/identity-and-access-management/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/identity-and-access-management/iam/concepts/#policy)) to do so. Management actions include adding and removing members to groups, attaching and detaching policies to/from groups and deleting groups from the Organization. +You can manage IAM groups in an Organization if you are the [Owner](/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/iam/concepts/#policy)) to do so. Management actions include adding and removing members to groups, attaching and detaching policies to/from groups and deleting groups from the Organization. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to access the group overview @@ -77,7 +77,7 @@ From the groups' [Overview page](#how-to-access-the-group-overview), scroll to t 1. In the **Policies** panel, click the **X** button next to the policy you want to detach from the group. A pop-up displays asking you to confirm the action. 2. Click **Detach policy** to confirm. - Since policies can only be attached to one [principal](/identity-and-access-management/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the application means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. ### Attach a policy to a group @@ -90,7 +90,7 @@ A group may be attached to multiple policies. The selected policy is attached to the group, and you are returned to the group's overview page. - To create a new policy, see our [dedicated how to](/identity-and-access-management/iam/how-to/create-policy/). + To create a new policy, see our [dedicated how to](/iam/how-to/create-policy/). ## How to delete a group diff --git a/identity-and-access-management/iam/how-to/manage-policies.mdx b/identity-and-access-management/iam/how-to/manage-policies.mdx index 9c7a0ff1f8..9df26a2613 100644 --- a/identity-and-access-management/iam/how-to/manage-policies.mdx +++ b/identity-and-access-management/iam/how-to/manage-policies.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -You can manage IAM [policies](/identity-and-access-management/iam/concepts/#policy) in an Organization if you are the [Owner](/identity-and-access-management/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via existing policies) to do so. Management actions including editing, attaching and detaching policies to/from groups and deleting groups from the Organization. +You can manage IAM [policies](/iam/concepts/#policy) in an Organization if you are the [Owner](/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via existing policies) to do so. Management actions including editing, attaching and detaching policies to/from groups and deleting groups from the Organization. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to access the policy overview @@ -40,13 +40,13 @@ From the policy's [Overview page](#how-to-access-the-policy-overview): 1. From the policy's [Overview page](#how-to-access-the-policy-overview), scroll down to the **Rules** panel and click next to the rule you want to edit. 2. Edit the rule as required, and click **Validate** to finish. - See our documentation about [creating policies](/identity-and-access-management/iam/how-to/create-policy/) for more help with building rules. + See our documentation about [creating policies](/iam/how-to/create-policy/) for more help with building rules. ## How to delete a policy - Be aware that when deleting a policy, all permissions it gives to its [principal](/identity-and-access-management/iam/concepts/#principal) (user, group, or application) will be revoked. + Be aware that when deleting a policy, all permissions it gives to its [principal](/iam/concepts/#principal) (user, group, or application) will be revoked. 1. From the policy's [Overview page](#how-to-access-the-policy-overview), scroll down to the **Delete policy** panel. diff --git a/identity-and-access-management/iam/how-to/manage-users.mdx b/identity-and-access-management/iam/how-to/manage-users.mdx index 9959cb38f0..871079d1dd 100644 --- a/identity-and-access-management/iam/how-to/manage-users.mdx +++ b/identity-and-access-management/iam/how-to/manage-users.mdx @@ -10,12 +10,12 @@ dates: posted: 2022-06-20 --- -You can manage IAM users of an Organization if you are the [Owner](/identity-and-access-management/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/identity-and-access-management/iam/concepts/#policy)) to do so. Management actions include adding and removing users to/from groups, attaching and detaching policies to/from users, viewing and deleting users' API keys and removing users from the Organization. +You can manage IAM users of an Organization if you are the [Owner](/iam/concepts/#owner) of that Organization, or if you have sufficient permissions (via [policies](/iam/concepts/#policy)) to do so. Management actions include adding and removing users to/from groups, attaching and detaching policies to/from users, viewing and deleting users' API keys and removing users from the Organization. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to access the user overview @@ -26,7 +26,7 @@ You can manage IAM users of an Organization if you are the [Owner](/identity-and ## How to view user information -From the user's [Overview tab](#how-to-access-the-user-overview), you can view information including the user's **status**, **type** (Guest or Owner), **joined on** date and whether they have [MFA](/console/account/concepts/#multifactor-authentication-mfa) enabled in the **User Information** panel at the top of the page. +From the user's [Overview tab](#how-to-access-the-user-overview), you can view information including the user's **status**, **type** (Guest or Owner), **joined on** date and whether they have [MFA](/account/concepts/#multifactor-authentication-mfa) enabled in the **User Information** panel at the top of the page. On this page you can also find an extensive list of the user's permission sets, the name of their associated policies and the scope they apply to. @@ -56,7 +56,7 @@ A user may be part of multiple groups at the same time. The user is added to the selected group, and you are returned to the **Overview** tab. - Learn [how to create a new IAM group](/identity-and-access-management/iam/how-to/create-group/). + Learn [how to create a new IAM group](/iam/how-to/create-group/). ## How to manage a user's policies @@ -70,7 +70,7 @@ From the user's [**Overview** tab](#how-to-access-the-user-overview), scroll dow 1. Click the **x** button next to the policy you want to detach from the user. A pop-up displays asking you to confirm the action. 2. Click **Detach policy** to confirm. - Since policies can only be attached to one [principal](/identity-and-access-management/iam/concepts/#principal) at a time, detaching a policy from the user means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. + Since policies can only be attached to one [principal](/iam/concepts/#principal) at a time, detaching a policy from the user means that the policy becomes orphaned. The policy will remain in your list of policies, but will have no effect until you attach it to another principal. ### Attach another policy to a user @@ -83,13 +83,13 @@ A user may be attached to multiple policies. The selected policy is attached to the user, and you are returned to the **Overview** tab. - To create a new policy, see our [dedicated how to](/identity-and-access-management/iam/how-to/create-policy/). + To create a new policy, see our [dedicated how to](/iam/how-to/create-policy/). ## How to view and delete user API keys 1. From the user's [Overview tab](#how-to-access-the-user-overview), click the **Credentials** tab. - You can view details of the user's [API keys](/identity-and-access-management/iam/how-to/create-api-keys/). + You can view details of the user's [API keys](/iam/how-to/create-api-keys/). You cannot see the secret key part of any API keys, nor can you create an API key for any IAM user other than yourself. @@ -102,7 +102,7 @@ A user may be attached to multiple policies. ## How to remove a user from the Organization - To remove any users other than yourself, you must either be the [Owner](/identity-and-access-management/iam/concepts#owner) of the Organization, or have [IAMManager permissions](/identity-and-access-management/iam/reference-content/permission-sets/). The exception to this is that you can always remove yourself as an IAM user from an Organization in which you are a [Guest](/identity-and-access-management/iam/concepts#guest), anytime. This equates to leaving the Organization. You cannot leave an Organization that you own. + To remove any users other than yourself, you must either be the [Owner](/iam/concepts#owner) of the Organization, or have [IAMManager permissions](/iam/reference-content/permission-sets/). The exception to this is that you can always remove yourself as an IAM user from an Organization in which you are a [Guest](/iam/concepts#guest), anytime. This equates to leaving the Organization. You cannot leave an Organization that you own. 1. From the user's [**Overview** tab](#how-to-access-the-user-overview), scroll down to the **Remove user** panel: diff --git a/identity-and-access-management/iam/how-to/view-logs.mdx b/identity-and-access-management/iam/how-to/view-logs.mdx index b632b3e6a5..608300e34b 100644 --- a/identity-and-access-management/iam/how-to/view-logs.mdx +++ b/identity-and-access-management/iam/how-to/view-logs.mdx @@ -14,7 +14,7 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from the top-right of your [Organization Dashboard](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. diff --git a/identity-and-access-management/iam/how-to/view-permission-sets.mdx b/identity-and-access-management/iam/how-to/view-permission-sets.mdx index 0124124b53..648423375b 100644 --- a/identity-and-access-management/iam/how-to/view-permission-sets.mdx +++ b/identity-and-access-management/iam/how-to/view-permission-sets.mdx @@ -14,7 +14,7 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from the top-right of the [Organization Dashboard](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. @@ -24,7 +24,7 @@ dates: 3. Scroll to the **Permission sets** section. -A list of your permission sets for the selected Organization displays. You can see the scope of the permissions, in which [IAM policy](/identity-and-access-management/iam/concepts/#policy) they were defined, and to which [principal](/identity-and-access-management/iam/concepts/#principal) they are attached to. +A list of your permission sets for the selected Organization displays. You can see the scope of the permissions, in which [IAM policy](/iam/concepts/#policy) they were defined, and to which [principal](/iam/concepts/#principal) they are attached to. diff --git a/identity-and-access-management/iam/index.mdx b/identity-and-access-management/iam/index.mdx index 99859dc141..dc59bc983f 100644 --- a/identity-and-access-management/iam/index.mdx +++ b/identity-and-access-management/iam/index.mdx @@ -8,7 +8,7 @@ meta: productName="IAM" productLogo="iam" description="Identity and Access Management helps you to securely share access to your Scaleway Organization and resources using highly customizable policies and rules." - url="/identity-and-access-management/iam/quickstart/" + url="/iam/quickstart/" label="IAM Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create applications, invite users to your Organization, and more, in a few steps." label="View Quickstart" - url="/identity-and-access-management/iam/quickstart/" + url="/iam/quickstart/" /> @@ -51,12 +51,12 @@ meta: diff --git a/identity-and-access-management/iam/quickstart.mdx b/identity-and-access-management/iam/quickstart.mdx index d659724e4f..919d0be34b 100644 --- a/identity-and-access-management/iam/quickstart.mdx +++ b/identity-and-access-management/iam/quickstart.mdx @@ -10,16 +10,16 @@ dates: posted: 2022-06-10 --- -**I**dentity and **A**ccess **M**anagement (IAM) allows you to share access to the management of your Scaleway resources and Organization settings, in a controlled and secure manner. With IAM, you can invite other users to your [Organization](/identity-and-access-management/iam/concepts/#organization), as well as create IAM applications that represent non-human users with their own API keys. You define permissions for users and applications in your Organization via highly customizable [policies](/identity-and-access-management/iam/concepts/#policy). Policies let you specify exactly what rights users and applications (or groups of users and applications) should have within your Organization. +**I**dentity and **A**ccess **M**anagement (IAM) allows you to share access to the management of your Scaleway resources and Organization settings, in a controlled and secure manner. With IAM, you can invite other users to your [Organization](/iam/concepts/#organization), as well as create IAM applications that represent non-human users with their own API keys. You define permissions for users and applications in your Organization via highly customizable [policies](/iam/concepts/#policy). Policies let you specify exactly what rights users and applications (or groups of users and applications) should have within your Organization. -Read our dedicated page for a [general overview of IAM](/identity-and-access-management/iam/reference-content/overview/) and how it works. +Read our dedicated page for a [general overview of IAM](/iam/reference-content/overview/) and how it works. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to invite a user to your Organization @@ -29,9 +29,9 @@ Invite other users to be able to give them access to your Organization. You will 2. Click **+ Add user**. The following screen displays: -3. Enter the email address of the person you want to invite. If you want to invite more than one user, enter multiple email addresses separated by commas. Optionally, you can also select a [group](/identity-and-access-management/iam/concepts/#group) to add the user to. +3. Enter the email address of the person you want to invite. If you want to invite more than one user, enter multiple email addresses separated by commas. Optionally, you can also select a [group](/iam/concepts/#group) to add the user to. 4. Click **Invite** to send the invitation. - The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/console/account/how-to/create-an-account/) first. + The user receives an email inviting them to accept your invitation. If they do not already have a Scaleway account, they will be prompted to [create one](/account/how-to/create-an-account/) first. 5. The user will appear in the list of your Organization's users once they have accepted the invitation. ## How to create an application @@ -54,7 +54,7 @@ IAM applications are non-human users in an Organization, enabling you to give pr ## How to give permissions to users and applications via policies -Users you have invited to your Organization, and applications you have created, have no rights or permissions until you attach [policies](/identity-and-access-management/iam/reference-content/policy/) to them, as described below. +Users you have invited to your Organization, and applications you have created, have no rights or permissions until you attach [policies](/iam/reference-content/policy/) to them, as described below. 1. Click **Identity and Access Management (IAM)** from the top-right of your [**Organization Dashboard**](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. 2. Click the **Policies** tab. A list of the Organization's existing policies displays: @@ -63,20 +63,20 @@ Users you have invited to your Organization, and applications you have created, 4. Complete the steps on the first page of the creation wizard: - Enter a **name** for the policy, - Enter a **description** (optional), - - Select a **principal**, who will be the target of your policy. The [principal](/identity-and-access-management/iam/concepts/#principal) should be the user, application, or group who you want to grant specific permissions to through this policy. + - Select a **principal**, who will be the target of your policy. The [principal](/iam/concepts/#principal) should be the user, application, or group who you want to grant specific permissions to through this policy. You can choose to create a policy without a principal for now, and attach the principal later. Be aware that the policy will have no effect until a principal is attached. A policy can only be attached to one principal at a time. 5. Click **Add rules** to progress to the next part of the policy creation wizard. - Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/identity-and-access-management/iam/reference-content/policy/). + Rules define the actions that the attached principal will be able to carry out within the Organization. When creating a rule, you first set the **scope** of the rule, and then select the **permission sets** to apply within the scope. See our dedicated documentation for more help with [policies, rules, scopes and permission sets](/iam/reference-content/policy/). 6. Select a **scope** for the rule: - - To give the principal permissions to view, create, edit and/or delete [resources](/identity-and-access-management/iam/concepts/#resource), select the **Access to resources** scope. Then, select the [Project](/identity-and-access-management/iam/concepts/#project) in which you want the permissions to apply. You can select from **all current and future Projects**, **all current Projects** or select specific Projects. - - To give the principal permissions to [Organization](/identity-and-access-management/iam/concepts/#organization)-level features such as IAM, billing, support & abuse tickets and project management, select the **Access to Organization features** scope. + - To give the principal permissions to view, create, edit and/or delete [resources](/iam/concepts/#resource), select the **Access to resources** scope. Then, select the [Project](/iam/concepts/#project) in which you want the permissions to apply. You can select from **all current and future Projects**, **all current Projects** or select specific Projects. + - To give the principal permissions to [Organization](/iam/concepts/#organization)-level features such as IAM, billing, support & abuse tickets and project management, select the **Access to Organization features** scope. 7. Click **Validate** to continue. -8. Choose the **permission sets** for the rule by selecting the required boxes. You can select as many permission sets as you like. The principal will have the rights defined in these permission sets within the scope you set in **step 6**. See our dedicated documentation for [more help with permission sets](/identity-and-access-management/iam/reference-content/permission-sets/). +8. Choose the **permission sets** for the rule by selecting the required boxes. You can select as many permission sets as you like. The principal will have the rights defined in these permission sets within the scope you set in **step 6**. See our dedicated documentation for [more help with permission sets](/iam/reference-content/permission-sets/). 9. Click **Validate**. The rule, with its scope and permission sets, is added to the list of the policy's rules. 10. Click **Add new rule** and repeat steps 6-8 as many times as required to add multiple rules to your policy. diff --git a/identity-and-access-management/iam/reference-content/overview.mdx b/identity-and-access-management/iam/reference-content/overview.mdx index 7cb9d1a04f..21188d7695 100644 --- a/identity-and-access-management/iam/reference-content/overview.mdx +++ b/identity-and-access-management/iam/reference-content/overview.mdx @@ -21,13 +21,13 @@ Organizations, Projects and resources are fundamental Scaleway concepts. Knowing ### Your Organization -When you create your Scaleway account, an [Organization](/identity-and-access-management/iam/concepts/#organization) is automatically created, of which you are the Owner. You have full access and rights to all resources within your own Organization, as well as to Organization management features (support plans, abuse tickets, support tickets etc.), billing and IAM features, as shown in the diagram below. +When you create your Scaleway account, an [Organization](/iam/concepts/#organization) is automatically created, of which you are the Owner. You have full access and rights to all resources within your own Organization, as well as to Organization management features (support plans, abuse tickets, support tickets etc.), billing and IAM features, as shown in the diagram below. ### Creating Resources & Projects -Once you set up your account, you can start creating resources such as Instances, Kubernetes Kapsules, Elastic Metal servers, etc. All resources that you create are added to your Organization's default [Project](/identity-and-access-management/iam/concepts/#project). However, you can choose to create multiple other Projects in your Organization, which lets you separate and group your resources as you wish. +Once you set up your account, you can start creating resources such as Instances, Kubernetes Kapsules, Elastic Metal servers, etc. All resources that you create are added to your Organization's default [Project](/iam/concepts/#project). However, you can choose to create multiple other Projects in your Organization, which lets you separate and group your resources as you wish. ## IAM @@ -35,9 +35,9 @@ Once you set up your account, you can start creating resources such as Instances If you want to give someone else permission to view, edit, create or manage resources (or features such as billing or support tickets) in your Organization, IAM makes this possible: -1. [Invite the user](/identity-and-access-management/iam/how-to/invite-user-to-orga/) to your Organization. They create their own Scaleway account, if they do not already have one, and can then accept your invitation. They will appear in your Organization as a Guest. +1. [Invite the user](/iam/how-to/invite-user-to-orga/) to your Organization. They create their own Scaleway account, if they do not already have one, and can then accept your invitation. They will appear in your Organization as a Guest. -2. Give the user permissions via [policies](/identity-and-access-management/iam/concepts/#policy). Create a policy to define what permissions and access rights you want the user to have in your Organization. +2. Give the user permissions via [policies](/iam/concepts/#policy). Create a policy to define what permissions and access rights you want the user to have in your Organization. Below are two examples of contrasting use cases for permissions: @@ -45,32 +45,32 @@ Below are two examples of contrasting use cases for permissions: - **Use case 1 - Extensive permissions**: You may give full rights to view and manage billing, IAM and Organization management features in your Organization, along with full rights to create, edit and view any type of resources in any and all current and future Projects. - **Use case 2 - Limited permissions**: You may give very restricted rights to simply view and list a single type of resource in one defined Project, e.g. “list Instances in Project A only”. -In reality, you will often want to give permissions sitting somewhere between the two use cases above. With IAM, you can define permissions in a very granular way. When you create your policy [rules](/identity-and-access-management/iam/concepts/#rule), you can accord exactly the rights ([permission sets](/identity-and-access-management/iam/concepts/#permission-set)) you want to give to each user for each specific type of resource. You can also give different permissions for different Projects and for different Organization-level features such as billing, support and IAM, thanks to the [scope](/identity-and-access-management/iam/concepts/#scope) feature. +In reality, you will often want to give permissions sitting somewhere between the two use cases above. With IAM, you can define permissions in a very granular way. When you create your policy [rules](/iam/concepts/#rule), you can accord exactly the rights ([permission sets](/iam/concepts/#permission-set)) you want to give to each user for each specific type of resource. You can also give different permissions for different Projects and for different Organization-level features such as billing, support and IAM, thanks to the [scope](/iam/concepts/#scope) feature. -Check out our full documentation on [policies](/identity-and-access-management/iam/reference-content/policy/) for detailed instructions. +Check out our full documentation on [policies](/iam/reference-content/policy/) for detailed instructions. ### Creating IAM applications -You may want to give access to your Organization and resources not to a specific human user, but to an application or service, e.g. when setting up a production environment. You can do this by creating [IAM applications](/identity-and-access-management/iam/concepts/#application). This feature lets you give programmatic access to resources by creating API keys that are not linked to a specific human, making your production code more robust. As with users, you can give permissions and access rights to each IAM application via policies. +You may want to give access to your Organization and resources not to a specific human user, but to an application or service, e.g. when setting up a production environment. You can do this by creating [IAM applications](/iam/concepts/#application). This feature lets you give programmatic access to resources by creating API keys that are not linked to a specific human, making your production code more robust. As with users, you can give permissions and access rights to each IAM application via policies. ### Defining groups -When you create a policy to define permissions for IAM users and applications, the [Groups](/identity-and-access-management/iam/concepts/#group) feature lets you apply one policy to multiple users and/or applications at the same time. For example, you can create a group called “Billing”, add all the users/applications who need access to billing, and then attach a policy to the group which gives rights to manage your Organization's billing. +When you create a policy to define permissions for IAM users and applications, the [Groups](/iam/concepts/#group) feature lets you apply one policy to multiple users and/or applications at the same time. For example, you can create a group called “Billing”, add all the users/applications who need access to billing, and then attach a policy to the group which gives rights to manage your Organization's billing. ### Generating API keys -You can use the [Scaleway console](https://console.scaleway.com) to create and manage resources without needing an [API key](/identity-and-access-management/iam/concepts/#api-key). However, an API key is necessary if you want to use the [Scaleway API](https://www.scaleway.com/en/developers/api/). +You can use the [Scaleway console](https://console.scaleway.com) to create and manage resources without needing an [API key](/iam/concepts/#api-key). However, an API key is necessary if you want to use the [Scaleway API](https://www.scaleway.com/en/developers/api/). -With the introduction of IAM, an API key is now associated with an IAM [user](/identity-and-access-management/iam/concepts/#user) or [application](/identity-and-access-management/iam/concepts/#application), and is always scoped per Organization. API keys inherit their permissions from their bearer (the user or application). You can generate one or several API keys for yourself in each of your Organizations via the console. If you are creating an IAM application, you can also generate API keys for that application. You cannot generate API keys for other human IAM users regardless of your IAM permissions, though you may be able to delete others' API keys within your Organization. +With the introduction of IAM, an API key is now associated with an IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application), and is always scoped per Organization. API keys inherit their permissions from their bearer (the user or application). You can generate one or several API keys for yourself in each of your Organizations via the console. If you are creating an IAM application, you can also generate API keys for that application. You cannot generate API keys for other human IAM users regardless of your IAM permissions, though you may be able to delete others' API keys within your Organization. ## Getting started -Check out our [quickstart](/identity-and-access-management/iam/quickstart/) or [full range of IAM documentation](/identity-and-access-management/iam/) to learn more. +Check out our [quickstart](/iam/quickstart/) or [full range of IAM documentation](/iam/) to learn more. diff --git a/identity-and-access-management/iam/reference-content/permission-sets.mdx b/identity-and-access-management/iam/reference-content/permission-sets.mdx index 892a052b6d..89c2f16cd8 100644 --- a/identity-and-access-management/iam/reference-content/permission-sets.mdx +++ b/identity-and-access-management/iam/reference-content/permission-sets.mdx @@ -9,7 +9,7 @@ dates: validation: 2024-10-23 --- -Permissions sets and their scope make up [IAM rules](/identity-and-access-management/iam/concepts/#rule), which define the access rights that a principal (user, group or application) should have. They consist of sets of one or multiple [permissions](/identity-and-access-management/iam/concepts/#permission). +Permissions sets and their scope make up [IAM rules](/iam/concepts/#rule), which define the access rights that a principal (user, group or application) should have. They consist of sets of one or multiple [permissions](/iam/concepts/#permission). Permission set names contain descriptions that clearly explain their purpose. For example, a permission set that grants access to all actions you can perform on Instances is called: `InstancesFullAccess`. diff --git a/identity-and-access-management/iam/reference-content/policy.mdx b/identity-and-access-management/iam/reference-content/policy.mdx index 25344af96f..9d0761c2ae 100644 --- a/identity-and-access-management/iam/reference-content/policy.mdx +++ b/identity-and-access-management/iam/reference-content/policy.mdx @@ -24,7 +24,7 @@ They are composed of: ## Principal -A principal is an entity that can be attached to a policy. Currently, you can attach either a [user](/identity-and-access-management/iam/reference-content/users-groups-and-applications/#users), a [group](/identity-and-access-management/iam/reference-content/users-groups-and-applications/#groups), or an [application](/identity-and-access-management/iam/reference-content/users-groups-and-applications/#applications) to a policy. Only one principal can be attached to each policy. +A principal is an entity that can be attached to a policy. Currently, you can attach either a [user](/iam/reference-content/users-groups-and-applications/#users), a [group](/iam/reference-content/users-groups-and-applications/#groups), or an [application](/iam/reference-content/users-groups-and-applications/#applications) to a policy. Only one principal can be attached to each policy. If a user or application is the principal of multiple policies, whether as sole principal or as part of a group, they benefit from all the permissions defined in each of these policies. @@ -32,7 +32,7 @@ A principal is an entity that can be attached to a policy. Currently, you can at ## Rules -A rule is the part of a policy that defines the permissions of the policy's [principal](/identity-and-access-management/iam/concepts/#principal), and the [scope](/identity-and-access-management/iam/concepts/#scope) of these permissions. It consists of a **scope** (at Project level or Organization level) and one or more **permission sets** (eg. "list all Instances"). +A rule is the part of a policy that defines the permissions of the policy's [principal](/iam/concepts/#principal), and the [scope](/iam/concepts/#scope) of these permissions. It consists of a **scope** (at Project level or Organization level) and one or more **permission sets** (eg. "list all Instances"). @@ -52,7 +52,7 @@ A scope defines where the permission sets should apply. At Scaleway, a scope can A permission set consists of one or multiple permissions to perform actions on resources or features. Each permission set has a clear description, e.g. `InstancesFullAccess`, `InstancesReadOnly`, `RelationalDatabaseFullAccess`, `BillingReadOnly`. - You can find a detailed list of all permission sets available at Scaleway in the permission sets [reference page](/identity-and-access-management/iam/reference-content/permission-sets/). + You can find a detailed list of all permission sets available at Scaleway in the permission sets [reference page](/iam/reference-content/permission-sets/). ### Example rule diff --git a/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx b/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx index 6bc5d2323f..8d961cebde 100644 --- a/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx +++ b/identity-and-access-management/iam/reference-content/reproduce-roles-project-api-keys.mdx @@ -13,7 +13,7 @@ categories: - console --- -[Identity and Access Management](/identity-and-access-management/iam/concepts/) provides a set of concepts and features to help you easily manage access to your Scaleway Organization. +[Identity and Access Management](/iam/concepts/) provides a set of concepts and features to help you easily manage access to your Scaleway Organization. If you created your Organization before December 5 2022, you may be used to using roles and Project-scoped API keys to grant rights: - Each user could have a role (Administrator, Billing Administrator or Editor) which gave specific permissions. @@ -23,7 +23,7 @@ We strongly recommend that you apply the principle of the least privilege when s ## How can I reproduce the deprecated roles of Administrator, Billing Administrator and Editor? -When your Organization was migrated to IAM, three [groups](/identity-and-access-management/iam/concepts/#group) were created, with three [policies](/identity-and-access-management/iam/concepts/#policy) attached to them. +When your Organization was migrated to IAM, three [groups](/iam/concepts/#group) were created, with three [policies](/iam/concepts/#policy) attached to them. @@ -33,9 +33,9 @@ You can keep adding users to these groups if you want to preserve the “old” If you previously deleted these groups from your Organization, you can recreate them by following these steps: -1. [Create a group](/identity-and-access-management/iam/how-to/create-group/) from the Groups tab, preferably with a name related to the corresponding role (e.g. “Administrators”, “Editors” or “Billing Administrators”). +1. [Create a group](/iam/how-to/create-group/) from the Groups tab, preferably with a name related to the corresponding role (e.g. “Administrators”, “Editors” or “Billing Administrators”). -2. [Create a policy](/identity-and-access-management/iam/how-to/create-policy/) from the Policies tab, attached to the group you have just created and with the appropriate permission sets: +2. [Create a policy](/iam/how-to/create-policy/) from the Policies tab, attached to the group you have just created and with the appropriate permission sets: | Former role | Necessary Permission Set | Scope for the Permission Set | @@ -46,18 +46,18 @@ If you previously deleted these groups from your Organization, you can recreate ## How can I reproduce Project-scoped API keys? -When your Organization was migrated to IAM, for each Project existing at the time of the migration, an [application](/identity-and-access-management/iam/concepts/#application) and a [policy](/identity-and-access-management/iam/concepts/#policy) were automatically created. These were both given the same name: `Project - [name of the project] (id of the project)`. +When your Organization was migrated to IAM, for each Project existing at the time of the migration, an [application](/iam/concepts/#application) and a [policy](/iam/concepts/#policy) were automatically created. These were both given the same name: `Project - [name of the project] (id of the project)`. If you want to create Project-scoped API keys for Projects created after your Organization migrated to IAM, follow these steps: -1. [Create an application](/identity-and-access-management/iam/how-to/create-application/), preferably with a name related to the Project. -2. [Create a policy](/identity-and-access-management/iam/how-to/create-policy/) from the policy tab, attached to the application you just created and with the permission set `AllProductsFullAccess` for the Project in question. +1. [Create an application](/iam/how-to/create-application/), preferably with a name related to the Project. +2. [Create a policy](/iam/how-to/create-policy/) from the policy tab, attached to the application you just created and with the permission set `AllProductsFullAccess` for the Project in question. Going forward, whenever you wish to create a new API key with full access to this Project, you can simply go to the application’s overview page, click the API keys tab, and create a new key. -If this API key will be used for Object Storage, make sure to select the Project in question as its [preferred Project for Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) when creating the key. +If this API key will be used for Object Storage, make sure to select the Project in question as its [preferred Project for Object Storage](/iam/api-cli/using-api-key-object-storage/) when creating the key. diff --git a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx index b4f56f3249..819f039b06 100644 --- a/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx +++ b/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas.mdx @@ -13,9 +13,9 @@ categories: - console --- -Every [Organization](/identity-and-access-management/iam/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Below is a list of quotas available for each resource. +Every [Organization](/iam/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Below is a list of quotas available for each resource. -At Scaleway, quotas are applicable per [Organization](/identity-and-access-management/iam/concepts/#organization). +At Scaleway, quotas are applicable per [Organization](/iam/concepts/#organization). If you have already validated your payment method and your identity and want to increase your quota beyond the values shown on this page, [contact our support team](https://console.scaleway.com/support/create). @@ -23,9 +23,9 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag ## Identity and Access Management -[Identity and Access Management (IAM)](/identity-and-access-management/iam/concepts/) allows you to share access to the management of your Scaleway resources, in a controlled and secure manner. +[Identity and Access Management (IAM)](/iam/concepts/) allows you to share access to the management of your Scaleway resources, in a controlled and secure manner. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card)| Payment method and [identity validated](/console/account/how-to/verify-identity/)| +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card)| Payment method and [identity validated](/account/how-to/verify-identity/)| |-------------|:----------------------------------------------------------------------------------------------------------:|:-----------------------------------------------------------------:| | API keys | 50 | 50 | | Applications| 100 | 100 | @@ -41,7 +41,7 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Maximum number of Projects in an Organization | 25 | 25 | @@ -54,7 +54,7 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | SSH keys allowed | 50 | 50 | @@ -62,64 +62,64 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| -| SMTP allowed | [Validate your identity](/console/account/how-to/verify-identity/) | Yes | +| SMTP allowed | [Validate your identity](/account/how-to/verify-identity/) | Yes | ## Instances - Quotas are applied manually for Enterprise (ENT) range Instances to Organizations that have their [identity validated](/console/account/how-to/verify-identity/). [Contact our support team.](https://console.scaleway.com/support/create) + Quotas are applied manually for Enterprise (ENT) range Instances to Organizations that have their [identity validated](/account/how-to/verify-identity/). [Contact our support team.](https://console.scaleway.com/support/create) -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/)| +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/)| |-------------|:----------------------------------------------------------------------------------------------------------:|:-----------------------------------------------------------------:| | DEV1-S | 10 | 20 | | DEV1-M | 8 | 15 | | DEV1-L | 5 | 10 | -| DEV1-XL | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 6 | +| DEV1-XL | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 6 | | PLAY2-PICO | 10 | 15 | | PLAY2-NANO | 5 | 10 | | PLAY2-MICRO | 3 | 5 | | GP1-XS | 1 | 4 | -| GP1-S | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| GP1-M | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | -| GP1-L | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| GP1-XL | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| GP1-S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| GP1-M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | +| GP1-L | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| GP1-XL | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | PRO2 XXS | 1 | 5 | -| PRO2 XS | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| PRO2 S | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| PRO2 M | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | -| PRO2 L | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| PRO2 XS | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| PRO2 S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| PRO2 M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | +| PRO2 L | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | ENT1 XXS | 1 | 5 | -| ENT1 XS | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| ENT1 S | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| ENT1 M | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | -| ENT1 L | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | -| ENT1 XL | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/).| +| ENT1 XS | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| ENT1 S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| ENT1 M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | +| ENT1 L | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | +| ENT1 XL | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | To use this product, you must [validate your identity](/account/how-to/verify-identity/).| | ENT1 2XL | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create)).| | POP2-2C-8G | 1 | 5 | -| POP2-4C-16G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| POP2-8C-32G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-16C-64G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-32C-128G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| POP2-4C-16G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| POP2-8C-32G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-16C-64G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-32C-128G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | POP2-64C-256G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create).| | POP2-HC-2C-4G | 1 | 5 | -| POP2-HC-4C-8G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| POP2-HC-8C-16G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-HC-16C-32G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-HC-32C-64G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| POP2-HC-4C-8G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| POP2-HC-8C-16G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-HC-16C-32G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-HC-32C-64G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | POP2-HC-64C-128G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create).| | POP2-HM-2C-16G | 1 | 5 | -| POP2-HM-4C-32G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | -| POP2-HM-8C-64G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-HM-16C-128G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-HM-32C-256G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| POP2-HM-4C-32G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | +| POP2-HM-8C-64G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-HM-16C-128G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-HM-32C-256G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | POP2-HM-64C-512G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create).| -| POP2-HN-3 | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| POP2-HN-5 | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | +| POP2-HN-3 | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| POP2-HN-5 | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | | POP2-HN-10 | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create).| @@ -131,17 +131,17 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag [Contact our support team](https://console.scaleway.com/support/create) if you want to increase your quotas to more than 1. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |-------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| -| RENDER-S | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | -| GPU 3070 - S| To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| RENDER-S | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | +| GPU 3070 - S| To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | H100-1-80G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | H100-2-80G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | -| L4-1-24G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| L4-1-24G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | L4-2-24G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | L4-4-24G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | L4-8-24G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | -| L40S-1-48G | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| L40S-1-48G | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | L40S-2-48G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | L40S-4-48G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | L40S-8-48G | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | @@ -150,49 +150,49 @@ At Scaleway, quotas are applicable per [Organization](/identity-and-access-manag -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |-------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| -| Apple silicon M1-M | 1 per [Availability Zone](/compute/instances/concepts/#availability-zone) | 3 per [Availability Zone](/compute/instances/concepts/#availability-zone) | -| Apple silicon M2-M | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 5 per [Availability Zone](/compute/instances/concepts/#availability-zone) | -| Apple silicon M2-L | 1 per [Availability Zone](/compute/instances/concepts/#availability-zone) | 5 per [Availability Zone](/compute/instances/concepts/#availability-zone) | +| Apple silicon M1-M | 1 per [Availability Zone](/instances/concepts/#availability-zone) | 3 per [Availability Zone](/instances/concepts/#availability-zone) | +| Apple silicon M2-M | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 5 per [Availability Zone](/instances/concepts/#availability-zone) | +| Apple silicon M2-L | 1 per [Availability Zone](/instances/concepts/#availability-zone) | 5 per [Availability Zone](/instances/concepts/#availability-zone) | ## Elastic Metal -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |-----------------|:----------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------:| | A210R SATA | 1 | 3 | | A310X SSD | 1 | 3 | | A315X SSD | 1 | 3 | -| A410X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | -| A510X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | -| A610R NVMe | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | +| A410X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | +| A510X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | +| A610R NVMe | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | | B111X SATA | 1 | 2 | | B112X SSD | 1 | 2 | -| B211X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B212X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B311X SATA | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B312X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B411X SATA | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B412X SSD | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | +| B211X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B212X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B311X SATA | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B312X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B411X SATA | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B412X SSD | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | | L101X SATA | 1 | 3 | -| L105X SATA | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 3 | -| L110X SATA | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | -| L210X SATA | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 1 | +| L105X SATA | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 3 | +| L110X SATA | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | +| L210X SATA | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 1 | | T210E NVMe | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | T510X NVMe | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | To use this product, you must [contact our support team](https://console.scaleway.com/support/create). | | B220E NVMe | 1 | 2 | -| B320E NVMe | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B420E NVMe | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | -| B420E NVMe | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 2 | +| B320E NVMe | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B420E NVMe | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | +| B420E NVMe | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 2 | After you order a server from the list of Elastic Metal servers compatible with Microsoft Windows Server, you can choose a version of Windows Server to install directly from our console. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |-----------------|:----------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------------------------:| | Windows License | Not available | Available | @@ -200,20 +200,20 @@ After you order a server from the list of Elastic Metal servers compatible with -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |------------------------------------------------------|:-----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------------------------------:| | Kubernetes Kapsule | 20 | 40 | | Kubernetes Kapsule with Dedicated control plane 4, 8 | 1 | 4 | -| Kubernetes Kapsule with Dedicated control plane 16 | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | +| Kubernetes Kapsule with Dedicated control plane 16 | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | | Kubernetes Kosmos | 20 | 40 | | Kubernetes Kosmos with Dedicated control plane 4, 8 | 1 | 4 | -| Kubernetes Kosmos with Dedicated control plane 16 | To use this product, you must [validate your identity](/console/account/how-to/verify-identity/). | 4 | +| Kubernetes Kosmos with Dedicated control plane 16 | To use this product, you must [validate your identity](/account/how-to/verify-identity/). | 4 | ## Container Registry -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Registry namespaces | 99 999 | 99 999 | | Registry images | 99 999 | 99 999 | @@ -225,14 +225,14 @@ After you order a server from the list of Elastic Metal servers compatible with #### Resources quotas -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Container namespaces | 25 | 25 | | Number of containers | 25 | 25 | #### RAM quotas -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Maximum RAM | 25 GB | 100 GB | @@ -246,14 +246,14 @@ For example, if you choose to create a container with 512 MB of memory and a max #### Resources quotas -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------|-------------------------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------| | Function namespaces | 10 | 20 | | Number of functions | 25 | 50 | #### RAM quotas -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------: |:------------------------------------------------------------------------------------:| | Maximum RAM | 25 GB | 100 GB | @@ -283,7 +283,7 @@ Note that in memory stream are not supported, please create your NATS stream usi ## Queues -Scaleway Queues is a product for creating managed messaging queues based on the [SQS](/serverless/messaging/concepts/#nats) protocol. The following usage limits are enforced as Organization quotas when using Scaleway NATS: +Scaleway Queues is a product for creating managed messaging queues based on the [SQS](/messaging/concepts/#nats) protocol. The following usage limits are enforced as Organization quotas when using Scaleway NATS: | Resource | Criteria | Limits | Scope | |------------------------------------------------|------------|----------|------------------| @@ -297,7 +297,7 @@ Scaleway Queues is a product for creating managed messaging queues based on the ## Topics and Events -Topics and Events is a product for creating managed messaging topics based on the [SNS](/serverless/messaging/concepts/#sns) protocol. The following usage limits are enforced as Organization quotas when using Scaleway NATS: +Topics and Events is a product for creating managed messaging topics based on the [SNS](/messaging/concepts/#sns) protocol. The following usage limits are enforced as Organization quotas when using Scaleway NATS: | Resource | Criteria | Limits | Scope | |------------------------------------------------|------------|----------|------------------| @@ -315,7 +315,7 @@ Local and Block Storage options are available with our compute offers. - The maximum Local Storage for a DEV Instance depends on the DEV Instance type. For example, for the DEV1-XL the maximum Local Storage is 120 GB. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/account/how-to/verify-identity/) | |------------------------------------------------|:------------------------------------------------------------------------------------------------------------:|:--------------------------------------------------------------------------------------:| | Block Storage total size in GB | 500 | 5 000 | | Local Storage total size in GB | 1 000 | 5 000 | @@ -329,7 +329,7 @@ Local and Block Storage options are available with our compute offers. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------------|:-----------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------:| | Object Storage buckets | 100 | 100 | @@ -337,7 +337,7 @@ Local and Block Storage options are available with our compute offers. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card ) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------------|:------------------------------------------------------------------------------------------------------------:|:------------------------------------------------------------------------------------:| | Database Instances | 5 | 10 | | Backups per Instance | 40 000 | 40 000 | @@ -351,7 +351,7 @@ Local and Block Storage options are available with our compute offers. Additional IP addresses and placement groups are available with our compute offers. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/)| +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/)| |---------------------------|:-----------------------------------------------------------------------------------------------------------:|:-----------------------------------------------------------------------------------:| | Elastic Metal Flexible IP | 64 | 64 | | Private Networks | 255 | 255 | @@ -366,7 +366,7 @@ Additional IP addresses and placement groups are available with our compute offe -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:-----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Public Gateway DHCP reservations | 1024 | 1024 | | Public Gateway DHCP servers | 255 | 255 | @@ -379,7 +379,7 @@ Additional IP addresses and placement groups are available with our compute offe -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Load Balancers | 50 | 50 | @@ -387,7 +387,7 @@ Additional IP addresses and placement groups are available with our compute offe -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Edge Services pipelines | 20 | 20 | @@ -395,7 +395,7 @@ Additional IP addresses and placement groups are available with our compute offe -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | Domain zones | 100 | 100 | | Domain user records | 10 000 | 10 000 | @@ -407,7 +407,7 @@ Additional IP addresses and placement groups are available with our compute offe -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |---------------------------|:----------------------------------------------------------------------------------------------------------:|:-------------------------------------------------------------:| | IoT Hubs Shared | 5 | 5 | | IoT Hubs Dedicated | 50 | 50 | @@ -424,7 +424,7 @@ Additional IP addresses and placement groups are available with our compute offe ## Transactional Email -Transactional Email is a platform that allows Scaleway clients to send [transactional emails](/managed-services/transactional-email/concepts/#transactional-email) with high quality [deliverability](/managed-services/transactional-email/concepts/#deliverability). +Transactional Email is a platform that allows Scaleway clients to send [transactional emails](/transactional-email/concepts/#transactional-email) with high quality [deliverability](/transactional-email/concepts/#deliverability). - Additional quotas can be added on a case-by-case basis. If you have already validated your payment method and your identity and want to increase your quota beyond the values shown on this page, [contact our support team](https://console.scaleway.com/support/create). @@ -432,7 +432,7 @@ Transactional Email is a platform that allows Scaleway clients to send [transact -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |-------------------------------------|-------------------------------------------------------------------------------------------------------------|------------------------------------------------------------------| | Max. of recipients | 3 | 3 | | Domains per Organization | 2 | 5 | @@ -445,9 +445,9 @@ Transactional Email is a platform that allows Scaleway clients to send [transact ## Secret Manager -Scaleway’s [Secret Manager](/identity-and-access-management/secret-manager/concepts/#secret-manager) allows you to conveniently store, access and share sensitive data such as passwords, API keys and certificates. +Scaleway’s [Secret Manager](/secret-manager/concepts/#secret-manager) allows you to conveniently store, access and share sensitive data such as passwords, API keys and certificates. -| Name | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| Name | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | Secrets | 100 | 250 | | Versions per secret | 20 | 20 | @@ -460,6 +460,6 @@ Web Hosting is a service that allows individuals and organizations to make their Scaleway provides several [Web Hosting plans](https://www.scaleway.com/en/web-hosting/) for individuals, professionals, and everyone in between. -| | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |--------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | Web Hostings | 1 | 2 | diff --git a/identity-and-access-management/organizations-and-projects/api-cli/managing-projects.mdx b/identity-and-access-management/organizations-and-projects/api-cli/managing-projects.mdx index c4238df179..f3361e5a44 100644 --- a/identity-and-access-management/organizations-and-projects/api-cli/managing-projects.mdx +++ b/identity-and-access-management/organizations-and-projects/api-cli/managing-projects.mdx @@ -18,8 +18,8 @@ This page explains how to manage Projects using [Scaleway APIs](https://www.scal - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Configured your API keys](/identity-and-access-management/iam/how-to/create-api-keys/) -- An API key with the [`IAMManager` or `ProjectManager` permission sets](/identity-and-access-management/iam/reference-content/permission-sets/) +- [Configured your API keys](/iam/how-to/create-api-keys/) +- An API key with the [`IAMManager` or `ProjectManager` permission sets](/iam/reference-content/permission-sets/) ## Creating a Project @@ -104,7 +104,7 @@ An output similar to the following displays: ## Retrieving a specific Project -You need your secret key and the ID of the Project you want to get for the step below. For this use case, we are getting the Project we have updated in the [updating Projects step](/identity-and-access-management/iam/api-cli/managing-projects/#updating-projects). +You need your secret key and the ID of the Project you want to get for the step below. For this use case, we are getting the Project we have updated in the [updating Projects step](/iam/api-cli/managing-projects/#updating-projects). Type the following command to list a specific Project. ``` @@ -124,7 +124,7 @@ An output similar to the following displays: ## Deleting a Project -You need your secret key and the ID of the Project you want to delete for the step below. For this use case, we are deleting the Project we have created in the [creating a Project step](/identity-and-access-management/iam/api-cli/managing-projects/#creating-a-project). +You need your secret key and the ID of the Project you want to delete for the step below. For this use case, we are deleting the Project we have created in the [creating a Project step](/iam/api-cli/managing-projects/#creating-a-project). 1. Type the following command to delete a Project. ``` diff --git a/identity-and-access-management/organizations-and-projects/concepts.mdx b/identity-and-access-management/organizations-and-projects/concepts.mdx index f69068b67d..e342c41484 100644 --- a/identity-and-access-management/organizations-and-projects/concepts.mdx +++ b/identity-and-access-management/organizations-and-projects/concepts.mdx @@ -14,7 +14,7 @@ categories: ## Default Project -Each [Organization](#organization) has at least one associated [Project](#project). Upon account creation, this Project is called **default**. The [Project name can be changed](/identity-and-access-management/organizations-and-projects/how-to/change-project-name/) later. The default Project takes on the Organization ID. Therefore, the default status cannot be transferred to other Projects. +Each [Organization](#organization) has at least one associated [Project](#project). Upon account creation, this Project is called **default**. The [Project name can be changed](/organizations-and-projects/how-to/change-project-name/) later. The default Project takes on the Organization ID. Therefore, the default status cannot be transferred to other Projects. ## Organization @@ -28,7 +28,7 @@ The Organization ID identifies the [Organization](#organization) created with yo ## Project -A Project is a grouping of Scaleway [resources](#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-region, meaning resources located in different [regions](/compute/instances/concepts/#region) can be grouped in one single Project. When grouping resources into different Projects, you can use [IAM](/identity-and-access-management/iam/concepts/#iam) to define custom access rights for each Project. +A Project is a grouping of Scaleway [resources](#resource). Each Scaleway Organization comes with a default Project, and you can create new Projects if necessary. Projects are cross-region, meaning resources located in different [regions](/instances/concepts/#region) can be grouped in one single Project. When grouping resources into different Projects, you can use [IAM](/iam/concepts/#iam) to define custom access rights for each Project. ## Project dashboard @@ -40,7 +40,7 @@ A Scaleway resource is either a product or a feature in the Scaleway Ecosystem. ## SSH key -An SSH key (**S**ecure **Sh**ell key) allows passwordless connection to an [Instance](/compute/instances/concepts/#instance). An SSH key is generated by creating an RSA key pair, consisting of two elements: +An SSH key (**S**ecure **Sh**ell key) allows passwordless connection to an [Instance](/instances/concepts/#instance). An SSH key is generated by creating an RSA key pair, consisting of two elements: - An **identification key** (also known as a private key), which you must keep securely on the computer you want to connect from. - A **public key** is uploaded to the Scaleway console, where it is displayed with a customizable name and a hash of its value, known as a fingerprint, to make it more identifiable. The private key is transferred to your Instance during the boot process. diff --git a/identity-and-access-management/organizations-and-projects/how-to/add-resources-project.mdx b/identity-and-access-management/organizations-and-projects/how-to/add-resources-project.mdx index 3b1a7794f3..b22f02f1f1 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/add-resources-project.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/add-resources-project.mdx @@ -16,11 +16,11 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added and validated a payment method](/console/billing/how-to/add-payment-method/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added and validated a payment method](/billing/how-to/add-payment-method/) - Make sure that you are editing the correct Project before adding new [resources](/identity-and-access-management/iam/concepts/#resource) to it. + Make sure that you are editing the correct Project before adding new [resources](/iam/concepts/#resource) to it. 1. Click the **Projects** tab from the [Organization Dashboard](https://console.scaleway.com/organization). A list of your Projects displays. @@ -35,7 +35,7 @@ categories: - It is currently not possible to transfer resources from one Project to another. For Object Storage, you can [import copies of your objects to buckets in different Projects](/storage/object/api-cli/migrating-buckets/). + It is currently not possible to transfer resources from one Project to another. For Object Storage, you can [import copies of your objects to buckets in different Projects](/object-storage/api-cli/migrating-buckets/). diff --git a/identity-and-access-management/organizations-and-projects/how-to/change-project-name.mdx b/identity-and-access-management/organizations-and-projects/how-to/change-project-name.mdx index 4aebc7de78..fe576f0212 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/change-project-name.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/change-project-name.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- a Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- a Scaleway [Project](/organizations-and-projects/concepts/#project) 1. Click the **Projects** tab from the [Organization Dashboard](https://console.scaleway.com/organization). A list of your Projects displays. 2. Click the name of the project you want to edit. diff --git a/identity-and-access-management/organizations-and-projects/how-to/create-a-project.mdx b/identity-and-access-management/organizations-and-projects/how-to/create-a-project.mdx index fb95a2c81e..8853c11f7d 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/create-a-project.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/create-a-project.mdx @@ -13,7 +13,7 @@ categories: - console --- -If you have a [Scaleway account](/console/account/how-to/create-an-account/), and subsequently an [Organization](/identity-and-access-management/iam/concepts/#organization), you will also automatically have a [default Project](/identity-and-access-management/organizations-and-projects/concepts/#default-project), that contains all your existing [resources](/identity-and-access-management/iam/concepts/#resource). You can also create additional Projects, allowing you to group your resources. +If you have a [Scaleway account](/account/how-to/create-an-account/), and subsequently an [Organization](/iam/concepts/#organization), you will also automatically have a [default Project](/organizations-and-projects/concepts/#default-project), that contains all your existing [resources](/iam/concepts/#resource). You can also create additional Projects, allowing you to group your resources. The default Project inherits the Organization ID. Therefore, the **default** status cannot be transferred to other Projects. @@ -22,7 +22,7 @@ If you have a [Scaleway account](/console/account/how-to/create-an-account/), an - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click the **Projects** tab from the [Organization Dashboard](https://console.scaleway.com/organization). A list of your Projects displays. 2. Click **+ Create Project** on the right-hand side. A pop-up displays. diff --git a/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key.mdx b/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key.mdx index 9e0704b005..dfd83c6633 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key.mdx @@ -13,7 +13,7 @@ categories: - console --- -[SSH keys](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key) allow you to securely connect to your Instances, Elastic Metal servers, and Mac minis without using a password. An SSH key consists of a key pair, which has two elements: +[SSH keys](/organizations-and-projects/concepts/#ssh-key) allow you to securely connect to your Instances, Elastic Metal servers, and Mac minis without using a password. An SSH key consists of a key pair, which has two elements: - An **identification key** (also known as a private key), which you must keep securely on the computer you want to connect from. - A **public key** is uploaded to the Scaleway console, where it is displayed with a customizable name and a hash of its value, known as a fingerprint, to make it more identifiable. The public key is transferred to your Instance during the boot process for authentication. @@ -23,7 +23,7 @@ You can generate the SSH key pair on your local machine. The process will depend - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to generate an Ed25519 SSH key pair @@ -127,19 +127,19 @@ On Windows, you can use the third-party application [PuTTYgen](https://www.chiar You must upload the content of the public part of the SSH key pair you just generated to the Scaleway interface. This is then transferred to your Instance during the boot process. You can then connect and authenticate from your local machine, where your private key is stored, to the remote Instance, where the public key can be found. -1. Log into the [Scaleway console](https://console.scaleway.com), and navigate to the [Credentials](/identity-and-access-management/iam/concepts/#api-key) tab of your Project Dashboard: +1. Log into the [Scaleway console](https://console.scaleway.com), and navigate to the [Credentials](/iam/concepts/#api-key) tab of your Project Dashboard: 2. Scroll down to the **SSH key** section, and click **Add a new SSH key**. 3. Paste the content of the public key (which you copied in the previous step) into the pop-up box, and optionally add a description. Then click **Add an SSH key**. - You will now be able to [connect to your Instances via SSH](/compute/instances/how-to/connect-to-instance/). + You will now be able to [connect to your Instances via SSH](/instances/how-to/connect-to-instance/). If you have any difficulties connecting to an Instance after uploading a new public SSH key to your Project, try the following: - If you cannot connect to your Instance at all via SSH, reboot your Instance from the console and try again. - If you can connect to your Instance using a previously uploaded SSH key but not the new one, go ahead and connect to your Instance with the old key. Once connected, run the `scw-fetch-ssh-keys --upgrade` command, which launches a script on your Instance to update your SSH keys. You can then check that the new key has been added to the `authorized_keys` file (`~/.ssh/authorized_keys`). Note that this command works only for Instances. - - For further information, refer to the [SSH connection troubleshooting](/compute/instances/troubleshooting/cant-connect-ssh/) documentation. + - For further information, refer to the [SSH connection troubleshooting](/instances/troubleshooting/cant-connect-ssh/) documentation. diff --git a/identity-and-access-management/organizations-and-projects/how-to/delete-a-project.mdx b/identity-and-access-management/organizations-and-projects/how-to/delete-a-project.mdx index f2b838683a..d7c2f2e3c7 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/delete-a-project.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/delete-a-project.mdx @@ -13,13 +13,13 @@ categories: - console --- -A Project can only be deleted once it has been emptied of its [resources](/identity-and-access-management/iam/concepts/#resource). To effectively delete your Project, you must therefore **empty its resources first**. +A Project can only be deleted once it has been emptied of its [resources](/iam/concepts/#resource). To effectively delete your Project, you must therefore **empty its resources first**. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Project](/identity-and-access-management/organizations-and-projects/how-to/create-a-project/) other than the [default Project](/identity-and-access-management/organizations-and-projects/concepts/#default-project) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Project](/organizations-and-projects/how-to/create-a-project/) other than the [default Project](/organizations-and-projects/concepts/#default-project) - Erased all the resources of the Project you want to delete 1. Click the **Projects** tab from the [Organization Dashboard](https://console.scaleway.com/organization). A list of your Projects displays. diff --git a/identity-and-access-management/organizations-and-projects/how-to/manage-quotas.mdx b/identity-and-access-management/organizations-and-projects/how-to/manage-quotas.mdx index 106a41510e..9d87bb88e3 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/manage-quotas.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/manage-quotas.mdx @@ -16,7 +16,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to view Organization quotas @@ -44,11 +44,11 @@ As shown in the image above, you can: Quotas are assigned by default according to each account level. There are two ways you can increase your account level: - - By [validating your payment method](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) - - By [verifying your identity](/console/account/how-to/verify-identity/) + - By [validating your payment method](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) + - By [verifying your identity](/account/how-to/verify-identity/) -For a detailed list of available quotas and the account levels necessary to increase quota capacity, as well as availability per location, refer to the [Understanding Organization Quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/) documentation page. +For a detailed list of available quotas and the account levels necessary to increase quota capacity, as well as availability per location, refer to the [Understanding Organization Quotas](/organizations-and-projects/additional-content/organization-quotas/) documentation page. - If you have already validated your payment method and identity and want to increase your quota beyond the values shown in the console or on the [Understanding Organization Quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/) documentation page, you must [contact our support team](https://console.scaleway.com/support/create). + If you have already validated your payment method and identity and want to increase your quota beyond the values shown in the console or on the [Understanding Organization Quotas](/organizations-and-projects/additional-content/organization-quotas/) documentation page, you must [contact our support team](https://console.scaleway.com/support/create). diff --git a/identity-and-access-management/organizations-and-projects/how-to/use-organizations.mdx b/identity-and-access-management/organizations-and-projects/how-to/use-organizations.mdx index e3c3dea82d..32fa0ffa32 100644 --- a/identity-and-access-management/organizations-and-projects/how-to/use-organizations.mdx +++ b/identity-and-access-management/organizations-and-projects/how-to/use-organizations.mdx @@ -13,24 +13,24 @@ categories: - console --- -When you [create a Scaleway account](/console/account/how-to/create-an-account/), an Organization, of which you are the [Owner](/identity-and-access-management/iam/concepts/#owner), is created for you. +When you [create a Scaleway account](/account/how-to/create-an-account/), an Organization, of which you are the [Owner](/iam/concepts/#owner), is created for you. -An Organization is made of one or several [Projects](/identity-and-access-management/organizations-and-projects/concepts/#project) that contain your resources. +An Organization is made of one or several [Projects](/organizations-and-projects/concepts/#project) that contain your resources. ## How to invite users to your Organization -You can invite other people to join your Organization: they will create their own Scaleway account (if they do not already have one) and then become [IAM users](/identity-and-access-management/iam/concepts/#user) of your Organization. +You can invite other people to join your Organization: they will create their own Scaleway account (if they do not already have one) and then become [IAM users](/iam/concepts/#user) of your Organization. -Refer to the [How to invite another user to an Organization](/identity-and-access-management/iam/how-to/invite-user-to-orga/) documentation page for more information. +Refer to the [How to invite another user to an Organization](/iam/how-to/invite-user-to-orga/) documentation page for more information. -You can also invite people to be IAM users of an Organization of which you are not the Owner, if you have sufficient permissions (via policies) to do so. See our documentation on [permission sets](/identity-and-access-management/iam/reference-content/permission-sets/) for more information. +You can also invite people to be IAM users of an Organization of which you are not the Owner, if you have sufficient permissions (via policies) to do so. See our documentation on [permission sets](/iam/reference-content/permission-sets/) for more information. -You can define the rights and permissions you want guests to have in your Organization via [policies](/identity-and-access-management/iam/concepts/#policy). +You can define the rights and permissions you want guests to have in your Organization via [policies](/iam/concepts/#policy). ## How to accept an invitation to an Organization -If you were invited to join an Organization, you can refer to the [How to accept an invitation to an Organization](/identity-and-access-management/iam/how-to/accept-invitation-to-orga/) documentation page for more information. \ No newline at end of file +If you were invited to join an Organization, you can refer to the [How to accept an invitation to an Organization](/iam/how-to/accept-invitation-to-orga/) documentation page for more information. \ No newline at end of file diff --git a/identity-and-access-management/organizations-and-projects/index.mdx b/identity-and-access-management/organizations-and-projects/index.mdx index dd187d9caf..7bc7566b38 100644 --- a/identity-and-access-management/organizations-and-projects/index.mdx +++ b/identity-and-access-management/organizations-and-projects/index.mdx @@ -8,7 +8,7 @@ meta: productName="Organizations and Projects" productLogo="accountExperience" description="Organizations and Projects help you organize and manage your resources." - url="/identity-and-access-management/organizations-and-projects/quickstart/" + url="/organizations-and-projects/quickstart/" label="Organizations and Projects Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to manage your Organizations and Projects in a few steps." label="View Quickstart" - url="/identity-and-access-management/organizations-and-projects/quickstart/" + url="/organizations-and-projects/quickstart/" /> diff --git a/identity-and-access-management/organizations-and-projects/quickstart.mdx b/identity-and-access-management/organizations-and-projects/quickstart.mdx index 8b0986686a..d1ce5cc99f 100644 --- a/identity-and-access-management/organizations-and-projects/quickstart.mdx +++ b/identity-and-access-management/organizations-and-projects/quickstart.mdx @@ -13,9 +13,9 @@ categories: - console --- -When you [create a Scaleway account](/console/account/how-to/create-an-account/), an Organization, of which you are the [Owner](/identity-and-access-management/iam/concepts/#owner), is created for you. +When you [create a Scaleway account](/account/how-to/create-an-account/), an Organization, of which you are the [Owner](/iam/concepts/#owner), is created for you. -An Organization is made of one or several [Projects](/identity-and-access-management/organizations-and-projects/concepts/#project) that contain your resources. This page helps you get started with using Projects and managing your resources. +An Organization is made of one or several [Projects](/organizations-and-projects/concepts/#project) that contain your resources. This page helps you get started with using Projects and managing your resources. ## How to generate an SSH key @@ -24,9 +24,9 @@ To establish connections with Instances, Elastic Metal servers, and Mac minis, y - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -[SSH keys](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key) allow you to securely connect to your Instances without using a password. +[SSH keys](/organizations-and-projects/concepts/#ssh-key) allow you to securely connect to your Instances without using a password. You can generate the SSH key pair on your local machine. The process will depend on your operating system. @@ -105,15 +105,15 @@ On Windows, you can use the third-party application [PuTTYgen](https://www.chiar You must upload the content of the public part of the SSH key pair you just created to the Scaleway interface. This is then associated with your Project and can be transferred to your Instances during the boot process. -1. From the [Scaleway console](https://console.scaleway.com), navigate to the [Credentials](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key) tab of your Project Dashboard. +1. From the [Scaleway console](https://console.scaleway.com), navigate to the [Credentials](/organizations-and-projects/concepts/#ssh-key) tab of your Project Dashboard. 2. Scroll down to the **SSH key** section, and click **Add a new SSH key**. 3. Paste the content of the public key (which you copied in the previous step) into the pop-up box, and optionally add a description. Then click **Add an SSH key**. - You will now be able to [connect to your Instances via SSH](/compute/instances/how-to/connect-to-instance/) + You will now be able to [connect to your Instances via SSH](/instances/how-to/connect-to-instance/) ## How to add resources to your Project -To add a new [resource](/identity-and-access-management/iam/concepts/#resource) to your Project, first ensure you are currently editing the correct Project. +To add a new [resource](/iam/concepts/#resource) to your Project, first ensure you are currently editing the correct Project. 1. Click **Project Dashboard** in the [Scaleway console](https://console.scaleway.com) side menu to check if you are logged in the correct Project. 2. You can also check if the name of your Project appears in the **Selected Project** drop-down menu. diff --git a/identity-and-access-management/secret-manager/api-cli/create-secret-path-migrate.mdx b/identity-and-access-management/secret-manager/api-cli/create-secret-path-migrate.mdx index b39e1d1264..255c83a4bb 100644 --- a/identity-and-access-management/secret-manager/api-cli/create-secret-path-migrate.mdx +++ b/identity-and-access-management/secret-manager/api-cli/create-secret-path-migrate.mdx @@ -18,9 +18,9 @@ This page shows you how to create a secret (`ultra-confidential`) and to migrate - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Configured the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#installation) -- [Created at least one Scaleway API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Created at least one Scaleway API key](/iam/how-to/create-api-keys/) - [Downloaded Go](https://go.dev/) 1. Open a terminal and run the following command to clone the repository containing the code you need to complete the procedure: diff --git a/identity-and-access-management/secret-manager/api-cli/create-secret-with-type.mdx b/identity-and-access-management/secret-manager/api-cli/create-secret-with-type.mdx index dff1f39676..a6240ddd62 100644 --- a/identity-and-access-management/secret-manager/api-cli/create-secret-with-type.mdx +++ b/identity-and-access-management/secret-manager/api-cli/create-secret-with-type.mdx @@ -18,8 +18,8 @@ This documentation shows you how to create a `database credentials` secret type, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) 1. Open a terminal and run the following command to create your `database credentials` secret type. Make sure that you replace `$SECRET_KEY` and `$SCW_PROJECT_ID` with your own values. @@ -64,5 +64,5 @@ This documentation shows you how to create a `database credentials` secret type, ``` - Find out about [other secret types and the expected JSON format](/identity-and-access-management/secret-manager/reference-content/secret-types-json-format/) for them. + Find out about [other secret types and the expected JSON format](/secret-manager/reference-content/secret-types-json-format/) for them. \ No newline at end of file diff --git a/identity-and-access-management/secret-manager/api-cli/external-secrets.mdx b/identity-and-access-management/secret-manager/api-cli/external-secrets.mdx index 4d07571800..2aa1120fd1 100644 --- a/identity-and-access-management/secret-manager/api-cli/external-secrets.mdx +++ b/identity-and-access-management/secret-manager/api-cli/external-secrets.mdx @@ -17,15 +17,15 @@ dates: [External Secrets](https://external-secrets.io) is a Kubernetes operator that allows you to manage the lifecycle of your secrets from external providers. -In this tutorial you will learn how to deploy External Secrets and its services on [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule), the managed Kubernetes service from Scaleway. +In this tutorial you will learn how to deploy External Secrets and its services on [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule), the managed Kubernetes service from Scaleway. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Configured [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Configured [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) - Installed `helm`, the Kubernetes [package manager](https://helm.sh/), on your local machine (version 3.2 or latest) ## Preparing the Kubernetes Kapsule cluster @@ -61,7 +61,7 @@ kubectl create secret generic scwsm-secret --from-file=./access-key --from-file= ## Create your first SecretStore Define a `SecretStore` resource in Kubernetes to inform External Secrets where to fetch secrets from. -Secret Manager is a regionalized product so you will need to specify the [region](/identity-and-access-management/secret-manager/concepts/#region) to create your secret in. +Secret Manager is a regionalized product so you will need to specify the [region](/secret-manager/concepts/#region) to create your secret in. 1. Copy the template below and paste it in a file named `secret-store.yaml`. diff --git a/identity-and-access-management/secret-manager/concepts.mdx b/identity-and-access-management/secret-manager/concepts.mdx index c22c911812..7b2fb3b61e 100644 --- a/identity-and-access-management/secret-manager/concepts.mdx +++ b/identity-and-access-management/secret-manager/concepts.mdx @@ -61,7 +61,7 @@ A PEM or **Privacy Enhanced Mail** file is a security certificate file used to e ## Region -A region is the geographical area in which your secrets, and versions are stored and run. They are duplicated on all [Availability Zones](/compute/instances/concepts/#availability-zone) of the selected region (Paris, Amsterdam, or Warsaw). +A region is the geographical area in which your secrets, and versions are stored and run. They are duplicated on all [Availability Zones](/instances/concepts/#availability-zone) of the selected region (Paris, Amsterdam, or Warsaw). Secret Manager allows you to select your resources by region. This allows you to better sort through your resources, if you have created them in different regions but with the same name, for example. @@ -83,7 +83,7 @@ Scaleway's Secret Manager can be managed using [APIs](https://www.scaleway.com/e ## Secret protection -Secret protection is a feature that prevents the deletion of your secrets. Users holding the `SecretManagerFullAccess`, `SecretManagerSecretWrite`, and `AllProductsFullAccess` [permission sets](/identity-and-access-management/iam/reference-content/permission-sets/) can enable it, ensuring that although your secrets can be accessed and modified, they remain **impossible to delete**. +Secret protection is a feature that prevents the deletion of your secrets. Users holding the `SecretManagerFullAccess`, `SecretManagerSecretWrite`, and `AllProductsFullAccess` [permission sets](/iam/reference-content/permission-sets/) can enable it, ensuring that although your secrets can be accessed and modified, they remain **impossible to delete**. This ensures the protection of critical information against accidental deletion while maintaining secret management flexibility. diff --git a/identity-and-access-management/secret-manager/how-to/create-secret.mdx b/identity-and-access-management/secret-manager/how-to/create-secret.mdx index ac4a5654ec..5407a391b4 100644 --- a/identity-and-access-management/secret-manager/how-to/create-secret.mdx +++ b/identity-and-access-management/secret-manager/how-to/create-secret.mdx @@ -13,12 +13,12 @@ categories: - identity-and-access-management --- -The [secret](/identity-and-access-management/secret-manager/concepts/#secret) creation process slightly differs depending on whether you are using Secret Manager for the first time or not. This page explains how to create a [secret](/identity-and-access-management/secret-manager/concepts/#secret) for the first time using the [Scaleway console](https://console.scaleway.com) and how to create a secret if you have already created resources in Secret Manager. +The [secret](/secret-manager/concepts/#secret) creation process slightly differs depending on whether you are using Secret Manager for the first time or not. This page explains how to create a [secret](/secret-manager/concepts/#secret) for the first time using the [Scaleway console](https://console.scaleway.com) and how to create a secret if you have already created resources in Secret Manager. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization @@ -26,7 +26,7 @@ The [secret](/identity-and-access-management/secret-manager/concepts/#secret) cr 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. 2. Click **+ Create secret**. - 3. Choose the [region](/identity-and-access-management/secret-manager/concepts/#region) in which you want to create your secret. + 3. Choose the [region](/secret-manager/concepts/#region) in which you want to create your secret. Secrets cannot be moved from one region to another after creation. @@ -35,11 +35,11 @@ The [secret](/identity-and-access-management/secret-manager/concepts/#secret) cr The maximum file size for your secret is 64 KiB. - - Choose a [secret type](/identity-and-access-management/secret-manager/concepts/#secret-types) and enter or upload your secret value. - 5. Create a [path](/identity-and-access-management/secret-manager/concepts/#path) in which to store your secret. The path name **must be prefixed** with a slash. + - Choose a [secret type](/secret-manager/concepts/#secret-types) and enter or upload your secret value. + 5. Create a [path](/secret-manager/concepts/#path) in which to store your secret. The path name **must be prefixed** with a slash. 6. Enter a name for your secret and add optional tags. - 7. Optionally, click to enable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). - 8. Optionally, click next to **Single access** or **Time to Live** to apply an [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. + 7. Optionally, click to enable [secret protection](/secret-manager/concepts/#secret-protection). + 8. Optionally, click next to **Single access** or **Time to Live** to apply an [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. - **Single access**: allows you to set your secret versions to **expire after one single access**. - **Time to Live**: allows you to set a time frame of up to one year, during which your secret versions are valid and accessible. @@ -49,14 +49,14 @@ The [secret](/identity-and-access-management/secret-manager/concepts/#secret) cr 9. Click **Create secret**. The **Overview** tab of your secret displays. - - The value of your secret is stored in its first version, which is enabled by default. At creation, your secret only has one version. Find out [how to add more versions](/identity-and-access-management/secret-manager/how-to/create-version/) to your secret. + - The value of your secret is stored in its first version, which is enabled by default. At creation, your secret only has one version. Find out [how to add more versions](/secret-manager/how-to/create-version/) to your secret. - Your path and secret are created on the go. 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. - 2. Select your desired [region](/identity-and-access-management/secret-manager/concepts/#region) in the **Region** drop-down. + 2. Select your desired [region](/secret-manager/concepts/#region) in the **Region** drop-down. Secrets cannot be moved from one region to another after creation. @@ -66,13 +66,13 @@ The [secret](/identity-and-access-management/secret-manager/concepts/#secret) cr The maximum file size for your secret is 64 KiB. - - Choose a [secret type](/identity-and-access-management/secret-manager/concepts/#secret-types) and enter or upload your secret value. - 5. Choose a [path](/identity-and-access-management/secret-manager/concepts/#path) for your secret: - - Enter an existing [path](/identity-and-access-management/secret-manager/concepts/#path). + - Choose a [secret type](/secret-manager/concepts/#secret-types) and enter or upload your secret value. + 5. Choose a [path](/secret-manager/concepts/#path) for your secret: + - Enter an existing [path](/secret-manager/concepts/#path). - Create a new path. The path name **must be prefixed** with a slash. 6. Enter a name for your secret and add optional tags. - 7. Optionally, click to enable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). - 8. Optionally, click next to **Single access** or **Time to Live** to apply an [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. + 7. Optionally, click to enable [secret protection](/secret-manager/concepts/#secret-protection). + 8. Optionally, click next to **Single access** or **Time to Live** to apply an [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. - **Single access**: allows you to set your secret versions to **expire after one single access**. - **Time to Live**: allows you to set a time frame of up to one year, during which your secret versions are valid and accessible. @@ -81,7 +81,7 @@ The [secret](/identity-and-access-management/secret-manager/concepts/#secret) cr 9. Click **Create secret**. The **Overview** tab of your secret displays. - - The value of your secret is stored in its first version, which is enabled by default. At creation, your secret only has one version. Find out [how to add more versions](/identity-and-access-management/secret-manager/how-to/create-version/) to your secret. + - The value of your secret is stored in its first version, which is enabled by default. At creation, your secret only has one version. Find out [how to add more versions](/secret-manager/how-to/create-version/) to your secret. - If you have created a path that did not exist yet, your path and secret are created on the go. diff --git a/identity-and-access-management/secret-manager/how-to/create-version.mdx b/identity-and-access-management/secret-manager/how-to/create-version.mdx index 4c56554c63..e8ddb3f0dc 100644 --- a/identity-and-access-management/secret-manager/how-to/create-version.mdx +++ b/identity-and-access-management/secret-manager/how-to/create-version.mdx @@ -13,19 +13,19 @@ categories: - identity-and-access-management --- -When creating a secret, its value is stored in its first version, which is [enabled](/identity-and-access-management/secret-manager/concepts/#enabling-a-version) by default. At creation, your secret only has one version. +When creating a secret, its value is stored in its first version, which is [enabled](/secret-manager/concepts/#enabling-a-version) by default. At creation, your secret only has one version. -This page explains how to add more [versions](/identity-and-access-management/secret-manager/concepts/#version) to a secret using the [Scaleway console](https://console.scaleway.com). +This page explains how to add more [versions](/secret-manager/concepts/#version) to a secret using the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/identity-and-access-management/iam/reference-content/permission-sets/) -- Created a [secret](/identity-and-access-management/secret-manager/how-to/create-secret/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Generated an API key](/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/iam/reference-content/permission-sets/) +- Created a [secret](/secret-manager/how-to/create-secret/) 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which the secret you want to update is, in the **Region** drop-down. +2. Select the [region](/secret-manager/concepts/#region) in which the secret you want to update is, in the **Region** drop-down. 3. Access the secret that you want to add a version to. Your secret's **Overview** tab displays. 4. Click the **Versions** tab. 5. Click **+ Create version**. A pop-up displays. @@ -41,7 +41,7 @@ This page explains how to add more [versions](/identity-and-access-management/se - By default, all your secret versions have the same type as the secret they belong to. You cannot change the type after you have created the secret. -8. Click the icon if you want to [enable](/identity-and-access-management/secret-manager/concepts/#enabling-a-version) the version. +8. Click the icon if you want to [enable](/secret-manager/concepts/#enabling-a-version) the version. 9. Click **Create version**. diff --git a/identity-and-access-management/secret-manager/how-to/delete-secret.mdx b/identity-and-access-management/secret-manager/how-to/delete-secret.mdx index 8bd9416ab0..62a2f8f499 100644 --- a/identity-and-access-management/secret-manager/how-to/delete-secret.mdx +++ b/identity-and-access-management/secret-manager/how-to/delete-secret.mdx @@ -13,24 +13,24 @@ categories: - identity-and-access-management --- -This page explains how to delete a [secret](/identity-and-access-management/secret-manager/concepts/#secret) using the [Scaleway console](https://console.scaleway.com). You **cannot delete protected secrets**, i.e. secrets to which you have applied [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). +This page explains how to delete a [secret](/secret-manager/concepts/#secret) using the [Scaleway console](https://console.scaleway.com). You **cannot delete protected secrets**, i.e. secrets to which you have applied [secret protection](/secret-manager/concepts/#secret-protection). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/identity-and-access-management/iam/reference-content/permission-sets/) -- Created a [secret](/identity-and-access-management/secret-manager/how-to/create-secret/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Generated an API key](/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/iam/reference-content/permission-sets/) +- Created a [secret](/secret-manager/how-to/create-secret/) 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which to delete the secret, in the **Region** drop-down. +2. Select the [region](/secret-manager/concepts/#region) in which to delete the secret, in the **Region** drop-down. 3. Access the secret you wish to delete. The secret's **Overview** tab displays. 4. Click **Delete secret**. A pop-up displays. 5. Type **DELETE** and click **Delete secret**. - - Although you cannot delete a [protected secret](/identity-and-access-management/secret-manager/concepts/#secret-protection), you can delete its versions + - Although you cannot delete a [protected secret](/secret-manager/concepts/#secret-protection), you can delete its versions - Deleting a secret is a permanent action. It erases every version you have created for your secret diff --git a/identity-and-access-management/secret-manager/how-to/delete-version.mdx b/identity-and-access-management/secret-manager/how-to/delete-version.mdx index 5cb8e0d2db..2d9d0d5d89 100644 --- a/identity-and-access-management/secret-manager/how-to/delete-version.mdx +++ b/identity-and-access-management/secret-manager/how-to/delete-version.mdx @@ -13,17 +13,17 @@ categories: - identity-and-access-management --- -This page explains how to delete a secret [version](/identity-and-access-management/secret-manager/concepts/#version) using the [Scaleway console](https://console.scaleway.com). +This page explains how to delete a secret [version](/secret-manager/concepts/#version) using the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/identity-and-access-management/iam/reference-content/permission-sets/) -- Created a [secret](/identity-and-access-management/secret-manager/how-to/create-secret/) and one or more [versions](/identity-and-access-management/secret-manager/how-to/create-version/) for it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Generated an API key](/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/iam/reference-content/permission-sets/) +- Created a [secret](/secret-manager/how-to/create-secret/) and one or more [versions](/secret-manager/how-to/create-version/) for it 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which to delete the version, in the **Region** drop-down. +2. Select the [region](/secret-manager/concepts/#region) in which to delete the version, in the **Region** drop-down. 3. Access the secret for which you want to delete the version. Your secret's **Overview** tab displays. 4. Click the **Versions** tab. 5. Click next to the version you want to delete. diff --git a/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx b/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx index 0110c85b17..5e2be6abc6 100644 --- a/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx +++ b/identity-and-access-management/secret-manager/how-to/filter-secrets.mdx @@ -13,25 +13,25 @@ categories: - identity-and-access-management --- -This page explains how to filter Secret Manager secrets by name, [type](/identity-and-access-management/secret-manager/concepts/#secret-types), and tags. +This page explains how to filter Secret Manager secrets by name, [type](/secret-manager/concepts/#secret-types), and tags. Filtering secrets by name allows you to quickly locate specific secrets, especially in environments with a large number of secrets. This helps in managing and retrieving the required information swiftly. -Filtering secrets by [type](/identity-and-access-management/secret-manager/concepts/#secret-types) allows you to categorize your secrets based on their usage (e.g., API keys, passwords, certificates). This helps in managing different types of secrets effectively. +Filtering secrets by [type](/secret-manager/concepts/#secret-types) allows you to categorize your secrets based on their usage (e.g., API keys, passwords, certificates). This helps in managing different types of secrets effectively. Filtering by tags allows you to categorize your secrets with more flexibility. Unlike rigid hierarchical structures, tags can be applied dynamically to group secrets based on various criteria. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created secrets](/identity-and-access-management/secret-manager/how-to/create-secret/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created secrets](/secret-manager/how-to/create-secret/) ## Filter secrets by name 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which the secrets you want to filter are located. +2. Select the [region](/secret-manager/concepts/#region) in which the secrets you want to filter are located. 3. In the **Filter by name** search bar, enter the name of the secret you are looking for. The search will only return secrets that were created in the path you are currently in. For example, if you have created the `/my-path` and `/my-second-path` paths, and your secret is inside `/my-second-path`, you need to access `/my-second-path` to find your secret. @@ -40,7 +40,7 @@ Filtering by tags allows you to categorize your secrets with more flexibility. U ## Filter secrets by tags 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which the secrets you want to filter are located. +2. Select the [region](/secret-manager/concepts/#region) in which the secrets you want to filter are located. 3. In the **Filter by tags** drop-down, select the tags you want to filter your secrets with. The search will only return secrets that were created in the path you are currently in. For example, if you have created the `/my-path` and `/my-second-path` paths, and your secret is inside `/my-second-path`, you need to access `/my-second-path` to find your secret. @@ -50,8 +50,8 @@ Filtering by tags allows you to categorize your secrets with more flexibility. U ## Filter secrets by type 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region) in which the secrets you want to filter are located. -3. In the **Filter by type** drop-down, select the [type](/identity-and-access-management/secret-manager/concepts/#secret-types) of secret you are looking for. +2. Select the [region](/secret-manager/concepts/#region) in which the secrets you want to filter are located. +3. In the **Filter by type** drop-down, select the [type](/secret-manager/concepts/#secret-types) of secret you are looking for. The search will only return secrets that were created in the path you are currently in. For example, if you have created the `/my-path` and `/my-second-path` paths, and your secret is inside `/my-second-path`, you need to access `/my-second-path` to find your secret. diff --git a/identity-and-access-management/secret-manager/how-to/manage-secret.mdx b/identity-and-access-management/secret-manager/how-to/manage-secret.mdx index 92c7686aeb..e162bb5563 100644 --- a/identity-and-access-management/secret-manager/how-to/manage-secret.mdx +++ b/identity-and-access-management/secret-manager/how-to/manage-secret.mdx @@ -13,35 +13,35 @@ categories: - identity-and-access-management --- -The process of managing a secret might differ depending on whether your secret is [ephemeral](/identity-and-access-management/secret-manager/concepts/#ephemeral-secret) or not. +The process of managing a secret might differ depending on whether your secret is [ephemeral](/secret-manager/concepts/#ephemeral-secret) or not. -Find out how to copy the ID of your [secret](/identity-and-access-management/secret-manager/concepts/#secret), how to update its description and tags, how to enable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection) on it, and how to update its [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) using the [Scaleway console](https://console.scaleway.com). +Find out how to copy the ID of your [secret](/secret-manager/concepts/#secret), how to update its description and tags, how to enable [secret protection](/secret-manager/concepts/#secret-protection) on it, and how to update its [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) using the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/identity-and-access-management/iam/reference-content/permission-sets/) -- [Created a secret](/identity-and-access-management/secret-manager/how-to/create-secret/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Generated an API key](/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/iam/reference-content/permission-sets/) +- [Created a secret](/secret-manager/how-to/create-secret/) 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. - 2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region), in the **Region** drop-down. + 2. Select the [region](/secret-manager/concepts/#region), in the **Region** drop-down. 3. Access the secret you wish to manage. The secret's **Overview** tab displays. 4. Click the copy icon next to **Secret's ID** to copy the ID of your secret. 5. Add a description under the **Description** section and save it. - 6. Click under the **Secret protection** section to enable or disable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). + 6. Click under the **Secret protection** section to enable or disable [secret protection](/secret-manager/concepts/#secret-protection). 7. Click the **Tags** bar and add tags to organize your secret. 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. - 2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region), in the **Region** drop-down. + 2. Select the [region](/secret-manager/concepts/#region), in the **Region** drop-down. 3. Access the secret you wish to manage. The secret's **Overview** tab displays. 4. Click the copy icon next to **Secret's ID** to copy the ID of your secret. 5. Add a description under the **Description** section and save it. - 6. Click under the **Secret protection** section to enable or disable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). - 7. Edit the [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) as you wish and click **Save**. + 6. Click under the **Secret protection** section to enable or disable [secret protection](/secret-manager/concepts/#secret-protection). + 7. Edit the [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) as you wish and click **Save**. Updating a secret's ephemeral policy impacts the secret's disabled versions when you enable them again: if you have created a version with the previous ephemeral policy's settings, disabled the version, and updated the ephemeral policy, the version will inherit its settings from those of the current policy when you enable it again. diff --git a/identity-and-access-management/secret-manager/how-to/manage-version.mdx b/identity-and-access-management/secret-manager/how-to/manage-version.mdx index 043f3e3c1f..9c3efd8b91 100644 --- a/identity-and-access-management/secret-manager/how-to/manage-version.mdx +++ b/identity-and-access-management/secret-manager/how-to/manage-version.mdx @@ -13,31 +13,31 @@ categories: - identity-and-access-management --- -This page explains how to manage a secret [version](/identity-and-access-management/secret-manager/concepts/#version) using the [Scaleway console](https://console.scaleway.com). +This page explains how to manage a secret [version](/secret-manager/concepts/#version) using the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/identity-and-access-management/iam/reference-content/permission-sets/) -- Created a [secret](/identity-and-access-management/secret-manager/how-to/create-secret/) and one or more [versions](/identity-and-access-management/secret-manager/how-to/create-version/) for it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Generated an API key](/iam/how-to/create-api-keys/) and enabled the `SecretManagerFullAccess` [permission set](/iam/reference-content/permission-sets/) +- Created a [secret](/secret-manager/how-to/create-secret/) and one or more [versions](/secret-manager/how-to/create-version/) for it 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. -2. Select the [region](/identity-and-access-management/secret-manager/concepts/#region), in the **Region** drop-down. +2. Select the [region](/secret-manager/concepts/#region), in the **Region** drop-down. 3. Access the relevant secret. Your secret's **Overview** tab displays. 4. Click the **Versions** tab. The versions of your secret display. 5. Click next to the version you want to manage. -6. Click **Disable** to [disable](/identity-and-access-management/secret-manager/concepts/#disabling-a-version) one specific version of your secret. -7. Click next to the version you have disabled, then click **Enable** to [enable](/identity-and-access-management/secret-manager/concepts/#enabling-a-version) it. +6. Click **Disable** to [disable](/secret-manager/concepts/#disabling-a-version) one specific version of your secret. +7. Click next to the version you have disabled, then click **Enable** to [enable](/secret-manager/concepts/#enabling-a-version) it. - Keep in mind that updating a secret's [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) impacts the secret's disabled versions when you enable them again. + Keep in mind that updating a secret's [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) impacts the secret's disabled versions when you enable them again. If you have created a version with the previous ephemeral policy's settings, disabled the version, and updated the ephemeral policy, the version will inherit its settings from those of the current policy when you enable it again. 8. Click **Copy version's value** to copy the value of your version. 9. Click to see the value of your version. - Make sure that the version does not have the **Single access** [ephemeral property](/identity-and-access-management/secret-manager/concepts/#ephemerality-properties). + Make sure that the version does not have the **Single access** [ephemeral property](/secret-manager/concepts/#ephemerality-properties). diff --git a/identity-and-access-management/secret-manager/index.mdx b/identity-and-access-management/secret-manager/index.mdx index 28a91cae09..e04bc7e10f 100644 --- a/identity-and-access-management/secret-manager/index.mdx +++ b/identity-and-access-management/secret-manager/index.mdx @@ -8,7 +8,7 @@ meta: productName="Secret Manager" productLogo="secretManager" description="Secret Manager allows you to conveniently store, access, and share sensitive data such as passwords, API keys, and certificates." - url="/identity-and-access-management/secret-manager/quickstart/" + url="/secret-manager/quickstart/" label="Secret Manager Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create secrets and versions, in a few steps." label="View Quickstart" - url="/identity-and-access-management/secret-manager/quickstart/" + url="/secret-manager/quickstart/" /> @@ -50,17 +50,17 @@ meta: diff --git a/identity-and-access-management/secret-manager/quickstart.mdx b/identity-and-access-management/secret-manager/quickstart.mdx index 6b7549c9c8..b428279248 100644 --- a/identity-and-access-management/secret-manager/quickstart.mdx +++ b/identity-and-access-management/secret-manager/quickstart.mdx @@ -10,18 +10,18 @@ dates: posted: 2023-02-21 --- -In this quickstart, we show you how to create a [secret](/identity-and-access-management/secret-manager/concepts/#secret) within a [path](/identity-and-access-management/secret-manager/concepts/#path), and how to add [versions](/identity-and-access-management/secret-manager/concepts/#version) to your newly-created secret. +In this quickstart, we show you how to create a [secret](/secret-manager/concepts/#secret) within a [path](/secret-manager/concepts/#path), and how to add [versions](/secret-manager/concepts/#version) to your newly-created secret. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a secret 1. Click **Secret Manager** in the **Security and Identity** section of the [Scaleway console](https://console.scaleway.com/) side menu. 2. Click **+ Create secret**. -3. Choose the [region](/identity-and-access-management/secret-manager/concepts/#region) in which you want to store your secret. +3. Choose the [region](/secret-manager/concepts/#region) in which you want to store your secret. Secrets cannot be moved from one region to another after creation. @@ -30,14 +30,14 @@ In this quickstart, we show you how to create a [secret](/identity-and-access-ma The maximum file size for your secret is 64 KiB. - - Choose a [secret type](/identity-and-access-management/secret-manager/concepts/#secret-types) and enter or upload your secret value. -5. Choose a [path](/identity-and-access-management/secret-manager/concepts/#path) for your secret. + - Choose a [secret type](/secret-manager/concepts/#secret-types) and enter or upload your secret value. +5. Choose a [path](/secret-manager/concepts/#path) for your secret. - A [path](/identity-and-access-management/secret-manager/concepts/#path) is the directory structure to access your secrets and their [versions](/identity-and-access-management/secret-manager/concepts/#version). Each path **must be prefixed** with a slash. + A [path](/secret-manager/concepts/#path) is the directory structure to access your secrets and their [versions](/secret-manager/concepts/#version). Each path **must be prefixed** with a slash. 6. Enter a name for your secret and add tags (optional). -7. Optionally, click to enable [secret protection](/identity-and-access-management/secret-manager/concepts/#secret-protection). -8. Optionally, click next to **Enable single access** or **Enable Time to Live** to apply an [ephemeral policy](/identity-and-access-management/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. +7. Optionally, click to enable [secret protection](/secret-manager/concepts/#secret-protection). +8. Optionally, click next to **Enable single access** or **Enable Time to Live** to apply an [ephemeral policy](/secret-manager/concepts/#ephemeral-policy) to your secret and its versions. - **Single access**: allows you to set your secret versions to **expire after one single access**. - **Time to Live**: allows you to set a time frame of up to one year, during which your secret versions are valid and accessible. @@ -47,7 +47,7 @@ In this quickstart, we show you how to create a [secret](/identity-and-access-ma 9. Click **Create secret**. The **Overview** tab of your secret displays. - - You have created a secret on the go. The value of your secret is stored in its first version, which is [enabled](/identity-and-access-management/secret-manager/concepts/#enabling-a-version) by default. At creation, your secret only has one version. Keep reading our quickstart to find out how to add more versions to your secret. + - You have created a secret on the go. The value of your secret is stored in its first version, which is [enabled](/secret-manager/concepts/#enabling-a-version) by default. At creation, your secret only has one version. Keep reading our quickstart to find out how to add more versions to your secret. ## How to add a secret version @@ -65,5 +65,5 @@ In this quickstart, we show you how to create a [secret](/identity-and-access-ma - Restoring a former version of a secret where you have applied the **Single access** ephemeral policy counts as an access, meaning it will then be disabled and/or deleted depending on the policies applied. - By default, all your secret versions have the same type as the secret they belong to. You cannot change the type after you have created the secret. -5. Click the icon if you want to [enable](/identity-and-access-management/secret-manager/concepts/#enabling-a-version) the version. +5. Click the icon if you want to [enable](/secret-manager/concepts/#enabling-a-version) the version. 6. Click **Create version**. Your secret versions display. \ No newline at end of file diff --git a/identity-and-access-management/secret-manager/reference-content/secret-manager-capabilities-limits.mdx b/identity-and-access-management/secret-manager/reference-content/secret-manager-capabilities-limits.mdx index 3418bb1102..ba96d830be 100644 --- a/identity-and-access-management/secret-manager/reference-content/secret-manager-capabilities-limits.mdx +++ b/identity-and-access-management/secret-manager/reference-content/secret-manager-capabilities-limits.mdx @@ -15,13 +15,13 @@ categories: This page provides information about the capabilities and limits of Scaleway Secret Manager, depending on user quotas. -Every [Organization](/identity-and-access-management/organizations-and-projects/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Below is a list of quotas available for Secret Manager. +Every [Organization](/organizations-and-projects/concepts/#organization) has quotas, which are limits on the number of Scaleway resources they can use. Below is a list of quotas available for Secret Manager. If you want to increase your quota beyond the values shown on this page, [contact our support team](https://console.scaleway.com/support/create). -| Name | [Payment method validated](/console/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/console/account/how-to/verify-identity/) | +| Name | [Payment method validated](/billing/how-to/add-payment-method/#how-to-add-a-credit-card) | Payment method and [identity validated](/account/how-to/verify-identity/) | |----------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------| | Secrets | 100 | 250 | | Versions per secret | 20 | 20 | diff --git a/identity-and-access-management/secret-manager/reference-content/secret-types-json-format.mdx b/identity-and-access-management/secret-manager/reference-content/secret-types-json-format.mdx index 1827e248a5..7b61a8545a 100644 --- a/identity-and-access-management/secret-manager/reference-content/secret-types-json-format.mdx +++ b/identity-and-access-management/secret-manager/reference-content/secret-types-json-format.mdx @@ -13,7 +13,7 @@ categories: - identity-and-access-management --- -[Secret types](/identity-and-access-management/secret-manager/concepts/#secret-types) are the different types of sensitive data you can create when using Secret Manager. +[Secret types](/secret-manager/concepts/#secret-types) are the different types of sensitive data you can create when using Secret Manager. This documentation page provides information about the different secret types available with the Secret Manager API, and how to use them with Terraform. diff --git a/index.mdx b/index.mdx index d8ff719fd2..e540d3bf76 100644 --- a/index.mdx +++ b/index.mdx @@ -18,28 +18,28 @@ meta: icon="console" description="Learn how to create an account and make the most of the Scaleway console." label="Start tour" - url="/console/account/quickstart/" + url="/account/quickstart/" /> diff --git a/macros/bare-metal/dedibox-scaleway-migration.mdx b/macros/bare-metal/dedibox-scaleway-migration.mdx index 805e506cf2..c2768f6cbc 100644 --- a/macros/bare-metal/dedibox-scaleway-migration.mdx +++ b/macros/bare-metal/dedibox-scaleway-migration.mdx @@ -2,5 +2,5 @@ macro: dedibox-scaleway-migration --- - Only users who **have completed** the linking of their the Dedibox account to the Scaleway console are granted access to the Dedibox section within the Scaleway console. For detailed information on the migration process, please refer to our [account linking documentation](/bare-metal/dedibox/how-to/link-dedibox-account/). **If you cannot locate the Dedibox link in Scaleway's console side menu, you can use the [Dedibox console](https://console.online.net)** to place orders, manage your Dediboxes, and access the [related documentation](/dedibox/dedicated-servers/quickstart/). + Only users who **have completed** the linking of their the Dedibox account to the Scaleway console are granted access to the Dedibox section within the Scaleway console. For detailed information on the migration process, please refer to our [account linking documentation](/dedibox-scaleway/how-to/link-dedibox-account/). **If you cannot locate the Dedibox link in Scaleway's console side menu, you can use the [Dedibox console](https://console.online.net)** to place orders, manage your Dediboxes, and access the [related documentation](/dedicated-servers/quickstart/). \ No newline at end of file diff --git a/macros/cockpit/plan-deprecation.mdx b/macros/cockpit/plan-deprecation.mdx index 8f1e38bbd7..45617ae8dd 100644 --- a/macros/cockpit/plan-deprecation.mdx +++ b/macros/cockpit/plan-deprecation.mdx @@ -6,7 +6,7 @@ macro: cockpit-plan-deprecation **Cockpit pricing plans were deprecated on January 1st 2025**

- The [retention](/observability/cockpit/concepts/#retention) period previously set for your Scaleway and custom logs, metrics and traces remains the same.

+ The [retention](/cockpit/concepts/#retention) period previously set for your Scaleway and custom logs, metrics and traces remains the same.

You can change the retention period for your metrics, logs, and traces for free during the retention period edition beta (starting January 1st 2025).

- Find out [how to change data retention period](/observability/cockpit/how-to/change-data-retention/) in the dedicated documentation. + Find out [how to change data retention period](/cockpit/how-to/change-data-retention/) in the dedicated documentation. diff --git a/macros/compute/container-registry.mdx b/macros/compute/container-registry.mdx index f4a5cc2cb1..dc076de136 100644 --- a/macros/compute/container-registry.mdx +++ b/macros/compute/container-registry.mdx @@ -2,4 +2,4 @@ macro: compute-container-registry --- -Scaleway Container Registry is a fully-managed mutualized Container Registry, designed to facilitate the storage, management and deployment of [container images](/containers/container-registry/concepts/#container-image). The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. \ No newline at end of file +Scaleway Container Registry is a fully-managed mutualized Container Registry, designed to facilitate the storage, management and deployment of [container images](/container-registry/concepts/#container-image). The service simplifies the development-to-production workflow, as there is no need to operate your own Container Registry or worry about the underlying infrastructure. \ No newline at end of file diff --git a/macros/compute/gpu-instances.mdx b/macros/compute/gpu-instances.mdx index 1b7bc804d4..29ddce08c4 100644 --- a/macros/compute/gpu-instances.mdx +++ b/macros/compute/gpu-instances.mdx @@ -2,4 +2,4 @@ macro: compute-gpu-instances --- -[GPU Instances](/compute/instances/concepts/#gpu-instance) (aka RENDER Instances) are powerful cloud Instances equipped with dedicated high-end Nvidia graphics processing units. They have been designed for artificial intelligence and rendering tasks. They support your most demanding workloads. \ No newline at end of file +[GPU Instances](/instances/concepts/#gpu-instance) (aka RENDER Instances) are powerful cloud Instances equipped with dedicated high-end Nvidia graphics processing units. They have been designed for artificial intelligence and rendering tasks. They support your most demanding workloads. \ No newline at end of file diff --git a/macros/compute/instances.mdx b/macros/compute/instances.mdx index ee8ee9d72b..18f165b8a6 100644 --- a/macros/compute/instances.mdx +++ b/macros/compute/instances.mdx @@ -2,4 +2,4 @@ macro: compute-instances --- -An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/compute/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [Development](/compute/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [GPU](/compute/instances/concepts/#gpu-instance), [Stardust](/compute/instances/reference-content/learning/#learning-range-stardust-instances) and [Enterprise](/compute/instances/reference-content/production-optimized/#production-optimized-range-ent1-instances). \ No newline at end of file +An Instance is a computing unit, either virtual or physical, that provides resources to run your applications on. Currently Scaleway offers the following Instance types: [General Purpose](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [Development](/instances/reference-content/cost-optimized/#development-instances-and-general-purpose-instances), [GPU](/instances/concepts/#gpu-instance), [Stardust](/instances/reference-content/learning/#learning-range-stardust-instances) and [Enterprise](/instances/reference-content/production-optimized/#production-optimized-range-ent1-instances). \ No newline at end of file diff --git a/macros/console/create-account.mdx b/macros/console/create-account.mdx index 644a1700cc..f3dcc31fd4 100644 --- a/macros/console/create-account.mdx +++ b/macros/console/create-account.mdx @@ -18,7 +18,7 @@ macro: create-account Fill out the required fields, then click **Add billing address**. This address will be used in your invoices. - You can click **Add later** to [enter your billing information at a later time](/console/billing/how-to/add-payment-method/), and directly access your Organization dashboard in the [Scaleway console](https://console.scaleway.com/organization). However, you will need to add a valid credit card to order Scaleway resources. + You can click **Add later** to [enter your billing information at a later time](/billing/how-to/add-payment-method/), and directly access your Organization dashboard in the [Scaleway console](https://console.scaleway.com/organization). However, you will need to add a valid credit card to order Scaleway resources. ## Add your credit card @@ -29,7 +29,7 @@ Fill out the required fields, then click **Add billing address**. This address w 1. Enter your credit card information, then click **Add credit card**. We will send you an authorization charge of €1, which will be automatically reimbursed within two days. A [3D Secure](https://en.wikipedia.org/wiki/3-D_Secure) validation is initiated. Depending on your bank, you may be asked to enter a code received by SMS or to confirm via an application on your smartphone. - You can click **Add later** to [enter your billing information at a later time](/console/billing/how-to/add-payment-method/), and directly access your Organization dashboard in the [Scaleway console](https://console.scaleway.com/organization). However, you will need to add a valid credit card to order Scaleway resources. + You can click **Add later** to [enter your billing information at a later time](/billing/how-to/add-payment-method/), and directly access your Organization dashboard in the [Scaleway console](https://console.scaleway.com/organization). However, you will need to add a valid credit card to order Scaleway resources. ## Validate your credit card diff --git a/macros/console/region-and-az.mdx b/macros/console/region-and-az.mdx index b35f849dc3..261b99d065 100644 --- a/macros/console/region-and-az.mdx +++ b/macros/console/region-and-az.mdx @@ -6,4 +6,4 @@ A region is a geographical area, such as France (Paris: `fr-par`) or the Netherl An Availability Zone refers to the geographical location within a region, such as `waw-1` (Warsaw, Poland), in which your Scaleway resource will be created. The latency between multiple AZs of the same region is low, as they have a common network layer. -For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/console/account/reference-content/products-availability/). \ No newline at end of file +For an extensive list of which regions and AZ a resource is available in, refer to our [Product availability guide](/account/reference-content/products-availability/). \ No newline at end of file diff --git a/macros/console/smtp.mdx b/macros/console/smtp.mdx index e5414dfd90..5e59b62349 100644 --- a/macros/console/smtp.mdx +++ b/macros/console/smtp.mdx @@ -2,4 +2,4 @@ macro: console-smtp --- -By default, remote email ports (25, 465, 587) are blocked, and cannot be reached from our infrastructure to avoid spam. You need to open the mail ports to send emails. You can [enable them](/compute/instances/how-to/send-emails-from-your-instance/) from the security group configuration. \ No newline at end of file +By default, remote email ports (25, 465, 587) are blocked, and cannot be reached from our infrastructure to avoid spam. You need to open the mail ports to send emails. You can [enable them](/instances/how-to/send-emails-from-your-instance/) from the security group configuration. \ No newline at end of file diff --git a/macros/console/ssh-keys.mdx b/macros/console/ssh-keys.mdx index e9f10f5040..943734b80e 100644 --- a/macros/console/ssh-keys.mdx +++ b/macros/console/ssh-keys.mdx @@ -2,4 +2,4 @@ macro: console-ssh-keys --- -An [SSH Key](/identity-and-access-management/organizations-and-projects/concepts/#ssh-key) (**S**ecure **Sh**ell Key) allows passwordless connection to an [Instance](/compute/instances/concepts/#instance). \ No newline at end of file +An [SSH Key](/organizations-and-projects/concepts/#ssh-key) (**S**ecure **Sh**ell Key) allows passwordless connection to an [Instance](/instances/concepts/#instance). \ No newline at end of file diff --git a/macros/developer-tools/scaleway-configuration-file.mdx b/macros/developer-tools/scaleway-configuration-file.mdx index 5aa115f80a..337c41fb9c 100644 --- a/macros/developer-tools/scaleway-configuration-file.mdx +++ b/macros/developer-tools/scaleway-configuration-file.mdx @@ -9,10 +9,10 @@ The Scaleway configuration file is a `config.yaml` file shared between the major The configuration file contains the following elements: **access_key** -: Your [Scaleway API access key](/identity-and-access-management/iam/how-to/create-api-keys/) +: Your [Scaleway API access key](/iam/how-to/create-api-keys/) **secret_key** -: Your [Scaleway API secret key](/identity-and-access-management/iam/how-to/create-api-keys/) +: Your [Scaleway API secret key](/iam/how-to/create-api-keys/) **default_organization_id** : The ID of the Scaleway Organization to use by default @@ -21,10 +21,10 @@ The configuration file contains the following elements: : The ID of the Scaleway Project to use by default **default_zone** -: The [availability zone](/console/account/reference-content/products-availability/) to use by default +: The [availability zone](/account/reference-content/products-availability/) to use by default **default_region** -: The [region](/console/account/reference-content/products-availability/) to use by default +: The [region](/account/reference-content/products-availability/) to use by default **api_url** : The API URL to use (`https://api.scaleway.com` by default) @@ -40,7 +40,7 @@ The configuration file contains the following elements: ## How to set up the configuration file -You can set up the Scaleway configuration file using several methods. However, we recommend that you use [The Scaleway CLI](/developer-tools/scaleway-cli/quickstart/). The `scw init` command allows you to initialize your configuration in just a few minutes. +You can set up the Scaleway configuration file using several methods. However, we recommend that you use [The Scaleway CLI](/scaleway-cli/quickstart/). The `scw init` command allows you to initialize your configuration in just a few minutes. To initialize the configuration without the Scaleway CLI, you can simply create a `config.yaml` file in the appropriate folder: @@ -100,7 +100,7 @@ You can select the profile to use by either: ## Troubleshooting -- Make sure that you have generated and specified a valid `access_key` and `secret_key` pair. Refer to the [API keys](/identity-and-access-management/iam/how-to/create-api-keys/) documentation for more information. +- Make sure that you have generated and specified a valid `access_key` and `secret_key` pair. Refer to the [API keys](/iam/how-to/create-api-keys/) documentation for more information. - Make sure that there is no conflicting environment variable set, such as `$SCW_ACCESS_KEY` and `$SCW_SECRET_KEY`. You can remove environment variables using the `unset` command as shown below: diff --git a/macros/developer-tools/scaleway-environment-variables.mdx b/macros/developer-tools/scaleway-environment-variables.mdx index 13718f55cc..21145c94ff 100644 --- a/macros/developer-tools/scaleway-environment-variables.mdx +++ b/macros/developer-tools/scaleway-environment-variables.mdx @@ -8,12 +8,12 @@ The following standardized Scaleway environment variables are used for the CLI a | Variable | Description | Legacy variables | | :----------------------------- | :----------------------------------------------------------------------------------------------- | :------------------------------------------------------------------------------------------------------------ | -| `$SCW_ACCESS_KEY` | The [access key](/identity-and-access-management/iam/how-to/create-api-keys/) of a token | `$SCALEWAY_ACCESS_KEY` (used by Terraform) | -| `$SCW_SECRET_KEY` | The [secret key](/identity-and-access-management/iam/how-to/create-api-keys/) of a token | `$SCW_TOKEN` (used by the CLI), `$SCALEWAY_TOKEN` (used by Terraform), `$SCALEWAY_ACCESS_KEY` (used by Terraform) | | +| `$SCW_ACCESS_KEY` | The [access key](/iam/how-to/create-api-keys/) of a token | `$SCALEWAY_ACCESS_KEY` (used by Terraform) | +| `$SCW_SECRET_KEY` | The [secret key](/iam/how-to/create-api-keys/) of a token | `$SCW_TOKEN` (used by the CLI), `$SCALEWAY_TOKEN` (used by Terraform), `$SCALEWAY_ACCESS_KEY` (used by Terraform) | | | `$SCW_DEFAULT_REGION` | Your default [region](https://www.scaleway.com/en/developers/api/#regions-and-zones) | `$SCW_REGION` (used by the CLI),`$SCALEWAY_REGION` (used by Terraform) | | `$SCW_DEFAULT_ZONE` | Your default [Availability Zone](https://www.scaleway.com/en/developers/api/#regions-and-zones) | `$SCW_ZONE` (used by the CLI),`$SCALEWAY_ZONE` (used by Terraform) | | `$SCW_API_URL` | URL of the API | - | -| `$SCW_INSECURE` | Set this variable to `true` to enable the [insecure mode](/managed-services/iot-hub/concepts/#insecure-connection) | `$SCW_TLSVERIFY` (inverse flag used by the CLI) | +| `$SCW_INSECURE` | Set this variable to `true` to enable the [insecure mode](/iot-hub/concepts/#insecure-connection) | `$SCW_TLSVERIFY` (inverse flag used by the CLI) | | `$SCW_PROFILE` | Set the configuration profile to use | - | | `$SCW_PROJECT_ID` | Your [Project ID](https://console.scaleway.com/project/settings) | `$SCW_DEFAULT_PROJECT_ID` | | `$SCW_ORGANIZATION_ID` | Your [Organization ID](https://console.scaleway.com/organization/settings) | `$SCW_DEFAULT_ORGANIZATION_ID`, `$SCW_ORGANIZATION` (used by the CLI),`$SCALEWAY_ORGANIZATION` (used by Terraform) | @@ -28,4 +28,4 @@ The order of precedence, from highest to lowest is the following. 2. Static variables (i.e. variables set in a Terraform configuration file). -3. Variables defined in the [Scaleway configuration file](/developer-tools/scaleway-sdk/reference-content/scaleway-configuration-file/) \ No newline at end of file +3. Variables defined in the [Scaleway configuration file](/scaleway-sdk/reference-content/scaleway-configuration-file/) \ No newline at end of file diff --git a/macros/edge-services/edge-services-bucket-benefits.mdx b/macros/edge-services/edge-services-bucket-benefits.mdx index 929b4d22a7..da80a33491 100644 --- a/macros/edge-services/edge-services-bucket-benefits.mdx +++ b/macros/edge-services/edge-services-bucket-benefits.mdx @@ -3,7 +3,7 @@ macro: edge-services-bucket-benefits --- - Customize your bucket's endpoint using a subdomain of your own domain -- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS +- Add your own SSL/TLS certificate, safeguarded in [Scaleway Secret Manager](/secret-manager/quickstart/), or generate a managed Let's Encrypt certificate, so your subdomain can serve content from your bucket over HTTPS - Enhance performance by caching your stored objects, to be served directly by Edge Services from the cache - Finely control your cached objects via purging (cache invalidation) diff --git a/macros/edge-services/edge-services-lb-benefits.mdx b/macros/edge-services/edge-services-lb-benefits.mdx index 3b61e4baac..d1e86eaefe 100644 --- a/macros/edge-services/edge-services-lb-benefits.mdx +++ b/macros/edge-services/edge-services-lb-benefits.mdx @@ -13,4 +13,4 @@ Edge Services lets you: - Customize your Edge Services pipeline endpoint using a subdomain of your own domain - Add an SSL/TLS certificate so that Edge Services can serve content over HTTPS for your subdomain -An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services. \ No newline at end of file +An Edge Services pipeline can be created for any Load Balancer with a public IP address. Load Balancers with frontends/backends using both TCP and/or HTTP are supported. [Private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers) are not compatible with Edge Services. \ No newline at end of file diff --git a/macros/network/dns-cloud.mdx b/macros/network/dns-cloud.mdx index a0f53c01d7..77b01861db 100644 --- a/macros/network/dns-cloud.mdx +++ b/macros/network/dns-cloud.mdx @@ -3,4 +3,4 @@ macro: network-dns-cloud --- -The **D**omain **N**ame **S**ystem (DNS) is a name management system for computing devices connected to a network, be it public (Internet) or private. It translates text-based [domain names](/network/domains-and-dns/concepts/#domain-name) to numerical [IP addresses](/network/public-gateways/concepts/#ip-address). Scaleway provides a [managed DNS](/network/domains-and-dns/concepts/#scaleway-domains-and-dns) service. \ No newline at end of file +The **D**omain **N**ame **S**ystem (DNS) is a name management system for computing devices connected to a network, be it public (Internet) or private. It translates text-based [domain names](/domains-and-dns/concepts/#domain-name) to numerical [IP addresses](/public-gateways/concepts/#ip-address). Scaleway provides a [managed DNS](/domains-and-dns/concepts/#scaleway-domains-and-dns) service. \ No newline at end of file diff --git a/macros/network/lb-create-backend-1-basic.mdx b/macros/network/lb-create-backend-1-basic.mdx index 850edcdc53..ba99c81126 100644 --- a/macros/network/lb-create-backend-1-basic.mdx +++ b/macros/network/lb-create-backend-1-basic.mdx @@ -17,5 +17,5 @@ macro: lb-create-backend-1-basic 4. Choose whether to activate **proxy protocol** (default setting is deactivated), to transfer connection information from the client through the Load Balancer and on to the destination backend server. If you choose to activate proxy protocol, you are prompted to select the **version** to use. - For more help understanding and choosing basic configuration settings for your backend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-backends/#configuring-basic-settings). + For more help understanding and choosing basic configuration settings for your backend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-backends/#configuring-basic-settings). \ No newline at end of file diff --git a/macros/network/lb-create-backend-2-traffic-mgnt.mdx b/macros/network/lb-create-backend-2-traffic-mgnt.mdx index 79ed5c6803..489b31b38a 100644 --- a/macros/network/lb-create-backend-2-traffic-mgnt.mdx +++ b/macros/network/lb-create-backend-2-traffic-mgnt.mdx @@ -14,11 +14,11 @@ Traffic management configuration lets you define how your Load Balancer's backen 2. Add the **Server IP addresses** of the servers the Load Balancer will forward requests/connections to. These will be your backend servers. - If you want your Load Balancer to communicate with its backend servers over an attached [Private Network](/network/vpc/concepts/#private-networks), ensure that you enter the servers' private IP addresses on that network. This is necessary in the case of a [private Load Balancer](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers), but may also be desired for public Load Balancers attached to Private Networks where backend servers are on the same Private Network. + If you want your Load Balancer to communicate with its backend servers over an attached [Private Network](/vpc/concepts/#private-networks), ensure that you enter the servers' private IP addresses on that network. This is necessary in the case of a [private Load Balancer](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers), but may also be desired for public Load Balancers attached to Private Networks where backend servers are on the same Private Network. 3. Choose whether to activate **sticky sessions** (default setting is deactivated). Sticky sessions enable the Load Balancer to bind a given user's sessions to a specific backend server. If you choose to activate sticky sessions, you are prompted to select either **IP-based** (clients' IPs are used to bind sessions) or **cookie-based** (an HTTP cookie is used to bind sessions, and you must choose a name for the cookie). - For more help choosing traffic management settings for your backend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-backends/#configuring-traffic-management). + For more help choosing traffic management settings for your backend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-backends/#configuring-traffic-management). \ No newline at end of file diff --git a/macros/network/lb-create-backend-3-advanced-settings.mdx b/macros/network/lb-create-backend-3-advanced-settings.mdx index 32e9b62545..aeee15d2f1 100644 --- a/macros/network/lb-create-backend-3-advanced-settings.mdx +++ b/macros/network/lb-create-backend-3-advanced-settings.mdx @@ -5,5 +5,5 @@ macro: lb-create-backend-3-advanced-settings Advanced settings are already configured for you at recommended default values. However, if you wish to modify these values you can do so by clicking the **Advanced settings** button, to access parameters for timeout values, backend protection, connection retries and a customized error page. - For more help choosing advanced settings for your backend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-backends/#configuring-advanced-settings). + For more help choosing advanced settings for your backend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-backends/#configuring-advanced-settings). \ No newline at end of file diff --git a/macros/network/lb-create-backend-4-healthcheck.mdx b/macros/network/lb-create-backend-4-healthcheck.mdx index cbf6639b3d..367d1c44f1 100644 --- a/macros/network/lb-create-backend-4-healthcheck.mdx +++ b/macros/network/lb-create-backend-4-healthcheck.mdx @@ -13,5 +13,5 @@ Health checks are regular, automized attempts by the Load Balancer to communicat 3. Choose whether to edit more settings for health checks by clicking the **Advanced settings** button. Otherwise, these settings will be left at the recommended default values. - For more help setting up health checks for your backend, including advanced settings such as defining intervals between health checks, timeout values and the unhealthy threshold, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-health-checks/). + For more help setting up health checks for your backend, including advanced settings such as defining intervals between health checks, timeout values and the unhealthy threshold, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-health-checks/). \ No newline at end of file diff --git a/macros/serverless/container-registry-note.mdx b/macros/serverless/container-registry-note.mdx index e407cb12c2..5918ae50c0 100644 --- a/macros/serverless/container-registry-note.mdx +++ b/macros/serverless/container-registry-note.mdx @@ -2,5 +2,5 @@ macro: container-registry-note --- -[Scaleway's Container Registry](/containers/container-registry/) allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). +[Scaleway's Container Registry](/container-registry/) allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). Serverless products support external public registries (such as [Docker Hub](https://hub.docker.com/search?q=)), but we do not recommend using them due to uncontrolled rate limiting, which can lead to failures when starting resources, unexpected usage conditions, and pricing changes. diff --git a/macros/serverless/cron-schedules.mdx b/macros/serverless/cron-schedules.mdx index 13a37ebb69..f4e32e4cd9 100644 --- a/macros/serverless/cron-schedules.mdx +++ b/macros/serverless/cron-schedules.mdx @@ -66,6 +66,6 @@ Several operators can be added to each field to further refine your schedule. ## Time zones -- Serverless Functions and Serverless Containers [CRON triggers](/serverless/functions/concepts#cron-trigger) use the **UTC** time zone. This parameter cannot be modified. +- Serverless Functions and Serverless Containers [CRON triggers](/serverless-functions/concepts#cron-trigger) use the **UTC** time zone. This parameter cannot be modified. -- Serverless Jobs allow modifying the time zone of their schedules via the Job **Settings** tab. Refer to [the job scheduling documentation](/serverless/jobs/how-to/manage-job-schedule/) for more information. \ No newline at end of file +- Serverless Jobs allow modifying the time zone of their schedules via the Job **Settings** tab. Refer to [the job scheduling documentation](/serverless-jobs/how-to/manage-job-schedule/) for more information. \ No newline at end of file diff --git a/macros/serverless/difference-jobs-functions-containers.mdx b/macros/serverless/difference-jobs-functions-containers.mdx index 8901c9d4c6..a88ba7ba10 100644 --- a/macros/serverless/difference-jobs-functions-containers.mdx +++ b/macros/serverless/difference-jobs-functions-containers.mdx @@ -36,7 +36,7 @@ macro: difference-jobs-functions-containers Serverless Jobs are designed for batch computing workloads, particularly large-scale and asynchronous tasks, like data processing, image rendering, or complex computations. -Choose Scaleway [Serverless Jobs](/serverless/jobs/quickstart/): +Choose Scaleway [Serverless Jobs](/serverless-jobs/quickstart/): - For long-running tasks and resource-intensive applications. - To handle numerous jobs concurrently. @@ -49,7 +49,7 @@ Choose Scaleway [Serverless Jobs](/serverless/jobs/quickstart/): ### Serverless Functions -Choose Scaleway [Serverless Functions](/serverless/functions/quickstart/): +Choose Scaleway [Serverless Functions](/serverless-functions/quickstart/): - For HTTP and event-driven tasks. - For optimum performance in lightweight scenarios. @@ -58,12 +58,12 @@ Choose Scaleway [Serverless Functions](/serverless/functions/quickstart/): - For stateless workloads. - Serverless Functions can only be written in languages [available as runtimes](/serverless/functions/reference-content/functions-lifecycle/#available-runtimes). + Serverless Functions can only be written in languages [available as runtimes](/serverless-functions/reference-content/functions-lifecycle/#available-runtimes). ### Serverless Containers -Choose Scaleway [Serverless Containers](/serverless/containers/quickstart/): +Choose Scaleway [Serverless Containers](/serverless-containers/quickstart/): - For HTTP and event-driven tasks. - If your programming language is not supported as a Serverless Function runtime. diff --git a/macros/storage/block-storage-migration.mdx b/macros/storage/block-storage-migration.mdx index 638ecfbbd7..2fbb423497 100644 --- a/macros/storage/block-storage-migration.mdx +++ b/macros/storage/block-storage-migration.mdx @@ -5,6 +5,6 @@ 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/). - - Find out about the [advantages of migrating the management of your volumes and snapshots](/storage/block/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](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/) from the Instance API to the Block Storage API. + - 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/macros/storage/block-storage-no-migration-for-k8s.mdx b/macros/storage/block-storage-no-migration-for-k8s.mdx index b74919231d..1fb655b649 100644 --- a/macros/storage/block-storage-no-migration-for-k8s.mdx +++ b/macros/storage/block-storage-no-migration-for-k8s.mdx @@ -4,5 +4,5 @@ macro: block-storage-no-migration-for-k8s

- **Kubernetes customers must not migrate their block volumes to the Block Storage API to prevent major disruptions to their Kubernetes service and block volume unavailability.** You can identify your volumes by [listing them](/storage/block/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`. + **Kubernetes customers must not migrate their block volumes to the Block Storage API to prevent major disruptions to their Kubernetes service and block volume unavailability.** You can identify your volumes by [listing them](/block-storage/api-cli/identifying-volume-snapshot-api/#listing-volumes-created-with-the-block-storage-api) and referring to the `name` field, next to which you should see an output similar to `k8s_base_node_2024-07-26`. \ No newline at end of file diff --git a/macros/storage/bucket-policy.mdx b/macros/storage/bucket-policy.mdx index 0a7dfd39f1..3a9c0ffa11 100644 --- a/macros/storage/bucket-policy.mdx +++ b/macros/storage/bucket-policy.mdx @@ -4,4 +4,4 @@ macro: storage-bucket-policy A **bucket policy** is a resource-based policy option. It allows you to grant more granular access to Object Storage resources. -By default, all Object Storage resources in a Project are private and can be accessed only by users or applications with [IAM permissions](/identity-and-access-management/iam/concepts/#permission). Adding a bucket policy to a bucket allows you to specify who can perform which actions on a bucket and the objects it contains. You can combine the different [elements of a bucket policy](/storage/object/api-cli/bucket-policy/#bucket-policies-description) to tailor your permissions according to your use case. \ No newline at end of file +By default, all Object Storage resources in a Project are private and can be accessed only by users or applications with [IAM permissions](/iam/concepts/#permission). Adding a bucket policy to a bucket allows you to specify who can perform which actions on a bucket and the objects it contains. You can combine the different [elements of a bucket policy](/object-storage/api-cli/bucket-policy/#bucket-policies-description) to tailor your permissions according to your use case. \ No newline at end of file diff --git a/macros/storage/important-bucket-policy.mdx b/macros/storage/important-bucket-policy.mdx index 402c4ca1e7..18c9052bfd 100644 --- a/macros/storage/important-bucket-policy.mdx +++ b/macros/storage/important-bucket-policy.mdx @@ -3,8 +3,8 @@ macro: important-bucket-policy --- - - You will lose access to your bucket if you are not the [owner](/identity-and-access-management/iam/concepts/#owner) of the Organization, and if you are not explicitly allowed by the bucket policy. - - The [owner](/identity-and-access-management/iam/concepts/#owner) of the Organization always has the right to put and delete bucket policies, even if he is not allowed to perform other bucket operations by the bucket policy. + - You will lose access to your bucket if you are not the [owner](/iam/concepts/#owner) of the Organization, and if you are not explicitly allowed by the bucket policy. + - The [owner](/iam/concepts/#owner) of the Organization always has the right to put and delete bucket policies, even if he is not allowed to perform other bucket operations by the bucket policy. - Each bucket can have only one bucket policy. - Pushing a new bucket policy to a bucket overwrites any existing bucket policy. \ No newline at end of file diff --git a/macros/vpc/pn-naming.mdx b/macros/vpc/pn-naming.mdx index 30834ea739..0cc368bead 100644 --- a/macros/vpc/pn-naming.mdx +++ b/macros/vpc/pn-naming.mdx @@ -3,5 +3,5 @@ macro: pn-naming --- -The resource name can only include alphanumeric characters and dashes. Avoid using a **T**op **L**evel **D**omain as your Private Network name, as this can cause addressing conflicts. For example, do not call your Private Network `dev`, `cloud` or `com`. For a complete reference of TLDs to avoid, see the full list provided by [IANA](https://data.iana.org/TLD/tlds-alpha-by-domain.txt). Read more about this issue in our [dedicated documentation](/network/vpc/troubleshooting/pn-name/). +The resource name can only include alphanumeric characters and dashes. Avoid using a **T**op **L**evel **D**omain as your Private Network name, as this can cause addressing conflicts. For example, do not call your Private Network `dev`, `cloud` or `com`. For a complete reference of TLDs to avoid, see the full list provided by [IANA](https://data.iana.org/TLD/tlds-alpha-by-domain.txt). Read more about this issue in our [dedicated documentation](/vpc/troubleshooting/pn-name/). \ No newline at end of file diff --git a/macros/webhosting/webhosting-online.mdx b/macros/webhosting/webhosting-online.mdx index 0c4e4b6321..1455aca8ca 100644 --- a/macros/webhosting/webhosting-online.mdx +++ b/macros/webhosting/webhosting-online.mdx @@ -5,5 +5,5 @@ macro: webhosting-online
This documentation describes the usage of a previous web hosting offer proposed by Online.net.
- Refer to the [Scaleway Web Hosting documentation](/managed-services/webhosting/quickstart/) for information about the current web hosting product. + Refer to the [Scaleway Web Hosting documentation](/webhosting/quickstart/) for information about the current web hosting product. \ No newline at end of file diff --git a/managed-databases/mongodb/api-cli/backup-and-restore.mdx b/managed-databases/mongodb/api-cli/backup-and-restore.mdx index e9680d2fce..d1860623e2 100644 --- a/managed-databases/mongodb/api-cli/backup-and-restore.mdx +++ b/managed-databases/mongodb/api-cli/backup-and-restore.mdx @@ -24,7 +24,7 @@ This tutorial shows how to backup and restore your MongoDB® Databases with the - A Scaleway account logged into the [console](https://console.scaleway.com) - - A [MongoDB® Database Instance](/managed-databases/mongodb/how-to/create-a-database-instance/) + - A [MongoDB® Database Instance](/managed-mongodb-databases/how-to/create-a-database-instance/) - Installed a [MongoDB®-compatible client](https://www.mongodb.com/try/download/shell) - Installed [mongodump and mongorestore tools](https://www.mongodb.com/docs/database-tools/installation/installation/) diff --git a/managed-databases/mongodb/concepts.mdx b/managed-databases/mongodb/concepts.mdx index b9ecdadca4..5698779523 100644 --- a/managed-databases/mongodb/concepts.mdx +++ b/managed-databases/mongodb/concepts.mdx @@ -22,7 +22,7 @@ Block Storage Legacy is a volume type that is decoupled from your compute resour Block Storage Low Latency is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. -Refer to the [Block Storage Low Latency documentation section](/storage/block/concepts/) to learn more about this volume type. +Refer to the [Block Storage Low Latency documentation section](/block-storage/concepts/) to learn more about this volume type. Block Low Latency volumes are only available with new-generation node types and in the PAR and AMS regions. @@ -34,7 +34,7 @@ A Database Instance is made up of multiple (at least 1) dedicated compute nodes, ## Database snapshot -A [Snapshot](/managed-databases/mongodb/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Snapshots can only be stored in the same location as the original data. +A [Snapshot](/managed-mongodb-databases/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Snapshots can only be stored in the same location as the original data. ## Document database diff --git a/managed-databases/mongodb/how-to/connect-database-instance.mdx b/managed-databases/mongodb/how-to/connect-database-instance.mdx index c5e9d1f568..beef5ade7e 100644 --- a/managed-databases/mongodb/how-to/connect-database-instance.mdx +++ b/managed-databases/mongodb/how-to/connect-database-instance.mdx @@ -21,8 +21,8 @@ Managed MongoDB® is currently in private beta. Click [here](https://www.scalewa - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [MongoDB® Database Instance](/managed-databases/mongodb/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB® Database Instance](/managed-mongodb-databases/quickstart/) - Installed either [mongosh](https://www.mongodb.com/docs/mongodb-shell/), or the [pymongo](https://pymongo.readthedocs.io/en/stable/) distribution for Python, or the Node.js [mongodb module](https://www.npmjs.com/package/mongodb) or the [mongo driver for Go](https://github.com/mongodb/mongo-go-driver), or [Mongoose](https://mongoosejs.com/) on your local machine diff --git a/managed-databases/mongodb/how-to/create-a-database-instance.mdx b/managed-databases/mongodb/how-to/create-a-database-instance.mdx index 84ab409534..17c9d8eb6d 100644 --- a/managed-databases/mongodb/how-to/create-a-database-instance.mdx +++ b/managed-databases/mongodb/how-to/create-a-database-instance.mdx @@ -24,7 +24,7 @@ Document databases enable users to store and retrieve data in a document format, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a database diff --git a/managed-databases/mongodb/how-to/delete-a-database-instance.mdx b/managed-databases/mongodb/how-to/delete-a-database-instance.mdx index 4fb091d5a1..94cd7801ed 100644 --- a/managed-databases/mongodb/how-to/delete-a-database-instance.mdx +++ b/managed-databases/mongodb/how-to/delete-a-database-instance.mdx @@ -20,8 +20,8 @@ Managed MongoDB® is currently in private beta. Click [here](https://www.scalewa - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [MongoDB® Database Instance](/managed-databases/mongodb/quickstart) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB® Database Instance](/managed-mongodb-databases/quickstart) 1. Click **MongoDB®** under **Managed Databases** on the side menu. A list of your Database Instances displays. diff --git a/managed-databases/mongodb/how-to/increase-volume.mdx b/managed-databases/mongodb/how-to/increase-volume.mdx index 894819ee32..4be903338e 100644 --- a/managed-databases/mongodb/how-to/increase-volume.mdx +++ b/managed-databases/mongodb/how-to/increase-volume.mdx @@ -22,8 +22,8 @@ You can increase the Block Storage volume of your MongoDB® Database Instance in - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [MongoDB® Database Instance](/managed-databases/mongodb/quickstart) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB® Database Instance](/managed-mongodb-databases/quickstart) ## How to increase a Block Storage volume diff --git a/managed-databases/mongodb/how-to/manage-snapshots.mdx b/managed-databases/mongodb/how-to/manage-snapshots.mdx index 08d30f07e5..6d90dacae4 100644 --- a/managed-databases/mongodb/how-to/manage-snapshots.mdx +++ b/managed-databases/mongodb/how-to/manage-snapshots.mdx @@ -17,15 +17,15 @@ categories: Managed MongoDB® is currently in private beta. Click [here](https://www.scaleway.com/en/managed-mongodb/) to join the waiting list. -[Snapshots](/managed-databases/mongodb/how-to/manage-snapshots/) allow you to restore data in a new Database Instance. +[Snapshots](/managed-mongodb-databases/how-to/manage-snapshots/) allow you to restore data in a new Database Instance. You can have up to 100 snapshots per Instance and project (depending on quotas). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [MongoDB® Database Instance](/managed-databases/mongodb/quickstart) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB® Database Instance](/managed-mongodb-databases/quickstart) ## How to create snapshots diff --git a/managed-databases/mongodb/how-to/manage-users.mdx b/managed-databases/mongodb/how-to/manage-users.mdx index 6c024f6c99..ee0acbe1cb 100644 --- a/managed-databases/mongodb/how-to/manage-users.mdx +++ b/managed-databases/mongodb/how-to/manage-users.mdx @@ -26,8 +26,8 @@ Users can connect to a database and access its data. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [MongoDB® Database Instance](/managed-databases/mongodb/quickstart) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [MongoDB® Database Instance](/managed-mongodb-databases/quickstart) ## How to change the password of your user diff --git a/managed-databases/mongodb/index.mdx b/managed-databases/mongodb/index.mdx index 38edb67ce0..398b6140c6 100644 --- a/managed-databases/mongodb/index.mdx +++ b/managed-databases/mongodb/index.mdx @@ -11,7 +11,7 @@ content: productName="Managed MongoDB® Databases" productLogo="mongoDB" description="Managed MongoDB® Databases provide fully-managed databases with a MongoDB® compatible API, relying on MongoDB® and PostgreSQL as storage engines. Enjoy automatic backups, scaling, monitoring and much more." - url="/managed-databases/mongodb/quickstart/" + url="/managed-mongodb-databases/quickstart/" label="Managed MongoDB® Databases Quickstart" /> @@ -27,28 +27,28 @@ Managed MongoDB® is currently in private beta. Click [here](https://www.scalewa icon="rocket" description="Learn how to create a Managed MongoDB® Database in a few steps." label="View Quickstart" - url="/managed-databases/mongodb/quickstart/" + url="/managed-mongodb-databases/quickstart/" /> {/* */} @@ -58,7 +58,7 @@ Managed MongoDB® is currently in private beta. Click [here](https://www.scalewa diff --git a/managed-databases/mongodb/quickstart.mdx b/managed-databases/mongodb/quickstart.mdx index d3a70e84e6..26cc62f372 100644 --- a/managed-databases/mongodb/quickstart.mdx +++ b/managed-databases/mongodb/quickstart.mdx @@ -24,7 +24,7 @@ MongoDB® databases enable users to store and retrieve data in a document format - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [MongoDB®-compatible client](https://www.mongodb.com/try/download/shell) installed ## How to create a Database Instance diff --git a/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx b/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx index 029a4bb044..b537ecd159 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases.mdx @@ -22,9 +22,9 @@ Refer to [this tutorial](/tutorials/migrate-databases-instance/) to migrate larg - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a target Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) to import your data into. +- [Created a target Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) to import your data into. - Checked that the target database you are importing data into is empty, or contains data you can overwrite. @@ -74,9 +74,9 @@ To complete this procedure, you must have installed PostgreSQL in a version comp You can find this information on the [overview page](https://console.scaleway.com/rdb/instances) of your database. -4. Enter the database password you defined upon [Database Instance creation](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) when prompted. +4. Enter the database password you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) when prompted. -5. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. +5. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. ### Using pgAdmin @@ -106,7 +106,7 @@ To complete the following procedure, you must have: #### Loading your data in your Managed Database for PostgreSQL -1. Register your new database in pgAdmin. Refer to the [How to connect to a Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) documentation page for more information. +1. Register your new database in pgAdmin. Refer to the [How to connect to a Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) documentation page for more information. 2. Connect to your database server by selecting it in the left-hand menu. @@ -126,7 +126,7 @@ To complete the following procedure, you must have: 8. Click **Restore**. The restore process starts, and you can follow its progress by clicking **View processes**. -9. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. +9. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. If the process fails and some data was already partly transferred, we suggest that you activate the **Clean before restore** option in the **Data options** tab to remove partly transferred data. @@ -193,7 +193,7 @@ To avoid any statement timeout errors with Managed Database for PostgreSQL (e.g. 7. When finished, make sure your data is stored in your new database by connecting to it, and performing a query. -This procedure does not currently work with Managed Databases for PostgreSQL. However, you can import your backup using [Managed Database for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/). +This procedure does not currently work with Managed Databases for PostgreSQL. However, you can import your backup using [Managed Database for PostgreSQL and MySQL](/managed-databases-for-postgresql-and-mysql/). ### Using Fivetran @@ -283,7 +283,7 @@ To complete the following procedure, you must have: 11. When finished, make sure your data is stored in your new database by connecting to it, and performing a query. -This procedure does not currently work with Managed Databases for PostgreSQL. However, you can import your backup using [Managed Database for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/). +This procedure does not currently work with Managed Databases for PostgreSQL. However, you can import your backup using [Managed Database for PostgreSQL and MySQL](/managed-databases-for-postgresql-and-mysql/). ### Using Meltano @@ -410,7 +410,7 @@ To complete the following procedure, you must have: You can find this information on the [overview page](https://console.scaleway.com/rdb/instances) of your database. These are the username and password that you defined upon Database Instance creation. -2. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. +2. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. ## Import Data from a file (.csv, .txt, etc.) @@ -464,4 +464,4 @@ You can create a `.csv` file from an existing PostgreSQL table with the [COPY TO The PostgreSQL [COPY command](https://www.postgresql.org/docs/current/sql-copy.html) cannot be used directly, as it requires the source file to be available on the PostgreSQL instance itself. -5. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. \ No newline at end of file +5. When finished, make sure your data is stored in your new database by [connecting to it](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/), and performing a query. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/api-cli/migrating-endpoints.mdx b/managed-databases/postgresql-and-mysql/api-cli/migrating-endpoints.mdx index 40357c7d85..4909f20118 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/migrating-endpoints.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/migrating-endpoints.mdx @@ -16,14 +16,14 @@ categories: You can migrate your endpoints from a Database Instance to another anytime, using the Scaleway CLI. -The following commands are useful when you [upgrade the version of your database engine](/managed-databases/postgresql-and-mysql/how-to/upgrade-version/) via the **Upgrade only** option. In this case, you must manually migrate your endpoint. +The following commands are useful when you [upgrade the version of your database engine](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version/) via the **Upgrade only** option. In this case, you must manually migrate your endpoint. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) -- Installed and set up the [Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) +- Installed and set up the [Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) - A [`jq` library](https://jqlang.github.io/jq/) installed on your local machine 1. Retrieve a list of your Database Instances. @@ -45,7 +45,7 @@ The following commands are useful when you [upgrade the version of your database - If you want to migrate a `load_balancer` endpoint type the target Database Instance must not have a `load_balancer` endpoint - If you want to migrate a `private_network` endpoint type the target Database Instance must not have a `private_network` endpoint - You can remove existing endpoints in the target Database Instance via the [Scaleway console](/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint/) or [the CLI](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/rdb.md#delete-a-database-instance-endpoint). + You can remove existing endpoints in the target Database Instance via the [Scaleway console](/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint/) or [the CLI](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/rdb.md#delete-a-database-instance-endpoint). diff --git a/managed-databases/postgresql-and-mysql/api-cli/pg-audit.mdx b/managed-databases/postgresql-and-mysql/api-cli/pg-audit.mdx index 912fed71e3..68b9b43f3c 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/pg-audit.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/pg-audit.mdx @@ -25,8 +25,8 @@ You can configure the extension to log only what is relevant to your audits. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) running a PostgreSQL engine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) running a PostgreSQL engine ## Enabling and installing pgaudit @@ -41,7 +41,7 @@ You can configure the extension to log only what is relevant to your audits. Restarting can take several seconds depending on the size of your Database Instance. -8. [Connect to your Database Instance](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/). +8. [Connect to your Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/). 9. Run the following command to install the `pgaudit` extension. ``` CREATE EXTENSION pgaudit @@ -59,7 +59,7 @@ You can configure the extension to log only what is relevant to your audits. To use each one, you must configure the `pgaudit.log` and `pgaudit.role` settings, respectively. -Both settings can be set up at the Database Instance level, meaning that a global configuration can be applied to all databases within the Instance. You can configure them in the [advanced settings](/managed-databases/postgresql-and-mysql/concepts/#advanced-settings) of your Database Instance. You can use both settings concurrently. +Both settings can be set up at the Database Instance level, meaning that a global configuration can be applied to all databases within the Instance. You can configure them in the [advanced settings](/managed-databases-for-postgresql-and-mysql/concepts/#advanced-settings) of your Database Instance. You can use both settings concurrently. `pgaudit.log` can also be configured for specific databases within your Instance. @@ -107,7 +107,7 @@ The possible values include: - 1. [Connect to your database](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. + 1. [Connect to your database](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. 2. Run the following command to set `pgaudit.log` for the database. Replace `` with the name of your database, and `` with one or more of the statement class values listed above. When listing more than one class, separate them with a comma and no spaces. For example: `WRITE,FUNCTION`. ``` database=> ALTER DATABASE SET pgaudit.log = '' @@ -157,7 +157,7 @@ Currently, only the `SELECT`, `INSERT`, `UPDATE`, and `DELETE` permissions are s To set up and grant permissions to the principal audit role follow these instructions: -1. [Connect to your database](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. +1. [Connect to your database](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. 2. Run the following command to create a new user. If no output is returned, the operation was successful. If you want to specify an existing role as the principal audit, you can skip this step. @@ -207,12 +207,12 @@ Your logs are accessible via the Scaleway Observability dashboard, [Cockpit](htt With Cockpit's free plan, your logs remain available for a week. If you want to extend the volume capacity and the duration of storage, you can upgrade to a paid plan. Refer to the [Cockpit FAQ](/faq/cockpit/#how-am-i-billed-for-using-cockpit-with-my-scaleway-data) for more information about plans and billing. -1. [Follow the Cockpit Quickstart](/observability/cockpit/quickstart/) to activate the feature and retrieve your Grafana credentials. -2. [Configure the Grafana agent](/observability/cockpit/api-cli/configuring-grafana-agent/). +1. [Follow the Cockpit Quickstart](/cockpit/quickstart/) to activate the feature and retrieve your Grafana credentials. +2. [Configure the Grafana agent](/cockpit/api-cli/configuring-grafana-agent/). 3. Connect to Grafana with the credentials you created. 4. Click **RDB PostgreSQL Overview** on the left-side menu. 5. Scroll to the **Logs** section and click to expand. -6. [View the logs](/observability/cockpit/api-cli/configuring-grafana-agent/#visualizing-logs-in-grafana). +6. [View the logs](/cockpit/api-cli/configuring-grafana-agent/#visualizing-logs-in-grafana). ### Technical Information - All management actions performed via API or the console, such as database creations and deletions, are logged, no matter the configuration. However, the associated read statements are not logged. For example, select statements used to check that actions have been correctly executed are not logged. @@ -223,7 +223,7 @@ Your logs are accessible via the Scaleway Observability dashboard, [Cockpit](htt ### Optimizing disk usage -- Audit logs are flushed and consume disk space. The [log ingestion rate](/observability/cockpit/reference-content/cockpit-limitations/#limits-for-loki) is **4 MB per second**. +- Audit logs are flushed and consume disk space. The [log ingestion rate](/cockpit/reference-content/cockpit-limitations/#limits-for-loki) is **4 MB per second**. To avoid log generation from exceeding ingestion, and the subsequent uncontrolled growth of disk usage, make sure you closely monitor the disk usage of the Database Instance. @@ -241,7 +241,7 @@ Your logs are accessible via the Scaleway Observability dashboard, [Cockpit](htt ## Deactivating pgaudit -1. [Connect to your database](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. +1. [Connect to your database](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) as an admin user. 2. Run the following command to deactivate the `pgaudit` extension in your Database Instance. ``` DROP EXTENSION pgaudit @@ -270,7 +270,7 @@ To set up session audit logging only of Data Manipulation Language (DML) stateme To set up session audit logging of all statements in only one database, you must: 1. Set `pgaudit.log` to `NONE` in the advanced settings tab of your Database Instance dashboard in the Scaleway console. -2. [Connect to your database](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) as an admin user and run the following command: +2. [Connect to your database](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) as an admin user and run the following command: ``` ALTER DATABASE mydb SET pgaudit.log = 'ALL'; ``` @@ -287,7 +287,7 @@ To set up: There is no default principal role. You must [create a new role, or specify an existing one](#setting-up-pgauditrole) as the principal audit. -2. [Connect to your database](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) as an admin user and run the following command: +2. [Connect to your database](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) as an admin user and run the following command: ``` GRANT SELECT, INSERT, UPDATE, DELETE on mydb.mytable diff --git a/managed-databases/postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx b/managed-databases/postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx index 5d80ffa227..8588a5f1a9 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/setting-up-encryption-at-rest.mdx @@ -21,7 +21,7 @@ The feature can be activated upon Database Instance creation via the console and - 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. - - Enabling encryption means your database data will be copied into a new, encrypted block volume. This takes approximately 1 hour per 100 GB of storage. When switching volumes, expect a few seconds of downtime towards the end of the copying process. Refer to the [Encryption at rest performance benchmark on Database Instances](/managed-databases/postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark) page. + - Enabling encryption means your database data will be copied into a new, encrypted block volume. This takes approximately 1 hour per 100 GB of storage. When switching volumes, expect a few seconds of downtime towards the end of the copying process. Refer to the [Encryption at rest performance benchmark on Database Instances](/managed-databases-for-postgresql-and-mysql/reference-content/encryption-at-rest-performance-benchmark) page. ## Creating a Database Instance with encryption at rest diff --git a/managed-databases/postgresql-and-mysql/api-cli/verify-ca-postgresql.mdx b/managed-databases/postgresql-and-mysql/api-cli/verify-ca-postgresql.mdx index 523d516847..86a2e44569 100644 --- a/managed-databases/postgresql-and-mysql/api-cli/verify-ca-postgresql.mdx +++ b/managed-databases/postgresql-and-mysql/api-cli/verify-ca-postgresql.mdx @@ -143,7 +143,7 @@ pool This option will verify that a server is trustworthy by checking the certificate chain up to the root certificate stored on the client. It will also verify whether the hostname specified in the server certificate matches the server's hostname. - `verify-full` is supported only for certificates created or renewed after 1st February 2023. The `verify-full` option does not work for certificates created before this date. If you want to use this option, you can [renew the certificate](/managed-databases/postgresql-and-mysql/how-to/renew-tls-certificate/). + `verify-full` is supported only for certificates created or renewed after 1st February 2023. The `verify-full` option does not work for certificates created before this date. If you want to use this option, you can [renew the certificate](/managed-databases-for-postgresql-and-mysql/how-to/renew-tls-certificate/). diff --git a/managed-databases/postgresql-and-mysql/concepts.mdx b/managed-databases/postgresql-and-mysql/concepts.mdx index b36b043a3c..6b2816b78a 100644 --- a/managed-databases/postgresql-and-mysql/concepts.mdx +++ b/managed-databases/postgresql-and-mysql/concepts.mdx @@ -15,7 +15,7 @@ categories: ## Allowed IPs -Access Control List (ACL) rules [define permissions for remote access to an Instance](/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses/). A rule consists of an IP address or an IP range. You can use them to define which host and networks can connect to your Database Instance's endpoint. You can add, edit, or delete rules from your ACLs. The initial setup of a Database Instance allows full network access from anywhere (`0.0.0.0/0`). +Access Control List (ACL) rules [define permissions for remote access to an Instance](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses/). A rule consists of an IP address or an IP range. You can use them to define which host and networks can connect to your Database Instance's endpoint. You can add, edit, or delete rules from your ACLs. The initial setup of a Database Instance allows full network access from anywhere (`0.0.0.0/0`). Access control is handled directly at network-level by Load Balancers, making the filtering more efficient, universal and relieving the Database Instance from this task. @@ -31,7 +31,7 @@ Block Storage Legacy is a volume type that is decoupled from your compute resour Block Storage Low Latency is a storage type similar to [Block Storage Legacy](#block-storage-legacy) that provides lower latency and high resiliency through 5k IOPS. You can increase your volume size to up to 10 TB. -Refer to the [Block Storage Low Latency documentation section](/storage/block/concepts/) to learn more about this volume type. +Refer to the [Block Storage Low Latency documentation section](/block-storage/concepts/) to learn more about this volume type. Block Low Latency volumes are only available with new-generation node types and in the PAR and AMS regions. @@ -51,7 +51,7 @@ A Database Instance is a managed database service created upon a custom base ima ## Database snapshot -A [snapshot](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Their limitation is that, unlike backups, snapshots can only be stored in the same location as the original data. +A [snapshot](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) is a consistent, instantaneous copy of the Block Storage volume of your Database Instance at a certain point in time. They are designed to recover your data in case of failure or accidental alterations of the data by a user. They allow you to quickly create a new Instance from a previous state of your database, regardless of the size of the volume. Their limitation is that, unlike backups, snapshots can only be stored in the same location as the original data. ## Encryption at rest @@ -89,7 +89,7 @@ The HA standby node is linked to the main node, using synchronous replication. S - HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/). + HA standby nodes are not accessible to users unless the main node becomes unavailable and the standby takes over. If you wish to run queries on a read-only node, you can use [Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/). ## Local Storage @@ -128,4 +128,4 @@ This is the type of storage used on your Database Instances. Three types are ava Block Low Latency volumes are only available with new-generation node types and only in the PAR and AMS regions. -You can select the volume type upon Database Instance creation, and you can [change the type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) anytime. \ No newline at end of file +You can select the volume type upon Database Instance creation, and you can [change the type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) anytime. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/add-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/add-a-database.mdx index 78de99cdb2..b34d3a8d72 100644 --- a/managed-databases/postgresql-and-mysql/how-to/add-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/add-a-database.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the Database Instance name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/postgresql-and-mysql/how-to/add-users.mdx b/managed-databases/postgresql-and-mysql/how-to/add-users.mdx index 1b0f8c2a0c..3ca702bca4 100644 --- a/managed-databases/postgresql-and-mysql/how-to/add-users.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/add-users.mdx @@ -19,8 +19,8 @@ Users can connect to a database and access its data. Each one has a different se - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/postgresql-and-mysql/how-to/apply-maintenance.mdx b/managed-databases/postgresql-and-mysql/how-to/apply-maintenance.mdx index 4d9392262b..a65801e1ed 100644 --- a/managed-databases/postgresql-and-mysql/how-to/apply-maintenance.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/apply-maintenance.mdx @@ -21,8 +21,8 @@ These maintenance operations are set up, run, and scheduled by Scaleway, but you - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) scheduled for maintenance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) scheduled for maintenance 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Look for an orange info icon to identify which Database Instances are scheduled for maintenance. diff --git a/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx b/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx index 6f06d6fd42..d86f99e3e3 100644 --- a/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/change-volume-type.mdx @@ -14,13 +14,13 @@ categories: - postgresql-and-mysql --- -It is possible to change your [volume type](/managed-databases/postgresql-and-mysql/concepts/#volume-type) anytime in the Scaleway console. +It is possible to change your [volume type](/managed-databases-for-postgresql-and-mysql/concepts/#volume-type) anytime in the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) with Local Storage +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) with Local Storage 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the Database Instance you want to edit. The database's Overview page displays. @@ -37,7 +37,7 @@ It is possible to change your [volume type](/managed-databases/postgresql-and-my The Database Instance goes into the `Initializing` state. - - When switching from a local volume to a block volume, and if [Autobackup](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage. + - When switching from a local volume to a block volume, and if [Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) is enabled, be aware that the snapshot type will change. Local volumes use logical backups, whereas Block Storage employs snapshots. Both types are priced at €0.03 per GB per month, but their distinct backup methods affect storage space differently, influencing the final monthly cost based on your usage. - Disk size cannot be reduced, so when switching from Local to Block, the volume size remains the same by default. - When switching from a block to a local volume, make sure to select a node with a Local Storage with size equal or greater than your current Block Storage. If you choose a Database Instance type with a local volume larger than your current block volume, you will be billed for the full capacity of the Database Instance. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx b/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx index 75c35d759a..b1a4aca194 100644 --- a/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/clone-a-database-instance.mdx @@ -23,8 +23,8 @@ The clone feature allows you to create a new Database Instance from an existing - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to clone a Database Instance @@ -35,9 +35,9 @@ The clone feature allows you to create a new Database Instance from an existing 5. Enter a name for your database or leave the default name suggested by the Scaleway console. 6. Select a node type. You can keep the same node type, or upgrade to a bigger one. - If you have a new-generation Database Instance using a local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

+ If you have a new-generation Database Instance using a local volume node type and want to upgrade to an Instance that uses Block volumes node type, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy). + Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) and want to create a clone on a first-generation Instance, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). 7. Click **Clone Database Instance**. diff --git a/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings.mdx b/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings.mdx index a93cbe8822..c57334ebb7 100644 --- a/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings.mdx @@ -19,8 +19,8 @@ Advanced settings allow you to modify the default configuration of your database - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) Changing the advanced settings can have an impact on the performance of your Database Instance. diff --git a/managed-databases/postgresql-and-mysql/how-to/connect-database-instance.mdx b/managed-databases/postgresql-and-mysql/how-to/connect-database-instance.mdx index b009c08122..19201d329f 100644 --- a/managed-databases/postgresql-and-mysql/how-to/connect-database-instance.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/connect-database-instance.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. @@ -37,7 +37,7 @@ categories: ```bash psql -h -p -U -d rdb ``` -5. Enter the password that you defined upon [Database Instance creation](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). +5. Enter the password that you defined upon [Database Instance creation](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). You are now connected to your Managed Database. diff --git a/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network.mdx b/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network.mdx index 63d9e8b094..323c17fc4e 100644 --- a/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network.mdx @@ -14,7 +14,7 @@ categories: - postgresql-and-mysql --- -[Private Networks](/network/vpc/concepts/#private-networks) allows you to enhance the security of your system's architecture by isolating it from the internet. +[Private Networks](/vpc/concepts/#private-networks) allows you to enhance the security of your system's architecture by isolating it from the internet. When using Private Networks, your application connects directly to your Database nodes without going through a Load Balancer. @@ -25,9 +25,9 @@ You can create new Database Instances to attach to your Private Network, or atta - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to attach a Database Instance to a Private Network @@ -58,9 +58,9 @@ You can create new Database Instances to attach to your Private Network, or atta 6. Click **Attach to Private Network** to conclude. -Managed Databases for PostgreSQL and MySQL are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). +Managed Databases for PostgreSQL and MySQL are currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). -You can use Public Gateways in [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. +You can use Public Gateways in [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. diff --git a/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx index 92efbde203..01d587f31d 100644 --- a/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/create-a-database.mdx @@ -23,7 +23,7 @@ Compared to traditional database management, which requires customers to provide - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. 2. Click **Create Database Instance**. The creation wizard displays. @@ -36,7 +36,7 @@ Compared to traditional database management, which requires customers to provide You can upgrade a standalone node to High Availability after Database Instance creation, but not the opposite. - - Enable [encryption at rest](/managed-databases/postgresql-and-mysql/concepts/#encryption-at-rest) if you want to ensure the permanent encryption of your database data. + - Enable [encryption at rest](/managed-databases-for-postgresql-and-mysql/concepts/#encryption-at-rest) if you want to ensure the permanent encryption of your database data. Once activated on a Database Instance, encryption at rest cannot be disabled.

@@ -50,13 +50,13 @@ Compared to traditional database management, which requires customers to provide - Choose your storage type and capacity. Two types of storage are available: - **Block Storage Legacy** - With this type, your storage is decoupled from your compute resources. You can increase your storage space without changing your node type. You can define your storage capacity by entering the desired amount in the box. The volume can be increased up to 10 TB. - - **Block Storage Low Latency**: This storage type works like the [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. + - **Block Storage Low Latency**: This storage type works like the [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy), while providing lower latency and high resiliency through 5k IOPS. You can increase your volume to up to 10 TB. - **Local SSD Storage** - Your storage is fixed and tied to your compute resource. The Local Storage option is only available with the first generation node types. - - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/), or select [Manual snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/). + - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/), or select [Manual snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/). - Add a name and set a password for your user. Your username and password must adhere to specific criteria. diff --git a/managed-databases/postgresql-and-mysql/how-to/create-read-replica.mdx b/managed-databases/postgresql-and-mysql/how-to/create-read-replica.mdx index e5c9d2b74a..ac76145473 100644 --- a/managed-databases/postgresql-and-mysql/how-to/create-read-replica.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/create-read-replica.mdx @@ -21,8 +21,8 @@ Read Replicas allow you to scale your Database Instance for read-heavy database - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. @@ -34,7 +34,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database - **Multi-AZ**: Your Read Replica is hosted in a different AZ, ensuring the resilience of your Replica. We recommend this option for ensuring the availability of your infrastructure, and improving your disaster recovery plan. - [Block Storage Low Latency volumes](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) are currently not available with Multi-AZ Read Replicas. + [Block Storage Low Latency volumes](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) are currently not available with Multi-AZ Read Replicas. 6. Select the network type. Two types are available: @@ -47,7 +47,7 @@ Read Replicas allow you to scale your Database Instance for read-heavy database - If you select **Public network**, you can [attach a Private Network](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-manage-private-networks) to your Read Replica after its creation. If you chose 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. + If you select **Public network**, you can [attach a Private Network](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-manage-private-networks) to your Read Replica after its creation. If you chose 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. 7. Click **Create Read Replica**. A list of your Read Replicas displays. diff --git a/managed-databases/postgresql-and-mysql/how-to/delete-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/delete-a-database.mdx index 361c5524cd..823c737218 100644 --- a/managed-databases/postgresql-and-mysql/how-to/delete-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/delete-a-database.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/postgresql-and-mysql/how-to/delete-db.mdx b/managed-databases/postgresql-and-mysql/how-to/delete-db.mdx index 094a7f0fbb..e7dfb5d995 100644 --- a/managed-databases/postgresql-and-mysql/how-to/delete-db.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/delete-db.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) -- A [database](/managed-databases/postgresql-and-mysql/how-to/add-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) +- A [database](/managed-databases-for-postgresql-and-mysql/how-to/add-a-database/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the Database Instance name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx b/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx index daf657c941..cb19a6bf6d 100644 --- a/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/enable-autobackup.mdx @@ -16,9 +16,9 @@ categories: With the autobackup feature, the creation and management of your Database Instance backups is automated according to your backup schedule configuration. -Two types of autobackups are available at Scaleway: [backups](/managed-databases/postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases/postgresql-and-mysql/concepts/#database-snapshot). +Two types of autobackups are available at Scaleway: [backups](/managed-databases-for-postgresql-and-mysql/concepts/#database-backup) and [snapshots](/managed-databases-for-postgresql-and-mysql/concepts/#database-snapshot). -Backups are used when your Database Instance's storage option is a local volume. Snapshots are available for Database Instances that use [Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy) and [Low Latency](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) Block Storage volumes. +Backups are used when your Database Instance's storage option is a local volume. Snapshots are available for Database Instances that use [Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy) and [Low Latency](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) Block Storage volumes. Although they bear the same feature name, automated snapshots and automated backups are different in their design. If you have a Database Instance using Block Storage, it is only possible to use automated snapshots as autobackup. @@ -27,8 +27,8 @@ Backups are used when your Database Instance's storage option is a local volume. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) The autobackup feature is enabled by default upon the creation of an Instance. Simultaneously, a schedule policy is created. The default autobackup frequency is of 1 per day with a retention period of 7 days. You can change this in the Database Instance information page after Instance creation. @@ -47,6 +47,6 @@ Backups are used when your Database Instance's storage option is a local volume. 4. Configure the backup frequency and retention, then click to confirm. -You can follow our documentation to [restore](/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and [export](/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups/#how-to-export-backups) your backups. +You can follow our documentation to [restore](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and [export](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-export-backups) your backups. -For snapshots, you can follow the [how to restore snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. \ No newline at end of file +For snapshots, you can follow the [how to restore snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) procedure to create a Database Instance from a snapshot. \ No newline at end of file diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx index 1ebea81089..58c83de37e 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses.mdx @@ -19,8 +19,8 @@ Allowed IPs define remote access restrictions for your Database Instance. The de - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) Allowed IP configuration is only available for public networks. diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx index 3a48dd17cd..04992fc947 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups.mdx @@ -21,8 +21,8 @@ You can create manual backups for Database Instances with Block Storage if the D - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to create manual backups diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-permissions.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-permissions.mdx index cb8ab812ec..1ae49911f3 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-permissions.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-permissions.mdx @@ -19,8 +19,8 @@ Permissions define the actions a user can perform on a logical database. A datab - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## Set permissions for an existing user @@ -41,7 +41,7 @@ Permissions define the actions a user can perform on a logical database. A datab ## Set permissions for a new user During user creation, the permissions panel can be accessed through the top tab menu. -For more information, see [how to add users](/managed-databases/postgresql-and-mysql/how-to/add-users/). +For more information, see [how to add users](/managed-databases-for-postgresql-and-mysql/how-to/add-users/). Permissions are applied on existing items **at the moment the configuration is set**, and not applied to any items created afterward. diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-read-replica.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-read-replica.mdx index 4feaed4f85..036c074a1e 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-read-replica.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-read-replica.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) -- [Created a Read Replica](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) +- [Created a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) ## How to resync a Read Replica @@ -96,7 +96,7 @@ If you already have an attached Private Network, you can detach it from your Rea ## How to delete a public endpoint -Refer to the [How to delete a public endpoint](/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint/#from-read-replicas) documentation page to do so for your Read Replica. +Refer to the [How to delete a public endpoint](/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint/#from-read-replicas) documentation page to do so for your Read Replica. ## How to delete Read Replicas diff --git a/managed-databases/postgresql-and-mysql/how-to/manage-snapshots.mdx b/managed-databases/postgresql-and-mysql/how-to/manage-snapshots.mdx index 20ae589a6e..4cc977f050 100644 --- a/managed-databases/postgresql-and-mysql/how-to/manage-snapshots.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/manage-snapshots.mdx @@ -14,17 +14,17 @@ categories: - postgresql-and-mysql --- -[Snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes. +[Snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/) allow you to restore data in a new Database Instance, instead of creating individual automated database backups. It is only available for Database Instances that use Block Storage volumes. -When you set up [autobackups](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) for Database Instances that use Block Storage, the automatic backups are created in snapshot format. +When you set up [autobackups](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) for Database Instances that use Block Storage, the automatic backups are created in snapshot format. You can have up to 100 snapshots per Instance and Project (depending on quotas). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to create snapshots diff --git a/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx b/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx index 11d9d6db91..a07df31743 100644 --- a/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/monitor-databases-cockpit.mdx @@ -14,7 +14,7 @@ categories: - postgresql-and-mysql --- -You can view your Managed Database for PostgreSQL or MySQL metrics and logs using [Scaleway Cockpit](/observability/cockpit/quickstart/). Managed Databases are fully integrated into Cockpit. +You can view your Managed Database for PostgreSQL or MySQL metrics and logs using [Scaleway Cockpit](/cockpit/quickstart/). Managed Databases are fully integrated into Cockpit. Monitoring is available for: - Primary Database Instance nodes @@ -26,12 +26,12 @@ This page explains how to get started with Scaleway Cockpit for viewing your Man - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created any [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created any [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to access the Grafana dashboard @@ -39,7 +39,7 @@ To view your Managed Database's metrics and logs, use the Grafana dashboard whic - First, you must create a user and their associated credentials (a username and password) for Grafana - Then, you can use these credentials to access the Grafana dashboard for all your Scaleway products, via the Scaleway console. -1. Create a Grafana user and retrieve their username and password by [following this procedure](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. Create a Grafana user and retrieve their username and password by [following this procedure](/cockpit/how-to/retrieve-grafana-credentials/). 2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. @@ -83,14 +83,14 @@ Log configuration is done by Scaleway. Note that: - The `log_error_verbosity` parameter is set to `VERBOSE` for PostgreSQL and `2` for MySQL by default. - On PostgreSQL, all queries longer than 5 seconds are logged. This parameter cannot be edited. -- On MySQL, slow queries are not activated by default, but can be activated in the [advanced settings](/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings/) of the Database Instance. The setting is called `slow_query_log` and the time can be edited with `long_query_time`. +- On MySQL, slow queries are not activated by default, but can be activated in the [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings/) of the Database Instance. The setting is called `slow_query_log` and the time can be edited with `long_query_time`. ## How to activate preconfigured alerts You can activate Scaleway preconfigured alerts for your Managed Databases with Scaleway Cockpit. - Refer to the [How to activate preconfigured alerts](/observability/cockpit/how-to/activate-managed-alerts/) to learn how to do so. + Refer to the [How to activate preconfigured alerts](/cockpit/how-to/activate-managed-alerts/) to learn how to do so. By default, three preconfigured alerts are available for Managed Databases: @@ -99,7 +99,7 @@ By default, three preconfigured alerts are available for Managed Databases: - `MySQLHighCPULoad` or `PostgreSQLHighCPULoad`- You are alerted if CPU usage is higher than 80% for 10 consecutive minutes. - `MySQLTooManyConnections` or `PostgreSQLTooManyConnections`- You are alerted if your connection usage is higher than 80% for 10 consecutive minutes. -You can also configure [your own alerts](/observability/cockpit/how-to/configure-alerts-for-scw-resources/) and set values for each of the parameters below to define when you want to be alerted: +You can also configure [your own alerts](/cockpit/how-to/configure-alerts-for-scw-resources/) and set values for each of the parameters below to define when you want to be alerted: ### MySQL diff --git a/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint.mdx b/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint.mdx index f1a737b3a6..92d51bbd57 100644 --- a/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint.mdx @@ -23,7 +23,7 @@ If you are using a public endpoint with your Database Instances or Read Replicas - A Scaleway account logged into the [console](https://console.scaleway.com) -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## From Database Instances @@ -47,7 +47,7 @@ If you are using a public endpoint with your Database Instances or Read Replicas - A Scaleway account logged into the [console](https://console.scaleway.com) -- A [Read Replica](/managed-databases/postgresql-and-mysql/how-to/create-read-replica/) +- A [Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/create-read-replica/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/postgresql-and-mysql/how-to/renew-tls-certificate.mdx b/managed-databases/postgresql-and-mysql/how-to/renew-tls-certificate.mdx index fe4e917386..629a41c0a0 100644 --- a/managed-databases/postgresql-and-mysql/how-to/renew-tls-certificate.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/renew-tls-certificate.mdx @@ -21,8 +21,8 @@ A certificate is generated automatically upon the creation of a Database Instanc - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. @@ -31,7 +31,7 @@ A certificate is generated automatically upon the creation of a Database Instanc Renewing a certificate means you: - - Will not be able to connect to your Database Instance with the previous certificate when using the [verify-ca and verify-full](/managed-databases/postgresql-and-mysql/api-cli/verify-ca-postgresql/). + - Will not be able to connect to your Database Instance with the previous certificate when using the [verify-ca and verify-full](/managed-databases-for-postgresql-and-mysql/api-cli/verify-ca-postgresql/). - Will need to download and update the new certificate for all database clients. diff --git a/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx b/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx index c534d25845..1187957b95 100644 --- a/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database.mdx @@ -19,8 +19,8 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL or MySQL Database Instance](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL or MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/quickstart/) ## How to increase a Block Storage volume @@ -37,9 +37,9 @@ You can upgrade your Database Instances in two ways: by increasing its Block Sto ## How to change the node type - If you have a Database Instance that uses a local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

+ If you have a Database Instance that uses a local volume, and you want to upgrade to a node type that uses Block volumes, you must [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to Block Storage first.

- Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases/postgresql-and-mysql/concepts/#block-storage-low-latency) node type and want to switch to a first-generation node type, you must first change the volume type to [Block Storage Legacy](/managed-databases/postgresql-and-mysql/concepts/#block-storage-legacy). + Similarly, if you have a new-generation Database Instance using a [Low Latency Block volume](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-low-latency) node type and want to switch to a first-generation node type, you must first change the volume type to [Block Storage Legacy](/managed-databases-for-postgresql-and-mysql/concepts/#block-storage-legacy). 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. diff --git a/managed-databases/postgresql-and-mysql/how-to/upgrade-version.mdx b/managed-databases/postgresql-and-mysql/how-to/upgrade-version.mdx index 360b140a93..175a58205e 100644 --- a/managed-databases/postgresql-and-mysql/how-to/upgrade-version.mdx +++ b/managed-databases/postgresql-and-mysql/how-to/upgrade-version.mdx @@ -23,14 +23,14 @@ You must upgrade your engine version if your Database Instance uses an End of Li The version upgrade is only available for: - Database Instances using engine versions preceding the most recent version available. - - Database Instances using Block volumes. If your Database Instance uses a local volume, you must first [change the volume type](/managed-databases/postgresql-and-mysql/how-to/change-volume-type/) to a Block volume and try again. + - Database Instances using Block volumes. If your Database Instance uses a local volume, you must first [change the volume type](/managed-databases-for-postgresql-and-mysql/how-to/change-volume-type/) to a Block volume and try again. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [PostgreSQL Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) running on an outdated engine version +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [PostgreSQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) running on an outdated engine version 1. Click **PostgreSQL and MySQL** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the name of the database whose engine you want to upgrade. The Database Instance information page appears. @@ -50,7 +50,7 @@ The version upgrade is only available for: - Follow the [migrating endpoints via the CLI](/managed-databases/postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to quickly migrate your endpoints. You can use this procedure to revert the migration anytime.

+ Follow the [migrating endpoints via the CLI](/managed-databases-for-postgresql-and-mysql/api-cli/migrating-endpoints/) procedure to quickly migrate your endpoints. You can use this procedure to revert the migration anytime.

Keep in mind that reverting the endpoint will not affect the data stored on the databases. This means that if some entries were added to the upgraded database, they will not be added back to the old version when you change the endpoints. 4. Click **Upgrade version**. A new Database Instance is created. diff --git a/managed-databases/postgresql-and-mysql/index.mdx b/managed-databases/postgresql-and-mysql/index.mdx index eca866f682..0ba6adb6db 100644 --- a/managed-databases/postgresql-and-mysql/index.mdx +++ b/managed-databases/postgresql-and-mysql/index.mdx @@ -8,7 +8,7 @@ meta: productName="Managed Database for PostgreSQL and MySQL" productLogo="managedDatabase" description="Managed Database for PostgreSQL and MySQL provides fully-managed relational Database Instances that offer you automatic backups, scaling, monitoring and more." - url="/managed-databases/postgresql-and-mysql/quickstart/" + url="/managed-databases-for-postgresql-and-mysql/quickstart/" label="PostgreSQL and MySQL Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create a Managed Database for PostgreSQL and MySQL in a few steps." label="View Quickstart" - url="/managed-databases/postgresql-and-mysql/quickstart/" + url="/managed-databases-for-postgresql-and-mysql/quickstart/" /> diff --git a/managed-databases/postgresql-and-mysql/quickstart.mdx b/managed-databases/postgresql-and-mysql/quickstart.mdx index 9d357f09d9..778dfe5d59 100644 --- a/managed-databases/postgresql-and-mysql/quickstart.mdx +++ b/managed-databases/postgresql-and-mysql/quickstart.mdx @@ -23,7 +23,7 @@ Compared to traditional database management, which requires customers to provide - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a database @@ -45,7 +45,7 @@ Compared to traditional database management, which requires customers to provide The local Storage option is only available with the first-generation node types. - - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) or select [Manual snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/). + - Select the snapshot configuration. You can either leave the default **Automatic** option to enable [autobackups](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) or select [Manual snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/). - Add a name and set a password for your user. Your username must adhere to specific criteria. diff --git a/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions.mdx b/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions.mdx index e0c58c3187..093c9ebfbe 100644 --- a/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions.mdx +++ b/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions.mdx @@ -66,7 +66,7 @@ The following `pg_extensions` are available with Scaleway Managed Databases for ## Extension best practices - When you use functions installed by postgres extensions, the best practice is to specify the namespace of the function if you do not modify the `search_path`. When functions come from extensions or are used in postgresql objects, it is necessary to specify the namespace of these functions independently of `search_path` management to avoid errors when restoring backups. -- Some extensions, such as `pg_audit`, must be configured from the [advanced settings](/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings) tab in the console. Refer to the [Setting up and using pgaudit](/managed-databases/postgresql-and-mysql/api-cli/pg-audit/) documentation page for more information. +- Some extensions, such as `pg_audit`, must be configured from the [advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings) tab in the console. Refer to the [Setting up and using pgaudit](/managed-databases-for-postgresql-and-mysql/api-cli/pg-audit/) documentation page for more information. ## Extension usage example diff --git a/managed-databases/postgresql-and-mysql/reference-content/security-and-reliability.mdx b/managed-databases/postgresql-and-mysql/reference-content/security-and-reliability.mdx index 58ddeebc37..c4244852c7 100644 --- a/managed-databases/postgresql-and-mysql/reference-content/security-and-reliability.mdx +++ b/managed-databases/postgresql-and-mysql/reference-content/security-and-reliability.mdx @@ -40,7 +40,7 @@ Managed Databases for PostgreSQL and MySQL targets the following SLOs for their You can configure your snapshots and/or backup settings to automate actions. When you define execution time, frequency, and expiration, you automate the creation and deletion of snapshots and backups. Creation happens at the defined frequency and deletion happens when resources reach their expiration date. -Refer to the [How to enable Autobackup](/managed-databases/postgresql-and-mysql/how-to/enable-autobackup/) documentation page for more information. +Refer to the [How to enable Autobackup](/managed-databases-for-postgresql-and-mysql/how-to/enable-autobackup/) documentation page for more information. ### Data restoration @@ -52,7 +52,7 @@ Keep in mind that: - Snapshots are disk "pictures" which contain all ready-to-use data structures for PostgreSQL and MySQL. Restoring a snapshot should usually take a few minutes. - Backups are logical backups of a database and only "raw" data from tables. Restoring a backup requires recreating objects such as indexes. Depending on the number of indexes, total data size, and database size, the restore operations can take from a few minutes to several hours. -Refer to the [How to manage backups](/managed-databases/postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and the [How to manage snapshots](/managed-databases/postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) documentation pages for more information. +Refer to the [How to manage backups](/managed-databases-for-postgresql-and-mysql/how-to/manage-manual-backups/#how-to-restore-backups) and the [How to manage snapshots](/managed-databases-for-postgresql-and-mysql/how-to/manage-snapshots/#how-to-create-a-database-instance-from-a-snapshot) documentation pages for more information. ### Failover @@ -68,11 +68,11 @@ Creating, deleting, and promoting a Read Replica are actions triggered by you. S The time it takes to create the Read Replica depends on the volume of data being replicated. -When [promoting a Read Replica](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) to a main node, make sure that the main node has completed all ongoing operations and that the Read Replica lag is down to zero before promoting it. +When [promoting a Read Replica](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) to a main node, make sure that the main node has completed all ongoing operations and that the Read Replica lag is down to zero before promoting it. If ongoing operations are not complete before the promote operation starts, some operations from the main node might not be contained in the newly promoted node. -Refer to the [How to manage Read Replicas](/managed-databases/postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page for more information. +Refer to the [How to manage Read Replicas](/managed-databases-for-postgresql-and-mysql/how-to/manage-read-replica/#how-to-promote-a-read-replica) documentation page for more information. ## Monitoring @@ -93,7 +93,7 @@ This includes: - For more granular log details, you can activate the [pgaudit extension](/managed-databases/postgresql-and-mysql/api-cli/pg-audit/). + For more granular log details, you can activate the [pgaudit extension](/managed-databases-for-postgresql-and-mysql/api-cli/pg-audit/). - MySQL logs at a default level `log_error_verbosity=2` ([see MySQL documentation](https://dev.mysql.com/doc/refman/8.0/en/server-system-variables.html#sysvar_log_error_verbosity)). Logging slow queries is not activated by default, but you can activate it using `slow_query_log` and `long_query_time`.  @@ -111,7 +111,7 @@ To troubleshoot the issue, you can either: - Increase disk volume size, or - Clear data from your database. -Refer to the [Dealing with disk_full mode in a Database Instance](/managed-databases/postgresql-and-mysql/troubleshooting/disk-full/) documentation page for more information. +Refer to the [Dealing with disk_full mode in a Database Instance](/managed-databases-for-postgresql-and-mysql/troubleshooting/disk-full/) documentation page for more information. You are responsible for monitoring disk size growth and performing any required disk size increases. @@ -134,7 +134,7 @@ Configuration and version management are critical for maintaining consistency, r Scaleway creates your Database Instance with a default configuration proven for standard use cases. Certain options are restricted to ensure reliability. -You can [modify some advanced settings](/managed-databases/postgresql-and-mysql/how-to/configure-advanced-settings/), such as `effective_cache_size` or `max_connections` in PostgreSQL, but you are responsible for any impacts on your database availability and performance. +You can [modify some advanced settings](/managed-databases-for-postgresql-and-mysql/how-to/configure-advanced-settings/), such as `effective_cache_size` or `max_connections` in PostgreSQL, but you are responsible for any impacts on your database availability and performance. ### Version management @@ -143,7 +143,7 @@ Two types of engine version upgrades are available for your databases: | Upgrade Type | Description| | ------------ | ------------------- | | Minor versions | These are updates within the same version and are performed automatically during maintenance periods. The updates include security fixes and bug fixes and are designed to be backward compatible. | -| Major versions | You can trigger major version upgrades on your Database Instance. Once you trigger an upgrade, Scaleway automatically creates a clone of your database with the chosen PostgreSQL version. Depending on the option you choose, you might need to manually switch traffic to your newly created database and/or stop write operations on your source database. Refer to the [How to upgrade your Database Instance engine version](/managed-databases/postgresql-and-mysql/how-to/upgrade-version/) documentation page for more information| +| Major versions | You can trigger major version upgrades on your Database Instance. Once you trigger an upgrade, Scaleway automatically creates a clone of your database with the chosen PostgreSQL version. Depending on the option you choose, you might need to manually switch traffic to your newly created database and/or stop write operations on your source database. Refer to the [How to upgrade your Database Instance engine version](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-version/) documentation page for more information| ### Database extensions @@ -186,14 +186,14 @@ Identity and access management allows you to enable granular control over user p ### Scaleway IAM -Managed Databases for PostgreSQL provides [IAM permissions sets](/identity-and-access-management/iam/reference-content/permission-sets/) that allow or restrict specific actions a user or application can perform, such as creating or deleting Database Instances. These are: +Managed Databases for PostgreSQL provides [IAM permissions sets](/iam/reference-content/permission-sets/) that allow or restrict specific actions a user or application can perform, such as creating or deleting Database Instances. These are: - `RelationalDatabasesReadOnly` and - `RelationalDatabasesFullAccess` You are responsible for attributing these permissions to the relevant users or applications and reviewing these accesses frequently. -Refer to the [How to create a policy](/identity-and-access-management/iam/how-to/create-policy/) documentation page to set up a policy for Managed Databases for PostgreSQL and MySQL. +Refer to the [How to create a policy](/iam/how-to/create-policy/) documentation page to set up a policy for Managed Databases for PostgreSQL and MySQL. ### Database access management @@ -207,7 +207,7 @@ You are responsible for giving access to the relevant users or applications and Moreover, these accesses are stored inside your Database Instance only and are independent of Scaleway IAM, which means you are responsible for ensuring they are properly backed up or removed when required. -Refer to the [How to manage user permissions](/managed-databases/postgresql-and-mysql/how-to/manage-permissions/) documentation page for more information. +Refer to the [How to manage user permissions](/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions/) documentation page for more information. ## Security best practices @@ -219,6 +219,6 @@ For optimal security, we recommend that you: 2. Restrict external access to databases by limiting IPs able to connect to the database. - You can use ACLs to restrict access. Refer to the [How to manage allowed IPs](/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses/) documentation page for more information. + You can use ACLs to restrict access. Refer to the [How to manage allowed IPs](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses/) documentation page for more information. diff --git a/managed-databases/postgresql-and-mysql/troubleshooting/disk-full.mdx b/managed-databases/postgresql-and-mysql/troubleshooting/disk-full.mdx index 641ef5f07e..f978145dc6 100644 --- a/managed-databases/postgresql-and-mysql/troubleshooting/disk-full.mdx +++ b/managed-databases/postgresql-and-mysql/troubleshooting/disk-full.mdx @@ -20,7 +20,7 @@ The Database Instance switches to `disk_full` mode when the free space falls und For Database Instances where 2% of the volume size is more than 2 GB, this threshold is 2 GB. -This state allows you to increase your volume, if you use Block Storage, or [upgrade your node type](/managed-databases/postgresql-and-mysql/how-to/upgrade-a-database/). You can also clear some space in your volume to increase your capacity. +This state allows you to increase your volume, if you use Block Storage, or [upgrade your node type](/managed-databases-for-postgresql-and-mysql/how-to/upgrade-a-database/). You can also clear some space in your volume to increase your capacity. When the Database Instance switches to `disk_full` state, the default transaction mode automatically switches to `read only`. This allows your applications to still access its data, while preventing new data from being added. @@ -51,7 +51,7 @@ scw rdb log purge instance-id=11111111-1111-1111-1111-111111111111 ## How to clear out space used by your Database engine -1. [Connect to your Database Instance](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/). +1. [Connect to your Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/). 2. Run the following commands to shift to a `read write` transaction: ```sql -- On PostgreSQL diff --git a/managed-databases/postgresql-and-mysql/troubleshooting/extension-errors.mdx b/managed-databases/postgresql-and-mysql/troubleshooting/extension-errors.mdx index 30abc60517..0b530d556c 100644 --- a/managed-databases/postgresql-and-mysql/troubleshooting/extension-errors.mdx +++ b/managed-databases/postgresql-and-mysql/troubleshooting/extension-errors.mdx @@ -34,4 +34,4 @@ For security reasons only the `pg_catalog` namespace is checked during backup re Run the function again while defining the namespace. -For more information and examples refer to the [PostgreSQL extensions reference](/managed-databases/postgresql-and-mysql/reference-content/postgresql-extensions) page. \ No newline at end of file +For more information and examples refer to the [PostgreSQL extensions reference](/managed-databases-for-postgresql-and-mysql/reference-content/postgresql-extensions) page. \ No newline at end of file diff --git a/managed-databases/redis/api-cli/managing-username-and-password.mdx b/managed-databases/redis/api-cli/managing-username-and-password.mdx index df72712900..3d12d805d3 100644 --- a/managed-databases/redis/api-cli/managing-username-and-password.mdx +++ b/managed-databases/redis/api-cli/managing-username-and-password.mdx @@ -13,15 +13,15 @@ categories: - redis --- -When you create a Redis™* Database Instance, you have to specify a user. It will be created with [set permissions](/managed-databases/redis/reference-content/default-user-permissions/). +When you create a Redis™* Database Instance, you have to specify a user. It will be created with [set permissions](/managed-databases-for-redis/reference-content/default-user-permissions/). You can specify a name for this user when you create a Database Instance. This allows you to ensure the username is compatible with different software integrations where specific usernames are not supported. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Downloaded and installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) - [Configured your environment variables](https://github.com/scaleway/scaleway-cli/blob/master/docs/commands/config.md) (optional) @@ -30,7 +30,7 @@ You can specify a name for this user when you create a Database Instance. This a Follow the [create a Database Instance](https://www.scaleway.com/en/developers/api/managed-database-redis/#quickstart) procedure. -You can also define a username when you [create a Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) via the Scaleway console. +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. You are required to specify a username and password for the default user in your POST request payload. diff --git a/managed-databases/redis/api-cli/using-pub-sub-feature.mdx b/managed-databases/redis/api-cli/using-pub-sub-feature.mdx index 7a143a3b97..810314a308 100644 --- a/managed-databases/redis/api-cli/using-pub-sub-feature.mdx +++ b/managed-databases/redis/api-cli/using-pub-sub-feature.mdx @@ -26,10 +26,10 @@ To implement Pub/Sub using Redis, you can run commands such as `PUBLISH` and `SU - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/quickstart/) with Redis™ version 6 or 7 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/quickstart/) with Redis™ version 6 or 7 -1. [Connect to your Redis™ Database Instance](/managed-databases/redis/how-to/connect-to-redis-database-instance/). +1. [Connect to your Redis™ Database Instance](/managed-databases-for-redis/how-to/connect-to-redis-database-instance/). 2. Subscribe to a topic. In this tutorial, we will use `temperature` as an example of topic. ``` > SUBSCRIBE temperature diff --git a/managed-databases/redis/concepts.mdx b/managed-databases/redis/concepts.mdx index 19c7ea543f..eee41289af 100644 --- a/managed-databases/redis/concepts.mdx +++ b/managed-databases/redis/concepts.mdx @@ -15,7 +15,7 @@ categories: ## Allowed IPs -Access control list (ACL) rules [define permissions for remote access to a Database Instance](/managed-databases/postgresql-and-mysql/how-to/manage-allowed-ip-addresses/). A rule consists of an IP address or an IP range. +Access control list (ACL) rules [define permissions for remote access to a Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/manage-allowed-ip-addresses/). A rule consists of an IP address or an IP range. ## Cluster @@ -27,7 +27,7 @@ Each Managed Database for Redis™ cluster consists of minimum three and maximum ## Endpoint -An endpoint is a point of connection to a database. The endpoint is associated with one or more public IPv4 addresses and a port, or with a private IPv4 and a port (if you use [Private Networks](/network/vpc/concepts/#private-networks)). +An endpoint is a point of connection to a database. The endpoint is associated with one or more public IPv4 addresses and a port, or with a private IPv4 and a port (if you use [Private Networks](/vpc/concepts/#private-networks)). ## Database Instance diff --git a/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx b/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx index 9870a028ce..4d2736307d 100644 --- a/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx +++ b/managed-databases/redis/how-to/configure-advanced-settings-redis.mdx @@ -19,8 +19,8 @@ Advanced settings allow you to modify the default configuration of your Redis™ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/quickstart/) Changing the advanced settings can have an impact on the performance of your Database Instance. diff --git a/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx b/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx index df88df18da..c102e35667 100644 --- a/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx +++ b/managed-databases/redis/how-to/connect-to-redis-database-instance.mdx @@ -19,11 +19,11 @@ You can connect to your Redis™* Database Instance using the [Redis - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) -To connect to a Redis™ Database Instance in a Private Network, you can use Public Gateways in [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding, as Managed Databases for Redis™ are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). +To connect to a Redis™ Database Instance in a Private Network, you can use Public Gateways in [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding, as Managed Databases for Redis™ are currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). 1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Redis™ Database Instances displays. diff --git a/managed-databases/redis/how-to/create-a-database-for-redis.mdx b/managed-databases/redis/how-to/create-a-database-for-redis.mdx index 831d85d142..81c5190bde 100644 --- a/managed-databases/redis/how-to/create-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/create-a-database-for-redis.mdx @@ -19,7 +19,7 @@ Managed Database for Redis™* is a low-latency caching solution base - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Redis™** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. 2. Click **Create Redis™ Database Instance**. The creation wizard displays. @@ -45,7 +45,7 @@ Managed Database for Redis™* is a low-latency caching solution base - If you want to use Private Networks, you must select the option upon creation. It is not possible to add the Redis™ Database Instance to a Private Network once it has been created. - Your private IP addresses are automatically allocated. They are managed via an IP Address Manager (IPAM). You can retrieve them on the Private Network tab of your Database Instance. To allocate IPs manually, you can use the Scaleway API and CLI, or Terraform. - - Managed Databases for Redis™ are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. + - Managed Databases for Redis™ are currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). You can use Public Gateways in [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) mode and perform port forwarding. - **Public network**: resources in a public network are publicly visible by default. The default Access Control List (ACL) settings allow anybody to connect to resources in your network. You can restrict access by configuring ACLs. diff --git a/managed-databases/redis/how-to/delete-a-database-for-redis.mdx b/managed-databases/redis/how-to/delete-a-database-for-redis.mdx index 854f6c9337..7490bf1f45 100644 --- a/managed-databases/redis/how-to/delete-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/delete-a-database-for-redis.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) 1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the database information page. diff --git a/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx b/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx index 99a77c6791..65e350e47c 100644 --- a/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx +++ b/managed-databases/redis/how-to/manage-allowed-ip-addresses-redis.mdx @@ -19,8 +19,8 @@ Allowed IPs restrict the IPs allowed to access your Redis™* Databas - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) Allowed IP configuration is only available for public networks. diff --git a/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx b/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx index 0a1124542e..da21b88100 100644 --- a/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx +++ b/managed-databases/redis/how-to/scale-up-a-database-for-redis.mdx @@ -24,8 +24,8 @@ If you want to scale up the size of your Redis™* Database Instance, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) 1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instances information page. @@ -41,8 +41,8 @@ If you want to scale up the size of your Redis™* Database Instance, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) in [cluster mode](/managed-databases/redis/concepts/#cluster-mode) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) in [cluster mode](/managed-databases-for-redis/concepts/#cluster-mode) 1. Click **Redis™** under **Database** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the Database Instance information page. diff --git a/managed-databases/redis/index.mdx b/managed-databases/redis/index.mdx index 690b32070a..58f07b7d25 100644 --- a/managed-databases/redis/index.mdx +++ b/managed-databases/redis/index.mdx @@ -8,7 +8,7 @@ meta: productName="Managed Database for Redis™" productLogo="redis" description="Managed Database for Redis™ is a low-latency caching solution based on in-memory data storage. Enjoy reliable performance, automatic backups and more." - url="/managed-databases/redis/quickstart/" + url="/managed-databases-for-redis/quickstart/" label="Managed Database for Redis™ Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create and set up a Redis™ Database Instance in a few steps." label="View Quickstart" - url="/managed-databases/redis/quickstart/" + url="/managed-databases-for-redis/quickstart/" /> diff --git a/managed-databases/redis/quickstart.mdx b/managed-databases/redis/quickstart.mdx index 11e9c90542..ac2913c784 100644 --- a/managed-databases/redis/quickstart.mdx +++ b/managed-databases/redis/quickstart.mdx @@ -21,7 +21,7 @@ Managed Database for Redis™ is a low-latency caching solution based on in-memo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Redis™** under **Managed Databases** on the side menu. If you do not have a database already created, the creation page displays. 2. Click **Create Redis™ Database Instance**. The creation wizard displays. @@ -71,8 +71,8 @@ Managed Database for Redis™ is a low-latency caching solution based on in-memo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) 1. Click **Redis™** under **Managed Databases** on the side menu. A list of your Database Instances displays. 2. Click the database name or > **More info** to access the database information page. diff --git a/managed-databases/redis/reference-content/default-user-permissions.mdx b/managed-databases/redis/reference-content/default-user-permissions.mdx index 7c266c64ce..4c3cc09ccb 100644 --- a/managed-databases/redis/reference-content/default-user-permissions.mdx +++ b/managed-databases/redis/reference-content/default-user-permissions.mdx @@ -40,7 +40,7 @@ For a username to be valid, it must: - not be `scalewayadmin` or `metrics` - You can change the default username and password anytime via the Scaleway API or the CLI. Refer to the [Managing the default user's username and password](/managed-databases/redis/api-cli/managing-username-and-password/) documentation page for more information. + You can change the default username and password anytime via the Scaleway API or the CLI. Refer to the [Managing the default user's username and password](/managed-databases-for-redis/api-cli/managing-username-and-password/) documentation page for more information.
diff --git a/managed-services/data-lab/how-to/connect-to-data-lab.mdx b/managed-services/data-lab/how-to/connect-to-data-lab.mdx index b610167891..cfce883d4d 100644 --- a/managed-services/data-lab/how-to/connect-to-data-lab.mdx +++ b/managed-services/data-lab/how-to/connect-to-data-lab.mdx @@ -17,10 +17,10 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Signed up to the private beta](https://www.scaleway.com/fr/betas/#distributed-data-lab) and received a confirmation email. -- Created a [Distributed Data Lab cluster](/managed-services/data-lab/how-to/create-data-lab/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- Created a [Distributed Data Lab cluster](/data-lab/how-to/create-data-lab/) +- A valid [API key](/iam/how-to/create-api-keys/) 1. Click **Data Lab** under **Managed Services** on the side menu. The Distributed Data Lab page displays. @@ -28,7 +28,7 @@ categories: 3. Click **Open Notebook** in the **Notebook** section. You are directed to the notebook login page. -4. Enter your [API secret key](/identity-and-access-management/iam/concepts/#api-key) when prompted for a password, then click **Log in**. You are directed to the lab's home screen. +4. Enter your [API secret key](/iam/concepts/#api-key) when prompted for a password, then click **Log in**. You are directed to the lab's home screen. 5. In the files list on the left, double-click the `quickstart.ipynb` file to open it. diff --git a/managed-services/data-lab/how-to/create-data-lab.mdx b/managed-services/data-lab/how-to/create-data-lab.mdx index 6a290467a4..6140fd4516 100644 --- a/managed-services/data-lab/how-to/create-data-lab.mdx +++ b/managed-services/data-lab/how-to/create-data-lab.mdx @@ -19,10 +19,10 @@ Distributed Data Lab is a product designed to assist data scientists and data en - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Signed up to the private beta](https://www.scaleway.com/fr/betas/#distributed-data-lab) and received a confirmation email. -- Optionally, an [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- Optionally, an [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- A valid [API key](/iam/how-to/create-api-keys/) 1. Click **Data Lab** under **Managed Services** on the side menu. The Distributed Data Lab page displays. diff --git a/managed-services/data-lab/how-to/manage-delete-data-lab.mdx b/managed-services/data-lab/how-to/manage-delete-data-lab.mdx index c4cdfd7040..bb6584a8ff 100644 --- a/managed-services/data-lab/how-to/manage-delete-data-lab.mdx +++ b/managed-services/data-lab/how-to/manage-delete-data-lab.mdx @@ -19,9 +19,9 @@ This page explains how to manage and delete your Distributed Data Lab. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Signed up to the private beta](https://www.scaleway.com/fr/betas/#distributed-data-lab) and received a confirmation email. -- Created a [Distributed Data Lab cluster](/managed-services/data-lab/how-to/create-data-lab/) +- Created a [Distributed Data Lab cluster](/data-lab/how-to/create-data-lab/) ## How to manage a Distributed Data Lab @@ -34,10 +34,10 @@ This page explains how to manage and delete your Distributed Data Lab. 4. From this view, you can: - Add, consult, or delete tags for your cluster. - - [Delete your Data Lab cluster](/managed-services/data-lab/how-to/manage-delete-data-lab/#how-to-delete-a-distributed-data-lab). + - [Delete your Data Lab cluster](/data-lab/how-to/manage-delete-data-lab/#how-to-delete-a-distributed-data-lab). -Once you have created a Data Lab cluster, you cannot edit its parameters, such as the node type, or its computing resources. You must [create a new Data Lab cluster](/managed-services/data-lab/how-to/create-data-lab/) instead. +Once you have created a Data Lab cluster, you cannot edit its parameters, such as the node type, or its computing resources. You must [create a new Data Lab cluster](/data-lab/how-to/create-data-lab/) instead. ## How to delete a Distributed Data Lab diff --git a/managed-services/data-lab/index.mdx b/managed-services/data-lab/index.mdx index 89684521c4..aaaf329d5c 100644 --- a/managed-services/data-lab/index.mdx +++ b/managed-services/data-lab/index.mdx @@ -8,7 +8,7 @@ meta: productName="Distributed Data Lab" productLogo="dataLab" description="Distributed Data Lab is designed to assist data scientists and data engineers perform calculations on a remotely managed Apache Spark infrastructure." - url="/managed-services/data-lab/quickstart" + url="/data-lab/quickstart" label="Distributed Data Lab Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to create, use, manage, and delete a Distributed Data Lab in a few steps." label="View Quickstart" - url="/managed-services/data-lab/quickstart/" + url="/data-lab/quickstart/" /> diff --git a/managed-services/data-lab/quickstart.mdx b/managed-services/data-lab/quickstart.mdx index a8a55f84fd..ecf51a09ef 100644 --- a/managed-services/data-lab/quickstart.mdx +++ b/managed-services/data-lab/quickstart.mdx @@ -29,9 +29,9 @@ The notebook, although capable of performing some local computations, primarily - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Signed up to the private beta](https://www.scaleway.com/fr/betas/#distributed-data-lab) and received a confirmation email. -- Optionally, an [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- Optionally, an [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to create a Distributed Data Lab cluster @@ -61,7 +61,7 @@ The notebook, although capable of performing some local computations, primarily 3. Click **Open Notebook** in the **Notebook** section. You are directed to the notebook login page. -4. Enter your [API secret key](/identity-and-access-management/iam/concepts/#api-key) when prompted for a password, then click **Log in**. You are directed to the notebook home screen. +4. Enter your [API secret key](/iam/concepts/#api-key) when prompted for a password, then click **Log in**. You are directed to the notebook home screen. ## How to run the demo file diff --git a/managed-services/iot-hub/api-cli/cli-db-tips-tricks.mdx b/managed-services/iot-hub/api-cli/cli-db-tips-tricks.mdx index 39a4bd6f70..177c0e2e53 100644 --- a/managed-services/iot-hub/api-cli/cli-db-tips-tricks.mdx +++ b/managed-services/iot-hub/api-cli/cli-db-tips-tricks.mdx @@ -16,7 +16,7 @@ tags: iot iot-hub database cli postgresql payload plsql json mysql Routes are integrations with the Scaleway ecosystem: they can forward MQTT messages to Scaleway services. -You can find the documentation here: [IoT Hub Routes](/managed-services/iot-hub/how-to/create-route/). +You can find the documentation here: [IoT Hub Routes](/iot-hub/how-to/create-route/). This page shows advanced usages of PostgreSQL and MySQL. @@ -29,8 +29,8 @@ This section shows two cases of data manipulation on the PostgreSQL side. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Followed the [Getting started with the IoT Hub CLI](/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli/) tutorial +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Followed the [Getting started with the IoT Hub CLI](/iot-hub/api-cli/getting-started-with-iot-hub-cli/) tutorial - A working PostgreSQL database, with valid credentials (username and password) - Set up environment variables as shown in the code box below: @@ -189,7 +189,7 @@ This section presents similar examples using MySQL: -- Followed the [Getting started with the IoT Hub CLI](/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli/) tutorial +- Followed the [Getting started with the IoT Hub CLI](/iot-hub/api-cli/getting-started-with-iot-hub-cli/) tutorial - A working MySQL database, with valid credentials (username and password). You can use a [Scaleway Database instance](https://console.scaleway.com/rdb/instances), or any other MySQL instance publicly accessible - Set up environment variables as shown in the code box below @@ -205,7 +205,7 @@ DBPASS= ### Basic MySQL example -This is a port of the [Database Route section of the CLI tutorial](/managed-services/iot-hub/api-cli/iot-hub-routes/) to MySQL. +This is a port of the [Database Route section of the CLI tutorial](/iot-hub/api-cli/iot-hub-routes/) to MySQL. NOTE: The `topic` database field **must** be a of _text_ type, and `payload` can be of _text_ or _blob_ type depending on your usage. diff --git a/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx b/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx index a04a6da52c..65c8bab64e 100644 --- a/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx +++ b/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-api.mdx @@ -19,8 +19,8 @@ The API reference is here: [IoT API](https://www.scaleway.com/en/developers/api/ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/). +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/). - Installed `curl`, `mosquitto-clients` (mqtt client), and `jq` (json parsing tool) You already set the `SCW_SECRET_KEY` variable above, now set the following variables from the same terminal on your local computer: diff --git a/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx b/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx index e073da1cb8..f2a051edd6 100644 --- a/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx +++ b/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli.mdx @@ -20,9 +20,9 @@ You can find the API reference documentation at the following link: [IoT API](ht - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed `mosquitto-clients` (mqtt client) and `jq` (json parsing tool) on your computer -- [Installed and configured the Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Installed and configured the Scaleway CLI](/scaleway-cli/quickstart/) ## Setting up the hub diff --git a/managed-services/iot-hub/api-cli/iot-hub-routes.mdx b/managed-services/iot-hub/api-cli/iot-hub-routes.mdx index 287fee496d..702f74acf9 100644 --- a/managed-services/iot-hub/api-cli/iot-hub-routes.mdx +++ b/managed-services/iot-hub/api-cli/iot-hub-routes.mdx @@ -15,15 +15,15 @@ tags: iot iot-hub mqtt cli s3cmd amazon-s3 Routes are integrations with the Scaleway ecosystem: they can forward MQTT messages to Scaleway services. - Find out more about IoT Hub Routes in the [Routes reference page](/managed-services/iot-hub/reference-content/routes/). + Find out more about IoT Hub Routes in the [Routes reference page](/iot-hub/reference-content/routes/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed `mosquitto-clients` (mqtt client) and `jq` (JSON parsing tool) on your computer -- Installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) and [read the accompanying IoT document](/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli/) +- Installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2) and [read the accompanying IoT document](/iot-hub/api-cli/getting-started-with-iot-hub-cli/) - Installed and configured [`s3cmd`](/tutorials/s3cmd/) for Scaleway ## Amazon S3 Routes @@ -31,7 +31,7 @@ Routes are integrations with the Scaleway ecosystem: they can forward MQTT messa The Amazon S3 route allows you to put the payload of MQTT messages directly into Scaleway's Object Storage. - This section is a continuation of the [Iot Hub CLI quickstart](/managed-services/iot-hub/api-cli/getting-started-with-iot-hub-cli/). Make sure to follow the quickstart before beginning. + This section is a continuation of the [Iot Hub CLI quickstart](/iot-hub/api-cli/getting-started-with-iot-hub-cli/). Make sure to follow the quickstart before beginning. 1. Run the following commands in a terminal on your computer: @@ -174,7 +174,7 @@ This tutorial covers the **PostgreSQL** database system. You can use a [Scaleway ``` - More examples including MySQL and more advanced features are available on the [Database Routes tips & tricks](/managed-services/iot-hub/api-cli/cli-db-tips-tricks/) page. + More examples including MySQL and more advanced features are available on the [Database Routes tips & tricks](/iot-hub/api-cli/cli-db-tips-tricks/) page. ## Rest Routes diff --git a/managed-services/iot-hub/api-cli/migrating-from-api-v1beta1.mdx b/managed-services/iot-hub/api-cli/migrating-from-api-v1beta1.mdx index ac5329abbb..d7b2816595 100644 --- a/managed-services/iot-hub/api-cli/migrating-from-api-v1beta1.mdx +++ b/managed-services/iot-hub/api-cli/migrating-from-api-v1beta1.mdx @@ -14,7 +14,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization To ensure that users of the `v1beta1` API have enough time to migrate, this version will remain online until **November 30th 2021**. diff --git a/managed-services/iot-hub/concepts.mdx b/managed-services/iot-hub/concepts.mdx index 3b5b711893..114f02fa37 100644 --- a/managed-services/iot-hub/concepts.mdx +++ b/managed-services/iot-hub/concepts.mdx @@ -22,7 +22,7 @@ A client refers to any software connected to the IoT Hub. The software could be ## Device -A device is a representation of a [client](#client). Each device that connects to the hub is represented by a unique ID. The concept of devices allows the hub to authenticate clients and modify its behavior towards each one appropriately. This includes the way the client connects to the hub, the way messages are filtered and the way metrics are collected. See [Understanding Devices](/managed-services/iot-hub/reference-content/devices/) for more information. +A device is a representation of a [client](#client). Each device that connects to the hub is represented by a unique ID. The concept of devices allows the hub to authenticate clients and modify its behavior towards each one appropriately. This includes the way the client connects to the hub, the way messages are filtered and the way metrics are collected. See [Understanding Devices](/iot-hub/reference-content/devices/) for more information. ## Device authentication @@ -62,7 +62,7 @@ Messages are the base data transmission unit for IoT Hub. A message contains a p ## Message Broker -IoT Hub is a message broker. It dispatches messages from publishers to subscribers (connected clients). With IoT Hub, subscribers receive a copy of published messages they are subscribed to. See [Understanding Hubs](/managed-services/iot-hub/reference-content/hubs/). +IoT Hub is a message broker. It dispatches messages from publishers to subscribers (connected clients). With IoT Hub, subscribers receive a copy of published messages they are subscribed to. See [Understanding Hubs](/iot-hub/reference-content/hubs/). ## Message Filter @@ -78,7 +78,7 @@ Mutual TLS is a method of mutual authentication. It indicates that both the TLS ## Network -Networks are the front doors to a Hub. Each Network supports a different protocol to exchange messages with the hub. See [Understanding Networks](/managed-services/iot-hub/reference-content/networks/) for more information. +Networks are the front doors to a Hub. Each Network supports a different protocol to exchange messages with the hub. See [Understanding Networks](/iot-hub/reference-content/networks/) for more information. ## Publish/Subscribe @@ -96,7 +96,7 @@ Increasing the QoS level decreases message throughput because of the additional ## Routes -IoT Routes forward messages to non publish/subscribe destinations such as databases, REST APIs, Serverless functions and Object Storage buckets. See [Understanding Routes](/managed-services/iot-hub/reference-content/routes/) for further information. +IoT Routes forward messages to non publish/subscribe destinations such as databases, REST APIs, Serverless functions and Object Storage buckets. See [Understanding Routes](/iot-hub/reference-content/routes/) for further information. ## TLS diff --git a/managed-services/iot-hub/how-to/add-device.mdx b/managed-services/iot-hub/how-to/add-device.mdx index fc6fcc3eb5..0e04637048 100644 --- a/managed-services/iot-hub/how-to/add-device.mdx +++ b/managed-services/iot-hub/how-to/add-device.mdx @@ -15,13 +15,13 @@ categories: A device is a representation of a device or program that is connected to the cloud. Through a hub, it exchanges messages with other devices and cloud services. -Devices use the [MQTT](http://mqtt.org/) protocol to send and receive messages. MQTT over WebSocket is also supported through a dedicated [network](/managed-services/iot-hub/how-to/connect-default-mqtt-network/). +Devices use the [MQTT](http://mqtt.org/) protocol to send and receive messages. MQTT over WebSocket is also supported through a dedicated [network](/iot-hub/how-to/connect-default-mqtt-network/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub on which you want to add a device. The hub's overview page displays. @@ -39,6 +39,6 @@ Devices use the [MQTT](http://mqtt.org/) protocol to send and receive messages. 8. Click **Close** to leave the wizard or **Add new device** to add another device. - Once the device is added, you may continue to configure [IoT Hub Routes](/managed-services/iot-hub/how-to/create-route/) to export your data to other Scaleway services. + Once the device is added, you may continue to configure [IoT Hub Routes](/iot-hub/how-to/create-route/) to export your data to other Scaleway services. diff --git a/managed-services/iot-hub/how-to/change-plan.mdx b/managed-services/iot-hub/how-to/change-plan.mdx index 3355ebfe3e..fddb21b5ad 100644 --- a/managed-services/iot-hub/how-to/change-plan.mdx +++ b/managed-services/iot-hub/how-to/change-plan.mdx @@ -18,11 +18,11 @@ If your project grows, you may need to upgrade your IoT Hub to a more powerful v - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) - To change your hub product plan, you must first [disable](/managed-services/iot-hub/how-to/enable-disable-hub/) your hub. + To change your hub product plan, you must first [disable](/iot-hub/how-to/enable-disable-hub/) your hub. 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. diff --git a/managed-services/iot-hub/how-to/connect-default-mqtt-network.mdx b/managed-services/iot-hub/how-to/connect-default-mqtt-network.mdx index b99a0f4f42..b53431d5fc 100644 --- a/managed-services/iot-hub/how-to/connect-default-mqtt-network.mdx +++ b/managed-services/iot-hub/how-to/connect-default-mqtt-network.mdx @@ -18,10 +18,10 @@ The default network, which is automatically created with a hub, is a **MQTT netw - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) -1. [Add a Hub device](/managed-services/iot-hub/how-to/add-device/) if you haven't already done so. +1. [Add a Hub device](/iot-hub/how-to/add-device/) if you haven't already done so. To keep this tutorial simple, choose to `Allow Insercure` connections. Insecure connections allow connections to the hub without encryption layer. 2. Configure the physical device (or client) to connect through the network, using the following parameters: diff --git a/managed-services/iot-hub/how-to/connect-default-websocket-network.mdx b/managed-services/iot-hub/how-to/connect-default-websocket-network.mdx index b448d11993..626083ac4b 100644 --- a/managed-services/iot-hub/how-to/connect-default-websocket-network.mdx +++ b/managed-services/iot-hub/how-to/connect-default-websocket-network.mdx @@ -18,10 +18,10 @@ Each Hub automatically creates a default WebSocket network, and, like the defaul - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) -1. [Add a Hub device](/managed-services/iot-hub/how-to/add-device/) if you haven't already done so. +1. [Add a Hub device](/iot-hub/how-to/add-device/) if you haven't already done so. As the WebSocket network does not implement Mutual TLS authentication, choose to `Allow Insecure` connections. 2. Configure the physical device (or client) to connect through the network, using the following parameters: diff --git a/managed-services/iot-hub/how-to/create-hub.mdx b/managed-services/iot-hub/how-to/create-hub.mdx index 6be4d9ba18..7705169ebe 100644 --- a/managed-services/iot-hub/how-to/create-hub.mdx +++ b/managed-services/iot-hub/how-to/create-hub.mdx @@ -20,7 +20,7 @@ Under the hood, a Hub acts as an MQTT broker, meaning devices use it to publish - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **IoT Hub** in the **Managed Services** section of the side menu. If you do not have a hub already created, the product presentation is displayed. 2. Click **Create hub**. The hub creation wizard displays. @@ -32,7 +32,7 @@ Under the hood, a Hub acts as an MQTT broker, meaning devices use it to publish * **High Availability (HA) Plan:** Not only are resources dedicated to the hub, but they are also replicated so that the broker is highly available. This setting is ideal for workloads that require greater robustness for their hub. 5. Click **Create** or **Create and add device**. - If you want to add a first device to the hub, click **Create hub and add device** and add your device using our [documentation on how to add a device](/managed-services/iot-hub/how-to/add-device/). + If you want to add a first device to the hub, click **Create hub and add device** and add your device using our [documentation on how to add a device](/iot-hub/how-to/add-device/). diff --git a/managed-services/iot-hub/how-to/create-route.mdx b/managed-services/iot-hub/how-to/create-route.mdx index fc6e1bdd04..f01befa016 100644 --- a/managed-services/iot-hub/how-to/create-route.mdx +++ b/managed-services/iot-hub/how-to/create-route.mdx @@ -24,8 +24,8 @@ Currently, the following routes are available: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub you want to configure. The hub's overview page displays. diff --git a/managed-services/iot-hub/how-to/delete-device.mdx b/managed-services/iot-hub/how-to/delete-device.mdx index 01b75dfd85..10d9019bbd 100644 --- a/managed-services/iot-hub/how-to/delete-device.mdx +++ b/managed-services/iot-hub/how-to/delete-device.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) and [added a device](/managed-services/iot-hub/how-to/add-device/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) and [added a device](/iot-hub/how-to/add-device/) to it 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub that contains the device to delete. The hub's overview page displays. diff --git a/managed-services/iot-hub/how-to/delete-hub.mdx b/managed-services/iot-hub/how-to/delete-hub.mdx index f360ce2d7a..0bbc71a4a9 100644 --- a/managed-services/iot-hub/how-to/delete-hub.mdx +++ b/managed-services/iot-hub/how-to/delete-hub.mdx @@ -18,8 +18,8 @@ If you do not need your IoT Hub anymore, you can remove it from your account via - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub you want to delete. The hub's overview page displays. diff --git a/managed-services/iot-hub/how-to/delete-route.mdx b/managed-services/iot-hub/how-to/delete-route.mdx index c8bd4bbe33..f812cbb036 100644 --- a/managed-services/iot-hub/how-to/delete-route.mdx +++ b/managed-services/iot-hub/how-to/delete-route.mdx @@ -24,9 +24,9 @@ Currently, the following routes are available: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) -- Created at least one [IoT Hub route](/managed-services/iot-hub/how-to/create-route/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) +- Created at least one [IoT Hub route](/iot-hub/how-to/create-route/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub with the route you want to delete. The hub's overview page displays. diff --git a/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx b/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx index 57a8a3160c..38e27c3ad4 100644 --- a/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx +++ b/managed-services/iot-hub/how-to/enable-auto-provisioning.mdx @@ -28,14 +28,14 @@ Created devices have the following properties: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) -- Created a [custom certificate authority](/managed-services/iot-hub/how-to/provide-own-certificate-authority/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) +- Created a [custom certificate authority](/iot-hub/how-to/provide-own-certificate-authority/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. A list of your IoT Hubs displays. 2. Click on the hub on which to enable the device auto-provisioning. 3. Scroll down to the **Device Auto-Provisioning** panel and slide the toggle to **Enabled**. - When auto-provisioning is enabled, IoT Hub will try to add new devices upon first connection. A [Hub Event](/managed-services/iot-hub/concepts/#hub-events) will be raised upon success or failure. + When auto-provisioning is enabled, IoT Hub will try to add new devices upon first connection. A [Hub Event](/iot-hub/concepts/#hub-events) will be raised upon success or failure. diff --git a/managed-services/iot-hub/how-to/enable-disable-hub.mdx b/managed-services/iot-hub/how-to/enable-disable-hub.mdx index 62ba7df1ab..e0d802a97b 100644 --- a/managed-services/iot-hub/how-to/enable-disable-hub.mdx +++ b/managed-services/iot-hub/how-to/enable-disable-hub.mdx @@ -13,13 +13,13 @@ categories: - managed-services --- -You can enable or disable your IoT Hub from the Scaleway console. This can be useful if you want to do maintenance actions on your hub, or if you want to change the [product plan](/managed-services/iot-hub/how-to/change-plan/) of your hub. +You can enable or disable your IoT Hub from the Scaleway console. This can be useful if you want to do maintenance actions on your hub, or if you want to change the [product plan](/iot-hub/how-to/change-plan/) of your hub. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. 2. Click the name of the IoT Hub you want to disable or enable. The hub's overview page displays. diff --git a/managed-services/iot-hub/how-to/provide-own-certificate-authority.mdx b/managed-services/iot-hub/how-to/provide-own-certificate-authority.mdx index d114ac235c..0b3b04b849 100644 --- a/managed-services/iot-hub/how-to/provide-own-certificate-authority.mdx +++ b/managed-services/iot-hub/how-to/provide-own-certificate-authority.mdx @@ -34,11 +34,11 @@ Switching to a custom Certificate Authority has several benefits: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) - To change your hub Certificate Authority, you must [disable your hub](/managed-services/iot-hub/how-to/enable-disable-hub/). + To change your hub Certificate Authority, you must [disable your hub](/iot-hub/how-to/enable-disable-hub/). 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. diff --git a/managed-services/iot-hub/how-to/provide-own-device-certificate.mdx b/managed-services/iot-hub/how-to/provide-own-device-certificate.mdx index 1910892ca4..dc6d088305 100644 --- a/managed-services/iot-hub/how-to/provide-own-device-certificate.mdx +++ b/managed-services/iot-hub/how-to/provide-own-device-certificate.mdx @@ -23,8 +23,8 @@ At Scaleway, a certificate is automatically created and attached to a device upo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) and [added a device](/managed-services/iot-hub/how-to/add-device/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) and [added a device](/iot-hub/how-to/add-device/) to it For a custom device certificate to be valid, it must be unique across all your Hubs. diff --git a/managed-services/iot-hub/how-to/renew-device-certificate.mdx b/managed-services/iot-hub/how-to/renew-device-certificate.mdx index a988f570a1..8d328c3bc7 100644 --- a/managed-services/iot-hub/how-to/renew-device-certificate.mdx +++ b/managed-services/iot-hub/how-to/renew-device-certificate.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) and [added a device](/managed-services/iot-hub/how-to/add-device/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) and [added a device](/iot-hub/how-to/add-device/) to it The renewal feature becomes unavailable once you have provided your own hub Certificate Authority or previously replaced the device certificate since, in this case, the certificate authority is no longer managed by Scaleway. diff --git a/managed-services/iot-hub/how-to/setup-use-rest-network.mdx b/managed-services/iot-hub/how-to/setup-use-rest-network.mdx index 9e9db1fa4b..7db1b91cc4 100644 --- a/managed-services/iot-hub/how-to/setup-use-rest-network.mdx +++ b/managed-services/iot-hub/how-to/setup-use-rest-network.mdx @@ -18,8 +18,8 @@ IoT Hub allows you to configure and use [REST](https://en.wikipedia.org/wiki/Rep - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) The REST network only allows publishing messages. diff --git a/managed-services/iot-hub/how-to/setup-use-sigfox-network.mdx b/managed-services/iot-hub/how-to/setup-use-sigfox-network.mdx index 8cde3b42fc..f237f9cb0a 100644 --- a/managed-services/iot-hub/how-to/setup-use-sigfox-network.mdx +++ b/managed-services/iot-hub/how-to/setup-use-sigfox-network.mdx @@ -18,8 +18,8 @@ The [Sigfox](https://www.sigfox.com/en) network type allows devices communicatin - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) - A [Sigfox account](https://build.sigfox.com/) diff --git a/managed-services/iot-hub/how-to/simulate-event.mdx b/managed-services/iot-hub/how-to/simulate-event.mdx index f026694441..11c9e46af0 100644 --- a/managed-services/iot-hub/how-to/simulate-event.mdx +++ b/managed-services/iot-hub/how-to/simulate-event.mdx @@ -15,13 +15,13 @@ categories: To demonstrate the use of hub Events, the following tutorial allows you to generate an error, and shows you how to receive this error. -For more information about hub Events, you can check out the [IoT Hub Events documentation](/managed-services/iot-hub/reference-content/hubs/#events). +For more information about hub Events, you can check out the [IoT Hub Events documentation](/iot-hub/reference-content/hubs/#events). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) - Installed [`mosquitto`](https://mosquitto.org/download/) on your local computer 1. Click **IoT Hub** in the **Managed Services** section of the side menu. The list of your IoT Hubs displays. diff --git a/managed-services/iot-hub/how-to/trigger-functions-from-messages.mdx b/managed-services/iot-hub/how-to/trigger-functions-from-messages.mdx index 8658befa38..4ed0bfecd1 100644 --- a/managed-services/iot-hub/how-to/trigger-functions-from-messages.mdx +++ b/managed-services/iot-hub/how-to/trigger-functions-from-messages.mdx @@ -20,9 +20,9 @@ IoT Hub allows messages to be exchanged between devices and business-specific so - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Serverless function](/serverless/functions/how-to/create-a-function/) -- Created an [IoT Hub](/managed-services/iot-hub/how-to/create-hub/) and [added a device](/managed-services/iot-hub/how-to/add-device/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Serverless function](/serverless-functions/how-to/create-a-function/) +- Created an [IoT Hub](/iot-hub/how-to/create-hub/) and [added a device](/iot-hub/how-to/add-device/) to it ## How to set up a route to a function @@ -72,7 +72,7 @@ The content of the message will be the body of the reply. If you require authentication to protect your Serverless Function, here is how to do it: 1. Click the settings tab of your function settings tab and tick the `Private` option. -2. [Generate a token](/serverless/functions/how-to/create-auth-token-from-console/) for your function. +2. [Generate a token](/serverless-functions/how-to/create-auth-token-from-console/) for your function. 3. Re-create your IoT Hub Route with the following HTTP header: `SCW_FUNCTIONS_TOKEN: `. Your function is now private and still accessible from IoT Hub. diff --git a/managed-services/iot-hub/how-to/understand-event-messages.mdx b/managed-services/iot-hub/how-to/understand-event-messages.mdx index a97ec45b6a..b40baeebc8 100644 --- a/managed-services/iot-hub/how-to/understand-event-messages.mdx +++ b/managed-services/iot-hub/how-to/understand-event-messages.mdx @@ -17,7 +17,7 @@ This section shows you the types of message that can be received in IoT Hub Even -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Device messages @@ -56,7 +56,7 @@ This section shows you the types of message that can be received in IoT Hub Even - `service level: publishing retained messages is forbidden on a shared hub`: It is not possible to publish retained messages when using a shared hub. - `service level: publishing QoS 2 messages is forbidden on a shared hub`: It is not possible to publish QoS 2 messages when using a shared hub. - `service level: subscribing with QoS 1-2 is forbidden on a shared hub`: It is not possible to subscribe using QoS 1-2 when using a shared hub. -- `service level: message payload is too large`: See [limits](/managed-services/iot-hub/reference-content/hubs/#limits-and-quotas) for the maximum allowed messages payload size. +- `service level: message payload is too large`: See [limits](/iot-hub/reference-content/hubs/#limits-and-quotas) for the maximum allowed messages payload size. ## Route messages diff --git a/managed-services/iot-hub/how-to/use-mqtt-webclient.mdx b/managed-services/iot-hub/how-to/use-mqtt-webclient.mdx index eb891a37c4..fd5b1fc22a 100644 --- a/managed-services/iot-hub/how-to/use-mqtt-webclient.mdx +++ b/managed-services/iot-hub/how-to/use-mqtt-webclient.mdx @@ -21,9 +21,9 @@ You can use it to connect to your hub as a device and publish and subscribe to t - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) -- [Added a device](/managed-services/iot-hub/how-to/add-device/) that allows insecure connections to your hub +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) +- [Added a device](/iot-hub/how-to/add-device/) that allows insecure connections to your hub 1. Open the WebClient by either: - Clicking **MQTT Webclient** in the top right corner of the Device overview tab. diff --git a/managed-services/iot-hub/how-to/view-metrics.mdx b/managed-services/iot-hub/how-to/view-metrics.mdx index 72189bbcee..7954789767 100644 --- a/managed-services/iot-hub/how-to/view-metrics.mdx +++ b/managed-services/iot-hub/how-to/view-metrics.mdx @@ -18,8 +18,8 @@ Metrics reports the usage of your IoT Hub and devices. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created an IoT Hub](/managed-services/iot-hub/how-to/create-hub/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created an IoT Hub](/iot-hub/how-to/create-hub/) ## How to view hub metrics diff --git a/managed-services/iot-hub/index.mdx b/managed-services/iot-hub/index.mdx index c9209bf3d5..f247081be5 100644 --- a/managed-services/iot-hub/index.mdx +++ b/managed-services/iot-hub/index.mdx @@ -8,7 +8,7 @@ meta: productName="IoT Hub" productLogo="iotHub" description="IoT Hub allows to connect and manage thousands of IoT devices effortlessly using the most popular protocols (MQTT, Sigfox, LoRaWAN, REST, and Websockets)." - url="/managed-services/iot-hub/concepts/" + url="/iot-hub/concepts/" label="IoT Hub Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, manage and delete a IoT Hub in a few steps." label="View Quickstart" - url="/managed-services/iot-hub/quickstart/" + url="/iot-hub/quickstart/" /> diff --git a/managed-services/iot-hub/quickstart.mdx b/managed-services/iot-hub/quickstart.mdx index 0ed5ad2386..b7b54f3e6a 100644 --- a/managed-services/iot-hub/quickstart.mdx +++ b/managed-services/iot-hub/quickstart.mdx @@ -13,14 +13,14 @@ categories: - managed-services --- -[Scaleway IoT Hub](/managed-services/iot-hub/quickstart/) is a resilient and multi-protocol message broker with export capabilities. Devices can connect to the hub to exchange messages, by which they get access to cloud services. Hub Routes also allow devices to push messages to other, non MQTT, services. +[Scaleway IoT Hub](/iot-hub/quickstart/) is a resilient and multi-protocol message broker with export capabilities. Devices can connect to the hub to exchange messages, by which they get access to cloud services. Hub Routes also allow devices to push messages to other, non MQTT, services. In this Quickstart, we show you how to create your first IoT Hub to connect objects, Scaleway services and applications. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create an IoT Hub @@ -33,12 +33,12 @@ In this Quickstart, we show you how to create your first IoT Hub to connect obje - **High Availability (HA) Plan:** Not only are resources dedicated to the hub, they are also replicated so that the broker is highly available. This setting is ideal for workloads that require greater robustness for their hub. 5. Click **Create hub** or **Create hub and add device**. - If you want to directly add a first device to the hub, click **Create hub and add device** and continue with the documentation [IoT Hub - Devices](/managed-services/iot-hub/how-to/add-device/) + If you want to directly add a first device to the hub, click **Create hub and add device** and continue with the documentation [IoT Hub - Devices](/iot-hub/how-to/add-device/) ## How to add a device -A [device](/managed-services/iot-hub/concepts/#device) is a “client” of the Hub. It can be a connected object or any other application. You have to add a “device” for each “client” to connect. Each device will be associated with a unique identifier to be used as “client ID” and a certificate/key pair for a maximum security level. +A [device](/iot-hub/concepts/#device) is a “client” of the Hub. It can be a connected object or any other application. You have to add a “device” for each “client” to connect. Each device will be associated with a unique identifier to be used as “client ID” and a certificate/key pair for a maximum security level. In this Quickstart, we add 2 devices: publisher and subscriber. Here, we accept low security connections for the devices. However, in a production environment, it is recommended to always use high-security settings. diff --git a/managed-services/iot-hub/reference-content/devices.mdx b/managed-services/iot-hub/reference-content/devices.mdx index 537729d272..02ec3ecfdc 100644 --- a/managed-services/iot-hub/reference-content/devices.mdx +++ b/managed-services/iot-hub/reference-content/devices.mdx @@ -27,7 +27,7 @@ Devices: - An MQTT Webclient is available in the console to publish and receive messages. Follow the procedure on this [tutorial](/managed-services/iot-hub/how-to/use-mqtt-webclient/). + An MQTT Webclient is available in the console to publish and receive messages. Follow the procedure on this [tutorial](/iot-hub/how-to/use-mqtt-webclient/). ## Connection security @@ -94,7 +94,7 @@ Message filters can be set up in the **Device messages** tab of the console. - Filters can also be applied to [last will messages](/managed-services/iot-hub/concepts/#last-will-message). + Filters can also be applied to [last will messages](/iot-hub/concepts/#last-will-message). ### Message filters template @@ -122,7 +122,7 @@ Will build the following filter when the Hub is named `MyHub` and the Device `My ``` - Issues when parsing the template will be reported through [Hub events](/managed-services/iot-hub/reference-content/hubs/#events) as warnings. In this case, the filter can be dropped from the list. + Issues when parsing the template will be reported through [Hub events](/iot-hub/reference-content/hubs/#events) as warnings. In this case, the filter can be dropped from the list. ## Multiple connections diff --git a/managed-services/iot-hub/reference-content/hubs.mdx b/managed-services/iot-hub/reference-content/hubs.mdx index b542f19392..83020092c5 100644 --- a/managed-services/iot-hub/reference-content/hubs.mdx +++ b/managed-services/iot-hub/reference-content/hubs.mdx @@ -38,20 +38,20 @@ There are three IoT Hub plans available: ## Certificate Authority -When you create a Hub, it comes with a Scaleway-generated [Certificate Authority](/managed-services/iot-hub/concepts/#hub-certificate-authority). The Hub Certificate Authority is used to authenticate connecting devices through mutual TLS authentication. +When you create a Hub, it comes with a Scaleway-generated [Certificate Authority](/iot-hub/concepts/#hub-certificate-authority). The Hub Certificate Authority is used to authenticate connecting devices through mutual TLS authentication. The Hub Certificate Authority is used to authenticate Devices. This is not to be confused with MQTT Network certificate authority which allows the Devices to authenticate to the Hub. -If you wish, you can [replace the Hub's certificate authority](/managed-services/iot-hub/how-to/provide-own-device-certificate/) with your own. Your Device certificates will then have to be signed by this new authority. +If you wish, you can [replace the Hub's certificate authority](/iot-hub/how-to/provide-own-device-certificate/) with your own. Your Device certificates will then have to be signed by this new authority. Mutual TLS authentication is available only on the Hub's MQTT Network. - You can refer to the Devices [reference documentation](/managed-services/iot-hub/reference-content/devices/) to learn more about Device authentication. + You can refer to the Devices [reference documentation](/iot-hub/reference-content/devices/) to learn more about Device authentication. ## Auto-Provisioning @@ -82,7 +82,7 @@ Event messages will be published using topics under the `prefix/source/identifie - `severity` tells how important the event is (info, warning, error, ...) - For more information about events, check out [how to understand event messages](/managed-services/iot-hub/how-to/understand-event-messages/). + For more information about events, check out [how to understand event messages](/iot-hub/how-to/understand-event-messages/). ## Metrics diff --git a/managed-services/iot-hub/reference-content/networks.mdx b/managed-services/iot-hub/reference-content/networks.mdx index 9d79ec6eeb..c2f6c244e0 100644 --- a/managed-services/iot-hub/reference-content/networks.mdx +++ b/managed-services/iot-hub/reference-content/networks.mdx @@ -50,7 +50,7 @@ You can connect Devices on this Network using the following methods: When using TLS to authenticate your Devices, you need the Hub server-side certificate authority. The CA and the endpoint information are available in the **Network** tab of the console. - For more information about how to use the default MQTT Network, see [How to connect to the default MQTT Network.](/managed-services/iot-hub/how-to/connect-default-mqtt-network/). + For more information about how to use the default MQTT Network, see [How to connect to the default MQTT Network.](/iot-hub/how-to/connect-default-mqtt-network/). ## Default WebSocket Network @@ -71,7 +71,7 @@ You can connect Devices on this Network using the following methods: - For more information about the default WebSocket Network, check out [how to connect to the default WebSocket Network.](/managed-services/iot-hub/how-to/connect-default-websocket-network/). + For more information about the default WebSocket Network, check out [how to connect to the default WebSocket Network.](/iot-hub/how-to/connect-default-websocket-network/). ## REST Networks @@ -81,7 +81,7 @@ This is a **Device-unaware** network that allows you to publish messages on a Hu Creating a REST Network will provide you with a secret token to use when calling this API. - For more information about how to use REST Networks, check out [how to set up and use REST Networks](/managed-services/iot-hub/how-to/setup-use-rest-network/). + For more information about how to use REST Networks, check out [how to set up and use REST Networks](/iot-hub/how-to/setup-use-rest-network/). ## Sigfox Networks @@ -91,7 +91,7 @@ This is a **Device-unaware** network that allows you to publish messages on a Hu Creating a Sigfox network will provide you with a secret token to use to set up the required callbacks in your Sigfox backend. - For more information about how to use Sigfox networks, check out [how to set up and use Sigfox networks](/managed-services/iot-hub/how-to/setup-use-sigfox-network/). + For more information about how to use Sigfox networks, check out [how to set up and use Sigfox networks](/iot-hub/how-to/setup-use-sigfox-network/). ## Limits and Quotas diff --git a/managed-services/iot-hub/reference-content/overview.mdx b/managed-services/iot-hub/reference-content/overview.mdx index 7088fb1e0d..50073fb8f9 100644 --- a/managed-services/iot-hub/reference-content/overview.mdx +++ b/managed-services/iot-hub/reference-content/overview.mdx @@ -26,13 +26,13 @@ It allows true hotplug, many-to-many, and asynchronous communications. Networks are the front door to your IoT Hub. They allow Devices and applications to exchange messages with the Hub through multiple protocols: MQTT, WebSockets, LoRaWAN, SigFox, REST, among others. -Each Network has its protocol-related specificities, which you can find in the [Networks reference documentation](/managed-services/iot-hub/reference-content/networks/). +Each Network has its protocol-related specificities, which you can find in the [Networks reference documentation](/iot-hub/reference-content/networks/). ## Security Device communications can be secured with Mutual TLS authentication and encryption, server-authentication TLS along with per-device message filtering. It is also possible to use plain communication for development or testing setups, we do not recommend this in production. -For more information about the different authentication protocols, refer to the [Devices reference documentation](/managed-services/iot-hub/reference-content/devices/). +For more information about the different authentication protocols, refer to the [Devices reference documentation](/iot-hub/reference-content/devices/). ## Message dispatching @@ -44,7 +44,7 @@ The publish/subscribe pattern is simple: when a client **publishes** a message t Topics can be any slash-separated string, just like a file path. There is no need to configure them before usage. -There are also multiple additional features such as topics wildcards, message retention and QoS levels. Head to our [Hubs reference documentation](/managed-services/iot-hub/reference-content/hubs/) for more information. +There are also multiple additional features such as topics wildcards, message retention and QoS levels. Head to our [Hubs reference documentation](/iot-hub/reference-content/hubs/) for more information. ## Routes @@ -52,6 +52,6 @@ Routes are the glue between your IoT Hub and other non-publish/subscribe service They subscribe to the requested topics and forward messages to services such as databases, Object Storage, REST APIs, Serverless Functions, AI Inference models and much more. -Services can reply with a message to publish back on your IoT Hub. For more information, check our [Routes reference documentation](/managed-services/iot-hub/reference-content/routes/). +Services can reply with a message to publish back on your IoT Hub. For more information, check our [Routes reference documentation](/iot-hub/reference-content/routes/). diff --git a/managed-services/iot-hub/reference-content/routes.mdx b/managed-services/iot-hub/reference-content/routes.mdx index 4ce63ead6c..de80e41815 100644 --- a/managed-services/iot-hub/reference-content/routes.mdx +++ b/managed-services/iot-hub/reference-content/routes.mdx @@ -22,7 +22,7 @@ IoT Routes interconnect your Hub with services that are not publish/subscribe co Routes subscribe to topics in your Hub and forward the messages' payloads to other services, automating the process. -You can [create](/managed-services/iot-hub/how-to/create-route/) and [delete](/managed-services/iot-hub/how-to/delete-route/) Routes in the **Routes** tab of your Hub in the console. All Routes require a name and a topic to subscribe to. Other settings are specific to the kind of Route you choose. +You can [create](/iot-hub/how-to/create-route/) and [delete](/iot-hub/how-to/delete-route/) Routes in the **Routes** tab of your Hub in the console. All Routes require a name and a topic to subscribe to. Other settings are specific to the kind of Route you choose. You can use wildcards as Routes topics. @@ -57,7 +57,7 @@ You can choose the connection settings and write an SQL query. This query will b ## Object Storage Route -Object Storage Routes forward your messages to a [Scaleway Object Storage](/storage/object/quickstart/) bucket. +Object Storage Routes forward your messages to a [Scaleway Object Storage](/object-storage/quickstart/) bucket. You can choose the bucket you want to write to, a path prefix, and one of the two following strategies: diff --git a/managed-services/transactional-email/api-cli/send-emails-with-api.mdx b/managed-services/transactional-email/api-cli/send-emails-with-api.mdx index 7ea552c81e..2518df51b3 100644 --- a/managed-services/transactional-email/api-cli/send-emails-with-api.mdx +++ b/managed-services/transactional-email/api-cli/send-emails-with-api.mdx @@ -18,11 +18,11 @@ This page shows you how to send a simple transactional email in `JSON` format to - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Configured your API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your API key](/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Installed curl](https://curl.se/download.html) -- [Configured](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) your domain name with Transactional Email -- [Added SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain +- [Configured](/transactional-email/how-to/configure-domain-with-transactional-email/) your domain name with Transactional Email +- [Added SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain 1. Open a terminal and paste the following code to configure your environment variables. Make sure that you add your own values. diff --git a/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx b/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx index de30174b71..35afdda2aa 100644 --- a/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx +++ b/managed-services/transactional-email/api-cli/use-webhooks-with-sns-topics.mdx @@ -15,22 +15,22 @@ categories: A webhook is an automated message sent in real-time from one system to another when a specific event happens, the message is typically conveyed using HTTP requests that are sent to an endpoint of your choice. -You can set up webhooks for Scaleway Transactional Email and subscribe them to [Topics and Events topics](/serverless/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints. +You can set up webhooks for Scaleway Transactional Email and subscribe them to [Topics and Events topics](/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain(s) with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) -- Added [SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/managed-services/transactional-email/how-to/add-dmarc-record/) records to your domain(s) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) +- Added [SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/transactional-email/how-to/add-dmarc-record/) records to your domain(s) - Have the necessary quotas to use Transactional Email Webhooks during beta. You can request quotas from the [Scaleway betas page](https://www.scaleway.com/fr/betas/#email-webhooks). -1. [Create a Topics and Events topic](/serverless/messaging/how-to/create-manage-topics/#how-to-create-a-topic) with Scaleway Topics and Events. +1. [Create a Topics and Events topic](/messaging/how-to/create-manage-topics/#how-to-create-a-topic) with Scaleway Topics and Events. 2. Copy the ARN identifier of the topic in the **Topics** tab as you will need it later. -3. [Create a subscription](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-create-a-subscription). Make sure you enter the endpoint to which you would like to send your Webhooks. +3. [Create a subscription](/messaging/how-to/create-manage-subscriptions/#how-to-create-a-subscription). Make sure you enter the endpoint to which you would like to send your Webhooks. If you do not yet have a webhook URL, you can use the tool [webhook.site](https://webhook.site/) to generate one and receive your events on the interface.

@@ -38,7 +38,7 @@ You can set up webhooks for Scaleway Transactional Email and subscribe them to [ -4. [Confirm your subscription](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). +4. [Confirm your subscription](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). If you are using [webhook.site](https://webhook.site/), you can refer to their interface to check the incoming requests and confirm the subscription. @@ -62,7 +62,7 @@ You can set up webhooks for Scaleway Transactional Email and subscribe them to [ ``` - In this example, we use `email_delivered` and `email_dropped` as the event types. Refer to the Transactional Email [concepts page](/managed-services/transactional-email/concepts/#webhook-event-type) to get an extensive list of Transactional Email events. + In this example, we use `email_delivered` and `email_dropped` as the event types. Refer to the Transactional Email [concepts page](/transactional-email/concepts/#webhook-event-type) to get an extensive list of Transactional Email events. Once your Webhook is created, you can try to send an email with your Transactional Email domain. diff --git a/managed-services/transactional-email/api-cli/webhook-events-payloads.mdx b/managed-services/transactional-email/api-cli/webhook-events-payloads.mdx index fb22e00beb..14aaea4199 100644 --- a/managed-services/transactional-email/api-cli/webhook-events-payloads.mdx +++ b/managed-services/transactional-email/api-cli/webhook-events-payloads.mdx @@ -15,7 +15,7 @@ categories: Events triggered by webhooks contain payloads that describe and detail the events. -Find below a detailed description of the fields in a [Webhoook event](/managed-services/transactional-email/how-to/create-webhooks/) payload. +Find below a detailed description of the fields in a [Webhoook event](/transactional-email/how-to/create-webhooks/) payload. | Tag | Description | @@ -42,7 +42,7 @@ Find below a detailed description of the fields in a [Webhoook event](/managed-s ## Examples of payload by event type -Webhooks may trigger different [types of events](/managed-services/transactional-email/concepts/#webhook-event-type). These types have varying payload fields. +Webhooks may trigger different [types of events](/transactional-email/concepts/#webhook-event-type). These types have varying payload fields. ## email_queued ```json diff --git a/managed-services/transactional-email/how-to/add-dmarc-record.mdx b/managed-services/transactional-email/how-to/add-dmarc-record.mdx index f3ea98d4af..87b074b87d 100644 --- a/managed-services/transactional-email/how-to/add-dmarc-record.mdx +++ b/managed-services/transactional-email/how-to/add-dmarc-record.mdx @@ -13,9 +13,9 @@ categories: - managed-services --- -This page shows you how to configure a basic [DMARC record](/managed-services/transactional-email/concepts/#dmarc-record) on your domain. +This page shows you how to configure a basic [DMARC record](/transactional-email/concepts/#dmarc-record) on your domain. If you have registered a domain at Scaleway Domains and DNS, you can still use this documentation, as the process is similar. -For more information about DMARC configuration and examples of DMARC records you can configure, refer to the [dedicated documentation](/managed-services/transactional-email/reference-content/dmarc-configuration/). +For more information about DMARC configuration and examples of DMARC records you can configure, refer to the [dedicated documentation](/transactional-email/reference-content/dmarc-configuration/). ## Before you start @@ -23,14 +23,14 @@ To complete the actions presented below, you must have: - A Scaleway account logged into the [console](https://console.scaleway.com/) - A domain name -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/). -- [Owner](/identity-and-access-management/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/identity-and-access-management/iam/concepts/#permission) +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). +- [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission) ## How to configure a DMARC record 1. Add a `TXT` record type in the same zone as your Transactional Email's domain, on your DNS zone. 2. Enter `_dmarc` in the **Name** field, followed by the domain name. For example, if your domain is called `my-domain.com`, you should have `_dmarc.my-domain.com.` in the **Name** field. -3. Enter your desired tags and their values in the **Value** section. Make sure that you add the mandatory `v` and `p` tags, and that you separate tags from each other with semi-colons. Find out about DMARC configuration in our [dedicated documentation](/managed-services/transactional-email/reference-content/dmarc-configuration/). +3. Enter your desired tags and their values in the **Value** section. Make sure that you add the mandatory `v` and `p` tags, and that you separate tags from each other with semi-colons. Find out about DMARC configuration in our [dedicated documentation](/transactional-email/reference-content/dmarc-configuration/). Your **Value** field should look similar to the following ``` v=DMARC1; p=none; rua=mailto:your@email.com diff --git a/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx b/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx index 7f1a00bd71..7d1d5c51c7 100644 --- a/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx +++ b/managed-services/transactional-email/how-to/add-mx-record-to-your-domain.mdx @@ -13,13 +13,13 @@ categories: - managed-services --- -Setting up an [MX record](/managed-services/transactional-email/concepts/#mx-record) ensures that your emails are delivered reliably. This page explains how to set up **your own MX record**, and how to set up Scaleway's blackhole MX if you do not have your own MX server. +Setting up an [MX record](/transactional-email/concepts/#mx-record) ensures that your emails are delivered reliably. This page explains how to set up **your own MX record**, and how to set up Scaleway's blackhole MX if you do not have your own MX server. - A Scaleway account logged into the [console](https://console.scaleway.com) - A domain name - - [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) - - [Added SPF and DKIM records](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to your domain + - [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) + - [Added SPF and DKIM records](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/) to your domain ## How to add your own MX record @@ -27,9 +27,9 @@ Setting up an [MX record](/managed-services/transactional-email/concepts/#mx-rec We recommend you use your own MX server if you have one. If you do not have an MX server, we recommend you use Scaleway's blackhole MX, as it allows you to avoid email rejection. However, this also means that the emails sent back to the Scaleway blackhole MX, will be lost and unrecoverable. -1. Add an [MX record](/managed-services/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. +1. Add an [MX record](/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. 2. Enter a name of your choice in the **Name** field. -3. Set `10` as a [priority](/managed-services/transactional-email/concepts/#priority) for your MX record. +3. Set `10` as a [priority](/transactional-email/concepts/#priority) for your MX record. Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. @@ -43,9 +43,9 @@ Setting up an [MX record](/managed-services/transactional-email/concepts/#mx-rec - If you have no MX server, we recommend you use Scaleway's blackhole MX to avoid getting your emails rejected. -1. Add an [MX record](/managed-services/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. +1. Add an [MX record](/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. 2. Enter a name of your choice in the **Name** field. -3. Set `10` as a [priority](/managed-services/transactional-email/concepts/#priority) for your MX record. +3. Set `10` as a [priority](/transactional-email/concepts/#priority) for your MX record. Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. diff --git a/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx b/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx index 9ddaa27c7e..99705a77a7 100644 --- a/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx +++ b/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain.mdx @@ -13,16 +13,16 @@ categories: - managed-services --- -This page shows you how to set up [SPF](/managed-services/transactional-email/concepts/#spf-record) and [DKIM](/managed-services/transactional-email/concepts/#dkim-record) records to your domain to verify it. +This page shows you how to set up [SPF](/transactional-email/concepts/#spf-record) and [DKIM](/transactional-email/concepts/#dkim-record) records to your domain to verify it. -After you have configured your domain with Transactional Email, you are prompted to verify your domain by adding SPF, DKIM and [MX records](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/). You can choose to do so right after you have validated your domain, or at a later time. +After you have configured your domain with Transactional Email, you are prompted to verify your domain by adding SPF, DKIM and [MX records](/transactional-email/how-to/add-mx-record-to-your-domain/). You can choose to do so right after you have validated your domain, or at a later time. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) 1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. Your newly-added domain displays. 2. Click your domain. You are redirected to the SPF, DKIM and MX configuration page. @@ -40,7 +40,7 @@ After you have configured your domain with Transactional Email, you are prompted 8. Paste the name you have copied in the root zone of your domain on your DNS zone. 9. Copy the value that displays in the console and paste it in the root zone of your domain on your DNS zone. -10. Add an [MX record](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/). +10. Add an [MX record](/transactional-email/how-to/add-mx-record-to-your-domain/). 11. Check the box "I have added these DNS records to my DNS zone" to confirm. 12. Click **Verify domain**. Your domain displays in the list of your domains. diff --git a/managed-services/transactional-email/how-to/autoconfigure-domain.mdx b/managed-services/transactional-email/how-to/autoconfigure-domain.mdx index de8c796839..6dcb7958ba 100644 --- a/managed-services/transactional-email/how-to/autoconfigure-domain.mdx +++ b/managed-services/transactional-email/how-to/autoconfigure-domain.mdx @@ -19,14 +19,14 @@ Automatic configuration of your DNS zone streamlines the setup of your domain fo You can enable autoconfiguration directly from the Scaleway console (see instructions below), through the [Transactional Email API](https://www.scaleway.com/en/developers/api/transactional-email/#path-domains-register-a-domain-in-a-project), or via [Terraform](https://github.com/scaleway/terraform-provider-scaleway/blob/master/docs/data-sources/tem_domain.md) using the `autoconfig` parameter (`bool`). - This documentation covers the use of DNS autoconfiguration for domains already registerd with Transactional Email. If you want to add a new domain, refer to [How to configure your sending domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/). + This documentation covers the use of DNS autoconfiguration for domains already registerd with Transactional Email. If you want to add a new domain, refer to [How to configure your sending domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A domain name registered with [Scaleway Domains and DNS](/network/domains-and-dns/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A domain name registered with [Scaleway Domains and DNS](/domains-and-dns/) ## How to enable DNS autoconfiguration diff --git a/managed-services/transactional-email/how-to/configure-bimi.mdx b/managed-services/transactional-email/how-to/configure-bimi.mdx index 045f40dce4..042b89fa79 100644 --- a/managed-services/transactional-email/how-to/configure-bimi.mdx +++ b/managed-services/transactional-email/how-to/configure-bimi.mdx @@ -20,14 +20,14 @@ Scaleway supports SPF, DKIM and DMARC with Transactional Email, which makes it p To complete the actions presented below, you must have: - A Scaleway account logged into the [console](https://console.scaleway.com/) -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/). -- A domain name that passed [SPF](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [DMARC](/managed-services/transactional-email/how-to/add-dmarc-record/) authentication checks +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). +- A domain name that passed [SPF](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [DMARC](/transactional-email/how-to/add-dmarc-record/) authentication checks - A logo of your brand saved in SVG format -- [Owner](/identity-and-access-management/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/identity-and-access-management/iam/concepts/#permission) +- [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission) ## How does BIMI work? -Before your brand's logo can be displayed, your email must first pass authentication checks. Checks are usually performed through [SPF (Sender Policy Framework)](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [DKIM (DomainKeys Identified Mail)](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [DMARC (Domain-based Message Authentication, Reporting, and Conformance)](/managed-services/transactional-email/how-to/add-dmarc-record/) checks, which are supported by Scaleway. Some email clients also require a Verified Mark Certificate (VMC) to ensure the logo's authenticity. +Before your brand's logo can be displayed, your email must first pass authentication checks. Checks are usually performed through [SPF (Sender Policy Framework)](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [DKIM (DomainKeys Identified Mail)](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [DMARC (Domain-based Message Authentication, Reporting, and Conformance)](/transactional-email/how-to/add-dmarc-record/) checks, which are supported by Scaleway. Some email clients also require a Verified Mark Certificate (VMC) to ensure the logo's authenticity. Currently, the only organizations that are capable of issuing a VMC brand certificates are [Digicert](https://www.digicert.com/blog/qualify-for-a-vmc-how-to-trademark-your-logo#offices) and [Entrust](https://www.entrust.com/fr/resources/learn/what-is-bimi). @@ -39,7 +39,7 @@ When the email passes all authentication checks and the record is considered val ## How to set up a BIMI record -In this tutorial we use [Scaleway Domains and DNS](/network/domains-and-dns/how-to/manage-dns-records/) to manage DNS records. You can, however, apply the following steps to any DNS client of your choice. Keep in mind that the field names might vary depending on the client. +In this tutorial we use [Scaleway Domains and DNS](/domains-and-dns/how-to/manage-dns-records/) to manage DNS records. You can, however, apply the following steps to any DNS client of your choice. Keep in mind that the field names might vary depending on the client. 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. 2. Click the domain you want to manage. This can be an internal or external domain. The domain's **Overview** page displays. diff --git a/managed-services/transactional-email/how-to/configure-domain-with-transactional-email.mdx b/managed-services/transactional-email/how-to/configure-domain-with-transactional-email.mdx index 1ec47ba605..0bd9790584 100644 --- a/managed-services/transactional-email/how-to/configure-domain-with-transactional-email.mdx +++ b/managed-services/transactional-email/how-to/configure-domain-with-transactional-email.mdx @@ -13,17 +13,17 @@ categories: - managed-services --- -This page shows you how to configure your sending domain to start sending [transactional emails](/managed-services/transactional-email/concepts/#transactional-email). +This page shows you how to configure your sending domain to start sending [transactional emails](/transactional-email/concepts/#transactional-email). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name ## Automatic configuration for a Scaleway domain -When you use a domain name registered with [Scaleway Domains and DNS](/network/domains-and-dns/), you can benefit from DNS autoconfiguration. We can automatically configure SPF, DKIM, DMARC, MX on your behalf so +When you use a domain name registered with [Scaleway Domains and DNS](/domains-and-dns/), you can benefit from DNS autoconfiguration. We can automatically configure SPF, DKIM, DMARC, MX on your behalf so your domain name can be validated automatically and you can focus on sending emails and observing the reputation status of your domain. 1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. The **Transactional Email** overview page displays. @@ -44,7 +44,7 @@ Validation time of domain ownership may be extended. 4. Tick the checkbox to confirm that you agree to Scaleway's antispam policy, then click **Validate domain name** to confirm. - For external domains, you need to configure your [SPF](/managed-services/transactional-email/concepts/#spf-record), [DKIM](/managed-services/transactional-email/concepts/#dkim-record) and [MX](/managed-services/transactional-email/concepts/#mx-record) records **manually** to verify your domain and to be able to send emails. + For external domains, you need to configure your [SPF](/transactional-email/concepts/#spf-record), [DKIM](/transactional-email/concepts/#dkim-record) and [MX](/transactional-email/concepts/#mx-record) records **manually** to verify your domain and to be able to send emails. diff --git a/managed-services/transactional-email/how-to/create-webhooks.mdx b/managed-services/transactional-email/how-to/create-webhooks.mdx index 95a262657c..d4dc90a718 100644 --- a/managed-services/transactional-email/how-to/create-webhooks.mdx +++ b/managed-services/transactional-email/how-to/create-webhooks.mdx @@ -17,16 +17,16 @@ A webhook is an automated message sent in real-time from one system to another w They can be used to track and respond to email-related events such as deliveries, bounces and spam. You can also trigger automated processes or alerts based on specific email events and sync your email events with CRM systems, analytics platforms, or other services. -You can set up webhooks for Scaleway Transactional Email and subscribe them to [Scaleway Topics and Events](/serverless/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints in the Scaleway console. +You can set up webhooks for Scaleway Transactional Email and subscribe them to [Scaleway Topics and Events](/messaging/how-to/create-manage-topics/) to have real-time event alerts sent to your endpoints in the Scaleway console. Currently, webhooks are integrated exclusively with the Scaleway Topics and Events. Billing for webhooks is based on the Scaleway [Topics and Events billing](https://www.scaleway.com/en/pricing/managed-databases/#messaging-and-queuing). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain(s) with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) -- Added [SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/managed-services/transactional-email/how-to/add-dmarc-record/) records to your domain(s) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) +- Added [SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/transactional-email/how-to/add-dmarc-record/) records to your domain(s) - Have the necessary quotas to use Transactional Email Webhooks during beta. You can request quotas from the [Scaleway betas page](https://www.scaleway.com/fr/betas/#email-webhooks). ## How to create a webhook @@ -50,7 +50,7 @@ You can create only one webhook per domain. - Choose the email events that will trigger the webhook and send information to your selected topic. - Refer to the [Transactional Email concepts page](/managed-services/transactional-email/concepts/#webhook-event-type) for a full list of available webhook event types. + Refer to the [Transactional Email concepts page](/transactional-email/concepts/#webhook-event-type) for a full list of available webhook event types. 6. Click **Create Webhook** to confirm. A list of your webhooks appears. diff --git a/managed-services/transactional-email/how-to/delete-tem-domain.mdx b/managed-services/transactional-email/how-to/delete-tem-domain.mdx index 8c14f8d661..2c09425e25 100644 --- a/managed-services/transactional-email/how-to/delete-tem-domain.mdx +++ b/managed-services/transactional-email/how-to/delete-tem-domain.mdx @@ -18,8 +18,8 @@ This page shows you how to delete a domain that you have configured with Transac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain name with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain name with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) 1. Click **Transactional Email** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. The list of your domains displays. 2. Click the domain you want to delete. The overview of your domain displays. diff --git a/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx b/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx index 729cad5fca..20fe31822e 100644 --- a/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx +++ b/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam.mdx @@ -10,23 +10,23 @@ dates: posted: 2022-11-07 --- -This page shows you how to generate [API keys](/identity-and-access-management/iam/concepts/#api-key) with IAM to send [transactional emails](/managed-services/transactional-email/concepts/#transactional-email) via API and SMTP. +This page shows you how to generate [API keys](/iam/concepts/#api-key) with IAM to send [transactional emails](/transactional-email/concepts/#transactional-email) via API and SMTP. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) -- Added [SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) +- Added [SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain ## Generate an API key using IAM and send emails via the API To send your emails via the API, a valid API key and your Project ID are required. -1. [Create an IAM application](/identity-and-access-management/iam/how-to/create-application/). -2. [Create a policy](/identity-and-access-management/iam/how-to/create-policy/) giving appropriate [permissions](/identity-and-access-management/iam/reference-content/permission-sets/) to carry out actions for Transactional Email in the desired Project(s), with the IAM application attached as a principal. -3. [Create an API key for your application](/identity-and-access-management/iam/how-to/create-api-keys/). +1. [Create an IAM application](/iam/how-to/create-application/). +2. [Create a policy](/iam/how-to/create-policy/) giving appropriate [permissions](/iam/reference-content/permission-sets/) to carry out actions for Transactional Email in the desired Project(s), with the IAM application attached as a principal. +3. [Create an API key for your application](/iam/how-to/create-api-keys/). Make sure you save your secret and access keys as you will need them in the following step. @@ -64,7 +64,7 @@ curl -X POST "https://api.scaleway.com/transactional-email/v1alpha1/regions/$REG -d @mail.json ``` - - If you have not configured your environment on your local machine, make sure you replace `\` with your [Project ID](/identity-and-access-management/organizations-and-projects/concepts/#project), `$REGION` with `fr-par` and `$TOKEN` with your secret key. If you do not replace the Project ID, the API displays a "permission denied" error message. + - If you have not configured your environment on your local machine, make sure you replace `\` with your [Project ID](/organizations-and-projects/concepts/#project), `$REGION` with `fr-par` and `$TOKEN` with your secret key. If you do not replace the Project ID, the API displays a "permission denied" error message. - Make sure you replace the email addresses with yours and your recipient's. @@ -82,7 +82,7 @@ The following output should display: The Transactional Email SMTP relay is available at `smtp.tem.scaleway.com` on ports `25`, `587`, `2587` (non TLS), `465` and `2465` (TLS). To send your emails using SMTP, a valid API secret key and your Project ID are required. -1. [Generate an API key](/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam#generate-an-api-key-using-iam-and-send-emails-via-the-api) as shown above. +1. [Generate an API key](/transactional-email/how-to/generate-api-keys-for-tem-with-iam#generate-an-api-key-using-iam-and-send-emails-via-the-api) as shown above. 2. Authenticate yourself to the server using your Project ID as a username. 3. Use your secret key as a password and start sending emails. diff --git a/managed-services/transactional-email/how-to/manage-email-activity.mdx b/managed-services/transactional-email/how-to/manage-email-activity.mdx index f2eb57abbf..24b204d13f 100644 --- a/managed-services/transactional-email/how-to/manage-email-activity.mdx +++ b/managed-services/transactional-email/how-to/manage-email-activity.mdx @@ -15,14 +15,14 @@ categories: This page shows you how to display your email activity and filter your emails using the [Scaleway console](https://console.scaleway.com/). -With [flags](/managed-services/transactional-email/concepts/#flags), you can also get more information on your emails' statuses. +With [flags](/transactional-email/concepts/#flags), you can also get more information on your emails' statuses. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain(s) with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) -- Added [SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain(s) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) +- Added [SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), and [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain(s) ## How to display your email activity @@ -53,15 +53,15 @@ With [flags](/managed-services/transactional-email/concepts/#flags), you can als | Rejected | The sending of your email failed | | Email canceled | The sending of your email was canceled | - | **[Flags](/managed-services/transactional-email/concepts/#flags)** | **Meaning** | + | **[Flags](/transactional-email/concepts/#flags)** | **Meaning** | |--------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Greylisted | Your email has been slightly delayed by the recipient, to ensure that Scaleway is not sending spam. | - | Hard bounce | A critical error occurred while sending the email. Find out more about [hard bounces](/managed-services/transactional-email/concepts/#hard-bounce). | + | Hard bounce | A critical error occurred while sending the email. Find out more about [hard bounces](/transactional-email/concepts/#hard-bounce). | | Mailbox full | Your email was not able to reach the recipient's mailbox, because it is full. | | Mailbox not found | Your email was not able to reach the recipient's mailbox, because it does not exist. | | Send before expiration | You have requested to send your email before a specific date (defined by you), and that your email expires after that date. This is useful if you are sending an email containing a password renewal link, for example. | - | Soft bounce | A non-critical error occurred while sending your email. Soft bounced emails are retried. Find out more about [soft bounces](/managed-services/transactional-email/concepts/#soft-bounce). | - | Spam | Your email has been considered spam. [Find out how to abide by emailing best practices](/managed-services/transactional-email/reference-content/understanding-tem-reputation-score/#emailing-best-practices-to-improve-your-domain-reputation). | + | Soft bounce | A non-critical error occurred while sending your email. Soft bounced emails are retried. Find out more about [soft bounces](/transactional-email/concepts/#soft-bounce). | + | Spam | Your email has been considered spam. [Find out how to abide by emailing best practices](/transactional-email/reference-content/understanding-tem-reputation-score/#emailing-best-practices-to-improve-your-domain-reputation). | Once you have chosen your filters, and clicked **Apply filters**, a list of emails matching the criteria displays: diff --git a/managed-services/transactional-email/index.mdx b/managed-services/transactional-email/index.mdx index 327afaaec9..4317446444 100644 --- a/managed-services/transactional-email/index.mdx +++ b/managed-services/transactional-email/index.mdx @@ -8,7 +8,7 @@ meta: productName="Transactional Email" productLogo="transactionalEmail" description="Transactional Email is a platform that allows you to send application-generated emails such as receipts, alerts, password resets, and more." - url="/managed-services/transactional-email/quickstart/" + url="/transactional-email/quickstart/" label="Transactional Email Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to configure a domain and add the necessary records to it in a few steps." label="View Quickstart" - url="/managed-services/transactional-email/quickstart/" + url="/transactional-email/quickstart/" /> diff --git a/managed-services/transactional-email/quickstart.mdx b/managed-services/transactional-email/quickstart.mdx index c13f15de47..e126f588a9 100644 --- a/managed-services/transactional-email/quickstart.mdx +++ b/managed-services/transactional-email/quickstart.mdx @@ -13,14 +13,14 @@ categories: - managed-services --- -Transactional Email is a platform that allows Scaleway clients to send [transactional emails](/managed-services/transactional-email/concepts/#transactional-email) with high quality [deliverability](/managed-services/transactional-email/concepts/#deliverability). +Transactional Email is a platform that allows Scaleway clients to send [transactional emails](/transactional-email/concepts/#transactional-email) with high quality [deliverability](/transactional-email/concepts/#deliverability). In this quickstart, we show you how to configure your domain with Transactional Email, how to add SPF, DKIM and MX records to your domain, and how to delete your domain. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name ## How to configure your domain with Transactional Email @@ -31,7 +31,7 @@ In this quickstart, we show you how to configure your domain with Transactional 4. Tick the box to acknowledge you have read Scaleway’s antispam policy, then, click **Validate domain name** to confirm. - You need to configure your [SPF](/managed-services/transactional-email/concepts/#spf-record), [DKIM](/managed-services/transactional-email/concepts/#dkim-record) and [MX](/managed-services/transactional-email/concepts/#mx-record) records to verify your domain and to be able to send emails. + You need to configure your [SPF](/transactional-email/concepts/#spf-record), [DKIM](/transactional-email/concepts/#dkim-record) and [MX](/transactional-email/concepts/#mx-record) records to verify your domain and to be able to send emails. @@ -65,12 +65,12 @@ After you have configured your domain with Transactional Email, you are prompted ## How to add your own MX record - If you do not own an MX server, we recommend [using Scaleway's blackhole MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-scaleways-mx-record) so the emails you send do not get rejected. However, this means that the **emails sent back to the MX, will be lost and unrecoverable**. + If you do not own an MX server, we recommend [using Scaleway's blackhole MX](/transactional-email/how-to/add-mx-record-to-your-domain/#how-to-add-scaleways-mx-record) so the emails you send do not get rejected. However, this means that the **emails sent back to the MX, will be lost and unrecoverable**. -1. Add an [MX record](/managed-services/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. +1. Add an [MX record](/transactional-email/concepts/#mx-record) type in the root zone of your domain on your DNS zone. 2. Enter a name of your choice in the **Name** field. -3. Set `10` as a [priority](/managed-services/transactional-email/concepts/#priority) for your MX record. +3. Set `10` as a [priority](/transactional-email/concepts/#priority) for your MX record. Priority indicates the order in which your mail servers should be tried by a mail server that is attempting to deliver emails. @@ -84,4 +84,4 @@ The **factors** used to determine your domain's reputation score **vary from one The only constant common denominator is that the **receiving platforms determine how your domain is used in your emails** and then **monitor how their users receive these emails**. Each domain has several reputations associated with different mail receivers. Reputation also depends on the volume of emails you send to specific receivers. -Read our [documentation](/managed-services/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how to improve or maintain a good domain [reputation](/managed-services/transactional-email/concepts/#reputation-score) score. \ No newline at end of file +Read our [documentation](/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how to improve or maintain a good domain [reputation](/transactional-email/concepts/#reputation-score) score. \ No newline at end of file diff --git a/managed-services/transactional-email/reference-content/dmarc-configuration.mdx b/managed-services/transactional-email/reference-content/dmarc-configuration.mdx index a61b3fa552..7582eb6838 100644 --- a/managed-services/transactional-email/reference-content/dmarc-configuration.mdx +++ b/managed-services/transactional-email/reference-content/dmarc-configuration.mdx @@ -13,11 +13,11 @@ categories: - managed-services --- -With [DMARC](/managed-services/transactional-email/concepts/#dmarc-record), domain owners publish a [policy](#dmarc-policy) in their DNS records, specifying what actions should be taken when an incoming email fails authentication checks. +With [DMARC](/transactional-email/concepts/#dmarc-record), domain owners publish a [policy](#dmarc-policy) in their DNS records, specifying what actions should be taken when an incoming email fails authentication checks. When setting up DMARC, you can include specific tags in your DNS records to define your policy and reporting preferences. These tags include information like the policy to be enforced (`p` tag), the percentage of emails to apply the policy to (`pct` tag), and the email address to which DMARC reports should be sent (`rua` and `ruf` tags). -This documentation provides information about the mandatory and optional tags to configure when [adding a DMARC record](/managed-services/transactional-email/how-to/add-dmarc-record/) to your domain, what they mean, the expected value for them, and their default value. You will also find examples of DMARC configurations according to your use-case. +This documentation provides information about the mandatory and optional tags to configure when [adding a DMARC record](/transactional-email/how-to/add-dmarc-record/) to your domain, what they mean, the expected value for them, and their default value. You will also find examples of DMARC configurations according to your use-case. ## DMARC Policy @@ -71,7 +71,7 @@ There are two main types of DMARC reports: ## Examples of DMARC configuration -Below are a few examples of DMARC configuration scenarios for inspiration to [configure your DMARC](/managed-services/transactional-email/how-to/add-dmarc-record/). +Below are a few examples of DMARC configuration scenarios for inspiration to [configure your DMARC](/transactional-email/how-to/add-dmarc-record/). @@ -93,7 +93,7 @@ The following DMARC configuration is the most basic one. It is commonly used for - `p=none` sets the DMARC policy to "none" meaning that no specific action should be taken based on the DMARC policy. This policy is typically used for monitoring purposes. - `rua=mailto:mydomain@example.com` specifies the email address to which aggregate reports should be sent (`mydomain@example.com`). -This configuration might be useful if you want to start implementing DMARC gradually, without immediately enforcing strict policies that could potentially affect your email [deliverability](/managed-services/transactional-email/concepts/#deliverability). +This configuration might be useful if you want to start implementing DMARC gradually, without immediately enforcing strict policies that could potentially affect your email [deliverability](/transactional-email/concepts/#deliverability). It allows you to monitor email authentication results and gather data without impacting the flow of incoming emails. ### Configuration for a moderate level of protection diff --git a/managed-services/transactional-email/reference-content/protecting-your-domain-reputation.mdx b/managed-services/transactional-email/reference-content/protecting-your-domain-reputation.mdx index 74b6fd7b8d..3f04e96155 100644 --- a/managed-services/transactional-email/reference-content/protecting-your-domain-reputation.mdx +++ b/managed-services/transactional-email/reference-content/protecting-your-domain-reputation.mdx @@ -15,7 +15,7 @@ categories: Scaleway applies reasonable and gradual sending strategies to preserve the reputation of your domain and increase the deliverability of your emails. These measures prevent your domain from being considered a spam sender. -In order to protect the reputation of your domain and our Transactional Email service, while effectively controlling the deliverability rate of your emails, Scaleway applies traffic management measures. This reduces the risk of your domain being blacklisted in the event of [reputation](/managed-services/transactional-email/concepts/#ip-reputation) problems. +In order to protect the reputation of your domain and our Transactional Email service, while effectively controlling the deliverability rate of your emails, Scaleway applies traffic management measures. This reduces the risk of your domain being blacklisted in the event of [reputation](/transactional-email/concepts/#ip-reputation) problems. These measures can apply if: @@ -29,5 +29,5 @@ Scaleway reasonably manages email traffic to make sure that your emails are deli You can [read our anti-spam policy](https://tem.s3.fr-par.scw.cloud/antispam_policy.pdf) for more information. - Find out [how to delist a blacklisted domain](/managed-services/transactional-email/troubleshooting/delist-domain/). + Find out [how to delist a blacklisted domain](/transactional-email/troubleshooting/delist-domain/). \ No newline at end of file diff --git a/managed-services/transactional-email/reference-content/smtp-configuration.mdx b/managed-services/transactional-email/reference-content/smtp-configuration.mdx index d234498c85..48338a79dd 100644 --- a/managed-services/transactional-email/reference-content/smtp-configuration.mdx +++ b/managed-services/transactional-email/reference-content/smtp-configuration.mdx @@ -33,7 +33,7 @@ On this page, we go through different elements you might find in a standard SMTP Your Scaleway SMTP username is the Project ID of the Project in which the TEM domain was created. You can find it under **Managed Services** > **Transactional Email** > **Domain Overview** in the Scaleway console. -Your password is the secret key of the API key of the project used to manage your TEM domain. Follow this procedure to [generate API keys for API and SMTP sending with IAM](/managed-services/transactional-email/how-to/generate-api-keys-for-tem-with-iam/). +Your password is the secret key of the API key of the project used to manage your TEM domain. Follow this procedure to [generate API keys for API and SMTP sending with IAM](/transactional-email/how-to/generate-api-keys-for-tem-with-iam/). 4 - **Encryption method** - An encrypted connection between your application and the SMTP server is **mandatory**, and two methods are available: diff --git a/managed-services/transactional-email/reference-content/understanding-tem-reputation-score.mdx b/managed-services/transactional-email/reference-content/understanding-tem-reputation-score.mdx index e321bbc97c..c14d536281 100644 --- a/managed-services/transactional-email/reference-content/understanding-tem-reputation-score.mdx +++ b/managed-services/transactional-email/reference-content/understanding-tem-reputation-score.mdx @@ -13,11 +13,11 @@ categories: - managed-services --- -Scaleway's Transactional Email service provides a weekly email report on your email activity, as well as alerts, to allow you to manage and improve your domain [reputation](/managed-services/transactional-email/concepts/#reputation-score). This documentation provides information about the alerts we send you and advice on how to maintain a good reputation score. +Scaleway's Transactional Email service provides a weekly email report on your email activity, as well as alerts, to allow you to manage and improve your domain [reputation](/transactional-email/concepts/#reputation-score). This documentation provides information about the alerts we send you and advice on how to maintain a good reputation score. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Transactional Email alerts @@ -28,10 +28,10 @@ Scaleway's Transactional Email service provides a weekly email report on your em | Missing or incorrect DNS records on your domain `domain-name` | Indicates that there is one or several issues with your domain’s DNS record configuration. The alert we send shows you what specific records (SPF, DKIM and/or MX) need to be reconfigured. | When the check for your domain's DNS records fails. | | You have reached 70% of your monthly email limit for `domain-name` | Indicates that you are nearing your Transactional Email's monthly quota limit | When you have reached 70% of your Transactional Email monthly quota consumption. | | Email rejection rate for `domain-name` | Indicates that your emails have a higher rejection rate than usual. The alert we send gives you a list of factors that could have contributed to this high rejection rate. | When 7% of your emails have been rejected over a 24-hour-span. | -| Your domain `domain-name` is locked | Indicates that your domain's reputation score is too low. Read our [documentation](/managed-services/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how you can improve it. | When your domain's reputation score drops below 50. | -| Your domain `domain name` is blacklisted | Indicates that [RBLs](/managed-services/transactional-email/concepts/#rbls) flag your domain as spam. The alert we send gives you a link to our [documentation on delisting your domain](/managed-services/transactional-email/troubleshooting/delist-domain/). | When your domain is listed on the Spamhaus blacklist. | +| Your domain `domain-name` is locked | Indicates that your domain's reputation score is too low. Read our [documentation](/transactional-email/reference-content/understanding-tem-reputation-score/) to find out how you can improve it. | When your domain's reputation score drops below 50. | +| Your domain `domain name` is blacklisted | Indicates that [RBLs](/transactional-email/concepts/#rbls) flag your domain as spam. The alert we send gives you a link to our [documentation on delisting your domain](/transactional-email/troubleshooting/delist-domain/). | When your domain is listed on the Spamhaus blacklist. | -Check out our [dedicated documentation](/managed-services/transactional-email/how-to/manage-email-activity/#how-to-use-your-domains-email-activity-tab) to learn about managing your email activity using your email statuses and flags. +Check out our [dedicated documentation](/transactional-email/how-to/manage-email-activity/#how-to-use-your-domains-email-activity-tab) to learn about managing your email activity using your email statuses and flags. ## Checking your domain reputation @@ -59,26 +59,26 @@ Many factors might affect your domain's reputation. The most common are the foll - Blacklists: Internet service providers and email providers may add domains and IPs to their blacklists to prevent spamming. Once your domain is blacklisted, your emails will be instantly flagged as spam. Your domain can also be blacklisted if a significant number of your recipients label your messages as spam. -- Spam traps: Your emails might be landing in [spam traps](/managed-services/transactional-email/concepts/#spam-trap) which in turn, negatively impacts your reputation score. +- Spam traps: Your emails might be landing in [spam traps](/transactional-email/concepts/#spam-trap) which in turn, negatively impacts your reputation score. ## Emailing best practices to improve your domain reputation For a good domain reputation, you need to implement the following emailing practices: -- Use the [preheader](/managed-services/transactional-email/concepts/#preheader) to entice your recipients to open your email. +- Use the [preheader](/transactional-email/concepts/#preheader) to entice your recipients to open your email. - Do not use spam phrases in the **subject line** of your emails. Spam words and phrases associated with scams, promises and free gifts arouse suspicion among email service providers. - Maintain a 60/40 text-to-image ratio. - Send emails with a coherent structure. - Keep a clean list of **engaged users** and delete email addresses of recipients that do not engage with your content. -- Do not purchase an email list as they might include [spam traps](/managed-services/transactional-email/concepts/#spam-trap). -- Delete emails that have [soft bounced](/managed-services/transactional-email/concepts/#soft-bounce) and [hard bounced](/managed-services/transactional-email/concepts/#hard-bounce). +- Do not purchase an email list as they might include [spam traps](/transactional-email/concepts/#spam-trap). +- Delete emails that have [soft bounced](/transactional-email/concepts/#soft-bounce) and [hard bounced](/transactional-email/concepts/#hard-bounce). - Use **shared IPs** if you are sending small volumes of emails (< 5 000 emails/day). A shared IP allows you to send emails without needing to warm up your IP, and improve your deliverability by pooling all its users' IP reputation. This also ensures that your reputation does not suffer if you are not sending enough emails consistently from your IP. - If you are sending large volumes of emails (> 300 000 emails/month), consider using a dedicated IP (not yet provided by Scaleway). This ensures that the emails you send are not affected by the reputation of senders using the same IP address. - - You need to [warm up](/managed-services/transactional-email/concepts/#ip-warming) your dedicated IP before starting to send emails. As new IP addresses have no reputation, internet service providers are suspicious of them. It is crucial that you send your emails progressively (100 emails/day) and slowly ramp up your volume over a period of weeks or months until you reach the desired volume. + - You need to [warm up](/transactional-email/concepts/#ip-warming) your dedicated IP before starting to send emails. As new IP addresses have no reputation, internet service providers are suspicious of them. It is crucial that you send your emails progressively (100 emails/day) and slowly ramp up your volume over a period of weeks or months until you reach the desired volume. - Find out [how to use your **Email activity** tab](/managed-services/transactional-email/how-to/manage-email-activity/#how-to-use-your-domains-email-activity-tab) to manage your domain reputation. + Find out [how to use your **Email activity** tab](/transactional-email/how-to/manage-email-activity/#how-to-use-your-domains-email-activity-tab) to manage your domain reputation. \ No newline at end of file diff --git a/managed-services/transactional-email/troubleshooting/delist-domain.mdx b/managed-services/transactional-email/troubleshooting/delist-domain.mdx index 440ef1166a..3a87dfb00d 100644 --- a/managed-services/transactional-email/troubleshooting/delist-domain.mdx +++ b/managed-services/transactional-email/troubleshooting/delist-domain.mdx @@ -13,9 +13,9 @@ categories: - managed-services --- -Spamhaus is a database that analyzes data and lists internet resources such as IP addresses or domains with poor [reputation](/managed-services/transactional-email/concepts/#ip-reputation). Spamhaus tracks ransomware, malware, phishing, and spam and produces several blocklists that mailbox providers use to protect themselves against malicious activity. +Spamhaus is a database that analyzes data and lists internet resources such as IP addresses or domains with poor [reputation](/transactional-email/concepts/#ip-reputation). Spamhaus tracks ransomware, malware, phishing, and spam and produces several blocklists that mailbox providers use to protect themselves against malicious activity. -Your [deliverability](/managed-services/transactional-email/concepts/#deliverability) will be affected if you are blacklisted on Spamhaus. +Your [deliverability](/transactional-email/concepts/#deliverability) will be affected if you are blacklisted on Spamhaus. ## How to get a domain removed from the Spamhaus Block List (SBL) diff --git a/managed-services/webhosting/concepts.mdx b/managed-services/webhosting/concepts.mdx index d74f3805a6..35bd9f8cc8 100644 --- a/managed-services/webhosting/concepts.mdx +++ b/managed-services/webhosting/concepts.mdx @@ -49,7 +49,7 @@ PHP is a server-side scripting language designed for web development but also us ## php.ini -The `php.ini` file is the configuration file used for applications that require PHP. It contains variable configurations such as upload size, file timeout, and resource limits. For Scaleway Web Hosting, we provide PHP with the most common values preconfigured. If required, you can [customize the configuration of PHP](/dedibox-console/classic-hosting/how-to/configure-php/) to suit your needs. +The `php.ini` file is the configuration file used for applications that require PHP. It contains variable configurations such as upload size, file timeout, and resource limits. For Scaleway Web Hosting, we provide PHP with the most common values preconfigured. If required, you can [customize the configuration of PHP](/classic-hosting/how-to/configure-php/) to suit your needs. ## Plesk diff --git a/managed-services/webhosting/how-to/configure-dns-webhosting.mdx b/managed-services/webhosting/how-to/configure-dns-webhosting.mdx index 393e8e6116..c2e341f76d 100644 --- a/managed-services/webhosting/how-to/configure-dns-webhosting.mdx +++ b/managed-services/webhosting/how-to/configure-dns-webhosting.mdx @@ -18,8 +18,8 @@ To link your domain name with Web Hosting, you must update the DNS configuration - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan 1. Navigate to the **Web Hosting** section under **Managed Services** in the [console](https://console.scaleway.com/) side menu. The **Web Hosting** overview page displays. diff --git a/managed-services/webhosting/how-to/manage-databases.mdx b/managed-services/webhosting/how-to/manage-databases.mdx index cfb3789f86..a0b2a0cd61 100644 --- a/managed-services/webhosting/how-to/manage-databases.mdx +++ b/managed-services/webhosting/how-to/manage-databases.mdx @@ -19,12 +19,12 @@ You can create and manage databases for your website and applications, including - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan - This guide focuses on managing your databases through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/managed-services/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). + This guide focuses on managing your databases through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). ## How to create a database diff --git a/managed-services/webhosting/how-to/manage-email-accounts.mdx b/managed-services/webhosting/how-to/manage-email-accounts.mdx index 81885c84f9..299009791a 100644 --- a/managed-services/webhosting/how-to/manage-email-accounts.mdx +++ b/managed-services/webhosting/how-to/manage-email-accounts.mdx @@ -18,12 +18,12 @@ Send, receive, and store electronic messages through the internet. Email account - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan - This guide focuses on managing your email accounts through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/managed-services/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). + This guide focuses on managing your email accounts through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). ## How to create an email account diff --git a/managed-services/webhosting/how-to/manage-ftp-accounts.mdx b/managed-services/webhosting/how-to/manage-ftp-accounts.mdx index 36c789ef8f..5f3f64ba34 100644 --- a/managed-services/webhosting/how-to/manage-ftp-accounts.mdx +++ b/managed-services/webhosting/how-to/manage-ftp-accounts.mdx @@ -20,12 +20,12 @@ You can create and manage FTP accounts directly from the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan - This guide focuses on managing your FTP accounts through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/managed-services/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). + This guide focuses on managing your FTP accounts through the Scaleway console. For advanced configurations, you can access your [Web Hosting control panel (cPanel or Plesk)](/webhosting/quickstart/#how-to-access-the-web-hosting-control-panel-from-the-scaleway-console). ## How to create an FTP account diff --git a/managed-services/webhosting/how-to/manage-webhosting.mdx b/managed-services/webhosting/how-to/manage-webhosting.mdx index f9c21c2eca..c188962b85 100644 --- a/managed-services/webhosting/how-to/manage-webhosting.mdx +++ b/managed-services/webhosting/how-to/manage-webhosting.mdx @@ -18,8 +18,8 @@ You can access the control panel for your Web Hosting from the Scaleway console - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan 1. Click **Web Hosting** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. The **Web Hosting** overview page displays. @@ -32,8 +32,8 @@ You can access the control panel for your Web Hosting from the Scaleway console 4. Enter your control panel credentials and click **Log in** to log into your Web Hosting control panel. - Scaleway provides Web Hosting offers with [cPanel](/managed-services/webhosting/reference-content/cpanel-reference-content/) or [Plesk](/managed-services/webhosting/reference-content/plesk-reference-content/). - For more information about them, refer to [Web Hosting additional content](/managed-services/webhosting/reference-content/). + Scaleway provides Web Hosting offers with [cPanel](/webhosting/reference-content/cpanel-reference-content/) or [Plesk](/webhosting/reference-content/plesk-reference-content/). + For more information about them, refer to [Web Hosting additional content](/webhosting/reference-content/). diff --git a/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx b/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx index 2f0006c6ee..5394a22c51 100644 --- a/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx +++ b/managed-services/webhosting/how-to/migrate-webhosting-plan.mdx @@ -16,15 +16,15 @@ categories: You now have the option to migrate your Dedibox Web Hosting Cloud (powered by cPanel) to our cutting-edge web hosting service within the Scaleway ecosystem. This new platform offers an intuitive graphical interface to streamline your web hosting management. By making the move to this upgraded system, you'll continue to access all the features included in your current Dedibox Web Hosting Cloud plan, along with the latest updates and performance enhancements for an even better hosting experience. - If you are migrating from a **Web Hosting Classic** plan, refer to our documentation [Web Hosting Classic migration - Technical information](/managed-services/webhosting/reference-content/classic-hosting-migration-information/) for further information. + If you are migrating from a **Web Hosting Classic** plan, refer to our documentation [Web Hosting Classic migration - Technical information](/webhosting/reference-content/classic-hosting-migration-information/) for further information. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added a valid payment method](/console/billing/how-to/add-payment-method/) to your Scaleway account -- [A Web Hosting Cloud (cPanel)](/dedibox-console/cpanel-hosting/quickstart/) plan in the Dedibox console +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added a valid payment method](/billing/how-to/add-payment-method/) to your Scaleway account +- [A Web Hosting Cloud (cPanel)](/cpanel-hosting/quickstart/) plan in the Dedibox console - A Dedibox account logged into the [console](https://console.online.net/) @@ -37,13 +37,13 @@ You now have the option to migrate your Dedibox Web Hosting Cloud (powered by cP * Migrating your Web Hosting plan **is a definitive decision**. Once completed, it is not possible to revert back to your previous plan. - * You must ensure that a [valid payment method has been added](/console/billing/how-to/add-payment-method/) to your Scaleway account before initiating the migration. This is a **mandatory** step to prevent any possible interruption or locking of your web hosting plan during the migration. + * You must ensure that a [valid payment method has been added](/billing/how-to/add-payment-method/) to your Scaleway account before initiating the migration. This is a **mandatory** step to prevent any possible interruption or locking of your web hosting plan during the migration. 1. Go to the [list of web hosting accounts](https://console.online.net/en/mut/list) and select the web hosting you want to migrate. 2. Click **Migrate** on the web hosting overview. This action will trigger a pop-up to appear. 3. Review the details related to your web hosting and click **Migrate** to automatically populate the migration information in the Scaleway console. You will be redirected to the Scaleway console. -4. The migration details for your web hosting will be shown. Make sure that you are within the [destination project](/identity-and-access-management/organizations-and-projects/quickstart/) for your hosting. Then, proceed to click **Migrate your Web Hosting**. +4. The migration details for your web hosting will be shown. Make sure that you are within the [destination project](/organizations-and-projects/quickstart/) for your hosting. Then, proceed to click **Migrate your Web Hosting**. The migration process will be completed within two business days. diff --git a/managed-services/webhosting/how-to/order-dedicated-ip.mdx b/managed-services/webhosting/how-to/order-dedicated-ip.mdx index 641f883e75..5688139542 100644 --- a/managed-services/webhosting/how-to/order-dedicated-ip.mdx +++ b/managed-services/webhosting/how-to/order-dedicated-ip.mdx @@ -29,8 +29,8 @@ Some potential advantages of having a dedicated IP address for Web Hosting are: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - A Web Hosting plan with a shared IP address ## Activate a dedicated IP address for a Web Hosting plan diff --git a/managed-services/webhosting/how-to/order-webhosting.mdx b/managed-services/webhosting/how-to/order-webhosting.mdx index 42e487ef56..f68f5e6df4 100644 --- a/managed-services/webhosting/how-to/order-webhosting.mdx +++ b/managed-services/webhosting/how-to/order-webhosting.mdx @@ -18,8 +18,8 @@ This page shows how to create a Scaleway Web Hosting plan. Web Hosting is a mana - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar 1. Click **Web Hosting** in the **Managed Services** section of the side menu. This takes you to the Web Hosting dashboard.
If you already have Web Hosting plans, they will be listed. Click the **+ Order Web Hosting** button to add more plans. @@ -29,11 +29,11 @@ This page shows how to create a Scaleway Web Hosting plan. Web Hosting is a mana * **cPanel**: A web-based control panel for managing web hosting accounts, emails, and websites through a graphical interface. * **Plesk**: A user-friendly web hosting control panel for managing websites, emails, and hosting accounts. - Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/managed-services/webhosting/reference-content/understanding-differences-cpanel-plesk/). + Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/webhosting/reference-content/understanding-differences-cpanel-plesk/). * Click Configure Web Hosting to continue. 4. Follow these steps to configure your Web Hosting: - - Enter your **domain name**. Remember, it must be pre-registered and you must be the registrant. Need to register one? [Read our documentation on how to register a domain name](/network/domains-and-dns/how-to/register-internal-domain/). + - Enter your **domain name**. Remember, it must be pre-registered and you must be the registrant. Need to register one? [Read our documentation on how to register a domain name](/domains-and-dns/how-to/register-internal-domain/). - Choose a **hosting plan** based on your needs. - Decide if you want to enable the **backup** feature: - Enable it for daily automated backups of your website, emails, and databases. The feature retains backups for three days, with a full weekly backup retained for two months. @@ -48,6 +48,6 @@ This page shows how to create a Scaleway Web Hosting plan. Web Hosting is a mana You will find the credentials (username/password) for your control panel in your email inbox. -Proceed with the [configuration of the DNS](/managed-services/webhosting/how-to/configure-dns-webhosting/) for your Web Hosting plan. +Proceed with the [configuration of the DNS](/webhosting/how-to/configure-dns-webhosting/) for your Web Hosting plan. diff --git a/managed-services/webhosting/how-to/protect-webhosting.mdx b/managed-services/webhosting/how-to/protect-webhosting.mdx index ee1c4177e4..4e75fce3bb 100644 --- a/managed-services/webhosting/how-to/protect-webhosting.mdx +++ b/managed-services/webhosting/how-to/protect-webhosting.mdx @@ -13,13 +13,13 @@ categories: - web-hosting --- -The [protected hosting](/managed-services/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancellations during routine maintenance or management activities. +The [protected hosting](/webhosting/concepts/#protected-hosting) feature is designed to prevent any accidental or unauthorized deletions of your Web Hosting plan. When enabled, this feature ensures that your Web Hosting plan cannot be deleted, providing an extra layer of protection against unintended disruptions. This is particularly useful for preventing errors, such as accidental cancellations during routine maintenance or management activities. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions within the intended Organization -- An active [Web Hosting plan](/managed-services/webhosting/how-to/order-webhosting/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions within the intended Organization +- An active [Web Hosting plan](/webhosting/how-to/order-webhosting/) 1. Click **Web Hosting** in the **Managed Services** section of the side menu. The [Web Hosting dashboard](https://console.scaleway.com/webhosting) displays. diff --git a/managed-services/webhosting/how-to/terminate-webhosting.mdx b/managed-services/webhosting/how-to/terminate-webhosting.mdx index c711417d62..d3886ce8e9 100644 --- a/managed-services/webhosting/how-to/terminate-webhosting.mdx +++ b/managed-services/webhosting/how-to/terminate-webhosting.mdx @@ -15,8 +15,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Registered a domain name](/network/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Registered a domain name](/domains-and-dns/how-to/register-internal-domain/) at Scaleway or another registrar - An active Web Hosting plan ### How to terminate your Web Hosting plan diff --git a/managed-services/webhosting/index.mdx b/managed-services/webhosting/index.mdx index ee7d89693f..d5072958b4 100644 --- a/managed-services/webhosting/index.mdx +++ b/managed-services/webhosting/index.mdx @@ -8,7 +8,7 @@ meta: productName="Web Hosting" productLogo="webHosting" description="Scaleway Web Hosting is a simple, scalable, and secure solution for personal, business, and everything in between. Our Web Hosting plans include 420+ click-to-deploy apps." - url="/managed-services/webhosting/quickstart" + url="/webhosting/quickstart" label="Web Hosting Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create, manage, and delete a Web Hosting plan in a few steps." label="View Quickstart" - url="/managed-services/webhosting/quickstart/" + url="/webhosting/quickstart/" /> diff --git a/managed-services/webhosting/quickstart.mdx b/managed-services/webhosting/quickstart.mdx index 43564f8e02..f0574ba79b 100644 --- a/managed-services/webhosting/quickstart.mdx +++ b/managed-services/webhosting/quickstart.mdx @@ -19,7 +19,7 @@ Scaleway provides several [Web Hosting plans](https://www.scaleway.com/en/web-ho All Scaleway Web Hosting plans use a user-friendly Web Hosting control panel tool. This interface provides users with intuitive graphical navigation and quick access icons for configuring and monitoring their hosting solutions. With features like website publishing, database launching, email creation, and file management, users can efficiently manage their hosting tasks through this interface, ensuring elevated performance. -Scaleway provides Web Hosting plans with [cPanel](/managed-services/webhosting/reference-content/cpanel-reference-content/) or [Plesk](/managed-services/webhosting/reference-content/plesk-reference-content/) control panels. Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/managed-services/webhosting/reference-content/understanding-differences-cpanel-plesk/). +Scaleway provides Web Hosting plans with [cPanel](/webhosting/reference-content/cpanel-reference-content/) or [Plesk](/webhosting/reference-content/plesk-reference-content/) control panels. Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/webhosting/reference-content/understanding-differences-cpanel-plesk/). ## How to order a Web Hosting plan @@ -32,10 +32,10 @@ Scaleway provides Web Hosting plans with [cPanel](/managed-services/webhosting/r * **Plesk**: A user-friendly web hosting control panel for managing websites, emails, and hosting accounts. - Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/managed-services/webhosting/reference-content/understanding-differences-cpanel-plesk/). + Unsure which control panel to choose? Check out our documentation on [Understanding the differences between cPanel and Plesk](/webhosting/reference-content/understanding-differences-cpanel-plesk/). 4. Follow these steps to configure your Web Hosting: - - Enter your **domain name**. Remember, it must be pre-registered and you must be the registrant. Need to register one? [Read our documentation how to register a domain name](/network/domains-and-dns/how-to/register-internal-domain/). + - Enter your **domain name**. Remember, it must be pre-registered and you must be the registrant. Need to register one? [Read our documentation how to register a domain name](/domains-and-dns/how-to/register-internal-domain/). - Choose a **hosting plan** based on your needs. - Decide on activating the **backup option**: - Enable for daily automated backups of your website, emails, and databases. Retains backups for three days, with a full weekly backup retained for two months. @@ -47,7 +47,7 @@ Scaleway provides Web Hosting plans with [cPanel](/managed-services/webhosting/r ## How to access the Web Hosting control panel from the Scaleway console - You can manage your [email accounts](/managed-services/webhosting/how-to/manage-email-accounts/), [databases](/managed-services/webhosting/how-to/manage-databases/), and [FTP accounts](/managed-services/webhosting/how-to/manage-ftp-accounts/) directly from the Scaleway console. + You can manage your [email accounts](/webhosting/how-to/manage-email-accounts/), [databases](/webhosting/how-to/manage-databases/), and [FTP accounts](/webhosting/how-to/manage-ftp-accounts/) directly from the Scaleway console. @@ -255,7 +255,7 @@ You can access the webmail platform for your Web Hosting directly from your Scal To link your domain name with your Web Hosting plan you have to update the nameservers in the DNS configuration at your registrar. Nameservers are servers used to translate domain names into IP addresses. When you enter a URL in a browser, they show you where the website is located, instead of memorizing entire numerical sequences in the form of IP addresses. - If you are migrating from another web hosting provider to Scaleway Web Hosting, you might need to [update your nameserver information](/managed-services/webhosting/how-to/configure-dns-webhosting/) with the information available in your console. + If you are migrating from another web hosting provider to Scaleway Web Hosting, you might need to [update your nameserver information](/webhosting/how-to/configure-dns-webhosting/) with the information available in your console. 1. Click **Web Hosting** in the **Managed Services** section of the [console](https://console.scaleway.com/) side menu. The **Web Hosting** overview page displays. diff --git a/managed-services/webhosting/reference-content/classic-hosting-migration-information.mdx b/managed-services/webhosting/reference-content/classic-hosting-migration-information.mdx index 9f91391f24..01d8f1ab22 100644 --- a/managed-services/webhosting/reference-content/classic-hosting-migration-information.mdx +++ b/managed-services/webhosting/reference-content/classic-hosting-migration-information.mdx @@ -20,7 +20,7 @@ You can now migrate your Online.net Web Hosting Classic plan to Scaleway's new W - **Up-to-date system:** cPanel's regular updates contribute to an up-to-date and secure hosting environment. This ensures that your system remains resilient in the face of evolving digital challenges. - **A wide range of features:** Explore a range of features offered by cPanel, covering file management, security options, email functionality, and database management. These features collectively form a powerful toolkit to address diverse hosting requirements. -You can initiate the migration of your Web Hosting plan directly from your [Dedibox/Online.net console](https://console.online.net/). For further information, refer to our dedicated documentation [How to migrate an Online.net/Dedibox web hosting plan to Scaleway](/managed-services/webhosting/how-to/migrate-webhosting-plan/). +You can initiate the migration of your Web Hosting plan directly from your [Dedibox/Online.net console](https://console.online.net/). For further information, refer to our dedicated documentation [How to migrate an Online.net/Dedibox web hosting plan to Scaleway](/webhosting/how-to/migrate-webhosting-plan/). * Migrating your Web Hosting plan **is a definitive decision**. Once completed, it is not possible to revert back to your previous plan. @@ -30,7 +30,7 @@ You can initiate the migration of your Web Hosting plan directly from your [Dedi ### What will my new hosting plan be? -After [initiating the migration](/managed-services/webhosting/how-to/migrate-webhosting-plan/) of your Online.net hosting plan, it will be transferred to Scaleway. During this transition, your existing offer will be temporarily moved to a migration plan. You will then have the possibility to select from Scaleway's range of Web Hosting plans, tailored to meet your specific requirements. +After [initiating the migration](/webhosting/how-to/migrate-webhosting-plan/) of your Online.net hosting plan, it will be transferred to Scaleway. During this transition, your existing offer will be temporarily moved to a migration plan. You will then have the possibility to select from Scaleway's range of Web Hosting plans, tailored to meet your specific requirements. Your current offer will be transferred to one of these migration plans: diff --git a/managed-services/webhosting/reference-content/cpanel-reference-content.mdx b/managed-services/webhosting/reference-content/cpanel-reference-content.mdx index 6a04b5bfe2..8d9437483a 100644 --- a/managed-services/webhosting/reference-content/cpanel-reference-content.mdx +++ b/managed-services/webhosting/reference-content/cpanel-reference-content.mdx @@ -17,7 +17,7 @@ categories: This documentation is for users who have a cPanel Web Hosting plan powered by Scaleway. -Refer to our [Quickstart](/managed-services/webhosting/quickstart/) which contains useful links that answer your **Frequently Asked Questions**. +Refer to our [Quickstart](/webhosting/quickstart/) which contains useful links that answer your **Frequently Asked Questions**. If you need additional help setting up your Web Hosting plan, or have any questions, refer to the index below: diff --git a/managed-services/webhosting/reference-content/php-version-overview.mdx b/managed-services/webhosting/reference-content/php-version-overview.mdx index 7a90107b3d..ceae6df141 100644 --- a/managed-services/webhosting/reference-content/php-version-overview.mdx +++ b/managed-services/webhosting/reference-content/php-version-overview.mdx @@ -15,7 +15,7 @@ categories: Scaleway Web Hosting is based on different infrastructures, each with varying support for PHP versions. -Below you find an overview of the available PHP versions for the existing infrastructures: [Dedibox Classic](/dedibox-console/classic-hosting/), [Dedibox cPanel](/dedibox-console/cpanel-hosting/), and [Scaleway Web Hosting](/managed-services/webhosting/) (cPanel and Plesk). +Below you find an overview of the available PHP versions for the existing infrastructures: [Dedibox Classic](/classic-hosting/), [Dedibox cPanel](/cpanel-hosting/), and [Scaleway Web Hosting](/webhosting/) (cPanel and Plesk). | PHP Version | Dedibox Classic | Dedibox cPanel | Scaleway cPanel | Scaleway Plesk | |-----------------|--------------------|-------------------|---------------------|--------------------| diff --git a/managed-services/webhosting/reference-content/plesk-reference-content.mdx b/managed-services/webhosting/reference-content/plesk-reference-content.mdx index 98ff9b395d..4266b090c3 100644 --- a/managed-services/webhosting/reference-content/plesk-reference-content.mdx +++ b/managed-services/webhosting/reference-content/plesk-reference-content.mdx @@ -17,7 +17,7 @@ categories: This documentation is for users who have a Plesk Web Hosting plan powered by Scaleway. -Refer to our [Quickstart](/managed-services/webhosting/quickstart/) which contains useful links that answer your **Frequently Asked Questions**. +Refer to our [Quickstart](/webhosting/quickstart/) which contains useful links that answer your **Frequently Asked Questions**. If you need additional help setting up your Web Hosting plan, or have any questions, refer to the index below: diff --git a/network/domains-and-dns/concepts.mdx b/network/domains-and-dns/concepts.mdx index 6af5b549c9..e3934db139 100644 --- a/network/domains-and-dns/concepts.mdx +++ b/network/domains-and-dns/concepts.mdx @@ -34,11 +34,11 @@ A DNS name server stores the [DNS Records](#dns-record) for given domains. Scale ## DNS record -A [DNS](#dns) Record holds information translating a domain or subdomain to an IP address, mail server or other domain/subdomain. DNS records for each [DNS Zone](#dns-zone) are stored within files called [DNS zone files](#dns-zone-file). These are hosted on [DNS nameservers](#dns-name-server). DNS records act as instructions for the DNS servers, so they know which domain names and IP addresses are associated with each other. DNS records can be of multiple types, called [resource records](#resource-records). Check out our documentation on [how to manage DNS records](/network/domains-and-dns/how-to/manage-dns-records/). +A [DNS](#dns) Record holds information translating a domain or subdomain to an IP address, mail server or other domain/subdomain. DNS records for each [DNS Zone](#dns-zone) are stored within files called [DNS zone files](#dns-zone-file). These are hosted on [DNS nameservers](#dns-name-server). DNS records act as instructions for the DNS servers, so they know which domain names and IP addresses are associated with each other. DNS records can be of multiple types, called [resource records](#resource-records). Check out our documentation on [how to manage DNS records](/domains-and-dns/how-to/manage-dns-records/). ## DNS zone -A DNS zone hosts the DNS records for a distinct part of the global domain namespace, and is managed by a specific organization or administrator. For example with Scaleway Domains and DNS, if you are managing the external domain `example.com` with us, this is your root zone. You can [create further zones and subdomains](/network/domains-and-dns/how-to/configure-dns-zones/), e.g. `mysubdomain.example.com`. +A DNS zone hosts the DNS records for a distinct part of the global domain namespace, and is managed by a specific organization or administrator. For example with Scaleway Domains and DNS, if you are managing the external domain `example.com` with us, this is your root zone. You can [create further zones and subdomains](/domains-and-dns/how-to/configure-dns-zones/), e.g. `mysubdomain.example.com`. ## DNS zone file diff --git a/network/domains-and-dns/how-to/add-external-domain.mdx b/network/domains-and-dns/how-to/add-external-domain.mdx index 8bd0d00788..0944d3aee4 100644 --- a/network/domains-and-dns/how-to/add-external-domain.mdx +++ b/network/domains-and-dns/how-to/add-external-domain.mdx @@ -13,12 +13,12 @@ categories: - network --- -Domains and DNS allows you to manage and register your [internal](/network/domains-and-dns/concepts/#internal-domain) and [external domains](/network/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. +Domains and DNS allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. 2. Click the **External domains** tab, then click **+ Manage new domain**. diff --git a/network/domains-and-dns/how-to/configure-autorenew.mdx b/network/domains-and-dns/how-to/configure-autorenew.mdx index 98774e206f..cbc69c1773 100644 --- a/network/domains-and-dns/how-to/configure-autorenew.mdx +++ b/network/domains-and-dns/how-to/configure-autorenew.mdx @@ -18,7 +18,7 @@ Autorenew is a feature that allows you, on a yearly basis, to automatically rene - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An internal domain registered with [Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/) ## How to activate autorenew diff --git a/network/domains-and-dns/how-to/configure-dns-zones.mdx b/network/domains-and-dns/how-to/configure-dns-zones.mdx index 477ac5e52a..4dbe58c770 100644 --- a/network/domains-and-dns/how-to/configure-dns-zones.mdx +++ b/network/domains-and-dns/how-to/configure-dns-zones.mdx @@ -13,17 +13,17 @@ categories: - network --- -A [DNS zone](/network/domains-and-dns/concepts/#dns-zone) is a distinct part of the [domain namespace](/network/domains-and-dns/concepts/#dns-namespace) that allows granular control of DNS components. +A [DNS zone](/domains-and-dns/concepts/#dns-zone) is a distinct part of the [domain namespace](/domains-and-dns/concepts/#dns-namespace) that allows granular control of DNS components. -It contains configuration stored in multiple [DNS records](/network/domains-and-dns/concepts/#dns-record). Each record consists at minimum of a type, a time to live (TTL), and a value. For example, type A records contain information to resolve a domain name to its associated IP address. +It contains configuration stored in multiple [DNS records](/domains-and-dns/concepts/#dns-record). Each record consists at minimum of a type, a time to live (TTL), and a value. For example, type A records contain information to resolve a domain name to its associated IP address. -Each **Zone Name** created translates into a [**Domain Name**](/network/domains-and-dns/concepts/#domain-name). For example, the zone `myzone` in the domain `example.com` becomes `myzone.example.com`. This works also on multiple levels, meaning that the zone `myzone.subdomain` becomes the domain name `myzone.subdomain.example.com`. +Each **Zone Name** created translates into a [**Domain Name**](/domains-and-dns/concepts/#domain-name). For example, the zone `myzone` in the domain `example.com` becomes `myzone.example.com`. This works also on multiple levels, meaning that the zone `myzone.subdomain` becomes the domain name `myzone.subdomain.example.com`. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked your domain](/network/domains-and-dns/how-to/add-external-domain/) with Scaleway DNS +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway DNS ## How to add a new DNS zone @@ -42,9 +42,9 @@ Each **Zone Name** created translates into a [**Domain Name**](/network/domains- 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays. 2. Click the domain for which you want to manage DNS records. The domain's **Overview** tab displays. 3. Click the **DNS Zones** tab. A list of DNS zones you have configured within the selected domain displays. -4. Click next to the DNS zone of your choice, then **Records** to manage the zone's [DNS records](/network/domains-and-dns/reference-content/understanding-dns-records/). +4. Click next to the DNS zone of your choice, then **Records** to manage the zone's [DNS records](/domains-and-dns/reference-content/understanding-dns-records/). 5. Click **+ Add records** to add records. -6. Select the desired [record type](/network/domains-and-dns/reference-content/understanding-dns-records/) in the drop-down, and fill out the required information. +6. Select the desired [record type](/domains-and-dns/reference-content/understanding-dns-records/) in the drop-down, and fill out the required information. 7. Click **Add records** to confirm. ## How to edit an existing DNS zone name diff --git a/network/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx b/network/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx index b5ed755ce4..ef79108b91 100644 --- a/network/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx +++ b/network/domains-and-dns/how-to/configure-dnssec-internal-domain.mdx @@ -20,7 +20,7 @@ This page shows you how to enable DNSSEC for your Domains and DNS internal domai - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An internal domain name managed with [Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/) ## How to activate DNSSEC diff --git a/network/domains-and-dns/how-to/delete-external-domain.mdx b/network/domains-and-dns/how-to/delete-external-domain.mdx index daef6a1dfb..4c4428a71b 100644 --- a/network/domains-and-dns/how-to/delete-external-domain.mdx +++ b/network/domains-and-dns/how-to/delete-external-domain.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added your domain](/network/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS screen displays. 2. Click the **External domains** tab, and click the domain you want to delete. diff --git a/network/domains-and-dns/how-to/manage-dns-records.mdx b/network/domains-and-dns/how-to/manage-dns-records.mdx index effba2658e..e8ef7575e2 100644 --- a/network/domains-and-dns/how-to/manage-dns-records.mdx +++ b/network/domains-and-dns/how-to/manage-dns-records.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked your domain](/network/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS ## How to add DNS records diff --git a/network/domains-and-dns/how-to/manage-external-domain.mdx b/network/domains-and-dns/how-to/manage-external-domain.mdx index 5354a8c4a9..072141aad8 100644 --- a/network/domains-and-dns/how-to/manage-external-domain.mdx +++ b/network/domains-and-dns/how-to/manage-external-domain.mdx @@ -18,8 +18,8 @@ Once your external domains have been created and validated, you can manage them - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Linked your domain](/network/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Linked your domain](/domains-and-dns/how-to/add-external-domain/) with Scaleway Domains and DNS 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. 2. Click the **External domains** tab. diff --git a/network/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx b/network/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx index 812c65d636..bda4cf16d3 100644 --- a/network/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx +++ b/network/domains-and-dns/how-to/manage-nameservers-internal-domain.mdx @@ -18,7 +18,7 @@ Scaleway Domains and DNS provides a managed DNS solution by providing default na - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name registered with Scaleway Domains and DNS 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays. diff --git a/network/domains-and-dns/how-to/register-internal-domain.mdx b/network/domains-and-dns/how-to/register-internal-domain.mdx index 7ddc4ddbb7..566b3a0656 100644 --- a/network/domains-and-dns/how-to/register-internal-domain.mdx +++ b/network/domains-and-dns/how-to/register-internal-domain.mdx @@ -13,13 +13,13 @@ categories: - network --- -Domains and DNS allows you to manage and register your [internal](/network/domains-and-dns/concepts/#internal-domain) and [external domains](/network/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. Domains and DNS provide support for queries via both IPv4 and IPv6. +Domains and DNS allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. Domains and DNS provide support for queries via both IPv4 and IPv6. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added a credit card](/console/billing/quickstart/#how-to-add-a-payment-method) to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The Domains and DNS dashboard displays. 2. Click **+ Search domain name**. diff --git a/network/domains-and-dns/how-to/renew-domain.mdx b/network/domains-and-dns/how-to/renew-domain.mdx index bf9a6c11d0..d947ac7bc0 100644 --- a/network/domains-and-dns/how-to/renew-domain.mdx +++ b/network/domains-and-dns/how-to/renew-domain.mdx @@ -18,8 +18,8 @@ This page shows you how to renew your domain using Scaleway Domains and DNS. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added a credit card](/console/billing/quickstart/#how-to-add-a-payment-method) to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account - Registered one or more domain names with Scaleway Domains and DNS 1. Click **Domains and DNS** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. The list of your domains displays. @@ -36,7 +36,7 @@ This page shows you how to renew your domain using Scaleway Domains and DNS. 6. Click **Renew this domain**. Your domain displays in the **Operations** tab until the renewal is complete. - You can [configure the autorenew feature](/network/domains-and-dns/how-to/configure-autorenew/) if you want to avoid renewing your domain manually. + You can [configure the autorenew feature](/domains-and-dns/how-to/configure-autorenew/) if you want to avoid renewing your domain manually. diff --git a/network/domains-and-dns/how-to/test-dns-zones-with-dig.mdx b/network/domains-and-dns/how-to/test-dns-zones-with-dig.mdx index 9f52a31230..64956df527 100644 --- a/network/domains-and-dns/how-to/test-dns-zones-with-dig.mdx +++ b/network/domains-and-dns/how-to/test-dns-zones-with-dig.mdx @@ -13,7 +13,7 @@ categories: - network --- -`Dig` or `domain information groper` is a command line tool used to query domain information on [DNS](/network/domains-and-dns/concepts/#dns) servers. You can use it to troubleshoot DNS issues. +`Dig` or `domain information groper` is a command line tool used to query domain information on [DNS](/domains-and-dns/concepts/#dns) servers. You can use it to troubleshoot DNS issues. `Dig` is installed by default on most Unix operating systems. You will however need to [install it if you are using Windows](https://www.isc.org/download/). @@ -22,8 +22,8 @@ This page shows you how to use the `dig` command to perform some common DNS test - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Added](/network/domains-and-dns/how-to/add-external-domain/) **external domains** with Scaleway Domains and DNS or not - - [Owner](/identity-and-access-management/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/identity-and-access-management/iam/concepts/#permission) + - [Added](/domains-and-dns/how-to/add-external-domain/) **external domains** with Scaleway Domains and DNS or not + - [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission) - Installed `dig` @@ -44,7 +44,7 @@ This command could be useful if you want to verify the DNS configuration of a we ## How to query a specific record type -The following command allows you to retrieve your domain's [DNAME](/network/domains-and-dns/reference-content/understanding-dns-records/#dname-record) record. This command allows you to focus on particular aspects of your domain's DNS configuration. +The following command allows you to retrieve your domain's [DNAME](/domains-and-dns/reference-content/understanding-dns-records/#dname-record) record. This command allows you to focus on particular aspects of your domain's DNS configuration. ``` dig DNAME diff --git a/network/domains-and-dns/how-to/trade-domain.mdx b/network/domains-and-dns/how-to/trade-domain.mdx index 627a6f0069..7ecda4b52f 100644 --- a/network/domains-and-dns/how-to/trade-domain.mdx +++ b/network/domains-and-dns/how-to/trade-domain.mdx @@ -13,7 +13,7 @@ categories: - network --- -Scaleway's Domains and DNS [trade](/network/domains-and-dns/concepts/#trade) feature allows you to edit your contact information for an internal domain, and update your data from the Scaleway console. +Scaleway's Domains and DNS [trade](/domains-and-dns/concepts/#trade) feature allows you to edit your contact information for an internal domain, and update your data from the Scaleway console. @@ -21,8 +21,8 @@ Scaleway's Domains and DNS [trade](/network/domains-and-dns/concepts/#trade) fea - A Scaleway account logged into the [console](https://console.scaleway.com) - Entered your credit card information on your account - - [Registered](/network/domains-and-dns/how-to/register-internal-domain/) at least one **internal domain** with Scaleway Domains and DNS - - [Owner](/identity-and-access-management/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/identity-and-access-management/iam/concepts/#permission) + - [Registered](/domains-and-dns/how-to/register-internal-domain/) at least one **internal domain** with Scaleway Domains and DNS + - [Owner](/iam/concepts/#owner) status of the Organization in which the actions will be performed, or be an IAM user with the [necessary permissions](/iam/concepts/#permission) The Domains and DNS trade feature allows you to **only edit the registrant contact information of an internal domain (to correct typing errors, for example), or information such as a company name, or a SIRET number**. diff --git a/network/domains-and-dns/how-to/transfer-external-domain.mdx b/network/domains-and-dns/how-to/transfer-external-domain.mdx index 7ce0317cc0..22e723f587 100644 --- a/network/domains-and-dns/how-to/transfer-external-domain.mdx +++ b/network/domains-and-dns/how-to/transfer-external-domain.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Added a credit card](/console/billing/quickstart/#how-to-add-a-payment-method) to your account +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Added a credit card](/billing/quickstart/#how-to-add-a-payment-method) to your account - External domains to transfer - Requested the authorization code to transfer your domain from your registrar diff --git a/network/domains-and-dns/how-to/unlock-internal-domain.mdx b/network/domains-and-dns/how-to/unlock-internal-domain.mdx index 0cd501bde1..95ae3dab9d 100644 --- a/network/domains-and-dns/how-to/unlock-internal-domain.mdx +++ b/network/domains-and-dns/how-to/unlock-internal-domain.mdx @@ -22,7 +22,7 @@ Domain names are locked by default to avoid any unsolicited outgoing transfer. I - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A domain name registered with Scaleway Domains and DNS ## How to unlock a domain name diff --git a/network/domains-and-dns/index.mdx b/network/domains-and-dns/index.mdx index ae65e21429..f36ce9a2a9 100644 --- a/network/domains-and-dns/index.mdx +++ b/network/domains-and-dns/index.mdx @@ -8,7 +8,7 @@ meta: productName="Domains and DNS" productLogo="domainsAndDns" description="Manage and register internal and external domains, and configure DNS zones with Domains and DNS." - url="/network/domains-and-dns/quickstart/" + url="/domains-and-dns/quickstart/" label="Domains and DNS Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to register internal and external domains, in a few easy steps." label="View Quickstart" - url="/network/domains-and-dns/quickstart/" + url="/domains-and-dns/quickstart/" /> diff --git a/network/domains-and-dns/quickstart.mdx b/network/domains-and-dns/quickstart.mdx index bdde70bbbc..7ebc977fff 100644 --- a/network/domains-and-dns/quickstart.mdx +++ b/network/domains-and-dns/quickstart.mdx @@ -13,12 +13,12 @@ categories: - network --- -[Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/) allows you to manage and register your [internal](/network/domains-and-dns/concepts/#internal-domain) and [external domains](/network/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. +[Scaleway Domains and DNS](https://www.scaleway.com/en/domains-and-dns/) allows you to manage and register your [internal](/domains-and-dns/concepts/#internal-domain) and [external domains](/domains-and-dns/concepts/#external-domain) and configure and manage their DNS zones. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to register an internal domain @@ -45,7 +45,7 @@ categories: 3. Enter the external domain name in the search bar and hit `Enter` to check if the domain exists. 4. Enter the number of million queries you need. The estimated cost for the domain name displays. 5. Click **Manage as external**. The instructions to set up your external domain display. -6. Copy the token displayed and [create](/network/domains-and-dns/how-to/manage-dns-records/#how-to-add-dns-records) a `TXT` record with the name `_scaleway-challenge` within your current DNS zone as instructed. +6. Copy the token displayed and [create](/domains-and-dns/how-to/manage-dns-records/#how-to-add-dns-records) a `TXT` record with the name `_scaleway-challenge` within your current DNS zone as instructed. The token's presence will be checked regularly. If it has not been set within 48 hours, the external domain will be deleted from the service. diff --git a/network/domains-and-dns/reference-content/understanding-dns-records.mdx b/network/domains-and-dns/reference-content/understanding-dns-records.mdx index 188bd91c2d..e0145c914a 100644 --- a/network/domains-and-dns/reference-content/understanding-dns-records.mdx +++ b/network/domains-and-dns/reference-content/understanding-dns-records.mdx @@ -15,7 +15,7 @@ categories: This page provides information about the different DNS record types available with Domains and DNS and how to use them. -Information in DNS zones is categorized and organized through a list of [DNS record](/network/domains-and-dns/concepts/#dns-record) types, called [resource records](/network/domains-and-dns/concepts/#resource-records) (RRs). +Information in DNS zones is categorized and organized through a list of [DNS record](/domains-and-dns/concepts/#dns-record) types, called [resource records](/domains-and-dns/concepts/#resource-records) (RRs). Each of these records has a type, an expiration time (Time to Live - TTL) and a name. Certain types of records also have type-specific data. @@ -39,14 +39,14 @@ An ALIAS record could be useful if you want your domain name (not its subdomains You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 ### CAA record -**CAA record** stands for **Certification Authority Authorization record**. It allows domain owners to specify which certificate authorities (CAs) are authorized to issue [SSL/TLS certificates](/network/domains-and-dns/concepts/#ssltls-certificates) for their domain. +**CAA record** stands for **Certification Authority Authorization record**. It allows domain owners to specify which certificate authorities (CAs) are authorized to issue [SSL/TLS certificates](/domains-and-dns/concepts/#ssltls-certificates) for their domain. This adds an extra layer of security, as it reduces the risk of unauthorized or fraudulent SSL/TLS certificates being issued by untrustworthy certificate authorities. @@ -70,12 +70,12 @@ The CAA record provided with Domains and DNS includes the following components: ### CNAME record -**CNAME record** stands for **Canonical name record**. It is used to point subdomains to a hostname. A CNAME record does not directly [resolve](/network/domains-and-dns/concepts/#domain-name-resolution) to an IP address. Instead, it refers to whether the domain is an [absolute](/network/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) or [relative](/network/domains-and-dns/concepts/#partially-qualified-domain-name-pqdn) domain. +**CNAME record** stands for **Canonical name record**. It is used to point subdomains to a hostname. A CNAME record does not directly [resolve](/domains-and-dns/concepts/#domain-name-resolution) to an IP address. Instead, it refers to whether the domain is an [absolute](/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) or [relative](/domains-and-dns/concepts/#partially-qualified-domain-name-pqdn) domain. You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 @@ -89,7 +89,7 @@ You should configure a DNAME record if you want to rename or restructure a domai You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 @@ -101,7 +101,7 @@ You should configure a DNAME record if you want to rename or restructure a domai You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 @@ -146,7 +146,7 @@ The authoritative name servers then provide the necessary DNS information to com You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 @@ -160,7 +160,7 @@ It includes details like the service's protocol, port number, priority, weight, You must end your domain with a **trailing dot** as this disables domain search, using only the complete domain name you have given.

- Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/network/domains-and-dns/concepts/#domain-name-resolution).
+ Not ending your domain name with a trailing dot results in your domain being tried with a domain name appended to it, or even a list of domain names until one [resolves](/domains-and-dns/concepts/#domain-name-resolution).

For example, if you want `mydomain.com` to point to `mynewdomain.com`, you **must** write `mynewdomain.com.` in the **Hostname** field. Otherwise, the CNAME record will direct your users to `mynewdomain.com.mynewdomain.com`.
 diff --git a/network/edge-services/concepts.mdx b/network/edge-services/concepts.mdx index 8329dcf822..5b828b9497 100644 --- a/network/edge-services/concepts.mdx +++ b/network/edge-services/concepts.mdx @@ -29,7 +29,7 @@ The CNAME record pointing your subdomain to the Edge Services endpoint, if you h ## Edge Services -Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](#origin), and a customizable and secure [endpoint](#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. ## Endpoint @@ -41,7 +41,7 @@ The endpoint can be customized with a user-defined subdomain, allowing you to re The primary source from which a Scaleway Edge Services pipeline retrieves and caches data. An origin can consist of either: -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/), or +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/), or - A [Load Balancer](#origin-load-balancer) and frontend port that Edge Services connects to to request content, and (optionally) a specified [host](#origin-host) associated with the Load Balancer, used in the HTTP request Host Header. ## Origin host @@ -58,7 +58,7 @@ The Load Balancer defined by the user as origin for a given Edge Services pipeli -An Edge Services pipeline consists of an [origin](#origin) for which Edge Services requests and [caches](#cache) content, and an [endpoint](#endpoint) from which this content is served via Edge Services. The pipeline's endpoint can be customized with a user-defined [subdomain](/network/domains-and-dns/concepts/#subdomain) and associated [certificate](#certificate) so that Edge Services can serve content over HTTPS. +An Edge Services pipeline consists of an [origin](#origin) for which Edge Services requests and [caches](#cache) content, and an [endpoint](#endpoint) from which this content is served via Edge Services. The pipeline's endpoint can be customized with a user-defined [subdomain](/domains-and-dns/concepts/#subdomain) and associated [certificate](#certificate) so that Edge Services can serve content over HTTPS. You can create an Edge Services pipeline for each of your Object Storage buckets or Load Balancer origins. Note that the cache can be enabled and disabled at will, so it is an optional part of the pipeline, as is the customization of the endpoint. diff --git a/network/edge-services/how-to/configure-custom-domain.mdx b/network/edge-services/how-to/configure-custom-domain.mdx index df883a4694..f700c23a6c 100644 --- a/network/edge-services/how-to/configure-custom-domain.mdx +++ b/network/edge-services/how-to/configure-custom-domain.mdx @@ -39,24 +39,24 @@ The procedure for adding a customized endpoint is as follows: ❌ example.com -4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/network/domains-and-dns/), or an external domain provider. Choose the appropriate tab below. +4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below. The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if: - - You [registered the domain](/network/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or - - You [transferred an externally-registered domain](/network/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS + - You [registered the domain](/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or + - You [transferred an externally-registered domain](/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS - If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/network/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6. + If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6. - You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/network/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console. + You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console. Scaleway cannot itself create the appropriate CNAME record to point your subdomain to Edge Services if your domain is managed by an external provider. You must create the CNAME record yourself. - Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/network/edge-services/reference-content/cname-record/). + Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/edge-services/reference-content/cname-record/). Back in the Scaleway console, click the `Verify CNAME` button to check whether your CNAME record has been correctly configured. Edge Services will carry out a check, and if it is successful the following message displays: @@ -68,7 +68,7 @@ The procedure for adding a customized endpoint is as follows: 5. Provide an SSL/TLS certificate for your subdomain so that Edge Services can serve traffic for it over HTTPS. You have three options for this: - Generate a free Let's Encrypt certificate, managed by Scaleway, including automatic renewals. - - Select an existing certificate that you have stored in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/). + - Select an existing certificate that you have stored in [Scaleway Secret Manager](/secret-manager/quickstart/). - Manually import a certificate into Scaleway Secret Manager: - Enter a name for your certificate (alphanumeric characters only) - Optionally, add tags by typing each tag and then pressing enter @@ -76,7 +76,7 @@ The procedure for adding a customized endpoint is as follows: Your certificate will be automatically stored in Secret Manager and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/). - For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/network/edge-services/reference-content/ssl-tls-certificate/). + For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/edge-services/reference-content/ssl-tls-certificate/). 6. Click **Customize domain** to finish. diff --git a/network/edge-services/how-to/create-pipeline-bucket.mdx b/network/edge-services/how-to/create-pipeline-bucket.mdx index 65217fa161..b7ebb6fe21 100644 --- a/network/edge-services/how-to/create-pipeline-bucket.mdx +++ b/network/edge-services/how-to/create-pipeline-bucket.mdx @@ -22,14 +22,14 @@ Read on to learn how to create an Edge Services pipeline for your Object Storage - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to create an Edge Services pipeline -You can create an Edge Services pipeline [from the Object Storage section of the console](/storage/object/how-to/get-started-edge-services/), by navigating to your bucket's dashboard and clicking the **Edge Services** tab. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console. +You can create an Edge Services pipeline [from the Object Storage section of the console](/object-storage/how-to/get-started-edge-services/), by navigating to your bucket's dashboard and clicking the **Edge Services** tab. However, in this documentation, we describe how to create a pipeline directly from the **Edge Services** section of the console. 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. @@ -52,7 +52,7 @@ You can create an Edge Services pipeline [from the Object Storage section of the - Your bucket's [visibility](/storage/object/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/storage/object/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. + Your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. @@ -65,4 +65,4 @@ Once you have created an Edge Services pipeline for your bucket, you can access | `https://bucket-name.s3.nl-ams.scw.cloud` | The **Bucket settings** tab | Edge Services is bypassed when the bucket is accessed via this endpoint | | `https://bucket-name.svc.edge.scw.cloud` | The **Edge Services** tab | Edge Services serves bucket content when this endpoint is used | -The two endpoints shown above are available as standard. However, with Edge Services, you can also choose to configure a **custom domain** from which your bucket can be accessed. Read more about this in the [next section](/network/edge-services/how-to/configure-custom-domain/). \ No newline at end of file +The two endpoints shown above are available as standard. However, with Edge Services, you can also choose to configure a **custom domain** from which your bucket can be accessed. Read more about this in the [next section](/edge-services/how-to/configure-custom-domain/). \ No newline at end of file diff --git a/network/edge-services/how-to/create-pipeline-lb.mdx b/network/edge-services/how-to/create-pipeline-lb.mdx index 479495109a..850f0a1a20 100644 --- a/network/edge-services/how-to/create-pipeline-lb.mdx +++ b/network/edge-services/how-to/create-pipeline-lb.mdx @@ -20,9 +20,9 @@ Edge Services is an additional feature for Scaleway Load Balancers and Object St - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) -- A [Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/) +- A [Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to create an Edge Services pipeline for Load Balancer @@ -36,7 +36,7 @@ You can create an Edge Services pipeline from the Load Balancer section of the c -3. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: +3. Configure the [origin](/edge-services/concepts/#origin) for this pipeline: - Select **Load Balancer** as the origin type. - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content. - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend. @@ -48,11 +48,11 @@ You can create an Edge Services pipeline from the Load Balancer section of the c 4. Define the protocol and origin host for this pipeline: - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup. - - Optionally, enter an [origin host](/network/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. + - Optionally, enter an [origin host](/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. 5. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. - The summary cost for the creation of this pipeline is displayed, notably whether it falls within the limits of your current [subscription plan](/network/edge-services/reference-content/understanding-pricing/) + The summary cost for the creation of this pipeline is displayed, notably whether it falls within the limits of your current [subscription plan](/edge-services/reference-content/understanding-pricing/) 6. Click **Create Edge Services pipeline** to finish. @@ -66,11 +66,11 @@ If you see the message `Edge Services was unable to contact the host via the Loa - **Protocol**: Ensure you did not select the wrong protocol, e.g. HTTP selected while the frontend chosen is configured to receive HTTPS, or the opposite. - **Origin host**: Ensure that you entered the correct origin host, with no typos, for a host that exists behind the selected Load Balancer. -- **Load Balancer ACLs**: Ensure that there are no [ACLs](/network/load-balancer/how-to/create-manage-acls/) configured on your Load Balancer which are blocking traffic from Edge Services. +- **Load Balancer ACLs**: Ensure that there are no [ACLs](/load-balancer/how-to/create-manage-acls/) configured on your Load Balancer which are blocking traffic from Edge Services. ## Help for Kubernetes Load Balancers -If you are setting up an Edge Services pipeline for a [Kubernetes Kapsule](/containers/kubernetes) Load Balancer, follow these steps to determine which Load Balancer and frontend to configure for your pipeline: +If you are setting up an Edge Services pipeline for a [Kubernetes Kapsule](/kubernetes) Load Balancer, follow these steps to determine which Load Balancer and frontend to configure for your pipeline: 1. Run `kubectl describe svc`. diff --git a/network/edge-services/how-to/delete-pipeline.mdx b/network/edge-services/how-to/delete-pipeline.mdx index 5f03278cdb..240cfc68f7 100644 --- a/network/edge-services/how-to/delete-pipeline.mdx +++ b/network/edge-services/how-to/delete-pipeline.mdx @@ -18,7 +18,7 @@ You can delete an Edge Services pipeline at any time by following the steps belo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An Edge Services pipeline 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. The **Pipelines** tab displays. diff --git a/network/edge-services/how-to/monitor-cockpit.mdx b/network/edge-services/how-to/monitor-cockpit.mdx index fbfeeda2a7..2f25fe6899 100644 --- a/network/edge-services/how-to/monitor-cockpit.mdx +++ b/network/edge-services/how-to/monitor-cockpit.mdx @@ -13,14 +13,14 @@ categories: - network --- -You can view your Edge Services metrics via [Scaleway Cockpit](/observability/cockpit/quickstart/). This allows you to monitor your ingress, egress, request rate, and cache hit ratio as well as other metrics, in a convenient managed Grafana dashboard. +You can view your Edge Services metrics via [Scaleway Cockpit](/cockpit/quickstart/). This allows you to monitor your ingress, egress, request rate, and cache hit ratio as well as other metrics, in a convenient managed Grafana dashboard. Access your Edge Services dashboard in the Scaleway console via either - Clicking **Track your Edge Services metrics with Cockpit** shortcut in the **Edge Services** dashboard of the pipeline in question. - The **Metrics** tab in the **Edge Services** section of the console. -Note that you will first need to [create a Grafana user and credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +Note that you will first need to [create a Grafana user and credentials](/cockpit/how-to/retrieve-grafana-credentials/). ### Understanding the dashboard diff --git a/network/edge-services/how-to/subscribe-edge-services.mdx b/network/edge-services/how-to/subscribe-edge-services.mdx index 7bc0bdd974..df1485aad4 100644 --- a/network/edge-services/how-to/subscribe-edge-services.mdx +++ b/network/edge-services/how-to/subscribe-edge-services.mdx @@ -17,25 +17,25 @@ Edge Services is an additional feature for Scaleway Load Balancers and Object St To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes: -- A fixed number of Edge Services [pipelines](/network/edge-services/concepts/#pipeline). You can create pipelines for either Load Balancers, Object Storage buckets, or a mixture of both, with your subscription plan. -- A certain amount of egress [cache](/network/edge-services/concepts/#cache) data (the quantity of data transferred from Edge Services' caches, not including the transfer from the origin bucket or Load Balancer). +- A fixed number of Edge Services [pipelines](/edge-services/concepts/#pipeline). You can create pipelines for either Load Balancers, Object Storage buckets, or a mixture of both, with your subscription plan. +- A certain amount of egress [cache](/edge-services/concepts/#cache) data (the quantity of data transferred from Edge Services' caches, not including the transfer from the origin bucket or Load Balancer). - A custom domain and SSL certificate (managed or custom) for each pipeline. If you create more pipelines than are included in your plan, or your pipelines' caches egress more data than is included, you will be charged additionally for this. The rates per pipeline/GB of data are indicated on the [pricing](https://www.scaleway.com/en/pricing/network/#edge-services) page. Subscriptions are pro-rata, meaning you can cancel your subscription or change your plan at any time, and you will be charged proportionally. -Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page. ## How to subscribe to Edge Services - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -You can subscribe to Edge Services from the Object Storage or Load Balancer dashboards of the Scaleway console. However, the instructions below detail how to describe from the dedicated Edge Services section of the console. Whichever path you use, the same pricing plans and subscription mechanisms apply. Subscribing from the Object Storage or Load Balancer dashboards does **not** limit you to only creating pipelines for that product with your subscription. Subscription plans are scoped to a single Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). +You can subscribe to Edge Services from the Object Storage or Load Balancer dashboards of the Scaleway console. However, the instructions below detail how to describe from the dedicated Edge Services section of the console. Whichever path you use, the same pricing plans and subscription mechanisms apply. Subscribing from the Object Storage or Load Balancer dashboards does **not** limit you to only creating pipelines for that product with your subscription. Subscription plans are scoped to a single Scaleway [Project](/organizations-and-projects/concepts/#project). 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. @@ -54,7 +54,7 @@ You can change your Edge Services subscription plan at any time. Subscriptions a If you upgrade your plan, any additional charges (for extra pipelines or cache data) that you had already accumulated before the time of upgrade will still stand. -Find out more about how Edge Service subscription plans and billing works, including scenarios for changing your plan mid-month, on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page. +Find out more about how Edge Service subscription plans and billing works, including scenarios for changing your plan mid-month, on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page. 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. Your Edge Services dashboard displays. diff --git a/network/edge-services/how-to/terminate-edge-services.mdx b/network/edge-services/how-to/terminate-edge-services.mdx index 9dea44dfbd..da90c90ada 100644 --- a/network/edge-services/how-to/terminate-edge-services.mdx +++ b/network/edge-services/how-to/terminate-edge-services.mdx @@ -20,9 +20,9 @@ Edge Services is an additional feature for Scaleway Load Balancers and Object St - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An active [Edge Services subscription](/network/edge-services/how-to/subscribe-edge-services/) -- [Deleted all your Edge Services pipelines](/network/edge-services/how-to/delete-pipeline/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An active [Edge Services subscription](/edge-services/how-to/subscribe-edge-services/) +- [Deleted all your Edge Services pipelines](/edge-services/how-to/delete-pipeline/) You can terminate your Edge Services subscription at any time, as long as you have deleted all your pipelines. You will be charged pro-rata for the month you cancel, based on how much of that month your subscription was active. diff --git a/network/edge-services/index.mdx b/network/edge-services/index.mdx index bbb72cca7e..d9b7221d92 100644 --- a/network/edge-services/index.mdx +++ b/network/edge-services/index.mdx @@ -8,14 +8,14 @@ meta: sentiment="info" title="Edge Services is now in General Availability!" > - Edge Services for Object Storage and Load Balancers is now in General Availability, and a subscription-based pricing plan applies. Find out more in our [dedicated documentation](/network/edge-services/reference-content/understanding-ga/). + Edge Services for Object Storage and Load Balancers is now in General Availability, and a subscription-based pricing plan applies. Find out more in our [dedicated documentation](/edge-services/reference-content/understanding-ga/). @@ -27,28 +27,28 @@ meta: icon="rocket" description="Learn how to create an Edge Services pipeline." label="View Quickstart" - url="/network/edge-services/quickstart/" + url="/edge-services/quickstart/" /> diff --git a/network/edge-services/quickstart.mdx b/network/edge-services/quickstart.mdx index e3b59645eb..5b4dec08a9 100644 --- a/network/edge-services/quickstart.mdx +++ b/network/edge-services/quickstart.mdx @@ -13,7 +13,7 @@ categories: - networks --- -Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/network/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/network/edge-services/concepts/#origin), and a customizable and secure [endpoint](/network/edge-services/concepts/#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. +Edge Services is an additional feature for Scaleway Load Balancers and Object Storage buckets. It provides a [caching service](/edge-services/how-to/configure-cache/) to improve performance by reducing load on your [origin](/edge-services/concepts/#origin), and a customizable and secure [endpoint](/edge-services/concepts/#endpoint) for accessing content via Edge Services, which can be set to a subdomain of your choice. To use Edge Services, you must take out a subscription plan, which then enables you to create a certain number of Edge Services pipelines towards your Load Balancer origins or Object Storage buckets. @@ -22,14 +22,14 @@ To use Edge Services, you must take out a subscription plan, which then enables - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created either a [Load Balancer](/network/load-balancer/how-to/create-load-balancer/) or an [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created either a [Load Balancer](/load-balancer/how-to/create-load-balancer/) or an [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to subscribe to Edge Services To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan includes a fixed number of pipelines, and a certain amount of egress cache data. Any consumption that exceeds the limits of the plan is charged at an additional rate. -Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page, or follow the steps below to subscribe. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page, or follow the steps below to subscribe. 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. @@ -41,7 +41,7 @@ Find out more about how Edge Service subscription plans and billing works on our ## How to create an Edge Services pipeline -You can create [pipelines](/network/edge-services/concepts/#pipeline) for either Object Storage buckets or Load Balancer origins. +You can create [pipelines](/edge-services/concepts/#pipeline) for either Object Storage buckets or Load Balancer origins. 1. Click **Edge Services** in the **Network** section of the [Scaleway console](https://console.scaleway.com/) side menu. @@ -56,19 +56,19 @@ You can create [pipelines](/network/edge-services/concepts/#pipeline) for either - 4. Configure the [origin](/network/edge-services/concepts/#origin) for this pipeline: + 4. Configure the [origin](/edge-services/concepts/#origin) for this pipeline: - Select **Load Balancer** as the origin type. - Select the **origin Load Balancer** from the dropdown list. The Edge Services pipeline will connect to this Load Balancer when requesting content. - Select a **frontend** associated with the origin Load Balancer from the dropdown list. The Edge Services pipeline will connect to the Load Balancer on this port when requesting content. We recommend that you select an HTTPS port, e.g. `443`. Note that if you are creating multiple pipelines for the same origin Load Balancer, each one must be configured for a different frontend. - For Kubernetes Load Balancers, see our [dedicated documentation](/network/edge-services/how-to/create-pipeline-lb/#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. + For Kubernetes Load Balancers, see our [dedicated documentation](/edge-services/how-to/create-pipeline-lb/#help-for-kubernetes-load-balancers) for help selecting the correct Load Balancer and frontend. 5. Define the protocol and origin host for this pipeline: - Select the protocol that Edge Services should use when making requests to the origin, either `HTTP` or `HTTPS` (recommended). Choose the protocol that corresponds with your Load Balancer setup. - - Optionally, enter an [origin host](/network/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. + - Optionally, enter an [origin host](/edge-services/concepts/#origin-host) associated with your Load Balancer for this pipeline. When specified, this host replaces the Load Balancer IP address in the HTTP Host Header of the requests made from Edge Services to your Load Balancer. 6. Enter a name for this Edge Services pipeline, or leave the auto-generated name in place. @@ -88,7 +88,7 @@ You can create [pipelines](/network/edge-services/concepts/#pipeline) for either 7. Check the summary cost for the pipeline, and click **Create Edge Services pipeline**. - Your bucket's [visibility](/storage/object/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/storage/object/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. + Your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. @@ -116,24 +116,24 @@ If you already own a domain, you can customize an Edge Services pipeline endpoin ❌ example.com -4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/network/domains-and-dns/), or an external domain provider. Choose the appropriate tab below. +4. This step depends on whether the domain used in the previous step is managed with [Scaleway Domains and DNS](/domains-and-dns/), or an external domain provider. Choose the appropriate tab below. The domain you are using for Edge Services is considered to be managed with Scaleway Domains and DNS if: - - You [registered the domain](/network/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or - - You [transferred an externally-registered domain](/network/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS + - You [registered the domain](/domains-and-dns/how-to/register-internal-domain/) with Domains and DNS, or + - You [transferred an externally-registered domain](/domains-and-dns/how-to/transfer-external-domain/) to Domains and DNS - If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/network/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6. + If either of the above is true, Scaleway will auto-detect that the domain is managed by Domains and DNS, and a message will display confirming that you do not need to create a CNAME record. We will auto-generate the appropriate CNAME record in your domain's [DNS records](/domains-and-dns/how-to/manage-dns-records/), to point your subdomain to the Edge Services endpoint. This record is generated when you click `Customize domain` in step 6. - You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/network/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console. + You should not attempt to modify or delete the CNAME record, which will be visible among your [DNS records](/domains-and-dns/how-to/manage-dns-records/) in the Scaleway console. Scaleway cannot itself create the appropriate CNAME record to point your subdomain to Edge Services if your domain is managed by an external provider. You must create the CNAME record yourself. - Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/network/edge-services/reference-content/cname-record/). + Log in to your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services pipeline endpoint displayed in the Scaleway console. For help setting up CNAME records and troubleshooting any problems, [check out our dedicated documentation](/edge-services/reference-content/cname-record/). Back in the Scaleway console, click the `Verify CNAME` button to check whether your CNAME record has been correctly configured. Edge Services will carry out a check, and if it is successful the following message displays: @@ -145,7 +145,7 @@ If you already own a domain, you can customize an Edge Services pipeline endpoin 5. Provide an SSL/TLS certificate for your subdomain so that Edge Services can serve traffic for it over HTTPS. You have three options for this: - Generate a free Let's Encrypt certificate, managed by Scaleway, including automatic renewals. - - Select an existing certificate that you have stored in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/). + - Select an existing certificate that you have stored in [Scaleway Secret Manager](/secret-manager/quickstart/). - Manually import a certificate into Scaleway Secret Manager: - Enter a name for your certificate (alphanumeric characters only) - Optionally, add tags by typing each tag and then pressing enter @@ -153,7 +153,7 @@ If you already own a domain, you can customize an Edge Services pipeline endpoin Your certificate will be automatically stored in Secret Manager and [billed accordingly](https://www.scaleway.com/en/pricing/security-and-account/). - For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/network/edge-services/reference-content/ssl-tls-certificate/). + For help with SSL/TLS certificates for Edge Services, and/or dealing with any errors you encounter importing a certificate into Secret Manager, see our [dedicated documentation](/edge-services/reference-content/ssl-tls-certificate/). 6. Click **Customize domain** to finish. @@ -184,7 +184,7 @@ You can disable and enable caching at will, as well as control the lifetime of a The cache is now enabled. -For information on purging your cache, see our [dedicated documentation](/network/edge-services/how-to/configure-cache/). +For information on purging your cache, see our [dedicated documentation](/edge-services/how-to/configure-cache/). ## How to delete an Edge Services pipeline diff --git a/network/edge-services/reference-content/cname-record.mdx b/network/edge-services/reference-content/cname-record.mdx index 5506012aed..15a7a184b3 100644 --- a/network/edge-services/reference-content/cname-record.mdx +++ b/network/edge-services/reference-content/cname-record.mdx @@ -12,11 +12,11 @@ categories: - network --- -This document contains information to help you successfully create a CNAME record for your customized [Edge Services](/network/edge-services/) domain, and troubleshoot any potential DNS problems. +This document contains information to help you successfully create a CNAME record for your customized [Edge Services](/edge-services/) domain, and troubleshoot any potential DNS problems. ## What is a CNAME record? -A **C**anonical **Name** (CNAME) record is a type of [DNS record](/network/domains-and-dns/concepts/#dns-record). Generally, DNS records hold information for translating a domain or subdomain to an IP address, mail server or other domain/subdomain. They are crucial in directing internet traffic to the correct servers. More specifically, CNAME records map one domain name (an alias) to another (the canonical name). +A **C**anonical **Name** (CNAME) record is a type of [DNS record](/domains-and-dns/concepts/#dns-record). Generally, DNS records hold information for translating a domain or subdomain to an IP address, mail server or other domain/subdomain. They are crucial in directing internet traffic to the correct servers. More specifically, CNAME records map one domain name (an alias) to another (the canonical name). A CNAME record may look like the following: @@ -24,17 +24,17 @@ A CNAME record may look like the following: |----------------------------|-------------------------------| | `videos.example.com` | `otherdomain.com` | -In this case, when a DNS server sees this record for `videos.example.com` it will know not to direct traffic to `videos.example.com`'s own IP address, but to that of `otherdomain.com`. It will find `othercomain.com`'s IP address via its [A record](/network/domains-and-dns/reference-content/understanding-dns-records/#a-record). +In this case, when a DNS server sees this record for `videos.example.com` it will know not to direct traffic to `videos.example.com`'s own IP address, but to that of `otherdomain.com`. It will find `othercomain.com`'s IP address via its [A record](/domains-and-dns/reference-content/understanding-dns-records/#a-record). When the client actually connects to `otherdomain.com`'s IP address, the web server can see that the requested URL was `videos.example.com`, and deliver the relevant content. ## When and why do I need to create a CNAME record for Edge Services? -When you create an Edge Services pipeline to an [origin](/network/edge-services/concepts/#origin) (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. `pipeline-id-or-bucket-name.svc.edge.scw.cloud`. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records. +When you create an Edge Services pipeline to an [origin](/edge-services/concepts/#origin) (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. `pipeline-id-or-bucket-name.svc.edge.scw.cloud`. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records. -However, if you choose to [customize your Edge Services endpoint with your own subdomain](/network/edge-services/how-to/configure-custom-domain/), a CNAME record must be created to point your subdomain to the Edge Services endpoint. +However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), a CNAME record must be created to point your subdomain to the Edge Services endpoint. - - If your domain is managed with [Scaleway Domains and DNS](/network/domains-and-dns/quickstart/), we take care of auto-generating the appropriate CNAME record for you, as well as deleting it if and when you deactivate Edge Services. There is no action for you to take. You should not attempt to modify or delete the CNAME record (which will be visible among your Domains and DNS records in the console). + - If your domain is managed with [Scaleway Domains and DNS](/domains-and-dns/quickstart/), we take care of auto-generating the appropriate CNAME record for you, as well as deleting it if and when you deactivate Edge Services. There is no action for you to take. You should not attempt to modify or delete the CNAME record (which will be visible among your Domains and DNS records in the console). - If your domain is managed by an external provider, Scaleway is unable to create the appropriate CNAME record for you. You will be prompted, as part of the process for customizing your Edge Services domain, to create this record yourself with your domain provider. @@ -83,7 +83,7 @@ See the table below for help with troubleshooting these errors: |-------------------------------------------|---------------------------------------------------------------------| | No CNAME record found | Make sure you have created a valid DNS record of type **CNAME** (not **A**, **AAAA** or another type), where your subdomain points to the Edge Services endpoint. | | Incorrect CNAME | Make sure your CNAME record points to the Edge Services endpoint in the format `bucket-name.svc.edge.scw.cloud.`, and that you have replaced `pipeline-id-or-bucket-name` with the name of your bucket in the case of an Object Storage origin, or the pipeline ID in the case of a Load Balancer origin. | -| Domain does not exist | You must own the domain name you are attempting to configure. If you do not already own the domain name, you cannot create a subdomain or CNAME record for it. Register the domain name, for example using our [Domains and DNS](/network/domains-and-dns/how-to/register-internal-domain/) product, then create a CNAME record for the subdomain. Otherwise, ensure you did not make a typo when entering the domain name into the Scaleway console. | +| Domain does not exist | You must own the domain name you are attempting to configure. If you do not already own the domain name, you cannot create a subdomain or CNAME record for it. Register the domain name, for example using our [Domains and DNS](/domains-and-dns/how-to/register-internal-domain/) product, then create a CNAME record for the subdomain. Otherwise, ensure you did not make a typo when entering the domain name into the Scaleway console. | | scw.cloud is forbidden | You cannot use subdomains of the `scw.cloud` domain, as the domain is owned and managed by Scaleway and you cannot create DNS records for it. Use your own domain and subdomain. | | Invalid Top Level Domain | Make sure the Top-Level Domain (e.g. `.com`, `.fr`) you entered is correct. | | Root domain not allowed | You cannot use a root domain alone to customize Edge Services (e.g. `example.com`. Make sure you use a subdomain (e.g. `blog.example.com`)) | | diff --git a/network/edge-services/reference-content/ssl-tls-certificate.mdx b/network/edge-services/reference-content/ssl-tls-certificate.mdx index 3517a68225..d9f6431f37 100644 --- a/network/edge-services/reference-content/ssl-tls-certificate.mdx +++ b/network/edge-services/reference-content/ssl-tls-certificate.mdx @@ -12,7 +12,7 @@ categories: - network --- -This document contains information to help you with SSL/TLS certificates that enable your origin bucket or Load Balancer content to be served over HTTPS, through your customized [Edge Services](/network/edge-services/) domain. +This document contains information to help you with SSL/TLS certificates that enable your origin bucket or Load Balancer content to be served over HTTPS, through your customized [Edge Services](/edge-services/) domain. ## Introduction @@ -28,9 +28,9 @@ The private key is also used by the host for generating digital signatures, whil ### When and why do I need an SSL/TLS certificate for Edge Services? -When you create an Edge Services pipeline, initially your [origin's](/network/edge-services/concepts/#origin) content is served through the standard Edge Services endpoint, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. Scaleway's own SSL/TLS certificate, which covers this subdomain, is used to establish the encrypted connection between client and host. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about creating SSL/TLS certificates. +When you create an Edge Services pipeline, initially your [origin's](/edge-services/concepts/#origin) content is served through the standard Edge Services endpoint, e.g. `https://pipeline-id-or-bucket-name.svc.edge.scw.cloud`. Scaleway's own SSL/TLS certificate, which covers this subdomain, is used to establish the encrypted connection between client and host. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about creating SSL/TLS certificates. -However, if you choose to [customize your Edge Services endpoint with your own subdomain](/network/edge-services/how-to/configure-custom-domain/), Scaleway's own SSL/TLS certificate can no longer be used to establish encrypted connections to your subdomain. Client connections are now initially going to a different domain which needs to be "guaranteed" by its own certificate (despite the CNAME record for the subdomain pointing to the Scaleway endpoint). +However, if you choose to [customize your Edge Services endpoint with your own subdomain](/edge-services/how-to/configure-custom-domain/), Scaleway's own SSL/TLS certificate can no longer be used to establish encrypted connections to your subdomain. Client connections are now initially going to a different domain which needs to be "guaranteed" by its own certificate (despite the CNAME record for the subdomain pointing to the Scaleway endpoint). Therefore, when you customize your Edge Services endpoint with a subdomain, you are prompted to generate or upload an SSL/TLS certificate for that subdomain. @@ -40,11 +40,11 @@ Even if you have an Edge Services pipeline for a Load Balancer origin, and you h ## How can I provide an SSL/TLS certificate for my Edge Services customized domain? -You will be prompted to choose one of the following options when [customizing your domain](/network/edge-services/how-to/configure-custom-domain/): +You will be prompted to choose one of the following options when [customizing your domain](/edge-services/how-to/configure-custom-domain/): - **Generate a Let's Encrypt certificate**: Scaleway generates a free, managed Let's Encrypt certificate for your domain and automatically renews it as necessary. -- **Select an existing certificate from Secret Manager**: You select a certificate that you have already uploaded in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/). +- **Select an existing certificate from Secret Manager**: You select a certificate that you have already uploaded in [Scaleway Secret Manager](/secret-manager/quickstart/). - **Manually import a certificate into Secret Manager**: You can manually create your own certificate and import it. It will be stored in Scaleway Secret Manager (check the [dedicated pricing page](https://www.scaleway.com/en/pricing/?tags=securityandidentity)). @@ -52,7 +52,7 @@ You will be prompted to choose one of the following options when [customizing yo This is the hassle-free option if you do not want to create or manage your own SSL/TLS certificate. Scaleway takes care of generating a certificate for your customized domain in the correct format. The certificate is automatically renewed before it expires. This option is available for free: it costs you nothing for Scaleway to generate and manage a Let's Encrypt certificate for your domain. -You must ensure that you have correctly set the [CNAME record](/network/edge-services/reference-content/cname-record/) for your domain. Without having done this, the Let's Encrypt certificate option in the console will not be available. It is also important to check the CNAME is correctly set up so that the certificate is properly generated and reviewed. +You must ensure that you have correctly set the [CNAME record](/edge-services/reference-content/cname-record/) for your domain. Without having done this, the Let's Encrypt certificate option in the console will not be available. It is also important to check the CNAME is correctly set up so that the certificate is properly generated and reviewed. Note that you will not have access to the generated certificate itself in Secret Manager or elsewhere. It is entirely generated and managed "behind the scenes", and is not configurable by the user. If you reset your domain, or delete your Edge Services, Scaleway automatically deletes the generated Let's Encrypt certificate. @@ -65,8 +65,8 @@ If there is a problem generating your managed Let's Encrypt certificate, an erro | Error | Solution | | ------------------------------------------------------------------------|---------------------------------------------------------------------| | Too many certificates already issued for this domain | Wait, before retrying. This error occurs when you hit the limit of generating 50 Let's Encrypt certificates in a rolling 7 day period for the same domain. | -| Internal managed certificate error | There has been an unspecified error in generating a managed Let's Encrypt certificate for your subdomain. Try [resetting your domain to the default endpoint](/network/edge-services/how-to/configure-custom-domain/#how-to-reset-your-customized-domain), and then recustomizing it again, to trigger generation of a new Let's Encrypt certificate. If that fails, [open a support ticket](https://console.scaleway.com/support/tickets/create). | -| Certificate cannot be renewed - Your CNAME record is no longer accurate | Your CNAME record has either been deleted or modified. Without a correct CNAME record, we cannot renew your managed Let's Encrypt certificate. [Rectify your CNAME record](/network/edge-services/reference-content/cname-record/#how-to-create-a-cname-record), and when Edge Services detects the correct record exists, your certificate will be automatically renewed. | +| Internal managed certificate error | There has been an unspecified error in generating a managed Let's Encrypt certificate for your subdomain. Try [resetting your domain to the default endpoint](/edge-services/how-to/configure-custom-domain/#how-to-reset-your-customized-domain), and then recustomizing it again, to trigger generation of a new Let's Encrypt certificate. If that fails, [open a support ticket](https://console.scaleway.com/support/tickets/create). | +| Certificate cannot be renewed - Your CNAME record is no longer accurate | Your CNAME record has either been deleted or modified. Without a correct CNAME record, we cannot renew your managed Let's Encrypt certificate. [Rectify your CNAME record](/edge-services/reference-content/cname-record/#how-to-create-a-cname-record), and when Edge Services detects the correct record exists, your certificate will be automatically renewed. | ## Using your own certificate @@ -82,7 +82,7 @@ Types of validation: Types of domain coverage: -- ✅ **Single domain certificate**. Secures a single domain or subdomain. Note that the certificate must be for `your-sub.domain.com`, where the subdomain corresponds to the [subdomain for Edge Services](/network/edge-services/how-to/configure-custom-domain/). A single domain certificate simply for `yourdomain.com` would not be acceptable, as it would not cover the subdomain for Edge Services. +- ✅ **Single domain certificate**. Secures a single domain or subdomain. Note that the certificate must be for `your-sub.domain.com`, where the subdomain corresponds to the [subdomain for Edge Services](/edge-services/how-to/configure-custom-domain/). A single domain certificate simply for `yourdomain.com` would not be acceptable, as it would not cover the subdomain for Edge Services. - ✅ **Wildcard certificate**. Secures multiple subdomains for a domain, using a wildcard `*` symbol. The **Common Name** of the certificate should look like `*.yourdomain.com`. - ✅ **Multi-domain (MD) / Subject Alternative Name (SAN) / Unified Communications Certificate (UCC) certificate**. Secures multiple explicitly-defined fully qualified domain names (`www.yourfirstdomain.com`, `sub.yourfirstdomain.com`, `yourfirstdomain.com`, `yourseconddomain.com`, `sub.yourseconddomain.com` etc.) @@ -173,9 +173,9 @@ To get a working Let's Encrypt certificate using certbot on the command line, fo ### Uploading your certificate -When you [configure your customized domain](/network/edge-services/how-to/configure-custom-domain/) with Edge Services for the first time, you are prompted to upload your certificate. You can do so in two ways: +When you [configure your customized domain](/edge-services/how-to/configure-custom-domain/) with Edge Services for the first time, you are prompted to upload your certificate. You can do so in two ways: - - Select an existing certificate that you have stored in a secret in [Scaleway Secret Manager](/identity-and-access-management/secret-manager/quickstart/). The secret must be of the **certificate** type in order to be visible to Edge Services. The type can be defined when creating a secret via the [API](https://www.scaleway.com/en/developers/api/secret-manager/#path-secrets-create-a-secret), but not via the console. For that reason, if you prefer to use the console to create your certificates, we suggest using the next option: + - Select an existing certificate that you have stored in a secret in [Scaleway Secret Manager](/secret-manager/quickstart/). The secret must be of the **certificate** type in order to be visible to Edge Services. The type can be defined when creating a secret via the [API](https://www.scaleway.com/en/developers/api/secret-manager/#path-secrets-create-a-secret), but not via the console. For that reason, if you prefer to use the console to create your certificates, we suggest using the next option: - Manually import a certificate into Scaleway Secret Manager, directly from the Edge Services **Configure domain** wizard (copy and paste the PEM formatted chain). Your certificate will be automatically stored in Secret Manager, held in a secret that automatically inherits the type "certificate". ### Keeping your certificate up to date @@ -186,11 +186,11 @@ SSL/TLS certificates all expire at some point. If your certificate expires befor You must renew your certificate or create a new one. A number of tools are available to ensure that certificates are automatically renewed before expiry, for example [Certbot for LetsEncrypt](https://eff-certbot.readthedocs.io/en/stable/using.html#renewing-certificates). However, since Certbot or other tools for automatically renewing certificates are not currently integrated into Edge Services, you will need to manually update the certificate via the Scaleway console. -When you have your up to date certificate, go to [Secret Manager](https://console.scaleway.com/secret-manager/secrets) in the console, and access the secret that contains your certificate. [Create a new version](/identity-and-access-management/secret-manager/how-to/create-version/) of the secret, to hold the up to date certificate. Edge Services will automatically detect and use the most recent enabled version of the secret. You can nonetheless choose to disable or delete the old version(s) as you prefer, which will also save your billing costs (since you are billed per version). +When you have your up to date certificate, go to [Secret Manager](https://console.scaleway.com/secret-manager/secrets) in the console, and access the secret that contains your certificate. [Create a new version](/secret-manager/how-to/create-version/) of the secret, to hold the up to date certificate. Edge Services will automatically detect and use the most recent enabled version of the secret. You can nonetheless choose to disable or delete the old version(s) as you prefer, which will also save your billing costs (since you are billed per version). -If you change your customized subdomain to something new, you will need to generate and import a new certificate for that subdomain. In this case, it is recommended to create a new [secret](/identity-and-access-management/secret-manager/concepts/#secret) to hold the new certificate, rather than creating a new version of an existing secret. +If you change your customized subdomain to something new, you will need to generate and import a new certificate for that subdomain. In this case, it is recommended to create a new [secret](/secret-manager/concepts/#secret) to hold the new certificate, rather than creating a new version of an existing secret. @@ -222,9 +222,9 @@ However, these errors may also be detected and displayed on your Edge Services d To fix the problem, you must generate a valid certificate, and then do one of the following: -- [Use Edge Services to import a new certificate directly](/network/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate) -- [Create a new secret](/identity-and-access-management/secret-manager/how-to/create-secret/) to hold the certificate in Secret Manager, and [edit your customized endpoint with Edge services](/network/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate) to tell it to use this secret -- [Create a new version](/identity-and-access-management/secret-manager/how-to/create-version/) of the existing secret holding your expired certificate, where the new version contains a valid certificate. If Edge Services is already using this secret, it will automatically detect and use the new version - it always uses the most recent enabled version of a secret. +- [Use Edge Services to import a new certificate directly](/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate) +- [Create a new secret](/secret-manager/how-to/create-secret/) to hold the certificate in Secret Manager, and [edit your customized endpoint with Edge services](/edge-services/how-to/configure-custom-domain/#how-to-edit-your-customized-domain-or-its-certificate) to tell it to use this secret +- [Create a new version](/secret-manager/how-to/create-version/) of the existing secret holding your expired certificate, where the new version contains a valid certificate. If Edge Services is already using this secret, it will automatically detect and use the new version - it always uses the most recent enabled version of a secret. #### Secret not visible for selection in Edge Services diff --git a/network/edge-services/reference-content/understanding-ga.mdx b/network/edge-services/reference-content/understanding-ga.mdx index b1c529d0bc..8eadb53a03 100644 --- a/network/edge-services/reference-content/understanding-ga.mdx +++ b/network/edge-services/reference-content/understanding-ga.mdx @@ -53,7 +53,7 @@ If you did not wish to be billed for Edge Services, you were warned that you mus ### Estimating your billing and understanding pricing -Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/network/edge-services/reference-content/understanding-pricing/) page. +Find out more about how Edge Service subscription plans and billing works on our [Understanding Edge Services pricing](/edge-services/reference-content/understanding-pricing/) page. ## Further support diff --git a/network/edge-services/reference-content/understanding-pricing.mdx b/network/edge-services/reference-content/understanding-pricing.mdx index fb8cc0c9d8..7b923a02ce 100644 --- a/network/edge-services/reference-content/understanding-pricing.mdx +++ b/network/edge-services/reference-content/understanding-pricing.mdx @@ -25,18 +25,18 @@ Edge Services billing is based on [monthly subscription plans](https://www.scale When you subscribe to a plan, you are billed its flat monthly fee, which allows you to: -- Run a fixed maximum number of Edge Services [pipelines](/network/edge-services/concepts/#pipeline) for the month. They can be for Object Storage or Load Balancer origins, or a mixture of both. -- Egress a fixed maximum amount of data from all your pipelines' [caches](/network/edge-services/concepts/#cache). +- Run a fixed maximum number of Edge Services [pipelines](/edge-services/concepts/#pipeline) for the month. They can be for Object Storage or Load Balancer origins, or a mixture of both. +- Egress a fixed maximum amount of data from all your pipelines' [caches](/edge-services/concepts/#cache). If you subscribe to a plan, and exceed its monthly limits for pipelines or cache data, you will incur additional charges that month. Essentially, your Edge Services monthly bill is made up of your **monthly subscription plan price** + **any additional pipeline charges incurred** + **any additional cache charges incurred**. -For full details of the price and limits of each plan, refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services). Subscription plans are scoped to a single Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). +For full details of the price and limits of each plan, refer to the [pricing page](https://www.scaleway.com/en/pricing/network/#edge-services). Subscription plans are scoped to a single Scaleway [Project](/organizations-and-projects/concepts/#project). ## Keeping track of your Edge Services consumption -You can check the number of pipelines you have at any one time in the **Pipelines** tab of the Edge Services dashboard in the Scaleway console. [Scaleway Cockpit](/network/edge-services/how-to/monitor-cockpit/) can be used to monitor the data egressing from your Edge Services caches. +You can check the number of pipelines you have at any one time in the **Pipelines** tab of the Edge Services dashboard in the Scaleway console. [Scaleway Cockpit](/edge-services/how-to/monitor-cockpit/) can be used to monitor the data egressing from your Edge Services caches. ## Included usage vs additional charges diff --git a/network/interlink/concepts.mdx b/network/interlink/concepts.mdx index 8b40d4db3c..a80940313d 100644 --- a/network/interlink/concepts.mdx +++ b/network/interlink/concepts.mdx @@ -22,7 +22,7 @@ InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), an The default rule blocks any and all routes from being propagated over InterLink. Attaching an allowed routes list (aka **routing policy**) allows you to define the ranges of routes that should be whitelisted. When creating an allowed routes list, you specify one or many IP ranges representing the outgoing routes to announce from the Scaleway VPC, and one or many IP ranges representing the incoming route announcements to accept from the external infrastructure. -Each InterLink can have one allowed routes list attached to it, but a single allowed routes list can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the allowed routes list are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/network/interlink/reference-content/overview/#routing-across-an-interLink) +Each InterLink can have one allowed routes list attached to it, but a single allowed routes list can be attached to multiple InterLinks, if desired. When [route propagation](#route-propagation) is activated, the route ranges defined in the allowed routes list are whitelisted, and traffic can flow across the InterLink along these routes. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink) You may also know allowed routes lists under the terms "routing policy", or "route filters". @@ -42,7 +42,7 @@ Currently, InterLink is available in **hosted** version only. This means that yo -For more information on how InterLink works, see our [detailed overview](/network/interlink/reference-content/overview/). +For more information on how InterLink works, see our [detailed overview](/interlink/reference-content/overview/). ## Location @@ -56,7 +56,7 @@ A pairing key is a unique identifier used to establish and authenticate an Inter A partner is a third party service provider that facilitates a hosted InterLink connection between a client's on-premises infrastructure, and their Scaleway infrastructure. Current partners include [Free Pro](https://pro.free.fr/), with more coming soon. -Partners are generally companies specialized in data transit, with their own fibers at data connection points. To establish an InterLink connection via a partner, generally you must be client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. See our information on [hosted InterLinks](/network/interlink/reference-content/overview/#hosted-interlinks) for more information. +Partners are generally companies specialized in data transit, with their own fibers at data connection points. To establish an InterLink connection via a partner, generally you must be client of that partner, e.g. with your infrastructure in their datacenter, or on your own premises using the partner as a network provider. See our information on [hosted InterLinks](/interlink/reference-content/overview/#hosted-interlinks) for more information. ## PoP @@ -64,11 +64,11 @@ See [Location](#location) ## Region -When creating an InterLink, you must specify a [region](/network/vpc/concepts/#region-and-availability-zone) for the resource. The region sets the scope for the Scaleway infrastructure that can be connected via the InterLink: it must correspond to the region of the VPC to attach to the InterLink. +When creating an InterLink, you must specify a [region](/vpc/concepts/#region-and-availability-zone) for the resource. The region sets the scope for the Scaleway infrastructure that can be connected via the InterLink: it must correspond to the region of the VPC to attach to the InterLink. ## Route propagation -Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must use an [allowed routes list](#allowed-routes-list) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/network/interlink/reference-content/overview/#routing-across-an-interLink) +Route propagation can be activated or deactivated at any given time on an InterLink. When activated, the Scaleway VPC and external infrastructure dynamically exchange and update information about their routes. Route propagation must be activated to allow traffic to flow over the InterLink. When deactivated, all pre-learned/announced routes are removed from the VPC's route table, and traffic cannot flow. Note that even with route propagation activated, the default rule blocks all route announcements: you must use an [allowed routes list](#allowed-routes-list) to specify the route ranges to whitelist. [Learn more about routing across an InterLink](/interlink/reference-content/overview/#routing-across-an-interLink) ## Routing policy diff --git a/network/interlink/index.mdx b/network/interlink/index.mdx index b52b540cc3..f9ec0575fe 100644 --- a/network/interlink/index.mdx +++ b/network/interlink/index.mdx @@ -16,7 +16,7 @@ meta: productName="InterLink" productLogo="interlink" description="InterLink lets you create a secure, private connection between your external infrastructure, and your Scaleway VPC." - url="/network/interlink/reference-content/overview/" + url="/interlink/reference-content/overview/" label="InterLink Overview" /> @@ -28,14 +28,14 @@ meta: icon="info" description="Core concepts that give you a better understanding of InterLink." label="View Concepts" - url="/network/interlink/concepts/" + url="/interlink/concepts/" /> diff --git a/network/interlink/reference-content/configuring.mdx b/network/interlink/reference-content/configuring.mdx index a22ea39326..74a423e8c9 100644 --- a/network/interlink/reference-content/configuring.mdx +++ b/network/interlink/reference-content/configuring.mdx @@ -19,7 +19,7 @@ dates: InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers. -Once your InterLink has been created and the [provisioning process](/network/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink. +Once your InterLink has been created and the [provisioning process](/interlink/reference-content/provisioning/) is complete, you must complete a number of configuration steps to enable traffic to flow across the InterLink. This document explains the process in full, and gives tips for troubleshooting any potential issues. @@ -33,9 +33,9 @@ Read more about each step, and possible errors at each stage, in the following s ### 1. Create the InterLink -Creating an InterLink is itself a multi-step process, that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/network/interlink/reference-content/provisioning/). +Creating an InterLink is itself a multi-step process, that requires action on both the Scaleway side, and on the partner side. This process is explained in full in [Provisioning an InterLink](/interlink/reference-content/provisioning/). -You must wait until the InterLink has reached `Active` [status](/network/interlink/reference-content/statuses/) before you can continue with the following configuration steps. +You must wait until the InterLink has reached `Active` [status](/interlink/reference-content/statuses/) before you can continue with the following configuration steps. ### 2. Attach VPC @@ -47,7 +47,7 @@ You can use the [Attach a VPC](https://www.scaleway.com/en/developers/api/interl ### 3. Attach allowed routes list (routing policy) -InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked** . You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) aka routing policy, to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. +InterLink uses [**B**order **G**ateway **P**rotocol](https://en.wikipedia.org/wiki/Border_Gateway_Protocol) to exchange routing information between the customer’s infrastructure and the Scaleway VPC. Each side advertises IP prefixes for its own internal subnets and resources, to allow the other side to dynamically learn and update its internal routes, facilitating efficient traffic flow. However, by default, **all routes across an InterLink are blocked** . You must create and attach an [allowed routes list](/interlink/concepts/#allowed-routes-list) aka routing policy, to set IP prefix filters for the route advertisements you want to whitelist. This facilitates traffic flow across the InterLink. You can [create](https://www.scaleway.com/en/developers/api/interlink/#path-routing-policies-create-a-routing-policy) and [attach](https://www.scaleway.com/en/developers/api/interlink/#path-links-attach-a-routing-policy) allowed routes lists via the API. @@ -60,7 +60,7 @@ Only one allowed routes list (routing policy) can be attached to an InterLink at Once you have attached a VPC and defined the routing policy/allowed routes, you must [activate route propagation](https://www.scaleway.com/en/developers/api/interlink/#path-links-enable-route-propagation) to allow traffic to flow over the InterLink. This enables all prefixes whitelisted in your allowed routes list / routing policy to be announced in the BGP session, so that traffic can flow along these routes. -Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka [allowed routes list](/network/interlink/concepts/#allowed-routes-list) to the InterLink to allow traffic to flow. +Even when route propagation is activated, remember that all routes are blocked by default. It is essential to attach a routing policy (aka [allowed routes list](/interlink/concepts/#allowed-routes-list) to the InterLink to allow traffic to flow. You can deactivate route propagation via the dedicated endpoint at any time. When you do this, all routes are blocked and removed from the VPC's route table. No traffic can flow across the InterLink until route propagation is reactivated. diff --git a/network/interlink/reference-content/overview.mdx b/network/interlink/reference-content/overview.mdx index 29dcaba3bf..6cfadb998b 100644 --- a/network/interlink/reference-content/overview.mdx +++ b/network/interlink/reference-content/overview.mdx @@ -32,7 +32,7 @@ Scaleway plans to offer two types of InterLink, though currently only the **host ### Hosted InterLinks -A hosted InterLink is provisioned via a [partner](/network/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/network/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. +A hosted InterLink is provisioned via a [partner](/interlink/concepts/#partner). Partners are telecom operators or network providers that have been pre-selected by Scaleway. They provide a shareable port on their router, with a certain amount of bandwidth, at a [PoP](/interlink/concepts/#location) (location) where both Scaleway and the partner's networks are present. The available bandwidth is shared between multiple customers: each gets a specified amount when creating their InterLink. By choosing a hosted InterLink, you can re-use existing connectivity between a PoP where both you and the partner are present, and the Scaleway network. Layer 2 isolation to your Scaleway VPC is preserved, with guaranteed bandwidth (100Mbps - 25Gbps) across the InterLink. @@ -49,11 +49,11 @@ A dedicated InterLink is provisioned, where the customer gets sole use of a sing ## Provisioning an InterLink -Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from Scaleway, the customer, and the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/network/interlink/reference-content/provisioning/) for full details. +Provisioning an InterLink is a multi-step process. As only hosted InterLinks (via partners) are currently available, specific action is required from Scaleway, the customer, and the selected partner in order to successfully complete the provisioning process. See our dedicated page on [provisioning an InterLink](/interlink/reference-content/provisioning/) for full details. ## Attaching a VPC -When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/network/interlink/reference-content/configuring/) page for more information. +When you initially create the InterLink, it is not associated with a specific VPC, only with a given Scaleway region. Attaching it to a VPC within the specified region is essential to complete the connection on the Scaleway side. You can only attach a VPC once the provisioning process is complete, and the InterLink has `Active` status. See the [configuration](/interlink/reference-content/configuring/) page for more information. While each InterLink can only be attached to a single Scaleway VPC, it is possible to attach two InterLinks to the same VPC to ensure redundancy and high availability. In this case, each InterLink must be provisioned and configured separately, and will be billed separately. Note that you can reuse the same [allowed routes lists](#allowed-routes-list) across multiple InterLinks. @@ -65,12 +65,12 @@ Each side advertises IP prefixes for its own internal subnets and resources, to In fact, each InterLink has two BGP sessions: one for IPv4 and one for IPv6. Each session handles the exchange of IP prefixes for its respective IP version. The separation of these sessions ensures that IPv4 and IPv6 traffic can be managed independently, and provides compatibility with networks that may only support one of the IP versions. -When both BGP sessions are up, the InterLink has `Active` status. If one BGP session is up, and the other down, the status moves to `Limited Connectivity`. If both BGP sessions are down, the status is marked as `Down`. See the page on [InterLink statuses](/network/interlink/reference-content/statuses) for full information. +When both BGP sessions are up, the InterLink has `Active` status. If one BGP session is up, and the other down, the status moves to `Limited Connectivity`. If both BGP sessions are down, the status is marked as `Down`. See the page on [InterLink statuses](/interlink/reference-content/statuses) for full information. ### Allowed routes list -By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach an [allowed routes list](/network/interlink/concepts/#allowed-routes-list) (aka routing policy), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on allowed routes lists. +By default, **all route announcements from both sides are blocked** by InterLink. This is part of a safety-net mechanism to allow customers to efficiently and safely control traffic flow across the link. You must create and attach an [allowed routes list](/interlink/concepts/#allowed-routes-list) (aka routing policy), to specify the IP prefix announcements to whitelist from each side. This is step one of two in allowing traffic to flow across the InterLink. See the [configuration](/interlink/reference-content/configuring/) page for more information on allowed routes lists. ### Route propagation -Even after attaching an allowed route list, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/network/interlink/reference-content/configuring/) page for more information on route propagation. +Even after attaching an allowed route list, traffic cannot flow across your InterLink until you **activate route propagation**. This is the second part of the safety-net mechanism enabling you to fine-tune the traffic that flows across your InterLink. Route propagation can be activated or deactivated whenever you want. See the [configuration](/interlink/reference-content/configuring/) page for more information on route propagation. diff --git a/network/interlink/reference-content/provisioning.mdx b/network/interlink/reference-content/provisioning.mdx index 24686b9544..3a3fa23b6f 100644 --- a/network/interlink/reference-content/provisioning.mdx +++ b/network/interlink/reference-content/provisioning.mdx @@ -19,7 +19,7 @@ dates: InterLink is currently in [Private Beta](https://www.scaleway.com/en/betas/), and only available to selected testers. -The process of ordering an InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/network/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure. +The process of ordering an InterLink has multiple stages: action is required both from Scaleway, the user, and from the selected [partner](/interlink/concepts/#partner). When preparing your InterLink order, you must choose appropriate location (aka **P**oint **o**f **P**resence), partner and region settings to ensure compatibility with your external and Scaleway infrastructure. @@ -31,7 +31,7 @@ This document explains the provisioning process in full, so you know what to exp The diagram above shows the four steps necessary to provision an InterLink. Only when all steps have been completed will the InterLink move to an **Active** status, ready for traffic to flow. Read more about each step, and possible errors at each stage, in the following sections. -For full information about different statuses an InterLink might flow through, see our [dedicated documentation on InterLink statuses](/network/interlink/reference-content/statuses/). +For full information about different statuses an InterLink might flow through, see our [dedicated documentation on InterLink statuses](/interlink/reference-content/statuses/). ### 1. User orders InterLink via Scaleway @@ -62,7 +62,7 @@ After ordering the InterLink from Scaleway, you **must** contact your chosen par Use the [Get a partner](https://www.scaleway.com/en/developers/api/interlink/#path-partners-get-a-partner) endpoint to get information about your selected partner. Each partner provides either a contact email address, and/or the URL of their online portal. You should make contact with your partner via one of these channels. -You should also provide the partner with your unique [pairing key](/network/interlink/concepts/#pairing-key), which you can get via the [Get an InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) endpoint. +You should also provide the partner with your unique [pairing key](/interlink/concepts/#pairing-key), which you can get via the [Get an InterLink](https://www.scaleway.com/en/developers/api/interlink/#path-links-get-a-link) endpoint. Your InterLink will remain in `Requested` status until the partner responds to your request. @@ -83,7 +83,7 @@ If your InterLink does not move to `Provisioning` status, you may see one of the When the partner has finished provisioning your InterLink, it moves to `Active` status. This indicates that the physical link and necessary accompanying configuration has been completed on the partner's side, and your InterLink is ready for use. -You must still configure your InterLink by attaching it to a VPC, attaching an allowed routes list, and activating route propagation, before traffic can flow over the InterLink. For help with these steps, see our documentation on [configuring your InterLink](/network/interlink/reference-content/configuring/). +You must still configure your InterLink by attaching it to a VPC, attaching an allowed routes list, and activating route propagation, before traffic can flow over the InterLink. For help with these steps, see our documentation on [configuring your InterLink](/interlink/reference-content/configuring/). If you see a `Limited connectivity` status, this indicates that the partner provisioned your InterLink, but either IPv4 or IPv6 connectivity is down. Similarly, a `Down` status indicates the InterLink is provisioned, but both IPv4 **and** IPv6 connectivity are down. Open a Scaleway support ticket, or contact your partner for assistance. diff --git a/network/ipam/concepts.mdx b/network/ipam/concepts.mdx index 163c222040..d4b23e9f9f 100644 --- a/network/ipam/concepts.mdx +++ b/network/ipam/concepts.mdx @@ -14,13 +14,13 @@ categories: ## CIDR notation -When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/network/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses. +When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses. ## IPAM -**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/network/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources. +**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. Managed products, such as Databases and Load Balancer, are fully integrated into IPAM, and Private Networks' [DHCP server](/vpc/concepts/#dhcp) uses IPAM to assign private, static IP addresses to attached resources. -The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging, and filtering all your [private IP addresses](#private-ip-address). You can also [reserve](/network/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer, Public Gateway, or Elastic Metal server to the network. +The public rollout of IPAM functionality is being carried out gradually. IPAM is now in General Availability, offering several different functionalities in the [Scaleway console](https://console.scaleway.com/ipam/), including viewing, tagging, and filtering all your [private IP addresses](#private-ip-address). You can also [reserve](/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer, Public Gateway, or Elastic Metal server to the network. More functionality is planned for the future, including: @@ -37,13 +37,13 @@ Scaleway resources may have a [public](#public-flexible-ip-address) IPv4 address Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`. -IPv6-compatible Scaleway resources may have a [public](#public-flexible-ip-address) IPv6 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv6 address for each Private Network they are attached to. [Find out more about IPv6 in the Scaleway ecosystem](/network/ipam/reference-content/ipv6/). +IPv6-compatible Scaleway resources may have a [public](#public-flexible-ip-address) IPv6 address (flexible IP) for accessibility from the public internet, and will have a [private](#private-ip-address) IPv6 address for each Private Network they are attached to. [Find out more about IPv6 in the Scaleway ecosystem](/ipam/reference-content/ipv6/). ## Private IP address -Private IP addresses identify devices on Private Networks. They are not routed on the public internet, and can be used to route traffic privately between resources attached to the Private Network, as well as to [other Private Networks in the same VPC](/network/vpc/concepts/#routing). +Private IP addresses identify devices on Private Networks. They are not routed on the public internet, and can be used to route traffic privately between resources attached to the Private Network, as well as to [other Private Networks in the same VPC](/vpc/concepts/#routing). -When you attach a resource to a Private Network, you can either specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use for the attachment, or let the Private Network's [DHCP](/network/vpc/concepts/#dhcp) assign it a private [IPv4](#ipv4) address from the Private Network's [CIDR](/network/vpc/concepts/#cidr-block) block. In both cases, the resource's private IP address will not change unless you detach the resource from the Private Network, or delete the resource. [IPv6](#ipv6) addresses can also be assigned for IPv6-compatible resources. +When you attach a resource to a Private Network, you can either specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use for the attachment, or let the Private Network's [DHCP](/vpc/concepts/#dhcp) assign it a private [IPv4](#ipv4) address from the Private Network's [CIDR](/vpc/concepts/#cidr-block) block. In both cases, the resource's private IP address will not change unless you detach the resource from the Private Network, or delete the resource. [IPv6](#ipv6) addresses can also be assigned for IPv6-compatible resources. Four IP addresses from each CIDR block are unavailable for reservation/use: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.256`. @@ -51,10 +51,10 @@ Four IP addresses from each CIDR block are unavailable for reservation/use: the Public IP addresses identify devices on the public internet. You can enter the public IP address of an Instance into any browser connected to the Internet, and access content being served from that Instance. -Depending on the type of resource and its configuration, it may or may not have a public IP address. For example, you can choose to give an [Instance](/compute/instances/) one or more public IP addresses ([IPv4](#ipv4) and/or IPv6), or alternatively, no public IP address at all. Find out more about managing public connectivity in our [best practices guide](/network/ipam/reference-content/public-connectivity-best-practices/). +Depending on the type of resource and its configuration, it may or may not have a public IP address. For example, you can choose to give an [Instance](/instances/) one or more public IP addresses ([IPv4](#ipv4) and/or IPv6), or alternatively, no public IP address at all. Find out more about managing public connectivity in our [best practices guide](/ipam/reference-content/public-connectivity-best-practices/). Public IP addresses at Scaleway are often called flexible IP addresses, because you can move them between different resources. However, flexible IP addresses are scoped to a single product and to a single Availability Zone. If you create a flexible IP address for an Instance in `PAR-2`, you can move it to a different Instance in `PAR-2`, but not to an Instance in `PAR-1`, nor to an Elastic Metal server in any AZ. ## Reserved IP address -A reserved IP address is a private IP address from the [CIDR block](/network/vpc/concepts/#cidr-block) of a given Private Network, that you have [reserved via IPAM](/network/ipam/how-to/reserve-ip/). Reserving an IP means that it can no longer be auto-allocated by DHCP to resources that join the network. You can then use the reserved IP to attach a specified resource of your choice to the Private Network. After you detach the resource, the IP remains reserved, and you can either use it to attach a different resource, or release it back into the pool of generally available IPs. \ No newline at end of file +A reserved IP address is a private IP address from the [CIDR block](/vpc/concepts/#cidr-block) of a given Private Network, that you have [reserved via IPAM](/ipam/how-to/reserve-ip/). Reserving an IP means that it can no longer be auto-allocated by DHCP to resources that join the network. You can then use the reserved IP to attach a specified resource of your choice to the Private Network. After you detach the resource, the IP remains reserved, and you can either use it to attach a different resource, or release it back into the pool of generally available IPs. \ No newline at end of file diff --git a/network/ipam/how-to/list-ips.mdx b/network/ipam/how-to/list-ips.mdx index 2f440c1cf2..80f0f01941 100644 --- a/network/ipam/how-to/list-ips.mdx +++ b/network/ipam/how-to/list-ips.mdx @@ -15,15 +15,15 @@ categories: **IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. -[Read more about IPAM and future planned functionality](/network/ipam/concepts/#ipam). +[Read more about IPAM and future planned functionality](/ipam/concepts/#ipam). -You can currently use IPAM in the Scaleway console to manage the IP address space of your Scaleway Private Networks. This document shows you how to list the [private IP addresses](/network/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks. +You can currently use IPAM in the Scaleway console to manage the IP address space of your Scaleway Private Networks. This document shows you how to list the [private IP addresses](/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one resource [attached to a Private Network](/network/vpc/how-to/attach-resources-to-pn/). +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one resource [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/). ## How to list and filter your private IP addresses @@ -32,14 +32,14 @@ You can currently use IPAM in the Scaleway console to manage the IP address spac A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM. This means either: - You manually reserved an address via IPAM (currently only possible via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or - - You [attached a resource to a Private Network](/network/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network. + - You [attached a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network. - The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/network/vpc/concepts/#cidr-block) do not display in the list. + The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/vpc/concepts/#cidr-block) do not display in the list. - When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/network/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses. + When viewing a private IP address in IPAM, it is shown in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation). For example, the address `172.16.12.2/22` represents the IPv4 address `172.16.12.2`and its associated CIDR block `172.16.12.0/22`, defined on the [Private Network](/vpc/how-to/create-private-network/#how-to-configure-cidr) and containing 1024 addresses. -2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/network/ipam/concepts/#ipv4) or [IPv6](/network/ipam/concepts/#ipv6) addresses: +2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/ipam/concepts/#ipv4) or [IPv6](/ipam/concepts/#ipv6) addresses: 3. Click **Apply filters** to activate the filters you chose, or **Reset** to reset all filters. diff --git a/network/ipam/how-to/manage-ips.mdx b/network/ipam/how-to/manage-ips.mdx index a446abde44..85878c4830 100644 --- a/network/ipam/how-to/manage-ips.mdx +++ b/network/ipam/how-to/manage-ips.mdx @@ -13,25 +13,25 @@ categories: - network --- -IPAM acts as a single source of truth for the IP addresses of your Scaleway resources. You can use IPAM in the console Scaleway console to manage [private IP addresses](/network/ipam/concepts/#private-ip-address) that are either attached to one of your resources on a Private Network, or [reserved via the IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip). +IPAM acts as a single source of truth for the IP addresses of your Scaleway resources. You can use IPAM in the console Scaleway console to manage [private IP addresses](/ipam/concepts/#private-ip-address) that are either attached to one of your resources on a Private Network, or [reserved via the IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip). The management actions currently available include: - Viewing the details of a private IP address, including its ID, tags, creation date and to which resource (if any) it is attached - Editing the tags of a private IP address -Learn [how to reserve a private IP address](/network/ipam/how-to/reserve-ip/). +Learn [how to reserve a private IP address](/ipam/how-to/reserve-ip/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one resource [attached to a Private Network](/network/vpc/how-to/attach-resources-to-pn/). +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one resource [attached to a Private Network](/vpc/how-to/attach-resources-to-pn/). ## How to view the details of a private IP address 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. - A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/network/vpc/how-to/attach-resources-to-pn/). + A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/vpc/how-to/attach-resources-to-pn/). 2. Modify the filters of the list using the drop-down menus at the top if necessary to display the required IP address. diff --git a/network/ipam/how-to/reserve-ip.mdx b/network/ipam/how-to/reserve-ip.mdx index 99566aded9..2a9aeea07f 100644 --- a/network/ipam/how-to/reserve-ip.mdx +++ b/network/ipam/how-to/reserve-ip.mdx @@ -15,7 +15,7 @@ categories: **IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. -You can use IPAM to reserve a private IP address from a given Private Network's [CIDR block](/network/vpc/concepts/#cidr-block). When you reserve an IP in this way, it stops it from being potentially auto-allocated to new resources being attached to the Private Network. You can then use the reserved address to attach the specific resource of your choice to the Private Network. If you later detach the resource from the network, the reserved IP will stay reserved, until you either release it back into the general pool, or use it to attach a different resource. +You can use IPAM to reserve a private IP address from a given Private Network's [CIDR block](/vpc/concepts/#cidr-block). When you reserve an IP in this way, it stops it from being potentially auto-allocated to new resources being attached to the Private Network. You can then use the reserved address to attach the specific resource of your choice to the Private Network. If you later detach the resource from the network, the reserved IP will stay reserved, until you either release it back into the general pool, or use it to attach a different resource. Currently, only **Instances**, **Elastic Metal servers**, **Load Balancers**, and **Public Gateways** are compatible with reserved private IPs. Support for Managed Databases will be coming soon. @@ -26,8 +26,8 @@ This page sets out the steps necessary to reserve an IP address with IPAM. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one [Private Network](/network/vpc/how-to/create-private-network/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one [Private Network](/vpc/how-to/create-private-network/) ## How to reserve a private IP address @@ -42,7 +42,7 @@ This page sets out the steps necessary to reserve an IP address with IPAM. - **Tags**: Tags to help you filter and manage your reserved IPs later - **Region**: The region in which you want to reserve a private IP address - **VPC**: The VPC in which you want to reserve a private IP address - - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/network/vpc/concepts/), and available to attach resources to this network. + - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/vpc/concepts/), and available to attach resources to this network. 4. Define whether you want to specify the IP address to reserve, or reserve any available IP on the Private Network (the IP selected will be displayed after reservation). If specifying the IP address yourself, do **not** include the network prefix (e.g. `/22`). @@ -86,11 +86,11 @@ You can currently attach **Instances**, **Elastic Metal servers**, **Load Balanc The option to use a reserved IP displays when you attach the resource to a Private Network in the console. Follow the instructions below: -- Attach a resource to a Private Network from the [Private Networks](/network/vpc/how-to/attach-resources-to-pn/) product dashboard -- Attach an Instance to a Private Network from the [Instances](/compute/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) product dashboard -- Attach an Elastic Metal server to a Private Network from the [Elastic Metal](/bare-metal/elastic-metal/how-to/use-private-networks/) product dashboard -- Attach a Load Balancer to a Private Network from the [Load Balancer](/network/load-balancer/how-to/use-with-private-network/) product dashboard -- Attach a Public Gateway to a Private Network from the [Public Gateways](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) product dashboard +- Attach a resource to a Private Network from the [Private Networks](/vpc/how-to/attach-resources-to-pn/) product dashboard +- Attach an Instance to a Private Network from the [Instances](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) product dashboard +- Attach an Elastic Metal server to a Private Network from the [Elastic Metal](/elastic-metal/how-to/use-private-networks/) product dashboard +- Attach a Load Balancer to a Private Network from the [Load Balancer](/load-balancer/how-to/use-with-private-network/) product dashboard +- Attach a Public Gateway to a Private Network from the [Public Gateways](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) product dashboard ## How to release a reserved private IP address diff --git a/network/ipam/index.mdx b/network/ipam/index.mdx index 13401fdd13..3c57dde83f 100644 --- a/network/ipam/index.mdx +++ b/network/ipam/index.mdx @@ -8,14 +8,14 @@ meta: sentiment="info" title="Public connectivity - best practices" > - Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment, with our [new guide](/network/ipam/reference-content/public-connectivity-best-practices/). Learn how to enhance performance and ensure robust protection. + Discover essential best practices for securing and optimizing public connectivity in your Scaleway cloud environment, with our [new guide](/ipam/reference-content/public-connectivity-best-practices/). Learn how to enhance performance and ensure robust protection. @@ -27,28 +27,28 @@ meta: icon="rocket" description="Learn how to get started using IPAM." label="View Quickstart" - url="/network/ipam/quickstart/" + url="/ipam/quickstart/" /> diff --git a/network/ipam/quickstart.mdx b/network/ipam/quickstart.mdx index 0da4e05364..a6f26ba56f 100644 --- a/network/ipam/quickstart.mdx +++ b/network/ipam/quickstart.mdx @@ -15,9 +15,9 @@ categories: **IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. -[Read more about IPAM and its current and future planned functionality](/network/ipam/concepts/#ipam). +[Read more about IPAM and its current and future planned functionality](/ipam/concepts/#ipam). -You can currently use IPAM in the Scaleway console to list the [private IP addresses](/network/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks, and view/edit their additional information. You can also [reserve](/network/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network. +You can currently use IPAM in the Scaleway console to list the [private IP addresses](/ipam/concepts/#private-ip-address) of all your Scaleway resources attached to Private Networks, and view/edit their additional information. You can also [reserve](/ipam/how-to/reserve-ip/) a private IP on one of your Private Networks and use it to attach an Instance, Load Balancer or Public Gateway to the network. ## How to list and filter your private IP addresses @@ -26,11 +26,11 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM. This means either: - You manually reserved an address via IPAM (currently only possible via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or - - You [attached a resource to a Private Network](/network/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network. + - You [attached a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/): this triggers IPAM to reserve and attach an IP address for the resource on the network. - The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/network/vpc/concepts/#cidr-block) do not display in the list. + The full range of IP addresses which are available but unreserved in each of your Private Network's [CIDR blocks](/vpc/concepts/#cidr-block) do not display in the list. -2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/network/ipam/concepts/#ipv4) or [IPv6](/network/ipam/concepts/#ipv6) addresses: +2. Modify the filters of the list using the drop-down menus at the top. You can filter for IP addresses within a given **region**, **VPC** and/or **Private Network**. You can also opt to filter for only [IPv4](/ipam/concepts/#ipv4) or [IPv6](/ipam/concepts/#ipv6) addresses: 3. Click **Apply filters** to activate the filters you chose, or **Reset** to reset all filters. @@ -38,7 +38,7 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre 1. Click **IPAM** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. - A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/network/vpc/how-to/attach-resources-to-pn/). + A list of your **private IP addresses** for the **region** and **VPC** pre-selected in the filters displays. Addresses are displayed here if they are reserved in IPAM (either manually reserved via the [IPAM API](https://www.scaleway.com/en/developers/api/ipam/#path-ips-book-a-new-ip)), or attached to a resource [on a Private Network](/vpc/how-to/attach-resources-to-pn/). 2. Modify the filters of the list using the drop-down menus at the top if necessary to display the required IP address. @@ -72,7 +72,7 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre - **Tags**: Tags to help you filter and manage your reserved IPs later - **Region**: The region in which you want to reserve a private IP address - **VPC**: The VPC in which you want to reserve a private IP address - - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/network/vpc/concepts/), and available to attach resources to this network. + - **Private Network**: The Private Network in which you want to reserve a private IP address. The reserved IP will be from this network's [CIDR block](/vpc/concepts/), and available to attach resources to this network. 4. Define whether you want to specify the IP address to reserve, or reserve any available IP on the Private Network (the IP selected will be displayed after reservation). If specifying the IP address yourself, do **not** include the network prefix (e.g. `/22`). @@ -80,4 +80,4 @@ You can currently use IPAM in the Scaleway console to list the [private IP addre Four IP addresses from each CIDR block are unavailable for reservation: the first two and last two in the block. For example, for the subnet `172.16.12.0/22` the following addresses cannot be reserved or assigned to any resource: `172.16.12.0`, `172.16.12.1`, `172.16.15.254` and `172.16.15.256`. - The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](/network/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address) it. \ No newline at end of file + The IP address is reserved, and you are returned to the list of your private IP addresses, where the reserved address now displays. You can use this address to attach a resource to the Private Network you reserved it from. If and when you no longer need the reserved IP, you can [release](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address) it. \ No newline at end of file diff --git a/network/ipam/reference-content/ipv6.mdx b/network/ipam/reference-content/ipv6.mdx index 7e85fa1fd5..295952d7d9 100644 --- a/network/ipam/reference-content/ipv6.mdx +++ b/network/ipam/reference-content/ipv6.mdx @@ -35,7 +35,7 @@ The following products support IPv6: ### Instances and IPv6 -Scaleway Instances are compatible with IPv6, with the caveat that the Instance must be using [routed IPs](/compute/instances/concepts/#routed-flexible-ip). +Scaleway Instances are compatible with IPv6, with the caveat that the Instance must be using [routed IPs](/instances/concepts/#routed-flexible-ip). #### Public IPv6 @@ -43,17 +43,17 @@ You can attach one or multiple public (flexible) IPv6 addresses to your Instance #### Private IPv6 -When you attach an Instance to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use. +When you attach an Instance to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use. #### Going further Go further with Instances and IPv6 in the following documentation: -- [How to use flexible IPs](/compute/instances/how-to/use-flexips/) -- [Compatibility between OS images and different flexible IP type combinations](/compute/instances/reference-content/comaptibility-scw-os-images-flexible-ip/) -- [Using routed IPs](/compute/instances/api-cli/using-routed-ips/) -- Fix lost IPv6 connectivity when migrating to routed IP for old [Debian Buster images](/compute/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/) or [RHEL images](/compute/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/) -- [Fix DNS resolution with a routed IPv6-only setup on Debian Bullseye](/compute/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye/) +- [How to use flexible IPs](/instances/how-to/use-flexips/) +- [Compatibility between OS images and different flexible IP type combinations](/instances/reference-content/comaptibility-scw-os-images-flexible-ip/) +- [Using routed IPs](/instances/api-cli/using-routed-ips/) +- Fix lost IPv6 connectivity when migrating to routed IP for old [Debian Buster images](/instances/troubleshooting/fix-lost-ip-connectivity-on-debian-buster/) or [RHEL images](/instances/troubleshooting/fix-unreachable-ipv6-rhel-based-instance/) +- [Fix DNS resolution with a routed IPv6-only setup on Debian Bullseye](/instances/troubleshooting/fix-dns-routed-ipv6-only-debian-bullseye/) ### Elastic Metal and IPv6 @@ -69,24 +69,24 @@ In addition to the possibility of attaching and detaching flexible IP addresses, #### Private IPv6 -When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use. +When you attach an Elastic Metal server to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use. You can also use IPAM's [reserve a private IP](https://www.scaleway.com/en/developers/api/ipam/#path-ips-reserve-a-new-ip) and [attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-ip-to-custom-resource) feature to attach an IPv6 address to a named resource via its MAC address. This is suitable for ensuring virtual machines on your Elastic Metal server get private IPv6 addresses. #### Going further Go further with Elastic Metal and IPv6 in the following documentation: -- [How to order a flexible IP](/bare-metal/elastic-metal/how-to/order-flexible-ip/) -- [How to attach/detach a flexible IP](/bare-metal/elastic-metal/how-to/attach-detach-flexible-ip/) -- [How to configure a flexible IPv6 address on your Elastic Metal server](/bare-metal/elastic-metal/how-to/configure-flexible-ipv6/) -- [How to configure a flexible IPv6 address on a virtual Proxmox machine](/bare-metal/elastic-metal/how-to/configure-ipv6-hypervisor/) -- [How to configure the network interface on your server for Private Networks](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) +- [How to order a flexible IP](/elastic-metal/how-to/order-flexible-ip/) +- [How to attach/detach a flexible IP](/elastic-metal/how-to/attach-detach-flexible-ip/) +- [How to configure a flexible IPv6 address on your Elastic Metal server](/elastic-metal/how-to/configure-flexible-ipv6/) +- [How to configure a flexible IPv6 address on a virtual Proxmox machine](/elastic-metal/how-to/configure-ipv6-hypervisor/) +- [How to configure the network interface on your server for Private Networks](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) ### Dedibox and IPv6 The Scaleway Dedibox network fully supports IPv6. IPv6 can serve as your server’s primary IP and also as a failover IP utilizing the concept of a virtual MAC address. -Full information on IPv6 with Dedibox can be found in our [dedicated documentation](/dedibox-network/ipv6/), or you can read more in our [blog post](https://www.scaleway.com/en/blog/ipv6-the-future-proof-internet-protocol/#ipv6-at-scaleway-dedibox). +Full information on IPv6 with Dedibox can be found in our [dedicated documentation](/dedibox-ipv6/), or you can read more in our [blog post](https://www.scaleway.com/en/blog/ipv6-the-future-proof-internet-protocol/#ipv6-at-scaleway-dedibox). ### Load Balancer and IPv6 @@ -98,7 +98,7 @@ You can attach a maximum of one (flexible) IPv6 address to your Load Balancer, i #### Private IPv6 -When you attach a Load Balancer to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/network/ipam/how-to/reserve-ip/) to use. +When you attach a Load Balancer to a Private Network, it gets both an IPv4 and an IPv6 address on that network. You can either let IPAM auto-allocate any available address, or specify a [reserved IP address](/ipam/how-to/reserve-ip/) to use. #### IPv6 at the backend @@ -107,7 +107,7 @@ Load Balancers can also use IPv6 to communicate with their backend servers. When #### Going further Go further with IPv6 and Load Balancers with the following documentation: -- [How to create and manage flexible IPs](/network/load-balancer/how-to/create-manage-flex-ips/) +- [How to create and manage flexible IPs](/load-balancer/how-to/create-manage-flex-ips/) ### VPC, Private Networks and IPv6 @@ -116,8 +116,8 @@ VPC and Private Networks are compatible with IPv6. - Private Networks are dual-stack, meaning each Private Network necessarily has both an IPv4 and and an IPv6 CIDR blocks. - For IPv6, this is a `/64` block, automatically created by Scaleway, guaranteed to be unique within the VPC and not overlapping with any of your other Private Networks. - All IPv6-compatible resources will automatically receive an IPv6 address when they join a Private Network, in addition to an IPv4 address. -- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/network/ipam/how-to/reserve-ip/) -- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/network/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPV4 and IPV6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process. +- This address can be auto-allocated from the pool, or specified by the user via a [reserved IP address](/ipam/how-to/reserve-ip/) +- Scaleway VPC routing supports both IPv4 and IPv6 protocols. [Managed routes](/vpc/how-to/manage-routing/#how-to-generate-a-managed-route) to Private Networks are simultaneously generated for both IPV4 and IPV6, and both are added to the VPC's route table. Note that auto-generated managed routes to Public Gateways are only created in IPv4, since Public Gateways are not yet IPv6-compatible. [Custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) are only created for the IP type specified during the creation process. ### Serverless Functions and Containers and IPv6 @@ -133,8 +133,8 @@ Alternatively, get in touch on the [Scaleway Slack Community](/tutorials/scalewa ## IPv6 best practices -**Only expose a public IPv6 address when necessary**: Adding both IPv4 and IPv6 public addresses to your resource expands the potential attack surface, particularly in terms of the large address space of IPv6. As stated in our [dedicated documentation](/network/ipam/reference-content/public-connectivity-best-practices/), you should favor connectivity over Private Networks, and detach public IP addresses from resources unless strictly necessary. +**Only expose a public IPv6 address when necessary**: Adding both IPv4 and IPv6 public addresses to your resource expands the potential attack surface, particularly in terms of the large address space of IPv6. As stated in our [dedicated documentation](/ipam/reference-content/public-connectivity-best-practices/), you should favor connectivity over Private Networks, and detach public IP addresses from resources unless strictly necessary. **Audit DNS and address exposure**: Regularly audit the DNS records and public IPv6 addresses associated with your resources to minimize exposure. -**Implement IPv6-specific security measures**: Features such as [security groups](/compute/instances/concepts/#security-group) for Instances and [ACLs](/network/load-balancer/concepts/#acl) for Load Balancers allow you to filter traffic based on both IPv4 and IPv6 addresses. Ensure that such security measures are equally robust for both protocols. \ No newline at end of file +**Implement IPv6-specific security measures**: Features such as [security groups](/instances/concepts/#security-group) for Instances and [ACLs](/load-balancer/concepts/#acl) for Load Balancers allow you to filter traffic based on both IPv4 and IPv6 addresses. Ensure that such security measures are equally robust for both protocols. \ No newline at end of file diff --git a/network/ipam/reference-content/public-connectivity-best-practices.mdx b/network/ipam/reference-content/public-connectivity-best-practices.mdx index 85f2430346..b15bffe9e3 100644 --- a/network/ipam/reference-content/public-connectivity-best-practices.mdx +++ b/network/ipam/reference-content/public-connectivity-best-practices.mdx @@ -19,14 +19,14 @@ This document sets out best practices for securing and optimizing public connect Public vs private connectivity defines how resources are accessed and exposed over networks. -- **Public connectivity**: Your resource has a [public IP address](/network/ipam/concepts/#public-flexible-ip-address) and is reachable over the public internet. Anyone with the right credentials can access the resource via its public IP address, e.g. over an [SSH connection](/compute/instances/how-to/connect-to-instance/) or simply by directly accessing its IP address in a browser to retrieve and display any content it is serving, e.g. over HTTP. -- **Private connectivity**: Your resources is reachable over an attached [Private Network](/network/vpc/concepts/#private-networks). The resource has a [private IP address](/network/vpc/concepts/#private-ip-address), but it can only be accessed via this address from within the VPC of the Private Network. Such a resource may or may not also have a public IP address. +- **Public connectivity**: Your resource has a [public IP address](/ipam/concepts/#public-flexible-ip-address) and is reachable over the public internet. Anyone with the right credentials can access the resource via its public IP address, e.g. over an [SSH connection](/instances/how-to/connect-to-instance/) or simply by directly accessing its IP address in a browser to retrieve and display any content it is serving, e.g. over HTTP. +- **Private connectivity**: Your resources is reachable over an attached [Private Network](/vpc/concepts/#private-networks). The resource has a [private IP address](/vpc/concepts/#private-ip-address), but it can only be accessed via this address from within the VPC of the Private Network. Such a resource may or may not also have a public IP address. ## Effectively managing IP addresses ### Flexible IP addresses: definition -Public connectivity for **Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/network/ipam/concepts/#public-flexible-ip-address). +Public connectivity for **Instances**, **Elastic Metal**, **Load Balancers** and **Public Gateways** is facilitated by a [flexible IP address](/ipam/concepts/#public-flexible-ip-address). - A flexible IP address is a public IP address that you can attach and detach from the resource at will. - If you detach it, it returns to the pool of flexible IP addresses kept in your account for that product, and you can attach it to a different resource (or reattach it to the same one as before). @@ -42,7 +42,7 @@ As flexible IP addresses can be moved between resources, they provide the follow - **Zero downtime during maintenance and migration**: When you need to carry out updates, migrations or maintenance on a resource, you can temporarily move its public IP to a backup resource to avoid disruption for users. - **IP retention and consistent endpoints**: Maintaining the same IP avoids the need for frequent DNS or firewall rule updates, and makes it easier to manage your dynamic cloud environments. -In the future, look out for even more improvements to our flexible IP offering, such as the ability to move flexible IPs between different types of products, and to manage all your public flexible IPs from your [IPAM](/network/ipam/) dashboard. +In the future, look out for even more improvements to our flexible IP offering, such as the ability to move flexible IPs between different types of products, and to manage all your public flexible IPs from your [IPAM](/ipam/) dashboard. ### Limiting public connectivity, prioritizing Private Networks @@ -61,9 +61,9 @@ Depending on the resource type, public connectivity can be disabled by: For some products, e.g. Apple Silicon, public connectivity cannot be disabled at any stage, and for other resources, eg Managed Databases for Redis, public connectivity options cannot be modified after resource creation. Check the documentation for your specific product to learn more. -Favor resources such as Public Gateways and Load Balancers to provide access to the public internet over the Private Network. This allows Instances and other attached resources to send and receive packets to the internet through a single, secure point of access. You can use the Public Gateway's SSH bastion feature to [connect to your resource via its private IP address](/network/public-gateways/how-to/use-ssh-bastion/#how-to-connect-to-a-resource-behind-your-ssh-bastion). +Favor resources such as Public Gateways and Load Balancers to provide access to the public internet over the Private Network. This allows Instances and other attached resources to send and receive packets to the internet through a single, secure point of access. You can use the Public Gateway's SSH bastion feature to [connect to your resource via its private IP address](/public-gateways/how-to/use-ssh-bastion/#how-to-connect-to-a-resource-behind-your-ssh-bastion). -Find out more about how to get the most from Private Network in our [dedicated documentation](/network/vpc/reference-content/getting-most-private-networks/) +Find out more about how to get the most from Private Network in our [dedicated documentation](/vpc/reference-content/getting-most-private-networks/) ## Implementing security controls @@ -71,13 +71,13 @@ Different products offer different security features and controls to help place ### Instances: Security groups -[Security groups](/compute/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow public traffic to and from your Instance. [Find out how to create and configure security groups](/compute/instances/how-to/use-security-groups/). +[Security groups](/instances/concepts/#security-group) act as firewalls, filtering public internet traffic on your Instances. They can be stateful or stateless, and allow you to create rules to drop or allow public traffic to and from your Instance. [Find out how to create and configure security groups](/instances/how-to/use-security-groups/). ### Load Balancers: ACLs -Learn how to use the ACL feature in our [dedicated how-to](/network/load-balancer/how-to/create-manage-acls/) and go deeper with our [reference documentation](/network/load-balancer/reference-content/acls/). +Learn how to use the ACL feature in our [dedicated how-to](/load-balancer/how-to/create-manage-acls/) and go deeper with our [reference documentation](/load-balancer/reference-content/acls/). ### Other controls @@ -96,21 +96,21 @@ Scaleway currently offers Autoscaling in Public Beta. Autoscaling allows you to ### Load Balancer -Placing a Scaleway Load Balancer in front of your backend servers allows you to expose multiple Instances through a single public IP. The Load Balancer distributes workload across the servers in the backend pool, ensurable scalable and continuously available applications, even during heavy traffic. You can manually add and remove servers from the backend pool as necessary, and configure the best balancing method for your particular needs. Find out more in the [Load Balancer documentation](/network/load-balancer/). +Placing a Scaleway Load Balancer in front of your backend servers allows you to expose multiple Instances through a single public IP. The Load Balancer distributes workload across the servers in the backend pool, ensurable scalable and continuously available applications, even during heavy traffic. You can manually add and remove servers from the backend pool as necessary, and configure the best balancing method for your particular needs. Find out more in the [Load Balancer documentation](/load-balancer/). ### Edge Services -Available for Load Balancers and Object Storage buckets, Scaleway Edge Services provides a caching service to reduce load on your origin. This means that content can be served directly to users from Edge Services' servers, instead of from your Load Balancer or Object Storage bucket. [Learn more about Edge Services](/network/edge-services/). +Available for Load Balancers and Object Storage buckets, Scaleway Edge Services provides a caching service to reduce load on your origin. This means that content can be served directly to users from Edge Services' servers, instead of from your Load Balancer or Object Storage bucket. [Learn more about Edge Services](/edge-services/). ### Kubernetes Kapsule -Hosting your containerized application in a managed Kubernetes cluster brings many benefits in terms of scaling and managing fluctuating demand. Kubernetes can automatically adjust the number of running resources within defined limits, based on current demand. It also offers self-healing capabilities in the case of node failure. Find out more in the [Scaleway Kubernetes](/containers/kubernetes/) documentation. +Hosting your containerized application in a managed Kubernetes cluster brings many benefits in terms of scaling and managing fluctuating demand. Kubernetes can automatically adjust the number of running resources within defined limits, based on current demand. It also offers self-healing capabilities in the case of node failure. Find out more in the [Scaleway Kubernetes](/kubernetes/) documentation. ## Monitoring and alerting via Scaleway Cockpit -We recommend that you use [Scaleway Cockpit](/observability/cockpit/) to monitor your resources. Cockpit stores metrics, logs and traces and provides a dedicated dashboarding system on Grafana for easy visualisation. Different metrics are available for different resource types, with metrics for network traffic being available for many, enabling you to monitor connections over the public interface. You can also configure managed and pre-configured alerts for your resources, to receive warnings for potentially abnormal behavior or unusual network activity. +We recommend that you use [Scaleway Cockpit](/cockpit/) to monitor your resources. Cockpit stores metrics, logs and traces and provides a dedicated dashboarding system on Grafana for easy visualisation. Different metrics are available for different resource types, with metrics for network traffic being available for many, enabling you to monitor connections over the public interface. You can also configure managed and pre-configured alerts for your resources, to receive warnings for potentially abnormal behavior or unusual network activity. -Read more about [Scaleway Cockpit](/observability/cockpit/). +Read more about [Scaleway Cockpit](/cockpit/). diff --git a/network/load-balancer/api-cli/configuring-balancing-rules.mdx b/network/load-balancer/api-cli/configuring-balancing-rules.mdx index 8b7defdedf..4ce1f8b2a4 100644 --- a/network/load-balancer/api-cli/configuring-balancing-rules.mdx +++ b/network/load-balancer/api-cli/configuring-balancing-rules.mdx @@ -26,15 +26,15 @@ This page shows you an example of a curl command to create a backend and configu - A Scaleway [account](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Setting up your environment Before configuring the Load Balancer from the API, prepare your environment to facilitate usage of the API. -- Ensure you have [generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/), and that you have the secret key at hand. +- Ensure you have [generated an API key](/iam/how-to/create-api-keys/), and that you have the secret key at hand. - Decide the [Availability Zone](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#technical-information) for your Load Balancer. -- Ensure that you have [created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/#how-to-create-a-load-balancer) and noted its Load Balancer ID. +- Ensure that you have [created a Load Balancer](/load-balancer/how-to/create-load-balancer/#how-to-create-a-load-balancer) and noted its Load Balancer ID. Set these elements as environment variables as follows: @@ -49,7 +49,7 @@ export LB_ID="" Use the following command to create a backend. Modify the parameters as you require. Ensure you replace `` with the IP address of your backend server. -For help on possible parameter values, see the [API documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-backends-create-a-backend-for-a-given-load-balancer). For assistance with configuring backends generally, see our [dedicated documentation]](/network/load-balancer/reference-content/configuring-backends/). +For help on possible parameter values, see the [API documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#path-backends-create-a-backend-for-a-given-load-balancer). For assistance with configuring backends generally, see our [dedicated documentation]](/load-balancer/reference-content/configuring-backends/). ```json diff --git a/network/load-balancer/api-cli/setting-up-ssl-offloading.mdx b/network/load-balancer/api-cli/setting-up-ssl-offloading.mdx index f49d946303..67170332e5 100644 --- a/network/load-balancer/api-cli/setting-up-ssl-offloading.mdx +++ b/network/load-balancer/api-cli/setting-up-ssl-offloading.mdx @@ -15,21 +15,21 @@ categories: SSL offloading describes a pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic), to forward it unencrypted to the backend servers. This effectively “offloads” the work of decrypting traffic from the backend server to the Load Balancer. -You can read more about SSL offloading, compared to SSL bridging or passthrough, in our [dedicated documentation](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) +You can read more about SSL offloading, compared to SSL bridging or passthrough, in our [dedicated documentation](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) This page shows you how to create a Load Balancer configured for SSL offloading using the [Load Balancer API](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Setting up your environment Before configuring the Load Balancer from the API, prepare your environment to facilitate usage of the API. -- Ensure you have [generated an API key](/identity-and-access-management/iam/how-to/create-api-keys/), and that you have the secret key to hand. -- Get your [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) ID from the [Scaleway console](https://console.scaleway.com/). +- Ensure you have [generated an API key](/iam/how-to/create-api-keys/), and that you have the secret key to hand. +- Get your [Project](/organizations-and-projects/concepts/#project) ID from the [Scaleway console](https://console.scaleway.com/). - Decide the [Availability Zone](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/#technical-information) for your Load Balancer. Set these elements as environment variables as follows: @@ -148,7 +148,7 @@ This tutorial supposes that a web application is running on port `80` of the bac ## Creating an SSL/TLS certificate -In order to achieve SSL offloading, your Load Balancer needs an [SSL/TLS certificate](/network/load-balancer/concepts/#certificate). In these steps, we create a Let's Encrypt certificate, which we will then add to the Load Balancer's frontend. +In order to achieve SSL offloading, your Load Balancer needs an [SSL/TLS certificate](/load-balancer/concepts/#certificate). In these steps, we create a Let's Encrypt certificate, which we will then add to the Load Balancer's frontend. 1. Create a new certificate for your Load Balancer. Replace `` with a friendly name for the certificate, and `` with your domain name (this domain must exist and resolve to your Load Balancer IP address). diff --git a/network/load-balancer/concepts.mdx b/network/load-balancer/concepts.mdx index d4a75fa4c6..66e513d53d 100644 --- a/network/load-balancer/concepts.mdx +++ b/network/load-balancer/concepts.mdx @@ -16,20 +16,20 @@ categories: - Learn how to use the ACL feature in our [dedicated how-to](/network/load-balancer/how-to/create-manage-acls/) and go deeper with our [reference documentation](/network/load-balancer/reference-content/acls/) + Learn how to use the ACL feature in our [dedicated how-to](/load-balancer/how-to/create-manage-acls/) and go deeper with our [reference documentation](/load-balancer/reference-content/acls/) ## Accessibility When creating a Load Balancer, you are prompted to configure its **accessibility**. There are two options: **private** or **public**: - - **Private**: A private Load Balancer has no public IP address, and is only accessible from the Private Network(s) it is attached to. Read more about [private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). + - **Private**: A private Load Balancer has no public IP address, and is only accessible from the Private Network(s) it is attached to. Read more about [private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). - **Public**: A public Load Balancer is accessible from the internet via its public IP address. Accessibility cannot be modified after creation of the Load Balancer. ## Backends -Each Load Balancer is configured with one or several backends. A backend represents a set of [backend servers](#backend-servers) that the Load Balancer's frontend forwards requests to using the specified configuration (port, protocol, Proxy Protocol etc.). Grouping backend servers into a backend allows load to be balanced between them based on a defined load-balancing algorithm configured as a backend setting. You can [add and manage backends via the console](/network/load-balancer/how-to/manage-frontends-and-backends/). +Each Load Balancer is configured with one or several backends. A backend represents a set of [backend servers](#backend-servers) that the Load Balancer's frontend forwards requests to using the specified configuration (port, protocol, Proxy Protocol etc.). Grouping backend servers into a backend allows load to be balanced between them based on a defined load-balancing algorithm configured as a backend setting. You can [add and manage backends via the console](/load-balancer/how-to/manage-frontends-and-backends/). ## Backend servers @@ -59,7 +59,7 @@ A certificate (aka SSL certificate / TLS certificate / TLS/SSL certificate) is a -You can [add a certificate](/network/load-balancer/how-to/add-certificate/) to your Load Balancer's frontend to enable the Load Balancer to decrypt/encrypt traffic, necessary for [SSL bridging and SSL offloading configurations](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). Scaleway Load Balancer enables you to generate a Let's Encrypt certificate, or import a third-party or self-signed certificate. +You can [add a certificate](/load-balancer/how-to/add-certificate/) to your Load Balancer's frontend to enable the Load Balancer to decrypt/encrypt traffic, necessary for [SSL bridging and SSL offloading configurations](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). Scaleway Load Balancer enables you to generate a Let's Encrypt certificate, or import a third-party or self-signed certificate. ## Connection timeout @@ -67,7 +67,7 @@ Connection timeout is a configurable value for your Load Balancer's backend. It ## Customized error page -With the [customized error page feature](/network/load-balancer/how-to/set-up-s3-failover/), you can redirect users to a static website hosted on Scaleway Object Storage if none of your Load Balancer's backends are available to serve the requested content. This website could be a simple, single webpage or else something much more complex: you build it according to your own requirements. +With the [customized error page feature](/load-balancer/how-to/set-up-s3-failover/), you can redirect users to a static website hosted on Scaleway Object Storage if none of your Load Balancer's backends are available to serve the requested content. This website could be a simple, single webpage or else something much more complex: you build it according to your own requirements. If you do not set up a customized error page, and none of your backend servers are available, your users will instead see a standard HTTP error displayed in their browser, e.g. `503 Service Unavailable`. @@ -89,19 +89,19 @@ See [balancing-methods](#balancing-methods). ## Frontends -Each Load Balancer is configured with one or several frontends. Frontends listen on a configured port, and forward requests to one or several backends. You can [add and manage frontends via the console](/network/load-balancer/how-to/manage-frontends-and-backends/). +Each Load Balancer is configured with one or several frontends. Frontends listen on a configured port, and forward requests to one or several backends. You can [add and manage frontends via the console](/load-balancer/how-to/manage-frontends-and-backends/). ## Flexible IP address Flexible IP addresses are public IP addresses that you can hold independently of any Load Balancer. By default, each Load Balancer is created automatically with a flexible IP address, that the frontend listens to. In case of a failure of the Load Balancer, a replica Load Balancer is immediately spawned and deployed, and the flexible IP address is automatically rerouted to this replica. -Find out how to create and manage flexible IP addresses in our [dedicated how-to](/network/load-balancer/how-to/create-manage-flex-ips/). +Find out how to create and manage flexible IP addresses in our [dedicated how-to](/load-balancer/how-to/create-manage-flex-ips/). ## Health checks Load Balancers should only forward traffic to “healthy” backend servers. To monitor the health of a backend server, health checks regularly attempt to communicate with backend servers using the protocol and port defined by the forwarding rules to ensure that servers are listening. Various protocols for health checks are available, including HTTP, HTTPS, MySQL, and more. -Read more about health checks, including the advanced settings available, in our [dedicated documentation](/network/load-balancer/reference-content/configuring-health-checks/). +Read more about health checks, including the advanced settings available, in our [dedicated documentation](/load-balancer/reference-content/configuring-health-checks/). ## High availability @@ -117,25 +117,25 @@ Scaleway Load Balancers can use the **Host** header field to define [routes](#ro HTTP/2 and HTTP/3 are newer, improved versions of the "classic" HTTP/1 protocol. Scaleway Load Balancers support HTTP/2 connections to frontends, and HTTP/2 connections from backends to backend servers. In addition, Scaleway Load Balancers support HTTP/3 connections to frontends, but do not support HTTP/3 connections from backends to backend servers. -Read more about HTTP/2 and HTTP/3 and how they can be configured on Scaleway Load Balancers in our [dedicated documentation](/network/load-balancer/reference-content/http2-http3/). +Read more about HTTP/2 and HTTP/3 and how they can be configured on Scaleway Load Balancers in our [dedicated documentation](/load-balancer/reference-content/http2-http3/). ## IPv4 Internet Protocol Version 4 is the standard protocol used for IP addresses, and routes most Internet traffic as of today. Each IPv4 address has 32 bits. Written in human-readable form, an IPv4 address is generally shown as four octets of numbers separated by periods, e.g. `192.0.2.1`. -When you [create a public (flexible) IP address for a Load Balancer](/network/load-balancer/how-to/create-manage-flex-ips/), this address can use either IPv4 or IPv6 protocol. An IPv4 address is obligatory for all public Load Balancers, but an IPv6 address can be optionally added. +When you [create a public (flexible) IP address for a Load Balancer](/load-balancer/how-to/create-manage-flex-ips/), this address can use either IPv4 or IPv6 protocol. An IPv4 address is obligatory for all public Load Balancers, but an IPv6 address can be optionally added. ## IPv6 Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Each IPv6 address has 128 bits. Written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits, each group representing 16 bits and separated by a colon, e.g. `1050:0000:0000:0000:0005:0600:300c:326b`. This can also be notated as `1050:0:0:0:5:600:300c:326b` by omitting leading zeros. -When you [create a public (flexible) IP address for a Load Balancer](/network/load-balancer/how-to/create-manage-flex-ips/), this address can use either IPv4 or IPv6 protocol. An IPv4 address is obligatory for all public Load Balancers, but an IPv6 address can be optionally added. +When you [create a public (flexible) IP address for a Load Balancer](/load-balancer/how-to/create-manage-flex-ips/), this address can use either IPv4 or IPv6 protocol. An IPv4 address is obligatory for all public Load Balancers, but an IPv6 address can be optionally added. ## Kubernetes Load Balancer -When you create a `LoadBalancer` service within your [Scaleway Kubernetes cluster](/containers/kubernetes/quickstart/), the Scaleway Cloud Controller Manager will spin up an external Scaleway Load Balancer with the correct configuration to expose the specified service in your cluster. +When you create a `LoadBalancer` service within your [Scaleway Kubernetes cluster](/kubernetes/quickstart/), the Scaleway Cloud Controller Manager will spin up an external Scaleway Load Balancer with the correct configuration to expose the specified service in your cluster. -The process for creating and managing Load Balancers for Kubernetes clusters is very specific - you **cannot** create or edit these via the Scaleway console or API. For full instructions on how to correctly create and configure a Scaleway Load Balancer for a Kubernetes cluster, see our [dedicated documentation](/containers/kubernetes/reference-content/kubernetes-load-balancer/). +The process for creating and managing Load Balancers for Kubernetes clusters is very specific - you **cannot** create or edit these via the Scaleway console or API. For full instructions on how to correctly create and configure a Scaleway Load Balancer for a Kubernetes cluster, see our [dedicated documentation](/kubernetes/reference-content/kubernetes-load-balancer/). ## Least connections @@ -143,11 +143,11 @@ See [balancing-methods](#balancing-methods). ## Load Balancers -[Load Balancers](/network/load-balancer/how-to/create-load-balancer/) are highly available and fully managed instances that allow you to distribute workload across multiple servers. They ensure the scaling of all your applications while securing their continuous availability, even in the event of heavy traffic. They are commonly used to improve the performance and reliability of websites, applications, databases and other services. +[Load Balancers](/load-balancer/how-to/create-load-balancer/) are highly available and fully managed instances that allow you to distribute workload across multiple servers. They ensure the scaling of all your applications while securing their continuous availability, even in the event of heavy traffic. They are commonly used to improve the performance and reliability of websites, applications, databases and other services. ## Private Load Balancer -A Load Balancer is defined as private when you choose the "private" [accessibility](#accessibility) option during Load Balancer creation. A Private Load Balancer has no public IP address, and only listens to requests or connections sent through the Private Network(s) to which it is attached. Read more about private Load Balancers and their characteristics and limitations in our [dedicated documentation](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). +A Load Balancer is defined as private when you choose the "private" [accessibility](#accessibility) option during Load Balancer creation. A Private Load Balancer has no public IP address, and only listens to requests or connections sent through the Private Network(s) to which it is attached. Read more about private Load Balancers and their characteristics and limitations in our [dedicated documentation](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). ## Protocol @@ -155,7 +155,7 @@ A protocol is a standard format for communication over a network. When you confi ## Proxy Protocol -Proxy Protocol is an internet protocol used to transfer connection information from the client (e.g. the client's IP address), through the Load Balancer and on to the destination server. For full information, see our [dedicated documentation](/network/load-balancer/reference-content/configuring-backends/#proxy-protocol). +Proxy Protocol is an internet protocol used to transfer connection information from the client (e.g. the client's IP address), through the Load Balancer and on to the destination server. For full information, see our [dedicated documentation](/load-balancer/reference-content/configuring-backends/#proxy-protocol). ## Round-robin @@ -171,7 +171,7 @@ See [customized error page](#customized-error-page) ## Server Name Identification (SNI) -SNI allows the server to host multiple [SSL/TLS certificates](#certificate) for multiple sites/applications on the same IP address and port number. It works as an extension to the [TLS](/network/load-balancer/concepts/#protocol) protocol: the client/browser specifies which hostname it is requesting at the start of the TLS handshake, allowing the server to respond appropriately. +SNI allows the server to host multiple [SSL/TLS certificates](#certificate) for multiple sites/applications on the same IP address and port number. It works as an extension to the [TLS](/load-balancer/concepts/#protocol) protocol: the client/browser specifies which hostname it is requesting at the start of the TLS handshake, allowing the server to respond appropriately. Scaleway Load Balancers can use SNI to define [routes](#routes) from a frontend to a specified TCP backend. @@ -181,15 +181,15 @@ Server timeout is a configurable value for your Load Balancer's backend. It defi ## SSL bridging -[SSL bridging](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) describes a configuration pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic) before initiating a new encrypted connection to the backend before forwarding traffic. +[SSL bridging](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) describes a configuration pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic) before initiating a new encrypted connection to the backend before forwarding traffic. ## SSL offloading -[SSL offloading](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) describes a pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic), with the intention to forward it unencrypted to the backend servers. This effectively "offloads" the work of decrypting traffic from the backend server to the Load Balancer. +[SSL offloading](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) describes a pattern where the Load Balancer terminates encrypted connections at the frontend (decrypting incoming traffic), with the intention to forward it unencrypted to the backend servers. This effectively "offloads" the work of decrypting traffic from the backend server to the Load Balancer. ## SSL passthrough -[SSL passthrough](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) is the simplest way to handle HTTPS traffic on a Load Balancer. As the name suggests, traffic is simply passed through the Load Balancer without being decrypted. +[SSL passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) is the simplest way to handle HTTPS traffic on a Load Balancer. As the name suggests, traffic is simply passed through the Load Balancer without being decrypted. ## Sticky session @@ -206,4 +206,4 @@ Tunnel timeout is a configurable value for your Load Balancer's backend. It defi ## Verify certificate -The [Verify Certificate configuration](/network/load-balancer/reference-content/configuring-backends/#verify-certificate) is relevant to Load Balancers with backends using HTTPS protocol, and specifies whether the Load Balancer should check the backend server's [certificate](#certificate) before initiating a connection. \ No newline at end of file +The [Verify Certificate configuration](/load-balancer/reference-content/configuring-backends/#verify-certificate) is relevant to Load Balancers with backends using HTTPS protocol, and specifies whether the Load Balancer should check the backend server's [certificate](#certificate) before initiating a connection. \ No newline at end of file diff --git a/network/load-balancer/how-to/add-certificate.mdx b/network/load-balancer/how-to/add-certificate.mdx index df5403106b..5ceb5d6c04 100644 --- a/network/load-balancer/how-to/add-certificate.mdx +++ b/network/load-balancer/how-to/add-certificate.mdx @@ -27,14 +27,14 @@ You may therefore hear certificates referred to as "SSL certificates", "TLS cert Adding an SSL/TLS certificate to your Load Balancer's frontend has the following effect: - Secure connections (e.g. HTTPS), can be established between the client and the Load Balancer. - The Load Balancer can therefore decrypt incoming secure traffic from the client and encrypt outgoing traffic on its way back to the client -- The Load Balancer can carry out layer 7 actions (e.g. establishing [cookie-based sticky sessions](/network/load-balancer/concepts/#sticky-session)) on the traffic it has decrypted. -- Depending on your Load Balancer's backend configuration, and whether your backend server also has a certificate, traffic can also be encrypted as it flows between the Load Balancer and the backend server ([SSL bridging](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-bridging)), or else left unencrypted ([SSL offloading](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-offloading)) +- The Load Balancer can carry out layer 7 actions (e.g. establishing [cookie-based sticky sessions](/load-balancer/concepts/#sticky-session)) on the traffic it has decrypted. +- Depending on your Load Balancer's backend configuration, and whether your backend server also has a certificate, traffic can also be encrypted as it flows between the Load Balancer and the backend server ([SSL bridging](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-bridging)), or else left unencrypted ([SSL offloading](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-offloading)) You may not need to add an SSL/TLS certificate to your Load Balancer's frontend if: -- Your backend server has an SSL/TLS certificate, and you want to use an [SSL passthrough](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-passthrough) setup for secure connections. Note that in this case, the Load Balancer will not be able to carry out any layer 7 actions on encrypted traffic. +- Your backend server has an SSL/TLS certificate, and you want to use an [SSL passthrough](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/#configuring-a-load-balancer-for-ssl-passthrough) setup for secure connections. Note that in this case, the Load Balancer will not be able to carry out any layer 7 actions on encrypted traffic. - Your backend server does not have an SSL/TLS certificate, but you do not want or need to allow clients to establish secure connections to the Load Balancer or your backend server. -Read [the documentation](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) about SSL bridging, offloading and passthrough configurations for more information on how to achieve these setups, and their advantages and disadvantages. +Read [the documentation](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) about SSL bridging, offloading and passthrough configurations for more information on how to achieve these setups, and their advantages and disadvantages. ### How does the secure connection work? @@ -52,20 +52,20 @@ Scaleway Load Balancer allows you to add certificates in two different ways: - [**Generate a Let's Encrypt certificate**](#how-to-generate-and-add-a-lets-encrypt-certificate) directly from the console. - [**Import an existing certificate**](#how-to-import-a-certificate), which can be from a Certificate Authority (CA) other than Let’s Encrypt, or be a self-signed certificate. -Note that after creating your certificate, you **must** [add it to a specified frontend](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) of your Load Balancer for it to take effect. +Note that after creating your certificate, you **must** [add it to a specified frontend](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) of your Load Balancer for it to take effect. ## How to generate and add a Let's Encrypt certificate - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) - A domain name, which points to your Load Balancer's IP address Bear in mind the following restrictions for creating Let's Encrypt certificates: -- They can only be added to Load Balancers that have [public accessibility](/network/load-balancer/concepts/#accessibility), that is to say that have a public IP address. It is not possible to add Let's Encrypt certificates to [private Load Balancers](/network/load-balancer/concepts/#private-load-balancer). +- They can only be added to Load Balancers that have [public accessibility](/load-balancer/concepts/#accessibility), that is to say that have a public IP address. It is not possible to add Let's Encrypt certificates to [private Load Balancers](/load-balancer/concepts/#private-load-balancer). - They cannot be created for Load Balancers which have a frontend listening on port 80 attached to a TCP backend. This is because the Let's Encrypt challenge would fail. Frontends listening on port 80 attached to an HTTP backend, or frontends listening on a port other than 80 and attached to a TCP backend, are both fine and compatible with Let's Encrypt certificates. @@ -105,8 +105,8 @@ Your certificate is added to your Load Balancer's frontend. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) - Either: - An existing certificate issued by a Certificate Authority, or - [Generated a self-signed certificate](#how-to-create-a-self-signed-certificate) diff --git a/network/load-balancer/how-to/create-frontends-backends.mdx b/network/load-balancer/how-to/create-frontends-backends.mdx index 9919f3d004..cf63faf1fb 100644 --- a/network/load-balancer/how-to/create-frontends-backends.mdx +++ b/network/load-balancer/how-to/create-frontends-backends.mdx @@ -18,20 +18,20 @@ When you create a Load Balancer, you can either add frontends and backends durin - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a frontend during creation of your Load Balancer -1. Follow the steps for [creating a Load Balancer](/network/load-balancer/how-to/create-load-balancer/). At the last stage, click **Add frontend and backend**. The following screen displays, the first step inviting you to configure a frontend: +1. Follow the steps for [creating a Load Balancer](/load-balancer/how-to/create-load-balancer/). At the last stage, click **Add frontend and backend**. The following screen displays, the first step inviting you to configure a frontend: 2. Enter a **name** for your frontend. -3. Enter a **port** number. The frontend will listen on this port, and forward the requests it receives from clients to the backend(s). Note that you cannot add an SSL certificate at this stage, but you can [add one after the creation of the Load Balancer](/network/load-balancer/how-to/add-certificate/). Similarly, you will be able to [enable HTTP/3](/network/load-balancer/reference-content/http2-http3/#configuring-your-load-balancer-for-http3) after adding a certificate. +3. Enter a **port** number. The frontend will listen on this port, and forward the requests it receives from clients to the backend(s). Note that you cannot add an SSL certificate at this stage, but you can [add one after the creation of the Load Balancer](/load-balancer/how-to/add-certificate/). Similarly, you will be able to [enable HTTP/3](/load-balancer/reference-content/http2-http3/#configuring-your-load-balancer-for-http3) after adding a certificate. - For more help with configuring your frontend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-frontends/). + For more help with configuring your frontend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-frontends/). Continue to the next section for [configuring a backend](#how-to-create-a-backend-during-creation-of-your-load-balancer). You will finalize creation of your frontend and backend at the same time, at the end of this section. @@ -81,14 +81,14 @@ You can add one or many frontends to your Load Balancer after its creation. Foll -5. Enter a **name**, **port** and (if necessary) [**SSL certificate(s)**](/network/load-balancer/how-to/add-certificate/) for your new frontend. Note that each frontend must listen on a different port. +5. Enter a **name**, **port** and (if necessary) [**SSL certificate(s)**](/load-balancer/how-to/add-certificate/) for your new frontend. Note that each frontend must listen on a different port. 6. Choose a **backend** to attach the frontend to, from the drop-down list provided. Alternatively, you can click the link to **create a new backend**, which opens the backend creation wizard in a new screen. -7. Under **Advanced Settings**, optionally use the to enable HTTP/3. The availability of this setting depends on your [Load Balancer's configuration](/network/load-balancer/reference-content/http2-http3/). +7. Under **Advanced Settings**, optionally use the to enable HTTP/3. The availability of this setting depends on your [Load Balancer's configuration](/load-balancer/reference-content/http2-http3/). - For more help with configuring your frontend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-frontends/). + For more help with configuring your frontend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-frontends/). 8. Click **Create frontend**. diff --git a/network/load-balancer/how-to/create-load-balancer.mdx b/network/load-balancer/how-to/create-load-balancer.mdx index 15b0be6114..4e90c4b60e 100644 --- a/network/load-balancer/how-to/create-load-balancer.mdx +++ b/network/load-balancer/how-to/create-load-balancer.mdx @@ -18,7 +18,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Load Balancer @@ -33,15 +33,15 @@ categories: 5. Select a Load Balancer **type**, according to your needs in terms of **bandwidth** and whether you want to be able to attach backend servers from other cloud providers than Scaleway (**Multi-cloud provider**). 6. Select the **accessibility** of your Load Balancer. Choose either: - - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/network/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). + - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). - **Public**: A public Load Balancer is accessible from the internet via its public IP address. You must choose from the following IP options: - - **IPv4**: A public [IPv4](/network/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/network/load-balancer/how-to/create-manage-flex-ips/). - - **IPv6**: You can optionally add a public [IPv6](/network/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/network/load-balancer/how-to/create-manage-flex-ips/). + - **IPv4**: A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). + - **IPv6**: You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). - Accessibility cannot be modified after creation of the Load Balancer. For more information about managing your Load Balancer's public IPs, see our [dedicated documentation](/network/load-balancer/how-to/create-manage-flex-ips/). + Accessibility cannot be modified after creation of the Load Balancer. For more information about managing your Load Balancer's public IPs, see our [dedicated documentation](/load-balancer/how-to/create-manage-flex-ips/). 7. Choose one of the following options: - Click **Create Load Balancer** to finish now and create your Load Balancer without any frontends or backends. You can configure and add frontends and backends to your Load Balancer whenever you want after creation. - - Click **Create and add front and backend** to create your Load Balancer and also immediately proceed to configuring a frontend and backend for it. See [how to create frontends and backends](/network/load-balancer/how-to/create-frontends-backends/) for help with this step. + - Click **Create and add front and backend** to create your Load Balancer and also immediately proceed to configuring a frontend and backend for it. See [how to create frontends and backends](/load-balancer/how-to/create-frontends-backends/) for help with this step. diff --git a/network/load-balancer/how-to/create-manage-acls.mdx b/network/load-balancer/how-to/create-manage-acls.mdx index 2e1b254a47..9a9cfca6d1 100644 --- a/network/load-balancer/how-to/create-manage-acls.mdx +++ b/network/load-balancer/how-to/create-manage-acls.mdx @@ -16,14 +16,14 @@ categories: -This page shows you how to create and manage ACLs. For more details on how ACLs work, and specification configuration examples, see our [ACL reference page](/network/load-balancer/reference-content/acls/). +This page shows you how to create and manage ACLs. For more details on how ACLs work, and specification configuration examples, see our [ACL reference page](/load-balancer/reference-content/acls/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) with a [frontend](/network/load-balancer/how-to/create-frontends-backends/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) with a [frontend](/load-balancer/how-to/create-frontends-backends/) ## How to create ACLs @@ -66,7 +66,7 @@ ACLs are created and managed at the frontend(s) of your Load Balancer. - Select a **scheme** (HTTP or HTTPS) and **port** for the redirect. - **Define custom**: Define a custom URI to direct to, in the format `https://{{host}}/{{path}}?{{query}}`. Note that the only valid placeholder values are `{{host}}`, `{{path}}` and `{{query}}`, and there must be no spaces between the curly braces and the string. You may use any, all or none of these placeholder values in your redirect URI. - For more information about using ACLs to set up redirections, see our [reference documentation](/network/load-balancer/reference-content/acls/#using-acls-to-redirect-traffic) + For more information about using ACLs to set up redirections, see our [reference documentation](/load-balancer/reference-content/acls/#using-acls-to-redirect-traffic) 9. Use the **Enable condition** toggle to choose whether to set a condition for the action. @@ -87,7 +87,7 @@ ACLs are created and managed at the frontend(s) of your Load Balancer. - **Path regex**: Enter a [regular expression](https://en.wikipedia.org/wiki/Regular_expression) to specify a pattern to search for in the HTTP request path, and click **Add filter**. Repeat this step to add multiple regex patterns to filter for, if required. Any traffic whose HTTP request path fits this regex will be considered to match the filter. - **Header**: Enter the **name** of the [HTTP header field](https://en.wikipedia.org/wiki/List_of_HTTP_header_fields) to use for the filter, and the **value** to filter for in this header, then click **Add filter**. For example, enter `Referer` followed by `exampledomain` to filter for occurrences of `exampledomain` in the `Referer` header. You can add multiple values to filter for if required but in only one header. Any traffic that has any of the specified values in the specified header field will be considered to match the filter. - For more information about setting up conditions and filters for ACLs, see our [reference documentation](/network/load-balancer/reference-content/acls/#what-conditions-can-be-set-for-acls) + For more information about setting up conditions and filters for ACLs, see our [reference documentation](/load-balancer/reference-content/acls/#what-conditions-can-be-set-for-acls) @@ -100,7 +100,7 @@ ACLs are created and managed at the frontend(s) of your Load Balancer. - If traffic matches an ACL's filter for an **Allow**, **Deny** or **Redirect** action (or if the action is applied unconditionally by that ACL), the action is applied immediately. The traffic is not subject to any further filtering or any further actions by any ACLs that follow. - Traffic that does **not** match criteria for the ACL's action will pass to the next ACL in the list, based on the order of priority. - If traffic reaches the end of the list of ACLs without having matched any filters to be explicitly allowed, denied or redirected, this traffic will be allowed to pass to the backend. - - **See our [reference documentation](/network/load-balancer/reference-content/acls/) for more information on how ACLs work and how you can configure them for different use cases.** + - **See our [reference documentation](/load-balancer/reference-content/acls/) for more information on how ACLs work and how you can configure them for different use cases.** ## How to edit ACLs diff --git a/network/load-balancer/how-to/create-manage-flex-ips.mdx b/network/load-balancer/how-to/create-manage-flex-ips.mdx index 793cb6bd8d..6987535565 100644 --- a/network/load-balancer/how-to/create-manage-flex-ips.mdx +++ b/network/load-balancer/how-to/create-manage-flex-ips.mdx @@ -13,9 +13,9 @@ categories: - network --- -This page shows you how to use [Load Balancer flexible IP addresses](/network/load-balancer/concepts/#flexible-ip-address). A flexible IP address is a public IP address for your Load Balancer. +This page shows you how to use [Load Balancer flexible IP addresses](/load-balancer/concepts/#flexible-ip-address). A flexible IP address is a public IP address for your Load Balancer. -- A flexible IP address can either be [IPv4](/network/load-balancer/concepts/#ipv4) or [IPv6](/network/load-balancer/concepts/#ipv6). +- A flexible IP address can either be [IPv4](/load-balancer/concepts/#ipv4) or [IPv6](/load-balancer/concepts/#ipv6). - You can create and hold flexible IP addresses independently of any Load Balancer. - When you create a Load Balancer with public accessibility, it must have a public IPv4 address. You can choose whether to create a new flexible IPv4 address for it, or use an existing one that you hold. The addition of a public IPv6 address is optional. If you would like to add one, you can choose whether to create a new flexible IPv6 address, or use an existing one that you hold. - When you delete the Load Balancer, you can choose to also delete its flexible IP address(es), or else hold the address(es) in your account to use with a future Load Balancer you create. @@ -30,12 +30,12 @@ The following limitations apply to Load Balancer flexible IPs: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to create a flexible IP address -When you create a Load Balancer, the creation wizard lets you create a new flexible IPv4 address (and, optionally, an IPv6 address as well) that will be automatically attached to the Load Balancer in question. See the [How to create a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) for full details. However, if you wish to create a flexible IP address to hold independently of any Load Balancer, follow the steps below: +When you create a Load Balancer, the creation wizard lets you create a new flexible IPv4 address (and, optionally, an IPv6 address as well) that will be automatically attached to the Load Balancer in question. See the [How to create a Load Balancer](/load-balancer/how-to/create-load-balancer/) for full details. However, if you wish to create a flexible IP address to hold independently of any Load Balancer, follow the steps below: 1. Click **Load Balancers** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. diff --git a/network/load-balancer/how-to/create-manage-routes.mdx b/network/load-balancer/how-to/create-manage-routes.mdx index aa28ccf3da..1bcfaab875 100644 --- a/network/load-balancer/how-to/create-manage-routes.mdx +++ b/network/load-balancer/how-to/create-manage-routes.mdx @@ -13,13 +13,13 @@ categories: - network --- -Routes allow you to specify, for a given frontend, which backends it should direct traffic to depending on the requested host. For [HTTP](/network/load-balancer/concepts/#protocol) frontends/backends, routes are based on HTTP Host headers. For [TCP](/network/load-balancer/concepts/#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single frontend. When no route rules match for an incoming connection/request, the frontend will forward to its default backend. +Routes allow you to specify, for a given frontend, which backends it should direct traffic to depending on the requested host. For [HTTP](/load-balancer/concepts/#protocol) frontends/backends, routes are based on HTTP Host headers. For [TCP](/load-balancer/concepts/#protocol) frontends/backends, they are based on **S**erver **N**ame **I**dentification (SNI). You can configure multiple routes on a single frontend. When no route rules match for an incoming connection/request, the frontend will forward to its default backend. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to create routes diff --git a/network/load-balancer/how-to/delete-load-balancer.mdx b/network/load-balancer/how-to/delete-load-balancer.mdx index 8f00632aa6..21ee5df000 100644 --- a/network/load-balancer/how-to/delete-load-balancer.mdx +++ b/network/load-balancer/how-to/delete-load-balancer.mdx @@ -16,8 +16,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to delete a Load Balancer diff --git a/network/load-balancer/how-to/manage-frontends-and-backends.mdx b/network/load-balancer/how-to/manage-frontends-and-backends.mdx index 44016c8e02..d9b843070b 100644 --- a/network/load-balancer/how-to/manage-frontends-and-backends.mdx +++ b/network/load-balancer/how-to/manage-frontends-and-backends.mdx @@ -23,16 +23,16 @@ This page shows you how to carry out these actions. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to create and add frontends to a Load Balancer -See our [dedicated documentation](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-after-creation-of-your-load-balancer). +See our [dedicated documentation](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-after-creation-of-your-load-balancer). ## How to create and add backends to a Load Balancer -See our [dedicated documentation](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-after-creation-of-your-load-balancer). +See our [dedicated documentation](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-after-creation-of-your-load-balancer). ## How to edit frontends @@ -49,9 +49,9 @@ See our [dedicated documentation](/network/load-balancer/how-to/create-frontends 6. Make your edits. You can change: - Frontend name - Port - - [SSL Certificate(s)](/network/load-balancer/how-to/add-certificate/) + - [SSL Certificate(s)](/load-balancer/how-to/add-certificate/) - Attached backend - - [HTTP/3 activation](/network/load-balancer/reference-content/http2-http3/#http3) (under **Advanced Settings**) + - [HTTP/3 activation](/load-balancer/reference-content/http2-http3/#http3) (under **Advanced Settings**) 4. Click **Edit frontend**. diff --git a/network/load-balancer/how-to/monitor-lb-cockpit.mdx b/network/load-balancer/how-to/monitor-lb-cockpit.mdx index 3021a3fca2..c696eb5b21 100644 --- a/network/load-balancer/how-to/monitor-lb-cockpit.mdx +++ b/network/load-balancer/how-to/monitor-lb-cockpit.mdx @@ -13,17 +13,17 @@ categories: - network --- -You can view your Load Balancer's metrics and logs by using [Scaleway Cockpit](/observability/cockpit/quickstart/). Load Balancer is fully integrated into Cockpit, and allows you to monitor your Load Balancers frontends, backends, and backend servers at a glance, and visualize your metrics, traffic and logs. This page explains how to get started with Scaleway Cockpit for viewing your Load Balancers metrics and logs. +You can view your Load Balancer's metrics and logs by using [Scaleway Cockpit](/cockpit/quickstart/). Load Balancer is fully integrated into Cockpit, and allows you to monitor your Load Balancers frontends, backends, and backend servers at a glance, and visualize your metrics, traffic and logs. This page explains how to get started with Scaleway Cockpit for viewing your Load Balancers metrics and logs. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to access the Grafana dashboard @@ -31,7 +31,7 @@ To view your Load Balancer's metrics and logs, use the Grafana dashboard which i - First, you must create a user and their associated credentials (a username and password) for Grafana - Then, you can use these credentials to access the Grafana dashboard for all your Scaleway products, via the Scaleway console. -1. Create a Grafana user and retrieve their username and password by [following this procedure](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. Create a Grafana user and retrieve their username and password by [following this procedure](/cockpit/how-to/retrieve-grafana-credentials/). 2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. @@ -65,8 +65,8 @@ In this section, you see various graphs which report on the status of different -- **Healthy loadbalancer backends**: Shows how many of your Load Balancer's backends currently have a healthy status. A backend is considered healthy if at least one of its [backend servers](/network/load-balancer/concepts/#backend-servers) is healthy and up. -- **Healthy loadbalancer backend servers**: Shows how many of your Load Balancer's backend servers are currently in a healthy state. A backend server is considered healthy if it passes its [health checks](/network/load-balancer/concepts/#health-checks), specifically if the number of failed health checks does not exceed the value set in the `Unhealthy threshold` parameter. +- **Healthy loadbalancer backends**: Shows how many of your Load Balancer's backends currently have a healthy status. A backend is considered healthy if at least one of its [backend servers](/load-balancer/concepts/#backend-servers) is healthy and up. +- **Healthy loadbalancer backend servers**: Shows how many of your Load Balancer's backend servers are currently in a healthy state. A backend server is considered healthy if it passes its [health checks](/load-balancer/concepts/#health-checks), specifically if the number of failed health checks does not exceed the value set in the `Unhealthy threshold` parameter. - **Backend servers health check**: Shows, for each backend server identified by its IP address and the name of the frontend it is attached to, its current status (`up` (i.e. healthy), or `down` (unhealthy)). - **"Backend name" health check**: Shows, for each backend identified by its name, how many of its backend servers are currently in a healthy state. diff --git a/network/load-balancer/how-to/resize-lb.mdx b/network/load-balancer/how-to/resize-lb.mdx index fcf3e9a179..8dab7d64f4 100644 --- a/network/load-balancer/how-to/resize-lb.mdx +++ b/network/load-balancer/how-to/resize-lb.mdx @@ -18,8 +18,8 @@ You can resize an existing Scaleway Load Balancer if you want to switch to a dif - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Load Balancer](/load-balancer/how-to/create-load-balancer/) 1. Click **Load Balancers** in the **Network** section of the [Scaleway console](https://console.scaleway.com) side menu. diff --git a/network/load-balancer/how-to/set-up-s3-failover.mdx b/network/load-balancer/how-to/set-up-s3-failover.mdx index c22abc2bb2..f16d255880 100644 --- a/network/load-balancer/how-to/set-up-s3-failover.mdx +++ b/network/load-balancer/how-to/set-up-s3-failover.mdx @@ -28,15 +28,15 @@ You can set up a customized error page during creation of your Load Balancer, or - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a bucket which is hosting a [bucket website](/storage/object/how-to/use-bucket-website/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a bucket which is hosting a [bucket website](/object-storage/how-to/use-bucket-website/) ## How to activate a customized error page failover during creation of your Load Balancer -1. Follow the instructions for [creating a Load Balancer](/network/load-balancer/how-to/create-load-balancer/). +1. Follow the instructions for [creating a Load Balancer](/load-balancer/how-to/create-load-balancer/). 2. Click the **+Advanced Settings** button while configuring your backend. -3. Slide the toggle to activate the customized error page feature, and enter a Scaleway Object Storage [Bucket Website](/storage/object/concepts/#bucket-website) URL in the box. Note that the URL of the bucket endpoint is not sufficient, the bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). +3. Slide the toggle to activate the customized error page feature, and enter a Scaleway Object Storage [Bucket Website](/object-storage/concepts/#bucket-website) URL in the box. Note that the URL of the bucket endpoint is not sufficient, the bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). This feature is only available for Load Balancers using the HTTP protocol on their backend. @@ -54,11 +54,11 @@ You can set up a customized error page during creation of your Load Balancer, or This feature is only available for Load Balancers using the HTTP protocol on their backend. -7. Enter a Scaleway Object Storage [Bucket Website](/storage/object/concepts/#bucket-website) URL in the box, if activating the feature. Note that the URL of the bucket endpoint is not sufficient, the bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). +7. Enter a Scaleway Object Storage [Bucket Website](/object-storage/concepts/#bucket-website) URL in the box, if activating the feature. Note that the URL of the bucket endpoint is not sufficient, the bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). 8. Click **Edit backend** to finish. ## How to create a static website for your customized error page -Having activated the customized error page feature on your Load Balancer, you must ensure that you have created a static website or webpage to display. See our [dedicated documentation](/storage/object/how-to/use-bucket-website/) to learn how to create a static website with Scaleway Object Storage. +Having activated the customized error page feature on your Load Balancer, you must ensure that you have created a static website or webpage to display. See our [dedicated documentation](/object-storage/how-to/use-bucket-website/) to learn how to create a static website with Scaleway Object Storage. diff --git a/network/load-balancer/how-to/use-edge-services.mdx b/network/load-balancer/how-to/use-edge-services.mdx index 2880c4cf71..cca1891568 100644 --- a/network/load-balancer/how-to/use-edge-services.mdx +++ b/network/load-balancer/how-to/use-edge-services.mdx @@ -22,14 +22,14 @@ Read on to learn how to create an Edge Services pipeline for your Load Balancer - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Load Balancer](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Load Balancer](/object-storage/how-to/create-a-bucket/) ## How to subscribe to Edge Services To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan lets you create a certain number of pipelines and consume a certain amount of cache data. -Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/network/edge-services/how-to/subscribe-edge-services/). +Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/edge-services/how-to/subscribe-edge-services/). ## How to create an Edge Services pipeline for Load Balancer @@ -45,13 +45,13 @@ You can create an Edge Services pipeline from the **Edge Services** section of t -4. [Follow step 3 onwards](/network/edge-services/how-to/create-pipeline-lb/#how-to-create-an-edge-services-pipeline-for-load-balancer) in our dedicated Edge Services documentation to finish creating your pipeline. +4. [Follow step 3 onwards](/edge-services/how-to/create-pipeline-lb/#how-to-create-an-edge-services-pipeline-for-load-balancer) in our dedicated Edge Services documentation to finish creating your pipeline. ## How to configure your pipeline See the dedicated Edge Services section of the documentation for help with: -- [Customizing your Edge Services endpoint](/network/edge-services/how-to/configure-custom-domain/) -- [Configuring your Edge Services cache](/network/edge-services/how-to/configure-cache/) +- [Customizing your Edge Services endpoint](/edge-services/how-to/configure-custom-domain/) +- [Configuring your Edge Services cache](/edge-services/how-to/configure-cache/) -To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/network/edge-services/) page. \ No newline at end of file +To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/edge-services/) page. \ No newline at end of file diff --git a/network/load-balancer/how-to/use-with-private-network.mdx b/network/load-balancer/how-to/use-with-private-network.mdx index 6ae307bf7c..2ba21f7dc0 100644 --- a/network/load-balancer/how-to/use-with-private-network.mdx +++ b/network/load-balancer/how-to/use-with-private-network.mdx @@ -13,16 +13,16 @@ categories: - network --- -The Private Network feature of the managed Load Balancers product lets you attach your Load Balancer to up to eight different Private Networks. [Scaleway Private Networks](/network/vpc/concepts/#private-networks) allow your cloud resources to communicate in an isolated and secure network. Load Balancers using Private Networks can communicate with their backend servers without using the public internet. +The Private Network feature of the managed Load Balancers product lets you attach your Load Balancer to up to eight different Private Networks. [Scaleway Private Networks](/vpc/concepts/#private-networks) allow your cloud resources to communicate in an isolated and secure network. Load Balancers using Private Networks can communicate with their backend servers without using the public internet. -[Private Load Balancers](/network/load-balancer/concepts/#private-load-balancer) must be connected to a Private Network in order to be functional, as they do not have a public IP address and can only receive requests from other resources on the Private Network. This is in contrast to public Load Balancers, which are accessible for requests via the internet through their public IP address, but can optionally use Private Networks to communicate with their backend servers. The procedure for attaching either a public or a private Load Balancer to a Private Network is the same, and described below. +[Private Load Balancers](/load-balancer/concepts/#private-load-balancer) must be connected to a Private Network in order to be functional, as they do not have a public IP address and can only receive requests from other resources on the Private Network. This is in contrast to public Load Balancers, which are accessible for requests via the internet through their public IP address, but can optionally use Private Networks to communicate with their backend servers. The procedure for attaching either a public or a private Load Balancer to a Private Network is the same, and described below. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Load Balancer](/network/load-balancer/how-to/create-load-balancer/) -- A [Private Network](/network/vpc/how-to/create-private-network/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Load Balancer](/load-balancer/how-to/create-load-balancer/) +- A [Private Network](/vpc/how-to/create-private-network/) ## How to attach a Private Network to your Load Balancer @@ -34,10 +34,10 @@ The Private Network feature of the managed Load Balancers product lets you attac 5. Select whether to attach to a new Private Network, or an existing one. -6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/network/ipam/concepts/#reserved-ip-address)** for the attachment. +6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. 7. Click **Attach to Private Network** to validate the form. The Private Network is attached to the Load Balancer and displays in the **Private Network** tab. - To attach several Private Networks to your Load Balancer, repeat the steps above for each of them. To see the Load Balancer's IP address on the Private Network, [follow this procedure](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). + To attach several Private Networks to your Load Balancer, repeat the steps above for each of them. To see the Load Balancer's IP address on the Private Network, [follow this procedure](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). ## How to detach a Private Network from your Load Balancer diff --git a/network/load-balancer/index.mdx b/network/load-balancer/index.mdx index bd78f5f138..d0aeeac17e 100644 --- a/network/load-balancer/index.mdx +++ b/network/load-balancer/index.mdx @@ -8,7 +8,7 @@ meta: productName="Load Balancer" productLogo="loadBalancers" description="Load Balancers distribute workloads across servers, ensuring scalable and continuously available applications, even during heavy traffic." - url="/network/load-balancer/quickstart/" + url="/load-balancer/quickstart/" label="Load Balancer Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create and configure a Load Balancer." label="View Quickstart" - url="/network/load-balancer/quickstart/" + url="/load-balancer/quickstart/" /> diff --git a/network/load-balancer/quickstart.mdx b/network/load-balancer/quickstart.mdx index 153e3cd90f..f31bb3197f 100644 --- a/network/load-balancer/quickstart.mdx +++ b/network/load-balancer/quickstart.mdx @@ -18,7 +18,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Load Balancer @@ -33,10 +33,10 @@ categories: 5. Select a Load Balancer **type**, according to your needs in terms of **bandwidth** and whether you want to be able to attach backend servers from other cloud providers than Scaleway (**Multi-cloud provider**). 6. Select the **accessibility** of your Load Balancer. Choose either: - - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/network/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/network/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). + - **Private**: A private Load Balancer will have no public IP address, and is only accessible from the Private Network(s) it is attached to. You can [attach your Load Balancer to a Private Network](/load-balancer/how-to/use-with-private-network/) after creation of the Load Balancer. [Read more about private Load Balancers](/load-balancer/reference-content/public-private-accessibility/#private-load-balancers). - **Public**: A public Load Balancer is accessible from the internet via its public IP address. You must choose from the following IP options: - - **IPv4**: A public [IPv4](/network/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/network/load-balancer/how-to/create-manage-flex-ips/). - - **IPv6**: You can optionally add a public [IPv6](/network/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/network/load-balancer/how-to/create-manage-flex-ips/). + - **IPv4**: A public [IPv4](/load-balancer/concepts/#ipv4) address is obligatory. You can either allocate a new IPv4 address, or select one of your [existing flexible IPv4 addresses](/load-balancer/how-to/create-manage-flex-ips/). + - **IPv6**: You can optionally add a public [IPv6](/load-balancer/concepts/#ipv6) address in addition to the IPv4 address. You can either allocate a new IPv6 address, or select one of your [existing flexible IPv6 addresses](/load-balancer/how-to/create-manage-flex-ips/). Accessibility cannot be modified after creation of the Load Balancer. @@ -48,10 +48,10 @@ categories: 1. Enter a **name** for your frontend. -2. Enter a **port** number. The frontend will listen on this port, and forward the requests it receives from clients to the backend(s). Note that you cannot add an SSL certificate at this stage, but you can [add one after the creation of the Load Balancer](/network/load-balancer/how-to/add-certificate/). Similarly, you will be able to [enable HTTP/3](/network/load-balancer/reference-content/http2-http3/#configuring-your-load-balancer-for-http3) after adding a certificate. +2. Enter a **port** number. The frontend will listen on this port, and forward the requests it receives from clients to the backend(s). Note that you cannot add an SSL certificate at this stage, but you can [add one after the creation of the Load Balancer](/load-balancer/how-to/add-certificate/). Similarly, you will be able to [enable HTTP/3](/load-balancer/reference-content/http2-http3/#configuring-your-load-balancer-for-http3) after adding a certificate. - For more help with configuring your frontend, see our [dedicated reference documentation](/network/load-balancer/reference-content/configuring-frontends/). + For more help with configuring your frontend, see our [dedicated reference documentation](/load-balancer/reference-content/configuring-frontends/). Continue to the next section for [creating a backend](#how-to-configure-your-backend). You will finalize creation of your frontend and backend at the same time, at the end of this section. @@ -88,10 +88,10 @@ When you have finished configuring your frontend and backend, click **Create fro Depending on your use case, you may need to carry out further configuration on your Load Balancer. Refer to the following documentation: -- [Add an SSL/TLS certificate](/network/load-balancer/how-to/add-certificate/), necessary for [SSL offloading or bridging](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) -- [Attach a Load Balancer to a Private Network](/network/load-balancer/how-to/use-with-private-network/) -- Set up Load Balancer [ACLs](/network/load-balancer/how-to/create-manage-acls/) or [routes](/network/load-balancer/how-to/create-manage-routes/) -- [Create an Edge Services pipeline](/network/load-balancer/how-to/use-edge-services/) for your Load Balancer +- [Add an SSL/TLS certificate](/load-balancer/how-to/add-certificate/), necessary for [SSL offloading or bridging](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/) +- [Attach a Load Balancer to a Private Network](/load-balancer/how-to/use-with-private-network/) +- Set up Load Balancer [ACLs](/load-balancer/how-to/create-manage-acls/) or [routes](/load-balancer/how-to/create-manage-routes/) +- [Create an Edge Services pipeline](/load-balancer/how-to/use-edge-services/) for your Load Balancer ## How to delete a Load Balancer @@ -102,5 +102,5 @@ Depending on your use case, you may need to carry out further configuration on y This will permanently delete your Load Balance, and all of its configuration data will be lost. This action is irreversible. 4. Type **DELETE** in the pop-up box. -5. Tick the checkbox if you want to delete the associated [flexible IP address](/network/load-balancer/how-to/create-manage-flex-ips/). +5. Tick the checkbox if you want to delete the associated [flexible IP address](/load-balancer/how-to/create-manage-flex-ips/). 6. Click **Delete Load Balancer**. \ No newline at end of file diff --git a/network/load-balancer/reference-content/acls.mdx b/network/load-balancer/reference-content/acls.mdx index a5e514df7b..420bcdd48e 100644 --- a/network/load-balancer/reference-content/acls.mdx +++ b/network/load-balancer/reference-content/acls.mdx @@ -17,7 +17,7 @@ categories: -You can learn how to set up ACLs in our [how to documentation](/network/load-balancer/how-to/create-manage-acls/). This page gives more detailed information, and advice about achieving specific configurations with your ACLs. +You can learn how to set up ACLs in our [how to documentation](/load-balancer/how-to/create-manage-acls/). This page gives more detailed information, and advice about achieving specific configurations with your ACLs. ## How do ACLs work? @@ -119,7 +119,7 @@ Use an ACL with the **redirect** action to redirect traffic. You can choose to r In this case, we want to redirect all incoming HTTP requests to HTTPS. Our Load Balancer already has an HTTP backend, with two frontends connected to this backend: -- Frontend 1 has an [SSL/TLS certificate](/network/load-balancer/how-to/add-certificate/), so is configured to receive HTTPS requests +- Frontend 1 has an [SSL/TLS certificate](/load-balancer/how-to/add-certificate/), so is configured to receive HTTPS requests - Frontend 2 has no SSL/TLS certificate, so receives clear text HTTP traffic. We will create our ACL on this frontend, to redirect HTTP traffic to HTTPS. Construct one ACL on the HTTP frontend as follows: diff --git a/network/load-balancer/reference-content/configuring-backends.mdx b/network/load-balancer/reference-content/configuring-backends.mdx index c6bd9cd054..7127d37f9d 100644 --- a/network/load-balancer/reference-content/configuring-backends.mdx +++ b/network/load-balancer/reference-content/configuring-backends.mdx @@ -18,9 +18,9 @@ dates: Each Load Balancer is configured with one or several backends. A backend represents a set of backend servers that the Load Balancer’s frontend(s) forwards requests to using the specified configuration (port, protocol, Proxy Protocol etc.). -You can create and configure frontends and backends [while creating a Load Balancer](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-during-creation-of-your-load-balancer) or choose to create an “empty” Load Balancer and [add frontends and backends](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-after-creation-of-your-load-balancer) later on. +You can create and configure frontends and backends [while creating a Load Balancer](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-during-creation-of-your-load-balancer) or choose to create an “empty” Load Balancer and [add frontends and backends](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-backend-after-creation-of-your-load-balancer) later on. -You have access to the same configuration settings for your backend whether you create it with the Load Balancer, or later. Any of these settings can be [edited](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) thereafter. Read on to find out more about the different configuration settings available for your backend. +You have access to the same configuration settings for your backend whether you create it with the Load Balancer, or later. Any of these settings can be [edited](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks) thereafter. Read on to find out more about the different configuration settings available for your backend. ## Configuring basic settings @@ -37,7 +37,7 @@ The Load Balancer initiates connections to its backend servers using the protoco The port number must be between 1 and 65535. -You may also be interested in reading about choosing protocols (and TLS encryption settings, below) for different [offloading / passthrough / bridging configurations](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). +You may also be interested in reading about choosing protocols (and TLS encryption settings, below) for different [offloading / passthrough / bridging configurations](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). ### TLS encryption @@ -53,7 +53,7 @@ When the Load Balancer initiates an encrypted connection to a backend server, th This setting mostly concerns those using self-signed certificates on the backend server/s. -Note that the same Verify Certificate setting you select here will also be used for [health checks](/network/load-balancer/reference-content/configuring-health-checks/), and cannot be overridden. +Note that the same Verify Certificate setting you select here will also be used for [health checks](/load-balancer/reference-content/configuring-health-checks/), and cannot be overridden. ### Proxy Protocol @@ -159,8 +159,8 @@ Benefits of this feature include: - Providing information on service status or maintenance - Redirecting to a mirrored site or skeleton site -Note that when entering the Object Storage link to redirect to, the URL of the bucket endpoint is not sufficient. The bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). See our [dedicated documentation](/network/load-balancer/how-to/set-up-s3-failover/) for further help. +Note that when entering the Object Storage link to redirect to, the URL of the bucket endpoint is not sufficient. The bucket website URL is specifically required (e.g.`https://my-bucket.s3-website.nl-ams.scw.cloud`). See our [dedicated documentation](/load-balancer/how-to/set-up-s3-failover/) for further help. ## Health checks -See our [dedicated documentation on configuring health checks](/network/load-balancer/reference-content/configuring-health-checks/). \ No newline at end of file +See our [dedicated documentation on configuring health checks](/load-balancer/reference-content/configuring-health-checks/). \ No newline at end of file diff --git a/network/load-balancer/reference-content/configuring-frontends.mdx b/network/load-balancer/reference-content/configuring-frontends.mdx index fc67867d92..9b104342fd 100644 --- a/network/load-balancer/reference-content/configuring-frontends.mdx +++ b/network/load-balancer/reference-content/configuring-frontends.mdx @@ -18,7 +18,7 @@ dates: Every Load Balancer must have at least one frontend, itself attached to a backend, in order to be functional. -You can [create a frontend at the same time as creating the Load Balancer itself](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-during-creation-of-your-load-balancer), or create an "empty" Load Balancer and [create/add a frontend(s) later](/network/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-after-creation-of-your-load-balancer). +You can [create a frontend at the same time as creating the Load Balancer itself](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-during-creation-of-your-load-balancer), or create an "empty" Load Balancer and [create/add a frontend(s) later](/load-balancer/how-to/create-frontends-backends/#how-to-create-a-frontend-after-creation-of-your-load-balancer). When creating a frontend and backend at the same time as creating the Load Balancer, you have access only to minimum configuration settings for the frontend: - Frontend name @@ -31,9 +31,9 @@ When creating a new frontend (or editing an existing one) **after** creating the - Backend to attach - Enable/disable HTTP/3 -You can [edit any of these settings](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) after creating the frontend, whenever you wish. +You can [edit any of these settings](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) after creating the frontend, whenever you wish. -You can create multiple frontends to listen on different ports, and connect them to different backends as required. You can also set up custom [ACL rules](/network/load-balancer/how-to/create-manage-acls/) and [routes](/network/load-balancer/how-to/create-manage-routes/) for each frontend. +You can create multiple frontends to listen on different ports, and connect them to different backends as required. You can also set up custom [ACL rules](/load-balancer/how-to/create-manage-acls/) and [routes](/load-balancer/how-to/create-manage-routes/) for each frontend. ## Frontend name @@ -55,11 +55,11 @@ You can only add an SSL certificate to a frontend after creation of the Load Bal -You can add an SSL/TLS certificate to your frontend to allow clients to securely connect to the Load Balancer via an encrypted connection. This is necessary for [SSL bridging and SSL offloading configurations](/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). +You can add an SSL/TLS certificate to your frontend to allow clients to securely connect to the Load Balancer via an encrypted connection. This is necessary for [SSL bridging and SSL offloading configurations](/load-balancer/reference-content/ssl-bridging-offloading-passthrough/). When creating a certificate you can generate a Let's Encrypt certificate directly from the console, or import an existing certificate. This could be from a third-party Certificate Authority (CA), or be a self-signed certificate. -Find out more about creating and adding different types of SSL certificates in our [dedicated documentation](/network/load-balancer/how-to/add-certificate/). +Find out more about creating and adding different types of SSL certificates in our [dedicated documentation](/load-balancer/how-to/add-certificate/). ## Attached backend @@ -69,7 +69,7 @@ When creating a frontend after creating the Load Balancer, you can choose which -You can attach different frontends to the same backend. They will all forward traffic to this backend. However, you cannot attach multiple backends to the same frontend. To forward traffic from the same frontend to various different backends depending on the client's HTTP Host headers or SNI, create [Routes](/network/load-balancer/how-to/create-manage-routes/) for your frontend. +You can attach different frontends to the same backend. They will all forward traffic to this backend. However, you cannot attach multiple backends to the same frontend. To forward traffic from the same frontend to various different backends depending on the client's HTTP Host headers or SNI, create [Routes](/load-balancer/how-to/create-manage-routes/) for your frontend. @@ -85,4 +85,4 @@ Enable HTTP/3 to allow HTTP/3 connections between the client and the Load Balanc Note that in order to enable HTTP/3, the frontend must have an SSL/TLS certificate, and be attached to a backend set to HTTP protocol. -Read more about HTTP/3 in our [dedicated documentation](/network/load-balancer/reference-content/http2-http3/). \ No newline at end of file +Read more about HTTP/3 in our [dedicated documentation](/load-balancer/reference-content/http2-http3/). \ No newline at end of file diff --git a/network/load-balancer/reference-content/configuring-health-checks.mdx b/network/load-balancer/reference-content/configuring-health-checks.mdx index 47ab5c8343..1244d445ef 100644 --- a/network/load-balancer/reference-content/configuring-health-checks.mdx +++ b/network/load-balancer/reference-content/configuring-health-checks.mdx @@ -22,7 +22,7 @@ In this document, we explain some of the different settings available when setti ## Health check types -Health checks are available in many different types. By default, the health check type is set to be the same as that of the [backend protocol](/network/load-balancer/reference-content/configuring-backends/#protocol-and-port), that is to say **TCP** or **HTTP**. However, this can be overridden. +Health checks are available in many different types. By default, the health check type is set to be the same as that of the [backend protocol](/load-balancer/reference-content/configuring-backends/#protocol-and-port), that is to say **TCP** or **HTTP**. However, this can be overridden. The following health check types are available: @@ -96,13 +96,13 @@ No additional settings are required for TCP health checks. This check consists o You can choose to activate or deactivate TLS for health checks. Activating TLS encrypts connections between the Load Balancer and the backend server(s) during health checks. Note that the backend server should have its own SSL/TLS certificate -The activation setting is inherited from your [backend configuration](/network/load-balancer/reference-content/configuring-backends/#tls-encryption), however, you can choose to override this for health checks if you wish. +The activation setting is inherited from your [backend configuration](/load-balancer/reference-content/configuring-backends/#tls-encryption), however, you can choose to override this for health checks if you wish. ## Verify certificate If you activated TLS encryption for your health check, the Verify Certificate setting displays. This determines whether the backend server's certificate is verified during health checks. -This setting is inherited from the [backend configuration](/network/load-balancer/reference-content/configuring-backends/#verify-certificate) and cannot be overridden: +This setting is inherited from the [backend configuration](/load-balancer/reference-content/configuring-backends/#verify-certificate) and cannot be overridden: - If you activated TLS on your backend, the Verify Certificate setting you chose there is inherited for health checks. - If you did not activate TLS on your backend configuration, the backend server's certificate will **not** be verified during health checks and you do not have the option to activate the setting here. @@ -119,7 +119,7 @@ The following versions of Proxy Protocol are available: * **Proxy Protocol v2-ssl**: Version two with SSL information extension added, which provides information on SSL connection settings originally sent by the client. * **Proxy Protocol v2-ssl-cn**: Version two with SSL information extension added as above, as well as the common name from the subject of the client certificate (if any). -If you activated Proxy Protocol on your [backend configuration](/network/load-balancer/reference-content/configuring-backends/#proxy-protocol), it will also be activated by default for your health checks. Note that: +If you activated Proxy Protocol on your [backend configuration](/load-balancer/reference-content/configuring-backends/#proxy-protocol), it will also be activated by default for your health checks. Note that: - You can choose to override the inherited setting and deactivate Proxy Protocol for health checks if you wish. - If you keep Proxy Protocol activated for health checks, the Proxy Protocol version is inherited from the backend configuration and cannot be overridden. diff --git a/network/load-balancer/reference-content/http2-http3.mdx b/network/load-balancer/reference-content/http2-http3.mdx index 12dd12c828..a30452bde6 100644 --- a/network/load-balancer/reference-content/http2-http3.mdx +++ b/network/load-balancer/reference-content/http2-http3.mdx @@ -56,12 +56,12 @@ In brief: HTTP/2 is supported by default on frontends meeting the following conditions: - The frontend is attached to an HTTP backend -- The frontend has an [SSL/TLS certificate](/network/load-balancer/how-to/add-certificate/). +- The frontend has an [SSL/TLS certificate](/load-balancer/how-to/add-certificate/). HTTP/2 is supported by default on backends meeting the following conditions: -- The backend has [TLS activated](/network/load-balancer/reference-content/configuring-backends/#tls-encryption). -- The [backend server](/network/load-balancer/concepts/#backend-servers) is configured to support HTTP/2. +- The backend has [TLS activated](/load-balancer/reference-content/configuring-backends/#tls-encryption). +- The [backend server](/load-balancer/concepts/#backend-servers) is configured to support HTTP/2. @@ -74,12 +74,12 @@ HTTP/2 is supported by default on backends meeting the following conditions: HTTP/3 is supported on frontends meeting the following conditions: - The frontend is attached to an HTTP backend -- The frontend has an [SSL/TLS certificate](/network/load-balancer/how-to/add-certificate/). +- The frontend has an [SSL/TLS certificate](/load-balancer/how-to/add-certificate/). - HTTP/3 has been activated on the frontend (see below). HTTP/3 is not supported on backends in any case. -To create a frontend that allows HTTP/3 connections, follow the instructions for [adding a frontend to your Load Balancer](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-create-and-add-frontends-to-a-load-balancer) or [editing an existing frontend](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) +To create a frontend that allows HTTP/3 connections, follow the instructions for [adding a frontend to your Load Balancer](/load-balancer/how-to/manage-frontends-and-backends/#how-to-create-and-add-frontends-to-a-load-balancer) or [editing an existing frontend](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-frontends) - Under **Configure backend**, ensure that you choose a backend using HTTP protocol. - Under **Advanced Settings**, select **Enable HTTP/3**. diff --git a/network/load-balancer/reference-content/kubernetes-load-balancer.mdx b/network/load-balancer/reference-content/kubernetes-load-balancer.mdx index 9d5c958eb7..0a3450bba3 100644 --- a/network/load-balancer/reference-content/kubernetes-load-balancer.mdx +++ b/network/load-balancer/reference-content/kubernetes-load-balancer.mdx @@ -13,17 +13,17 @@ categories: - network --- -If you are using Scaleway's [managed Kubernetes solution](/containers/kubernetes/quickstart/), you may want to create a Load Balancer in order to expose an application running inside your cluster to the internet. +If you are using Scaleway's [managed Kubernetes solution](/kubernetes/quickstart/), you may want to create a Load Balancer in order to expose an application running inside your cluster to the internet. Load Balancers for Kubernetes clusters should **always** be provisioned via the cluster's Cloud Controller Manager. It is **not** correct procedure to provision the Load Balancer by creating a Scaleway Load Balancer in the console or via the API, and then attempting to use it as your cluster's external Load Balancer. Full documentation for creating and configuring a Load Balancer for your cluster can be found in the Kubernetes section, on the following pages: -- [Exposing Kubernetes services to the internet](/containers/kubernetes/reference-content/exposing-services/) -- [Creating, configuring and troubleshooting a Load Balancer service](/containers/kubernetes/reference-content/kubernetes-load-balancer/) -- [Managing Load Balancer IPs](/containers/kubernetes/reference-content/managing-load-balancer-ips/) -- [Using Load Balancer annotations](/containers/kubernetes/reference-content/using-load-balancer-annotations/) -- [Exposing a Kubernetes Kapsule ingress controller service with a Load Balancer](/containers/kubernetes/reference-content/lb-ingress-controller/) +- [Exposing Kubernetes services to the internet](/kubernetes/reference-content/exposing-services/) +- [Creating, configuring and troubleshooting a Load Balancer service](/kubernetes/reference-content/kubernetes-load-balancer/) +- [Managing Load Balancer IPs](/kubernetes/reference-content/managing-load-balancer-ips/) +- [Using Load Balancer annotations](/kubernetes/reference-content/using-load-balancer-annotations/) +- [Exposing a Kubernetes Kapsule ingress controller service with a Load Balancer](/kubernetes/reference-content/lb-ingress-controller/) You may also find the following resources helpful: diff --git a/network/load-balancer/reference-content/public-private-accessibility.mdx b/network/load-balancer/reference-content/public-private-accessibility.mdx index a876c1f971..2b567ae82b 100644 --- a/network/load-balancer/reference-content/public-private-accessibility.mdx +++ b/network/load-balancer/reference-content/public-private-accessibility.mdx @@ -31,7 +31,7 @@ A Load Balancer is defined as public when you choose the "public" accessibility - It can optionally have an additional public IPv6 address. - The Load Balancer is accessible over the public internet via its public IP address(es), but can optionally also be attached to up to eight different Private Networks. - It can be configured or deleted using the Scaleway API, console, CLI, Terraform or other devtools. -- It provides its metrics to [Scaleway Cockpit](/observability/cockpit/concepts/#cockpit), allows the use of Let's Encrypt certificates, and (if the appropriate Load Balancer type is selected), supports multi-cloud IP addresses for its backend servers. +- It provides its metrics to [Scaleway Cockpit](/cockpit/concepts/#cockpit), allows the use of Let's Encrypt certificates, and (if the appropriate Load Balancer type is selected), supports multi-cloud IP addresses for its backend servers. @@ -40,17 +40,17 @@ A Load Balancer is defined as public when you choose the "public" accessibility A Load Balancer is defined as private when you choose the "private" accessibility option during Load Balancer creation. A private Load Balancer has the following characteristics: - It has no public IP address for sending requests or initiating TCP connections. -- It only listens to requests or connections sent to its interface(s) on the [Private Network(s)](/network/vpc/concepts/#private-networks) it is attached to. It is not accessible over the public internet. +- It only listens to requests or connections sent to its interface(s) on the [Private Network(s)](/vpc/concepts/#private-networks) it is attached to. It is not accessible over the public internet. - Like a public Load Balancer, it can be attached to up to eight different Private Networks. - It can be configured or deleted using the Scaleway API, console, CLI, Terraform, or other devtools. -- It provides its metrics to [Scaleway Cockpit](/observability/cockpit/concepts/#cockpit), even though there is no traffic. -- It does not allow the use of a Let's Encrypt [certificate](/network/load-balancer/concepts/#certificate) - only imported certificates are supported. +- It provides its metrics to [Scaleway Cockpit](/cockpit/concepts/#cockpit), even though there is no traffic. +- It does not allow the use of a Let's Encrypt [certificate](/load-balancer/concepts/#certificate) - only imported certificates are supported. - It does not support multi-cloud IP addresses for its backend servers, since it is not directly connected to the internet. Routes to them are thus, not guaranteed. A private Load Balancer can be used to balance requests between backends internally, where your backends' clients are in the same VPC as the Load Balancer. The security of your infrastructure is strengthened, as the Load Balancer does not have a public IP address and is not accessible over the public internet. -When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address). [VPC routing](/network/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate. +When you attach a private Load Balancer to multiple Private Networks, it has an IP address in each one. The Load Balancer can then forward traffic to any resource or service attached to any of its Private Networks, thus allowing inter-Private-Networks load balancing. Scaleway's managed DNS also makes it possible to contact the Load Balancer over the Private Network without knowing its IP address (using `lb-name.pn-name`, which then resolves to its private IP address). [VPC routing](/vpc/concepts/#routing) also allows Load Balancers on different Private Networks in the same VPC to communicate. \ No newline at end of file diff --git a/network/load-balancer/reference-content/sni-route-deprecation.mdx b/network/load-balancer/reference-content/sni-route-deprecation.mdx index c7ce55e302..11def42332 100644 --- a/network/load-balancer/reference-content/sni-route-deprecation.mdx +++ b/network/load-balancer/reference-content/sni-route-deprecation.mdx @@ -15,7 +15,7 @@ categories: This page documents the deprecation of SNI routes with HTTP backends on Scaleway Load Balancers -We removed the ability to create SNI based [routes](/network/load-balancer/how-to/create-manage-routes/) to HTTP backends in Scaleway Load Balancer. This feature was deprecated on March 1st 2023, and removed on June 1st 2023. +We removed the ability to create SNI based [routes](/load-balancer/how-to/create-manage-routes/) to HTTP backends in Scaleway Load Balancer. This feature was deprecated on March 1st 2023, and removed on June 1st 2023. - SNI routes are still available and supported for TCP backends. - SNI routes with HTTP backends are no longer available. diff --git a/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough.mdx b/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough.mdx index c9588f8cac..e414669750 100644 --- a/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough.mdx +++ b/network/load-balancer/reference-content/ssl-bridging-offloading-passthrough.mdx @@ -29,9 +29,9 @@ SSL bridging allows the user to initiate a secure, encrypted connection with the To configure your Load Balancer for SSL bridging: -- The frontend must have a [certificate](/network/load-balancer/how-to/add-certificate/). +- The frontend must have a [certificate](/load-balancer/how-to/add-certificate/). - The frontend must be linked to a backend which has TLS activated. -- The backend server should have its own [certificate](/network/load-balancer/concepts/#certificate). +- The backend server should have its own [certificate](/load-balancer/concepts/#certificate). ## Configuring a Load Balancer for SSL offloading @@ -41,11 +41,11 @@ SSL offloading, also known as SSL termination, allows the user to initiate a sec To configure your Load Balancer for SSL offloading: -- The frontend must have a [certificate](/network/load-balancer/how-to/add-certificate/). +- The frontend must have a [certificate](/load-balancer/how-to/add-certificate/). - The frontend must be linked to a backend which uses HTTP protocol. - The backend server does not need its own certificate. -If you want to configure your Load Balancer for SSL offloading using the API, see our [dedicated guide](/network/load-balancer/api-cli/setting-up-ssl-offloading/). If you have a Kubernetes Load Balancer configured for SSL offloading and are having SSL certificate issues, see our [troubleshooting section](/containers/kubernetes/reference-content/kubernetes-load-balancer/#load-balancer-certificate-error-using-ssl-offload). +If you want to configure your Load Balancer for SSL offloading using the API, see our [dedicated guide](/load-balancer/api-cli/setting-up-ssl-offloading/). If you have a Kubernetes Load Balancer configured for SSL offloading and are having SSL certificate issues, see our [troubleshooting section](/kubernetes/reference-content/kubernetes-load-balancer/#load-balancer-certificate-error-using-ssl-offload). ## Configuring a Load Balancer for SSL passthrough @@ -58,4 +58,4 @@ To configure your Load Balancer for SSL passthrough: - The frontend does not need a certificate and can listen on any port. - The frontend must be linked to a backend which uses TCP protocol, and the TLS toggle should be disabled in the backend configuration. - The backend server must listen with its HTTP server process on the same port as configured for the backend. -- The backend server must have its own [certificate](/network/load-balancer/concepts/#certificate). \ No newline at end of file +- The backend server must have its own [certificate](/load-balancer/concepts/#certificate). \ No newline at end of file diff --git a/network/load-balancer/troubleshooting/load-balancer-limitations.mdx b/network/load-balancer/troubleshooting/load-balancer-limitations.mdx index d55bd8d2ad..1a49a8519c 100644 --- a/network/load-balancer/troubleshooting/load-balancer-limitations.mdx +++ b/network/load-balancer/troubleshooting/load-balancer-limitations.mdx @@ -18,6 +18,6 @@ This page sets out some current limitations of Scaleway Load Balancer. - A public Load Balancer must have an IPv4 address, it cannot only have an IPv6 address. However, it is possible to allocate a public IPv6 address in addition to an IPv4 address. IPv6 is also supported between your Load Balancer and backend servers. - Each Load Balancer supports only one public IPv4 and one IPv6 address at a time. -For more information about restrictions with Load Balancer public IP addresses, see the [dedicated documentation](/network/load-balancer/how-to/create-manage-flex-ips/) +For more information about restrictions with Load Balancer public IP addresses, see the [dedicated documentation](/load-balancer/how-to/create-manage-flex-ips/) -For further information generally, refer to the [Load Balancers How To](/network/load-balancer/how-to/), [Load Balancers FAQ](/faq/loadbalancer/) and [API documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/). +For further information generally, refer to the [Load Balancers How To](/load-balancer/how-to/), [Load Balancers FAQ](/faq/loadbalancer/) and [API documentation](https://www.scaleway.com/en/developers/api/load-balancer/zoned-api/). diff --git a/network/public-gateways/concepts.mdx b/network/public-gateways/concepts.mdx index 076be8ea24..1930850ad2 100644 --- a/network/public-gateways/concepts.mdx +++ b/network/public-gateways/concepts.mdx @@ -19,22 +19,22 @@ The Public Gateway can advertise a default route to resources on an attached Pri You can choose to activate the advertisement of the default route when attaching a Private Network to a Public Gateway. The default route is propagated through DHCP. -After activating the default route, all outbound and inbound traffic for resources attached to the Private Network is directed through the Public Gateway. This includes SSH traffic destined for Instances, which means you will need to [manage SSH connections differently](/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/). +After activating the default route, all outbound and inbound traffic for resources attached to the Private Network is directed through the Public Gateway. This includes SSH traffic destined for Instances, which means you will need to [manage SSH connections differently](/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/). ## DHCP -DHCP was previously a functionality of Scaleway Public Gateways, but has now been moved and is integrated directly into Private Networks. [Read more about DHCP on Private Networks](/network/vpc/concepts#dhcp). +DHCP was previously a functionality of Scaleway Public Gateways, but has now been moved and is integrated directly into Private Networks. [Read more about DHCP on Private Networks](/vpc/concepts#dhcp). ## DNS The **D**omain **N**ame **S**ystem (DNS) is a naming system for devices connected to the internet or Private Networks. Most prominently, DNS servers translate text-based domain names (e.g. www.scaleway.com) to numerical IP addresses (e.g. 51.158.66.220). -[Private Networks](/network/vpc/concepts#private-networks) benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). When a Private Network is attached to a [legacy Public Gateway](#ipam) however, the gateway's DNS takes priority over that of the Private Network, to allow hostname resolution across different Private Networks. +[Private Networks](/vpc/concepts#private-networks) benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). When a Private Network is attached to a [legacy Public Gateway](#ipam) however, the gateway's DNS takes priority over that of the Private Network, to allow hostname resolution across different Private Networks. ## Flexible IP -Flexible IP addresses are [public IP addresses](#public-ip-address) associated with your account, which you can hold independently of any created resource. When you create a Public Gateway, it receives a flexible (public) IP address by default. You can [detach, reattach and migrate](/network/public-gateways/how-to/use-flexible-ips/) your flexible IPs between your Public Gateways at your convenience. Note that: +Flexible IP addresses are [public IP addresses](#public-ip-address) associated with your account, which you can hold independently of any created resource. When you create a Public Gateway, it receives a flexible (public) IP address by default. You can [detach, reattach and migrate](/public-gateways/how-to/use-flexible-ips/) your flexible IPs between your Public Gateways at your convenience. Note that: - Each Public Gateway **must** have a public IP attached to it, so if you detach one flexible IP from the Public Gateway you must attach another. - Public Gateway flexible IPs are unique to Public Gateways, and cannot be used with other products (and vice versa). - Public Gateways are not compatible with IPv6, so its flexible IP is necessarily IPv4. @@ -49,11 +49,11 @@ Scaleway is implementing [IP mobility](https://www.scaleway.com/en/blog/ip-mobil ## IPAM -IPAM is Scaleway's **IP** **A**ddress **M**anager tool. Read more about it in our [dedicated IPAM documentation](/network/ipam/). +IPAM is Scaleway's **IP** **A**ddress **M**anager tool. Read more about it in our [dedicated IPAM documentation](/ipam/). Scaleway Public Gateways are either in **Legacy mode** or **IPAM mode**. The mode of each of your gateways is displayed via a badge in the [gateway listing](https://console.scaleway.com/public-gateway/public-gateways) page of the Scaleway console. -**Legacy** Public Gateways use a [workaround](/network/vpc/reference-content/vpc-migration/#public-gateways-and-vpc) to ensure IPAM compatibility. Your gateway is a legacy gateway if: +**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 devtools 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). @@ -67,10 +67,10 @@ Private Networks attached to legacy Public Gateways must stay in the gateway's a - 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 cannot "migrate" a legacy Public Gateway to become an IPAM-mode gateway. While legacy Public Gateways continue to function thanks to our [workaround](/network/vpc/reference-content/vpc-migration/#public-gateways-and-vpc), you cannot modify them to become natively integrated IPAM networks. If you wish to have an IPAM-mode Public Gateway, for example to benefit from IP management via Scaleway's [IPAM](https://www.scaleway.com/en/developers/api/vpc/) API as more features become available, or to use Kapsule with full isolation, you must create a new gateway. +You cannot "migrate" a legacy Public Gateway to become an IPAM-mode gateway. While legacy Public Gateways continue to function thanks to our [workaround](/vpc/reference-content/vpc-migration/#public-gateways-and-vpc), you cannot modify them to become natively integrated IPAM networks. If you wish to have an IPAM-mode Public Gateway, for example to benefit from IP management via Scaleway's [IPAM](https://www.scaleway.com/en/developers/api/vpc/) API as more features become available, or to use Kapsule with full isolation, you must create a new gateway. -When creating a Kubernetes Kapsule cluster with [full isolation](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be an IPAM-mode gateway. +When creating a Kubernetes Kapsule cluster with [full isolation](/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be an IPAM-mode gateway. ## Legacy gateway @@ -85,19 +85,19 @@ See [IPAM](#ipam). - **Static NAT** enables ingress traffic from the public internet towards devices on a Private Network by mapping pre-defined ports of the public IP address of the gateway to specific ports and IP addresses on the Private Network. You can optionally add Static NAT configurations to your Public Gateway. -See our documentation on [reviewing and configuring NAT](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) for more information. +See our documentation on [reviewing and configuring NAT](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) for more information. ## Private IP address -Private [IP addresses](#ip-address) identify devices on local/Private Networks. They are not routed on the internet. When you attach a Public Gateway to a Private Network, it will [automatically receive a private IPv4 address on that network](/network/vpc/concepts/#cidr-block), and can communicate securely with other attached resources via their private IP addresses. As Public Gateways are not compatible with IPv6, they will not receive a private IPv6 address on the network. +Private [IP addresses](#ip-address) identify devices on local/Private Networks. They are not routed on the internet. When you attach a Public Gateway to a Private Network, it will [automatically receive a private IPv4 address on that network](/vpc/concepts/#cidr-block), and can communicate securely with other attached resources via their private IP addresses. As Public Gateways are not compatible with IPv6, they will not receive a private IPv6 address on the network. ## Private Network -See [the VPC documentation](/network/vpc/concepts#private-networks). +See [the VPC documentation](/vpc/concepts#private-networks). ## Public Gateway -Public Gateways sit at the border of Private Networks and provide a secure point of entry from the public internet to your infrastructure. They also offer extra functionality, including [NAT](#nat) and [SSH bastion](#ssh-bastion). You can [add a Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway#how-to-attach-a-public-gateway-to-a-private-network) to each of your Private Networks. +Public Gateways sit at the border of Private Networks and provide a secure point of entry from the public internet to your infrastructure. They also offer extra functionality, including [NAT](#nat) and [SSH bastion](#ssh-bastion). You can [add a Public Gateway](/public-gateways/how-to/configure-a-public-gateway#how-to-attach-a-public-gateway-to-a-private-network) to each of your Private Networks. ## Public IP address @@ -113,7 +113,7 @@ See [IP mobility](#ip-mobility). ## SSH bastion -[SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) is a server dedicated to managing connections to the infrastructure behind your Public Gateway. When you activate SSH bastion on your Public Gateway, all the SSH keys held in your Project credentials are imported to the SSH bastion, providing a single point of entry. This makes management of your infrastructure easier and more secure. +[SSH bastion](/public-gateways/how-to/use-ssh-bastion/) is a server dedicated to managing connections to the infrastructure behind your Public Gateway. When you activate SSH bastion on your Public Gateway, all the SSH keys held in your Project credentials are imported to the SSH bastion, providing a single point of entry. This makes management of your infrastructure easier and more secure. ## Tags diff --git a/network/public-gateways/how-to/configure-a-public-gateway.mdx b/network/public-gateways/how-to/configure-a-public-gateway.mdx index 3ffe298a86..43868e4202 100644 --- a/network/public-gateways/how-to/configure-a-public-gateway.mdx +++ b/network/public-gateways/how-to/configure-a-public-gateway.mdx @@ -13,13 +13,13 @@ categories: - network --- -This page shows you how to attach a [Public Gateway](/network/public-gateways/concepts/#public-gateway) to a Private Network, how to configure NAT and how to enable SMTP. +This page shows you how to attach a [Public Gateway](/public-gateways/concepts/#public-gateway) to a Private Network, how to configure NAT and how to enable SMTP. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) ## How to attach a Public Gateway to a Private Network @@ -36,9 +36,9 @@ This page shows you how to attach a [Public Gateway](/network/public-gateways/co Only Private Networks which are in the same region as the Public Gateway are displayed in this list. - - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/network/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region. A name for the Private Network will be suggested for you, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network. -6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/network/ipam/concepts/#reserved-ip-address)** for the attachment. -7. Use the toggle to select whether to **Advertise the default route**. Find out more about this setting in our [concepts documentation](/network/public-gateways/concepts/#default-route). + - If you want to create and attach a new Private Network, select **Attach to a new Private Network**. The Private Network will be created with default configuration (a [CIDR block](/vpc/concepts#cidr-block) will be automatically defined), in your default VPC for the region. A name for the Private Network will be suggested for you, but feel free to overwrite this with a new name of your choice. Dynamic NAT will be automatically activated on the Public Gateway for the Private Network. +6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. +7. Use the toggle to select whether to **Advertise the default route**. Find out more about this setting in our [concepts documentation](/public-gateways/concepts/#default-route). 8. Click **Attach to Private Network** to finish. You are taken back to the Private Networks tab, where the network you attached now appears, along with the services configured and the IP address of the Public Gateway. Your Private Network is now attached to your Public Gateway. You can repeat the steps above to attach more Private Networks to the same Public Gateway if you wish. @@ -63,14 +63,14 @@ Dynamic NAT is automatically activated. However, you can review and (if you wish ## How to enable SMTP -By default, the SMTP ports (25, 465, 587 and 2525) on your Public Gateway are blocked to avoid spam. If you wish to send emails from resources located behind your Public Gateway, make sure those resources [have also enabled SMTP](/compute/instances/how-to/send-emails-from-your-instance/) and then enable SMTP on your Public Gateway as follows: +By default, the SMTP ports (25, 465, 587 and 2525) on your Public Gateway are blocked to avoid spam. If you wish to send emails from resources located behind your Public Gateway, make sure those resources [have also enabled SMTP](/instances/how-to/send-emails-from-your-instance/) and then enable SMTP on your Public Gateway as follows: 1. Click **Public Gateways** in the **Network** section of the side menu. 2. Click the Public Gateway whose configuration you wish to modify. You are taken to the **Overview** page for that Public Gateway. 3. Scroll down to the **SMTP** panel, and use the toggle to enable SMTP. - See our [troubleshooting](/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/) documentation if you have any problems configuring your Public Gateway. + See our [troubleshooting](/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway/) documentation if you have any problems configuring your Public Gateway. diff --git a/network/public-gateways/how-to/create-a-public-gateway.mdx b/network/public-gateways/how-to/create-a-public-gateway.mdx index b94f20c148..b018f775ae 100644 --- a/network/public-gateways/how-to/create-a-public-gateway.mdx +++ b/network/public-gateways/how-to/create-a-public-gateway.mdx @@ -18,7 +18,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Public Gateway diff --git a/network/public-gateways/how-to/delete-a-public-gateway.mdx b/network/public-gateways/how-to/delete-a-public-gateway.mdx index da9ec2ed33..38bbdca9db 100644 --- a/network/public-gateways/how-to/delete-a-public-gateway.mdx +++ b/network/public-gateways/how-to/delete-a-public-gateway.mdx @@ -13,13 +13,13 @@ categories: - network --- -This page shows you how to delete a [Public Gateway](/network/public-gateways/concepts/#public-gateway). +This page shows you how to delete a [Public Gateway](/public-gateways/concepts/#public-gateway). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) 1. Click **Public Gateways** in the **Network** section of the side menu. 2. Click next to the Public Gateway you wish to delete, and select **Delete** from the drop-down menu. diff --git a/network/public-gateways/how-to/move-to-routed-ip.mdx b/network/public-gateways/how-to/move-to-routed-ip.mdx index 9bfde8d393..c214757817 100644 --- a/network/public-gateways/how-to/move-to-routed-ip.mdx +++ b/network/public-gateways/how-to/move-to-routed-ip.mdx @@ -13,7 +13,7 @@ categories: - network --- -Public Gateways have a [public flexible IP address](/network/public-gateways/concepts/#flexible-ip) which makes the Public Gateway accessible over the internet. Internally at Scaleway, these IP addresses were originally implemented via a NAT (Network Address Translation) solution. We have now moved to a more efficient routed IP solution. +Public Gateways have a [public flexible IP address](/public-gateways/concepts/#flexible-ip) which makes the Public Gateway accessible over the internet. Internally at Scaleway, these IP addresses were originally implemented via a NAT (Network Address Translation) solution. We have now moved to a more efficient routed IP solution. Scaleway users were invited to manually move their Public Gateways from NAT to routed at a time that suited them. Between the 27th and 31st May 2024, all remaining Public Gateways will NAT IPs were then automatically moved to routed IPs. diff --git a/network/public-gateways/how-to/upgrade-public-gateway.mdx b/network/public-gateways/how-to/upgrade-public-gateway.mdx index 73c3d16151..954af702c6 100644 --- a/network/public-gateways/how-to/upgrade-public-gateway.mdx +++ b/network/public-gateways/how-to/upgrade-public-gateway.mdx @@ -18,8 +18,8 @@ This page shows you how to upgrade your Public Gateway to a superior offer type, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) that is not already a PGW-L (the most powerful offer type availble). +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) that is not already a PGW-L (the most powerful offer type availble). 1. Click **Public Gateways** in the **Network** section of the side menu. 2. Click the Public Gateway you want to upgrade. Its **Overview** dashboard displays. diff --git a/network/public-gateways/how-to/use-flexible-ips.mdx b/network/public-gateways/how-to/use-flexible-ips.mdx index f5fdb29cb6..c9c90d5692 100644 --- a/network/public-gateways/how-to/use-flexible-ips.mdx +++ b/network/public-gateways/how-to/use-flexible-ips.mdx @@ -13,12 +13,12 @@ categories: - network --- -This page shows you how to use [flexible IP addresses](/network/public-gateways/concepts/#flexible-ip) with your Public Gateways. +This page shows you how to use [flexible IP addresses](/public-gateways/concepts/#flexible-ip) with your Public Gateways. Flexible IP addresses are public IPs that you can hold independently of any Public Gateway, and attach and detach to/from any of your Public Gateways as you wish. You can keep a number of flexible IP addresses in your account at any given time. - This how-to concerns the creation of Public Gateway flexible IPs. For the creation of [Instance flexible IPs](/compute/instances/how-to/use-flexips/) or [Elastic Metal flexible IPs](/bare-metal/elastic-metal/how-to/configure-flexible-ip/), refer to the relevant documentation. Note that each set of flexible IPs is independent, and can only be used with that product. Instance flexible IPs cannot be attached to Public Gateways and vice versa. Public Gateway flexible IPs are scoped to a single Availability Zone. + This how-to concerns the creation of Public Gateway flexible IPs. For the creation of [Instance flexible IPs](/instances/how-to/use-flexips/) or [Elastic Metal flexible IPs](/elastic-metal/how-to/configure-flexible-ip/), refer to the relevant documentation. Note that each set of flexible IPs is independent, and can only be used with that product. Instance flexible IPs cannot be attached to Public Gateways and vice versa. Public Gateway flexible IPs are scoped to a single Availability Zone. @@ -26,7 +26,7 @@ Flexible IP addresses are public IPs that you can hold independently of any Publ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a new flexible IP address diff --git a/network/public-gateways/how-to/use-ssh-bastion.mdx b/network/public-gateways/how-to/use-ssh-bastion.mdx index 123d198dd2..0e7f98bccd 100644 --- a/network/public-gateways/how-to/use-ssh-bastion.mdx +++ b/network/public-gateways/how-to/use-ssh-bastion.mdx @@ -18,9 +18,9 @@ SSH bastion is a server dedicated to managing connections to the infrastructure - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) -- [Attached](/network/vpc/how-to/attach-resources-to-pn/) your Public Gateway to a Private Network +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) +- [Attached](/vpc/how-to/attach-resources-to-pn/) your Public Gateway to a Private Network ## How to activate SSH bastion @@ -31,15 +31,15 @@ SSH bastion is a server dedicated to managing connections to the infrastructure 4. Enter the port that you want your SSH bastion to listen on (or leave the default port in place). - The default port is 61000. When setting your own port, you must choose a port number between 1024 and 59999. The port that the SSH bastion listens on must not be a port already in use by a [NAT rule](/network/public-gateways/concepts/#nat). + The default port is 61000. When setting your own port, you must choose a port number between 1024 and 59999. The port that the SSH bastion listens on must not be a port already in use by a [NAT rule](/public-gateways/concepts/#nat). 5. Copy the command to connect to a resource, and click **Save SSH bastion settings**. - You are redirected to your Public Gateway's **Overview** page, where SSH bastion is now activated. All the SSH keys in your [Project credentials](/identity-and-access-management/iam/concepts/#api-key) at the time of activation are copied to the SSH bastion. + You are redirected to your Public Gateway's **Overview** page, where SSH bastion is now activated. All the SSH keys in your [Project credentials](/iam/concepts/#api-key) at the time of activation are copied to the SSH bastion. ## How to reimport SSH keys -If you add new SSH keys to your [Project credentials](/identity-and-access-management/iam/concepts/#api-key) after activating SSH bastion, you will need to perform a reimport to update the bastion with the new keys. +If you add new SSH keys to your [Project credentials](/iam/concepts/#api-key) after activating SSH bastion, you will need to perform a reimport to update the bastion with the new keys. 1. Click **Public Gateways** in the **Network** section of the Scaleway console side menu. 2. Click the Public Gateway for which you want to update the SSH bastion. You are taken to the **Overview** page for that Public Gateway. diff --git a/network/public-gateways/index.mdx b/network/public-gateways/index.mdx index a121722495..b45e69621d 100644 --- a/network/public-gateways/index.mdx +++ b/network/public-gateways/index.mdx @@ -8,15 +8,15 @@ meta: sentiment="info" title="Public Gateways are evolving - make sure you stay informed" > - - DHCP has moved from Public Gateways to Private Networks. Read more in our [migration guide](/network/vpc/reference-content/vpc-migration/) - - Legacy Public Gateways are not compatible with Scaleway IPAM. Find out more in the [IPAM documentation](/network/public-gateways/concepts/#ipam) + - DHCP has moved from Public Gateways to Private Networks. Read more in our [migration guide](/vpc/reference-content/vpc-migration/) + - Legacy Public Gateways are not compatible with Scaleway IPAM. Find out more in the [IPAM documentation](/public-gateways/concepts/#ipam) @@ -28,21 +28,21 @@ meta: icon="rocket" description="Learn how to create a Public Gateway and attach it to a Private Network." label="View Quickstart" - url="/network/public-gateways/quickstart/" + url="/public-gateways/quickstart/" /> diff --git a/network/public-gateways/quickstart.mdx b/network/public-gateways/quickstart.mdx index 1595fd9546..412b1c5e6b 100644 --- a/network/public-gateways/quickstart.mdx +++ b/network/public-gateways/quickstart.mdx @@ -18,7 +18,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- Created a [Private Network](/network/vpc/how-to/create-private-network/) +- Created a [Private Network](/vpc/how-to/create-private-network/) ## How to create a Public Gateway @@ -45,8 +45,8 @@ categories: Only Private Networks which are in the same region as the Public Gateway are displayed in this list. -6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/network/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/network/ipam/concepts/#reserved-ip-address)** for the attachment. -7. Use the toggle to tell the gateway whether or not it should [advertise the default route](/network/public-gateways/concepts/#default-route) to the internet for attached resources. +6. Choose whether to **auto-allocate an available IP from the pool** (the [CIDR block](/vpc/concepts/#cidr-block) defined at the time of creating the Private Network), or use a **[reserved IP address](/ipam/concepts/#reserved-ip-address)** for the attachment. +7. Use the toggle to tell the gateway whether or not it should [advertise the default route](/public-gateways/concepts/#default-route) to the internet for attached resources. 8. Click **Attach to Private Network** to finish. You are taken back to the Private Networks tab, where the network you attached now appears, along with the services configured and the IP address of the Public Gateway. Your Private Network is now attached to your Public Gateway. You can repeat the steps above to attach more Private Networks to the same Public Gateway if you wish. @@ -60,8 +60,8 @@ When you activate SSH bastion on your Public Gateway, all [SSH keys held in your 3. Under **SSH Bastion**, click the **Activate** button. A pop-up displays. 4. Enter the port that you want your SSH bastion to listen on (or leave the default port in place). - The default port is `61000`. When setting your own port, you must choose a port number between `1024` and `59999`. The port that the SSH bastion listens on must not be a port already in use by a [NAT rule](/network/public-gateways/concepts/#nat). + The default port is `61000`. When setting your own port, you must choose a port number between `1024` and `59999`. The port that the SSH bastion listens on must not be a port already in use by a [NAT rule](/public-gateways/concepts/#nat). 5. Copy the command to connect to a resource, and click **Save SSH bastion settings**. - You are redirected to your Public Gateway's **Overview** page, where SSH bastion is now activated. All the SSH keys in your [Project credentials](/identity-and-access-management/iam/concepts/#api-key) at the time of activation are copied to the SSH bastion. The command to use to connect to resources behind the bastion is displayed. See the [SSH bastion documentation](/network/public-gateways/how-to/use-ssh-bastion/) for further help. \ No newline at end of file + You are redirected to your Public Gateway's **Overview** page, where SSH bastion is now activated. All the SSH keys in your [Project credentials](/iam/concepts/#api-key) at the time of activation are copied to the SSH bastion. The command to use to connect to resources behind the bastion is displayed. See the [SSH bastion documentation](/public-gateways/how-to/use-ssh-bastion/) for further help. \ No newline at end of file diff --git a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx index d7c14450e2..c145efed2f 100644 --- a/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx +++ b/network/public-gateways/troubleshooting/cant-connect-to-instance-with-pn-gateway.mdx @@ -13,18 +13,18 @@ categories: - network --- -If you are having trouble [connecting to your Instance via SSH](/compute/instances/how-to/connect-to-instance/), when the Instance is attached to a Private Network which also has an attached Public Gateway, read on for help and solutions. +If you are having trouble [connecting to your Instance via SSH](/instances/how-to/connect-to-instance/), when the Instance is attached to a Private Network which also has an attached Public Gateway, read on for help and solutions. The action to take depends on whether: -- The Private Network(s) attached to your Instance have [DHCP enabled](/network/vpc/how-to/activate-dhcp/), and -- Your Public Gateway is set to [advertise a default route](/network/public-gateways/concepts/#default-route) (true by default). +- The Private Network(s) attached to your Instance have [DHCP enabled](/vpc/how-to/activate-dhcp/), and +- Your Public Gateway is set to [advertise a default route](/public-gateways/concepts/#default-route) (true by default). If the above two conditions are not true, there may be other factors impacting your Instance, like one of your Instances running a DHCP server. Try disconnecting and reconnecting the Instance from the Private Network. If DHCP **is** activated and your Public Gateway **is** set to advertise a default route, not being able to connect to your Instance via SSH is **expected behavior**. All the traffic towards your Instance now goes through the Public Gateway. -To access your Instance using SSH in this scenario, the recommended solution is to use [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/). +To access your Instance using SSH in this scenario, the recommended solution is to use [SSH bastion](/public-gateways/how-to/use-ssh-bastion/). SSH bastion is the recommended solution. For advanced users only, another manual workaround is to create a static NAT association between a port of your Public Gateway (e.g. `2222`) and the private IP assigned to your Instance, on the SSH port (`22` by default). Then, SSH to the Public Gateway's IP on port `2222`. diff --git a/network/public-gateways/troubleshooting/gateway-services-not-working.mdx b/network/public-gateways/troubleshooting/gateway-services-not-working.mdx index d231b55749..1a4dd35c40 100644 --- a/network/public-gateways/troubleshooting/gateway-services-not-working.mdx +++ b/network/public-gateways/troubleshooting/gateway-services-not-working.mdx @@ -16,7 +16,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization First, check whether the gateway is properly plugged into the Private Network. We currently have a known issue where the GatewayNetwork gets created successfully without the gateway actually getting plugged into the network. To check whether this is the issue you are experiencing, do the following: @@ -30,6 +30,6 @@ First, check whether the gateway is properly plugged into the Private Network. W If the address does ping, then you may be either experiencing another issue, where the interface gets misconfigured, or just have an error in your configuration. To test for this, update any property of your GatewayNetwork or the associated DHCP configuration in order to trigger a reconfiguration. If this does not fix it, check your configuration. -It may also be useful to try the steps outlined in [this troubleshooting](/network/vpc/troubleshooting/autoconfig-not-working/). +It may also be useful to try the steps outlined in [this troubleshooting](/vpc/troubleshooting/autoconfig-not-working/). If the problem persists, do not hesitate to [contact us on the #public-gateway channel on the Scaleway Community Slack](https://scaleway-community.slack.com/archives/C01NTFET64D). \ No newline at end of file diff --git a/network/public-gateways/troubleshooting/gw-limitations.mdx b/network/public-gateways/troubleshooting/gw-limitations.mdx index 4086203034..c8254b6a10 100644 --- a/network/public-gateways/troubleshooting/gw-limitations.mdx +++ b/network/public-gateways/troubleshooting/gw-limitations.mdx @@ -23,7 +23,7 @@ Leases are not automatically renewed on the client side when changing the DHCP s #### CentOS autoconfiguration does not work with multiple Private Networks. -When a CentOS Instance is attached to multiple Private Networks, which are themselves attached to a Public Gateway, routing metric priorities will not be enforced across reboot. You will have to disable routes autoconfiguration and configure them by yourself as explained in the [this document](/network/vpc/troubleshooting/autoconfig-not-working/) section. +When a CentOS Instance is attached to multiple Private Networks, which are themselves attached to a Public Gateway, routing metric priorities will not be enforced across reboot. You will have to disable routes autoconfiguration and configure them by yourself as explained in the [this document](/vpc/troubleshooting/autoconfig-not-working/) section. #### In some cases, local DNS fails on autoconfigured Instances. @@ -31,8 +31,8 @@ This is due to a conflict between the Public Gateway and the API metadata DNS se #### Only Public Gateways created after 17 October 2023 are natively integrated with Scaleway's IPAM -Find out more about this in our [IPAM documentation](/network/public-gateways/concepts/#ipam). +Find out more about this in our [IPAM documentation](/public-gateways/concepts/#ipam). #### Static NAT is not compatible with Managed Databases for PostgreSQL and MySQL -Managed Databases for PostgreSQL and MySQL are currently not compatible with the [Static NAT](/network/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/network/public-gateways/concepts/#public-gateway). \ No newline at end of file +Managed Databases for PostgreSQL and MySQL are currently not compatible with the [Static NAT](/public-gateways/concepts/#nat) feature of [Scaleway Public Gateways](/public-gateways/concepts/#public-gateway). \ No newline at end of file diff --git a/network/vpc/concepts.mdx b/network/vpc/concepts.mdx index 9d9a3aed10..ab327a0921 100644 --- a/network/vpc/concepts.mdx +++ b/network/vpc/concepts.mdx @@ -24,47 +24,47 @@ An IPv4 CIDR block and an IPv6 CIDR block are defined for each Scaleway Private ## Default VPC -Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default VPC is automatically created for each region, in each Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC. +Scaleway currently has three regions: Paris, Amsterdam and Warsaw. One default VPC is automatically created for each region, in each Scaleway [Project](/organizations-and-projects/concepts/#project). Any new Private Networks that you create will be added to the default VPC for their region, unless you override this by specifying a different VPC. ## DHCP **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP) is a network management protocol for dynamically assigning IP addresses and other configuration parameters to devices in a Private Network. -Managed DHCP was previously a feature of Scaleway's [Public Gateway](/network/public-gateways/concepts/#public-gateway), but is now built into Private Networks. A [CIDR block](#cidr-block) representing a range of available IP addresses is defined when creating the Private Network, and when you attach a resource to the network it is assigned a static, private IP address from this subnet. These IP addresses are managed by our internal [IPAM](#ipam), which acts a single source of truth and ensures full consistency. There is no need for users to manually assign private IP addresses to their resources as they join or leave the network. However, you can choose to assign particular [reserved IP addresses](/network/ipam/how-to/reserve-ip/) if you wish. +Managed DHCP was previously a feature of Scaleway's [Public Gateway](/public-gateways/concepts/#public-gateway), but is now built into Private Networks. A [CIDR block](#cidr-block) representing a range of available IP addresses is defined when creating the Private Network, and when you attach a resource to the network it is assigned a static, private IP address from this subnet. These IP addresses are managed by our internal [IPAM](#ipam), which acts a single source of truth and ensures full consistency. There is no need for users to manually assign private IP addresses to their resources as they join or leave the network. However, you can choose to assign particular [reserved IP addresses](/ipam/how-to/reserve-ip/) if you wish. Even with automatic IP address assignment, thanks to managed DHCP, a resource's IP address will never change as long as that resource is not detached from the Private Network. It remains stable across reboots and long poweroffs. The IP is allocated when the resource is attached, and released only when the resource is detached or deleted. The IPv4 address of Private Networks' DHCP server is `169.254.169.254`. The IPv6 address is `fe80:200:22ff:fe05:ca1e`. -While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/network/vpc/reference-content/vpc-migration/) documentation for more information. +While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information. ## DNS The **D**omain **N**ame **S**ystem (DNS) is a naming system for devices connected to the internet or Private Networks. Most prominently, DNS servers translate text-based domain names (e.g. www.scaleway.com) to numerical IP addresses (e.g. `51.158.66.220`). -Private Networks benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). See [full information](/network/vpc/reference-content/dns/) on Scaleway DNS and how to reach a resource via its hostname. +Private Networks benefit from managed DNS, which resolves the hostnames of attached resources into their IP addresses. The hostname for a given device is generally the name defined when creating the resource (and which in the case of an Instance, for example, displays in the shell when connected to that resource by SSH). See [full information](/vpc/reference-content/dns/) on Scaleway DNS and how to reach a resource via its hostname. ## IPAM -**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. See our [dedicated IPAM documentation](/network/ipam/) for full information. +**IP** **A**ddress **M**anager (IPAM) is Scaleway's tool for planning, tracking and managing the IP address space of Scaleway products. It acts as a single source of truth for the IP addresses of Scaleway resources. See our [dedicated IPAM documentation](/ipam/) for full information. ## IPv4 Internet Protocol Version 4 is the standard protocol used for IP addresses. Composed of 32 bits, when written in human-readable form an IPv4 address is generally shown as four octets separated by periods, e.g. `151.115.59.87`. -When a resource is attached to a Private Network, it has a private IPv4 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv4 address (as well as an IPv6 address, if the resource is IPv6-compatible) when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/network/ipam/how-to/reserve-ip/). +When a resource is attached to a Private Network, it has a private IPv4 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv4 address (as well as an IPv6 address, if the resource is IPv6-compatible) when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/ipam/how-to/reserve-ip/). ## IPv6 Internet Protocol Version 6 is the most recent version of the IP protocol used for IP addresses. Composed of 128 bits, written in human-readable form, an IPv6 address can be shown as eight groups of four hexadecimal digits separated by a colon, e.g. `2001:0DB8:0000:0003:0000:01FF:0000:002E`. This can also be notated as `2001:DB8::3:0:1FF:0:2E`. -When an IPv6-compatible resource is attached to a Private Network, it has a private IPv6 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv6 address when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/network/ipam/how-to/reserve-ip/). +When an IPv6-compatible resource is attached to a Private Network, it has a private IPv6 address on that network. Scaleway Private Networks' [DHCP](#dhcp) functionality assigns this private IPv6 address when the resource joins the network. Alternatively you can reserve and attach an IP address of your choice with [IPAM](/ipam/how-to/reserve-ip/). ## Private IP address -A [private IP address](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) identifies a resource on a Private Network. When you attach a resource (e.g. an Instance) to the network, you can either [use a reserved IP address](/network/ipam/how-to/reserve-ip/), or let [DHCP](#dhcp) assign one IPv4 and (if the resource is IPv6-compatible) one IPv6 address from the designated [CIDR blocks](#cidr-block) to that resource. +A [private IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) identifies a resource on a Private Network. When you attach a resource (e.g. an Instance) to the network, you can either [use a reserved IP address](/ipam/how-to/reserve-ip/), or let [DHCP](#dhcp) assign one IPv4 and (if the resource is IPv6-compatible) one IPv6 address from the designated [CIDR blocks](#cidr-block) to that resource. For example, a private IPv4 address may resemble `172.16.16.2/22`. This format encapsulates information both about the resource's IP address, and also the subnet (Private Network) itself. If you configure an Instance manually with this address, it sets both the correct IP and a route to the correct subnet. @@ -74,12 +74,12 @@ Private Networks let you connect Scaleway resources across multiple AZs within t **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP) is built into each Private Network, making it easy to manage the private IP addresses of your resources on the network. -Read our dedicated documentation on [creating a Private Network](/network/vpc/how-to/create-private-network/). +Read our dedicated documentation on [creating a Private Network](/vpc/how-to/create-private-network/). Previously, Private Networks at Scaleway were zoned. Only resources from within one defined AZ could be attached to each network. Now, all Private Networks are regional, and resources from any AZ within that network's region can be attached. "Old" zoned Private Networks have all been automatically migrated to become regional. -While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/network/vpc/reference-content/vpc-migration/) documentation for more information. +While DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information. ## Region and Availability Zone @@ -88,7 +88,7 @@ While DHCP is built into all new Private Networks, it may not be automatically a ## Route table -A [route table](/network/vpc/reference-content/understanding-routing/#route-table) is used to manage and control the routing of traffic within a VPC. The routes within a route table tell the VPC where to send traffic trying to get to a specific destination IP address. One line in the route table corresponds to one route. +A [route table](/vpc/reference-content/understanding-routing/#route-table) is used to manage and control the routing of traffic within a VPC. The routes within a route table tell the VPC where to send traffic trying to get to a specific destination IP address. One line in the route table corresponds to one route. Routes can be of the following types: - Auto-generated, fully managed `Local subnet routes` for routes to Private Networks. @@ -99,11 +99,11 @@ When deciding which route to apply, the route table reads the routes from most s ## Routing -Routing allows Private Networks in the same VPC to communicate with each other, via managed and custom routes. Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/network/vpc/how-to/manage-routing/#how-to-activate-routing). +Routing allows Private Networks in the same VPC to communicate with each other, via managed and custom routes. Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/vpc/how-to/manage-routing/#how-to-activate-routing). -Each routed VPC has a [route table](#route-table) which is automatically populated with routes to each Private Network in the VPC, as well as to any attached Public Gateways. These routes allow the VPC to automatically route packets between its Private Networks, or from a given Private Network to its attached Public Gateway when the destination is outside the VPC. You can also create your own [custom routes](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route). +Each routed VPC has a [route table](#route-table) which is automatically populated with routes to each Private Network in the VPC, as well as to any attached Public Gateways. These routes allow the VPC to automatically route packets between its Private Networks, or from a given Private Network to its attached Public Gateway when the destination is outside the VPC. You can also create your own [custom routes](/vpc/how-to/manage-routing/#how-to-create-a-custom-route). -Read more about how routing works in [our detailed guide](/network/vpc/reference-content/understanding-routing/). +Read more about how routing works in [our detailed guide](/vpc/reference-content/understanding-routing/). ## vRouter @@ -113,7 +113,7 @@ A vRouter is a virtualized router that sits inside a VPC and manages layer 3 rou VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. -One default VPC for every available region is automatically created in each Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). +One default VPC for every available region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project). VPC currently comprises the [Private Networks](#private-networks) product. Layer 2 Private Networks sit inside the layer 3 VPC. diff --git a/network/vpc/how-to/activate-dhcp.mdx b/network/vpc/how-to/activate-dhcp.mdx index 4d7d25f99b..8e7026401f 100644 --- a/network/vpc/how-to/activate-dhcp.mdx +++ b/network/vpc/how-to/activate-dhcp.mdx @@ -13,12 +13,12 @@ categories: - network --- -All Private Networks created after July 12 2023 have **DHCP built into them**. A CIDR block is defined when you create the Private Network. When a resource is attached to the Private Network, an IPv4 and IPv6 address is statically allocated to them from this block. This is all managed by our internal [IPAM](/network/vpc/concepts/#ipam) and removes the need for manual configuration of your IP addresses. +All Private Networks created after July 12 2023 have **DHCP built into them**. A CIDR block is defined when you create the Private Network. When a resource is attached to the Private Network, an IPv4 and IPv6 address is statically allocated to them from this block. This is all managed by our internal [IPAM](/vpc/concepts/#ipam) and removes the need for manual configuration of your IP addresses. However, while DHCP is built into all new Private Networks, it may not be automatically activated for older Private Networks. Previously, DHCP was a function of Public Gateways. Only legacy Private Networks that were previously attached to a Public Gateway with DHCP, have DHCP automatically activated on them. On all other Private Networks created prior to July 12 2023, DHCP remains deactivated by default. -Check out our [migration](/network/vpc/reference-content/vpc-migration/) documentation for full information about how "old" Private Networks were migrated when VPC went into General Availability, and for more information about DHCP. +Check out our [migration](/vpc/reference-content/vpc-migration/) documentation for full information about how "old" Private Networks were migrated when VPC went into General Availability, and for more information about DHCP. We highly recommend activating DHCP on all of your Private Networks, to let us take care of IP address management in our fully-integrated ecosystem. This page explains how to activate DHCP on Private Networks where it has not been automatically activated. @@ -26,13 +26,13 @@ We highly recommend activating DHCP on all of your Private Networks, to let us t **Activating DHCP is permanent, and there is no way to undo the activation.**

-Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network. Attached resources will receive new dynamically assigned private IP addresses (one IPv4 and one IPv6) from the network's pre-defined CIDR block. The CIDR block will be displayed at the time of activation (see step 5 below), and you will be able to [view your resources' newly assigned IP addresses](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) after activation. +Activating DHCP will overwrite any existing manually configured static IP addresses for resources attached to the network. Attached resources will receive new dynamically assigned private IP addresses (one IPv4 and one IPv6) from the network's pre-defined CIDR block. The CIDR block will be displayed at the time of activation (see step 5 below), and you will be able to [view your resources' newly assigned IP addresses](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) after activation. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Created a Private Network in which DHCP is not yet activated, before July 12, 2023 ## How to activate DHCP on a Private Network @@ -57,6 +57,6 @@ Activating DHCP will overwrite any existing manually configured static IP addres 5. Read the warning message carefully, and click **Activate DHCP** when you are ready. -DHCP is activated on your network, and attached resources will receive dynamically assigned static IP addresses no later than one hour from the time of activation. You can view their IP addresses by [following this procedure](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). +DHCP is activated on your network, and attached resources will receive dynamically assigned static IP addresses no later than one hour from the time of activation. You can view their IP addresses by [following this procedure](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). diff --git a/network/vpc/how-to/attach-resources-to-pn.mdx b/network/vpc/how-to/attach-resources-to-pn.mdx index 082596c6e1..61ce46245d 100644 --- a/network/vpc/how-to/attach-resources-to-pn.mdx +++ b/network/vpc/how-to/attach-resources-to-pn.mdx @@ -33,8 +33,8 @@ The following resource types can be attached to a Private Network: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Private Network](/network/vpc/how-to/create-private-network/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Private Network](/vpc/how-to/create-private-network/) - Created at least one Scaleway resource in the same region as your Private Network ## How to attach a resource to a Private Network @@ -62,7 +62,7 @@ The following resource types can be attached to a Private Network: 6. Select the type of resource (Instance, Elastic Metal server etc.) that you want to attach. Then select the specific resource to attach. Only resources within the same region (or one of its Availability Zones) as the Private Network will be displayed. - When attaching Instances, Load Balancers, Public Gateways, and Elastic Metal servers, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network or specify an IP that you have already [reserved via IPAM](/network/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type. + When attaching Instances, Load Balancers, Public Gateways, and Elastic Metal servers, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network or specify an IP that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type. Support for using reserved IPs to attach Managed Databases to Private Networks will be coming soon. @@ -74,20 +74,20 @@ The following resource types can be attached to a Private Network: You can also attach a resource to a Private Network from the resource's own section of the console. Follow the relevant steps below: -- [Instance](/compute/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) -- [Elastic Metal server](/bare-metal/elastic-metal/how-to/use-private-networks/#from-the-elastic-metal-section-of-the-console) -- [Managed Database for PostgreSQL and MySQL](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/) -- [Load Balancer](/network/load-balancer/how-to/use-with-private-network/) -- [Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) +- [Instance](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) +- [Elastic Metal server](/elastic-metal/how-to/use-private-networks/#from-the-elastic-metal-section-of-the-console) +- [Managed Database for PostgreSQL and MySQL](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) +- [Load Balancer](/load-balancer/how-to/use-with-private-network/) +- [Public Gateway](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) Note that for Kubernetes Kapsules and Managed Databases for Redis™, you can only attach the resource to a Private Network at the time of creating the resource itself. ## How to view the resource's IP address -When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/network/ipam/how-to/reserve-ip/). +When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/ipam/how-to/reserve-ip/). -No matter whether it is auto-allocated or pre-reserved, the IP remains stable for as long as the resource is attached to the Private Network, and does not risk changing even across reboots and long poweroffs. An auto-allocated IP is lost only when you delete the resource or detach it from the Private Network. Reserved IPs remain reserved even after you delete the resource or detach it from the Private Network, until you [release the address](/network/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address). +No matter whether it is auto-allocated or pre-reserved, the IP remains stable for as long as the resource is attached to the Private Network, and does not risk changing even across reboots and long poweroffs. An auto-allocated IP is lost only when you delete the resource or detach it from the Private Network. Reserved IPs remain reserved even after you delete the resource or detach it from the Private Network, until you [release the address](/ipam/how-to/reserve-ip/#how-to-release-a-reserved-private-ip-address). You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 5 above). @@ -96,29 +96,29 @@ You can view a resource's IPv4 or v6 address in the **Attached Resources** tab o It can also be viewed via the **Private Networks** tab of the resource's own dashboard. -Refer to our documentation on [IPv4](/network/vpc/how-to/create-private-network/#how-to-configure-cidr), [IPv6](/network/vpc/how-to/create-private-network/#ipv6-cidr-block) and [CIDR](/network/vpc/how-to/create-private-network/#ipv4-cidr-block) blocks for further information about these concepts. +Refer to our documentation on [IPv4](/vpc/how-to/create-private-network/#how-to-configure-cidr), [IPv6](/vpc/how-to/create-private-network/#ipv6-cidr-block) and [CIDR](/vpc/how-to/create-private-network/#ipv4-cidr-block) blocks for further information about these concepts. -When you attach an Instance or Elastic Metal server to a legacy Private Network on which you [have not activated DHCP](/network/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks), no IP address is configured or shown on the screen shown above.

+When you attach an Instance or Elastic Metal server to a legacy Private Network on which you [have not activated DHCP](/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks), no IP address is configured or shown on the screen shown above.

You will need to carry out manual configuration to set the IP address on the resource, or activate DHCP.

-We strongly recommend that you [activate DHCP on the Private Network](/network/vpc/how-to/activate-dhcp/) to let us automatically handle IP address management.

+We strongly recommend that you [activate DHCP on the Private Network](/vpc/how-to/activate-dhcp/) to let us automatically handle IP address management.

-If you do not see an IP address in the screens above for your resource, and you think you should, check out our [troubleshooting](/network/vpc/troubleshooting/resource-attached-no-ip/) guide.

+If you do not see an IP address in the screens above for your resource, and you think you should, check out our [troubleshooting](/vpc/troubleshooting/resource-attached-no-ip/) guide.

-Note that in any case, for Elastic Metal servers, some [manual configuration is required](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) even after activating DHCP. This is not required for Instances or other types of resources. +Note that in any case, for Elastic Metal servers, some [manual configuration is required](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks) even after activating DHCP. This is not required for Instances or other types of resources. ## How to access a resource on a Private Network via its hostname (DNS) -In addition to using its IP address, you can also access a resource on a Private Network via its hostname, thanks to VPC's inbuilt [private DNS](/network/vpc/concepts/#dns). +In addition to using its IP address, you can also access a resource on a Private Network via its hostname, thanks to VPC's inbuilt [private DNS](/vpc/concepts/#dns). A resource's hostname is equivalent to the name you gave the resource when creating it. For example, if you have an Instance with the name `instance123` attached to a Private Network named `prodpn`, its address on that network is `instance123.prodpn.internal`. -For full information on Scaleway internal DNS and hostname formats, including troubleshooting advice, see our [dedicated documentation](/network/vpc/reference-content/dns/). +For full information on Scaleway internal DNS and hostname formats, including troubleshooting advice, see our [dedicated documentation](/vpc/reference-content/dns/). ## How to detach a resource from a Private Network diff --git a/network/vpc/how-to/create-private-network.mdx b/network/vpc/how-to/create-private-network.mdx index 5a834dcb22..4195f03924 100644 --- a/network/vpc/how-to/create-private-network.mdx +++ b/network/vpc/how-to/create-private-network.mdx @@ -15,16 +15,16 @@ categories: VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create multiple **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in an isolated and secure layer 2 network, away from the public internet. -Private Networks also have built-in **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP), making it easy to manage the private IP addresses of your resources on the network. IPs are statically allocated when resources are attached to a Private Network, and are managed by our internal [IPAM](/network/vpc/concepts/#ipam). You can find out how to get the most from your Private Networks in our [dedicated guide](/network/vpc/reference-content/getting-most-private-networks/). +Private Networks also have built-in **D**ynamic **H**ost **C**onfiguration **P**rotocol (DHCP), making it easy to manage the private IP addresses of your resources on the network. IPs are statically allocated when resources are attached to a Private Network, and are managed by our internal [IPAM](/vpc/concepts/#ipam). You can find out how to get the most from your Private Networks in our [dedicated guide](/vpc/reference-content/getting-most-private-networks/). -While DHCP is built into all new Private Networks, it may not be automatically activated for Private Networks created before July 2023. Check our [migration](/network/vpc/reference-content/vpc-migration/) documentation for more information. +While DHCP is built into all new Private Networks, it may not be automatically activated for Private Networks created before July 2023. Check our [migration](/vpc/reference-content/vpc-migration/) documentation for more information. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a Private Network @@ -49,7 +49,7 @@ While DHCP is built into all new Private Networks, it may not be automatically a 6. Click **Create Private Network** to finish. Your Private Network is created. -See our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. +See our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. ## How to configure CIDR @@ -95,6 +95,6 @@ If you prefer, you can define your own custom IPv4 CIDR block when creating your ### Viewing IP addresses of attached resources -When you attach resources to the Private Network, they will be assigned IP addresses from the CIDR block you defined. See [how to attach a resource to a Private Network](/network/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) and [how to view the resource's IP address](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for more information. +When you attach resources to the Private Network, they will be assigned IP addresses from the CIDR block you defined. See [how to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) and [how to view the resource's IP address](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) for more information. diff --git a/network/vpc/how-to/create-vpc.mdx b/network/vpc/how-to/create-vpc.mdx index 05092fe3e4..0f2ebe6c85 100644 --- a/network/vpc/how-to/create-vpc.mdx +++ b/network/vpc/how-to/create-vpc.mdx @@ -13,16 +13,16 @@ categories: - network --- -VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in isolated and secured networks, away from the public internet. The [routing](/network/vpc/concepts/#routing) feature allows the different Private Networks of a VPC to communicate with each other. More features and resources will be coming to the VPC product in the future. +VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. Within each VPC, you can create **Private Networks** and attach Scaleway resources to them, as long as the resources are in an AZ within the network's region. Attached resources can then communicate between themselves in isolated and secured networks, away from the public internet. The [routing](/vpc/concepts/#routing) feature allows the different Private Networks of a VPC to communicate with each other. More features and resources will be coming to the VPC product in the future. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to identify your default VPCs -One default VPC per region is automatically created per Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). +One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project). Click **VPC** in the **Network** section of the Scaleway console side menu. Your VPC [dashboard](https://console.scaleway.com/vpc/vpc) displays: diff --git a/network/vpc/how-to/delete-private-network.mdx b/network/vpc/how-to/delete-private-network.mdx index 2530490f13..fcf16e2c28 100644 --- a/network/vpc/how-to/delete-private-network.mdx +++ b/network/vpc/how-to/delete-private-network.mdx @@ -16,9 +16,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Private Network](/network/vpc/how-to/create-private-network/) -- [Detached all resources](/network/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) from the Private Network you want to delete +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Private Network](/vpc/how-to/create-private-network/) +- [Detached all resources](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) from the Private Network you want to delete ## How to delete a Private Network diff --git a/network/vpc/how-to/delete-vpc.mdx b/network/vpc/how-to/delete-vpc.mdx index 5366c397bd..aa08b5381e 100644 --- a/network/vpc/how-to/delete-vpc.mdx +++ b/network/vpc/how-to/delete-vpc.mdx @@ -21,7 +21,7 @@ categories: You can only delete VPCs that: - Do not contain any Private Networks -- Are not the [default VPC](/network/vpc/concepts/#default-vpc) for their region +- Are not the [default VPC](/vpc/concepts/#default-vpc) for their region 1. Click **VPC** in the **Network** section of the Scaleway console side menu. The list of your VPCs displays: diff --git a/network/vpc/how-to/manage-routing.mdx b/network/vpc/how-to/manage-routing.mdx index 152b2bf7aa..e5ec8b3ce2 100644 --- a/network/vpc/how-to/manage-routing.mdx +++ b/network/vpc/how-to/manage-routing.mdx @@ -13,9 +13,9 @@ categories: - network --- -Routing is used to manage and control the flow of traffic within a VPC. It tells the VPC where to send traffic trying to get to a specific destination IP address. Notably, it allows traffic to be automatically routed between resources attached to different Private Networks within the VPC, using their [private IP addresses](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). You can also create your own custom routes. +Routing is used to manage and control the flow of traffic within a VPC. It tells the VPC where to send traffic trying to get to a specific destination IP address. Notably, it allows traffic to be automatically routed between resources attached to different Private Networks within the VPC, using their [private IP addresses](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address). You can also create your own custom routes. -Read more about the VPC routing feature, including detailed explanations, usage considerations, limitations and best practices in our [dedicated reference content](/network/vpc/reference-content/understanding-routing/). +Read more about the VPC routing feature, including detailed explanations, usage considerations, limitations and best practices in our [dedicated reference content](/vpc/reference-content/understanding-routing/). @@ -23,7 +23,7 @@ Read more about the VPC routing feature, including detailed explanations, usage ## How to activate routing -Routing is activated as standard whenever you [create a new VPC](/network/vpc/how-to/create-vpc/#how-to-create-a-vpc). +Routing is activated as standard whenever you [create a new VPC](/vpc/how-to/create-vpc/#how-to-create-a-vpc). To activate routing on a pre-existing VPC, follow these steps: @@ -44,7 +44,7 @@ To activate routing on a pre-existing VPC, follow these steps: Two types of auto-generated routes exist: - **Local subnet route**: Generated when you create a Private Network in a VPC. Allows traffic to be routed between different Private Networks in the VPC. -- **Default route to internet**: Generated when you attach a Public Gateway to a Private Network in the VPC, and set it to advertise a [default route](/network/public-gateways/concepts/#default-route). Allows traffic to be routed to addresses outside the VPC (i.e. the public internet) via the gateway. +- **Default route to internet**: Generated when you attach a Public Gateway to a Private Network in the VPC, and set it to advertise a [default route](/public-gateways/concepts/#default-route). Allows traffic to be routed to addresses outside the VPC (i.e. the public internet) via the gateway. Public Gateways remain scoped to the Private Network(s) to which they are attached. They do not advertise the default route on other Private Networks in the VPC. For example, an Instance attached to Private Network A will not be able to access the internet via a Public Gateway in Private Network B. @@ -72,7 +72,7 @@ Your VPC's **route table** can be found in its **Routing** tab. The route table - For help with understanding the route table and how to read it, [refer to our documentation about route tables](/network/vpc/reference-content/understanding-routing/#route-table). + For help with understanding the route table and how to read it, [refer to our documentation about route tables](/vpc/reference-content/understanding-routing/#route-table). ### How to view VPC routes in IPV6 @@ -125,7 +125,7 @@ If you delete a resource used as a next hop in a custom route, or detach it from To resolve this, you must either: -- [Reattach the next hop resource to the Private Network](/network/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) **and** then [edit the route](#how-to-edit-a-custom-route) to reselect the next hop resource, or +- [Reattach the next hop resource to the Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) **and** then [edit the route](#how-to-edit-a-custom-route) to reselect the next hop resource, or - [Edit the route](#how-to-edit-a-custom-route) to select a new next hop, or - [Delete the route](#how-to-delete-a-custom-route) diff --git a/network/vpc/index.mdx b/network/vpc/index.mdx index df8420ec0c..859561fb01 100644 --- a/network/vpc/index.mdx +++ b/network/vpc/index.mdx @@ -8,7 +8,7 @@ meta: sentiment="info" title="VPC Basic Use Case" > - Read our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. + Read our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. @@ -16,7 +16,7 @@ meta: productName="VPC" productLogo="vpc" description="Virtual Private Cloud (VPC) uses Private Networks to connect your Scaleway resources so they can communicate with each other securely, away from the public internet." - url="/network/vpc/quickstart/" + url="/vpc/quickstart/" label="VPC Quickstart" /> @@ -28,28 +28,28 @@ meta: icon="rocket" description="Learn how to create Private Networks in a VPC, and attach Scaleway resources to them." label="View Quickstart" - url="/network/vpc/quickstart/" + url="/vpc/quickstart/" /> diff --git a/network/vpc/quickstart.mdx b/network/vpc/quickstart.mdx index 9b9b8cb250..0353d66381 100644 --- a/network/vpc/quickstart.mdx +++ b/network/vpc/quickstart.mdx @@ -13,7 +13,7 @@ categories: - network --- -VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. One default VPC per region is automatically created per Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project), and you can create more if you wish. Within each VPC, you can create **Private Networks** and attach Scaleway resources (Instances, Elastic Metal servers, Load Balancers etc.) to them, as long as the resources are within the network's region. Attached resources can then communicate between themselves in an isolated and secure virtual layer 2 network, away from the public internet. More features and resources will be coming to the VPC product in the future. +VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Scaleway's shared public cloud. One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project), and you can create more if you wish. Within each VPC, you can create **Private Networks** and attach Scaleway resources (Instances, Elastic Metal servers, Load Balancers etc.) to them, as long as the resources are within the network's region. Attached resources can then communicate between themselves in an isolated and secure virtual layer 2 network, away from the public internet. More features and resources will be coming to the VPC product in the future. @@ -21,7 +21,7 @@ VPC allows you to build your own **V**irtual **P**rivate **C**loud on top of Sca ## How to identify your default VPCs -One default VPC per region is automatically created per Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). You can [create more](/network/vpc/how-to/create-vpc/) if you wish, but it is not necessary for basic use cases. +One default VPC per region is automatically created per Scaleway [Project](/organizations-and-projects/concepts/#project). You can [create more](/vpc/how-to/create-vpc/) if you wish, but it is not necessary for basic use cases. Click **VPC** in the **Network** section of the Scaleway console side menu. Your [VPC dashboard](https://console.scaleway.com/vpc/vpc) displays: @@ -80,7 +80,7 @@ Any new Private Networks that you create will be added to the default VPC for th 6. Select the type of resource (Instance, Elastic Metal server etc.) that you want to attach. Then select the specific resource to attach. Only resources within the same region (or one of its Availability Zones) as the Private Network will be displayed. - When attaching Instances, Load Balancers and Public Gateways, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network, or to specify an IP that you have already [reserved via IPAM](/network/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type. + When attaching Instances, Load Balancers and Public Gateways, you have the option to either auto-allocate an available IP from the pool of addresses for the Private Network, or to specify an IP that you have already [reserved via IPAM](/ipam/how-to/reserve-ip/). For Instances, which support both IPv4 and IPv6 for private IP addresses, you can also choose to auto-allocate or specify a reserved IP for each address type. Support for using reserved IPs to attach Elastic Metal servers and Managed Databases to Private Networks will be coming soon. @@ -90,7 +90,7 @@ Any new Private Networks that you create will be added to the default VPC for th You are returned to the list of attached resources, where the newly-attached resource now displays. - **Viewing the resource's private IP**: When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/network/ipam/how-to/reserve-ip/). You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 4 above). It can also be viewed via the **Private Networks** tab of the resource's own dashboard. + **Viewing the resource's private IP**: When you attach a resource to a Private Network, it gets a private IPv4 address on that network (and also an IPv6 address, if supported by the resource). Private IPs are assigned from the CIDR block defined at the time of the Private Network's creation, either via auto-assignment or specification of a particular [reserved IP](/ipam/how-to/reserve-ip/). You can view a resource's IPv4 or v6 address in the **Attached Resources** tab of the Private Network itself (follow steps 1 - 4 above). It can also be viewed via the **Private Networks** tab of the resource's own dashboard. ## How to manage routing @@ -106,8 +106,8 @@ Your VPC’s route table can be found in its **Routing** tab. The route table sh Routes are automatically generated and added to the route table when you: - [Create a Private Network](#how-to-create-a-private-network) in the VPC (this generates a local subnet route, which allows the VPC to automatically route traffic between Private Networks), or - - [Attach a Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) to a Private Network and set it to advertise a default route. This generates a default route to the internet. - - [Create a custom route](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route). + - [Attach a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) to a Private Network and set it to advertise a default route. This generates a default route to the internet. + - [Create a custom route](/vpc/how-to/manage-routing/#how-to-create-a-custom-route). When your route table starts to populate, it will look something like this: @@ -117,7 +117,7 @@ For help with understanding the route table and how to read it, refer to our doc ## How to delete a Private Network -You must [detach](/network/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources from the Private Network before you can delete it. +You must [detach](/vpc/how-to/attach-resources-to-pn/#how-to-detach-a-resource-from-a-private-network) all resources from the Private Network before you can delete it. 1. Click **VPC** in the **Network** section of the side menu. diff --git a/network/vpc/reference-content/dns.mdx b/network/vpc/reference-content/dns.mdx index 744d2c9084..1248471991 100644 --- a/network/vpc/reference-content/dns.mdx +++ b/network/vpc/reference-content/dns.mdx @@ -24,7 +24,7 @@ The **D**omain **N**ame **S**ystem (DNS) is a naming system for devices connecte Scaleway Private Networks benefit from managed internal DNS. This allows the resolution of resources' **hostnames** on the Private Network, into their private IP addresses. This managed DNS service is automatically exposed in each Private Network and no user configuration is required. -When a Private Network is attached to a [legacy Public Gateway](/network/public-gateways/concepts/#ipam), the gateway’s DNS takes priority over that of the Private Network. +When a Private Network is attached to a [legacy Public Gateway](/public-gateways/concepts/#ipam), the gateway’s DNS takes priority over that of the Private Network. ## Hostname format @@ -78,8 +78,8 @@ If you experience problems with DNS, try the following steps: 2. **Check resource hostname**. Issues can arise if your resource has a dot in its name. Rename it if necessary to eliminate the dot, and detach/reattach it from the Private Network. -3. **Check Private Network name**. Issues can arise with Private Networks who share a name with a TLD. See our [dedicated document](/network/vpc/troubleshooting/pn-name/) for more help. +3. **Check Private Network name**. Issues can arise with Private Networks who share a name with a TLD. See our [dedicated document](/vpc/troubleshooting/pn-name/) for more help. -4. **Check whether you are using Network Manager**: DNS does not work out of the box for Linux distributions using Network Managed, such as **RockyLinux**. Find out how to resolve this problem [on our troubleshooting page](/network/vpc/troubleshooting/private-dns-dhcp-not-working/#distributions-running-network-manager) +4. **Check whether you are using Network Manager**: DNS does not work out of the box for Linux distributions using Network Managed, such as **RockyLinux**. Find out how to resolve this problem [on our troubleshooting page](/vpc/troubleshooting/private-dns-dhcp-not-working/#distributions-running-network-manager) If you are still having problems reaching a resource attached to a Private Network via its hostname, [open a support ticket](https://console.scaleway.com/support). \ No newline at end of file diff --git a/network/vpc/reference-content/getting-most-private-networks.mdx b/network/vpc/reference-content/getting-most-private-networks.mdx index 48bd66b198..df2e7b4145 100644 --- a/network/vpc/reference-content/getting-most-private-networks.mdx +++ b/network/vpc/reference-content/getting-most-private-networks.mdx @@ -31,7 +31,7 @@ VPCs and Private Networks are both **regional** resources. When you create a Pri | Netherlands - Amsterdam | AMS1, AMS2, AMS3 | | Poland - Warsaw | WAW1, WAW2, WAW3 | -One default VPC for each region is automatically created in each Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project). The [**VPC routing**](/network/vpc/concepts/#routing) feature allows for managed and custom routes between the Private Networks of a VPC, so resources on different Private Networks can communicate. +One default VPC for each region is automatically created in each Scaleway [Project](/organizations-and-projects/concepts/#project). The [**VPC routing**](/vpc/concepts/#routing) feature allows for managed and custom routes between the Private Networks of a VPC, so resources on different Private Networks can communicate. @@ -47,10 +47,10 @@ When you start creating resources and building your infrastructure with Scaleway For example, you may use one Private Network for frontend resources and another for backend resources, limiting public access only via Load Balancers and/or Public Gateways, stripping other resources of public IP addresses. You may want to create different VPCs for production and test environments, allowing you to isolate potential errors in testing from the production environment. -When [creating a Private Network](/network/vpc/how-to/create-private-network/), you can let Scaleway automatically generate a CIDR block for it that is guaranteed to be unique in this VPC. All resources attached to the Private Network get a private IP address from this block. However, you also have the option to define your own CIDR block for the network. Ensure you choose a prefix and network size that is appropriate for your needs, does not overlap with that of any other Private Network in the VPC, and contains enough IP addresses for all resources that will be attached to the Private Network. +When [creating a Private Network](/vpc/how-to/create-private-network/), you can let Scaleway automatically generate a CIDR block for it that is guaranteed to be unique in this VPC. All resources attached to the Private Network get a private IP address from this block. However, you also have the option to define your own CIDR block for the network. Ensure you choose a prefix and network size that is appropriate for your needs, does not overlap with that of any other Private Network in the VPC, and contains enough IP addresses for all resources that will be attached to the Private Network. -See our [Basic VPC use case](/network/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. +See our [Basic VPC use case](/vpc/reference-content/use-case-basic/) documentation for full details of how to create a simple infrastructure that leverages the advantages of Private Networks, including accompanying Terraform templates. ## Attaching resources to Private Networks @@ -67,7 +67,7 @@ Note that when you select this option, the IP address randomly assigned to the r ### Using reserved IP addresses -You can reserve private IP addresses from your Private Networks' CIDR blocks thanks to Scaleway's [**IP A**ddress **M**anagement solution](/network/ipam/), which helps you plan, track and manage the IP address space of your VPCs and their Private Networks. From the [IPAM space](https://console.scaleway.com/ipam/) in the Scaleway console, simply use the **Reserve private IP** feature to select the Private Network you want to reserve an IP address on, and choose to either reserve any available address, or a specific address not currently attached to any resource. The reserved address will then not risk being auto-assigned by Scaleway to other resources during network attachment, and can be kept until you are ready to use it to attach a specific resource. +You can reserve private IP addresses from your Private Networks' CIDR blocks thanks to Scaleway's [**IP A**ddress **M**anagement solution](/ipam/), which helps you plan, track and manage the IP address space of your VPCs and their Private Networks. From the [IPAM space](https://console.scaleway.com/ipam/) in the Scaleway console, simply use the **Reserve private IP** feature to select the Private Network you want to reserve an IP address on, and choose to either reserve any available address, or a specific address not currently attached to any resource. The reserved address will then not risk being auto-assigned by Scaleway to other resources during network attachment, and can be kept until you are ready to use it to attach a specific resource. Further, when you attach a resource to a Private Network and specify a reserved IP to use, the IP will remain reserved even after you detach the resource from the network. You can choose to either release the IP back into the pool, or keep it reserved until you use it to attach another resource. @@ -75,31 +75,31 @@ Using reserved IP addresses is ideal to ensure that certain IP addresses are nev ### DNS and hostnames -Scaleway Private Networks benefit from managed internal DNS. This allows the resolution of resources' **hostnames** on the Private Network, into their private IP addresses. See our documentation on [Understanding Scaleway DNS](/network/vpc/reference-content/dns/) for full details of how to effectively use hostname addressing and the capabilities of Private Networks' DNS resolver service. +Scaleway Private Networks benefit from managed internal DNS. This allows the resolution of resources' **hostnames** on the Private Network, into their private IP addresses. See our documentation on [Understanding Scaleway DNS](/vpc/reference-content/dns/) for full details of how to effectively use hostname addressing and the capabilities of Private Networks' DNS resolver service. ## Removing public IPs from resources -We strongly recommend that you disable public connectivity on all of your Scaleway resources, unless it is absolutely required. It is preferable to attach resources to Private Networks wherever possible, and direct all traffic to the resource's private IP address on that network. This ensures optimal security, reduced cost and enhanced latency. Find out more in our documentation about [public connectivity best practices](/network/ipam/reference-content/public-connectivity-best-practices). +We strongly recommend that you disable public connectivity on all of your Scaleway resources, unless it is absolutely required. It is preferable to attach resources to Private Networks wherever possible, and direct all traffic to the resource's private IP address on that network. This ensures optimal security, reduced cost and enhanced latency. Find out more in our documentation about [public connectivity best practices](/ipam/reference-content/public-connectivity-best-practices). ## Public connectivity over Private Networks ### Public Gateways -You can use Scaleway [Public Gateways](/network/public-gateways/) to provide resources on a Private Network with a secure point of access to and from the public internet. +You can use Scaleway [Public Gateways](/public-gateways/) to provide resources on a Private Network with a secure point of access to and from the public internet. - Set the Public Gateway to advertize a default route to the internet, allowing attached resources to send packets to the internet via the gateway, without needing their own public IP address. -- Activate the [SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) so that you can establish SSH connections to resources on the Private Network via the gateway's bastion. +- Activate the [SSH bastion](/public-gateways/how-to/use-ssh-bastion/) so that you can establish SSH connections to resources on the Private Network via the gateway's bastion. - Use static NAT to map ingress traffic from the public internet towards resources on the Private Network, using private IP addresses and ports. ### Load Balancers -Another option is to attach a Scaleway [Load Balancer](/network/load-balancer/) to the Private Network. By giving the Load Balancer a public IP address, and configuring Instances on the Private Network as backend servers for the Load Balancer via their private IP addresses, the Load Balancer can securely and efficiently distribute traffic to the Instances. This solution is suitable when you have multiple Instances serving the same application, although you can also use multiple frontends/backends and [routes](/network/load-balancer/how-to/create-manage-routes/) to direct traffic to specific server pools. +Another option is to attach a Scaleway [Load Balancer](/load-balancer/) to the Private Network. By giving the Load Balancer a public IP address, and configuring Instances on the Private Network as backend servers for the Load Balancer via their private IP addresses, the Load Balancer can securely and efficiently distribute traffic to the Instances. This solution is suitable when you have multiple Instances serving the same application, although you can also use multiple frontends/backends and [routes](/load-balancer/how-to/create-manage-routes/) to direct traffic to specific server pools. You can also disable public connectivity on the Load Balancer itself. This may be relevant if the Load Balancer is configured to receive and distribute traffic from resources on a different Private Network within the same VPC, for example. ## Connecting a VPC to external infrastructure -Watch this space for Scaleway's upcoming solution to provide private, secure connectivity between resources in a Scaleway VPC and your external or on-premises architecture. In the meantime, you may consider installing a manual VPN on a Scaleway Instance to connect to other non-Scaleway infrastructure, and create a [custom route](/network/vpc/how-to/manage-routing/#how-to-create-a-custom-route) towards this VPN so traffic on your Private Network can securely communicate with resources at the other end of your VPN tunnel. +Watch this space for Scaleway's upcoming solution to provide private, secure connectivity between resources in a Scaleway VPC and your external or on-premises architecture. In the meantime, you may consider installing a manual VPN on a Scaleway Instance to connect to other non-Scaleway infrastructure, and create a [custom route](/vpc/how-to/manage-routing/#how-to-create-a-custom-route) towards this VPN so traffic on your Private Network can securely communicate with resources at the other end of your VPN tunnel. ## Resource-specific information @@ -108,7 +108,7 @@ Different types of Scaleway resources may have different requirements and possib * **Max attached PNs**: The maximum number of Private Networks that a resource can be attached to * **Mandatory PN**: Whether or not a Private Network must necessarily be attached to this resource * **Compatible with private IPv6**: Whether or not the resource is compatible with private IPv6 addressing. Compatible resources generally acquire both an IPv4 and an IPv6 address when attached to a Private Network. -* **Compatible with reserved IPs**: Whether or not you can use a [reserved IP](/network/ipam/how-to/reserve-ip/#how-to-attach-a-resource-to-a-private-network-using-a-reserved-ip-address) to attach the resource to a Private Network +* **Compatible with reserved IPs**: Whether or not you can use a [reserved IP](/ipam/how-to/reserve-ip/#how-to-attach-a-resource-to-a-private-network-using-a-reserved-ip-address) to attach the resource to a Private Network | | Instance | Elastic Metal | Kubernetes | Managed Inference | |------------------------------|----------|---------------|------------|-------------------| @@ -117,7 +117,7 @@ Different types of Scaleway resources may have different requirements and possib | Compatible with private IPv6 | Yes | Yes | Yes | No | | Compatible with reserved IPs | Yes | Yes | No | No | | Additional information | -- | [Paid-for
feature](https://www.scaleway.com/en/pricing/elastic-metal/#network) | PN cannot be changed
after cluster creation | Must have at least one of
private and/or public endpoint | -| Documentation | [Go](/compute/instances/how-to/use-private-networks/) | [Go](/bare-metal/elastic-metal/how-to/use-private-networks/) | [Go](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster) | [Go](/ai-data/managed-inference/how-to/managed-inference-with-private-network/) | +| Documentation | [Go](/instances/how-to/use-private-networks/) | [Go](/elastic-metal/how-to/use-private-networks/) | [Go](/kubernetes/reference-content/secure-cluster-with-private-network/#why-have-a-private-network-for-your-kubernetes-kapsule-cluster) | [Go](/managed-inference/how-to/managed-inference-with-private-network/) | | | Managed Database | Managed Database for Redis™ | Public Gateways | Load Balancer | @@ -127,6 +127,6 @@ Different types of Scaleway resources may have different requirements and possib | Compatible with private IPv6 | No | No | No | No | | Compatible with reserved IPs | No | No | Yes | Yes | | Additional information | Must have at least one of
private and/or public endpoint | Must have at least one of
private and/or public endpoint | -- | Private LBs must have a PN | -| Documentation | [Go](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/faq/databases-for-redis/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/network/load-balancer/how-to/use-with-private-network/) +| Documentation | [Go](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) | [Go](/faq/databases-for-redis/#what-is-the-private-networks-feature-for-redistm-database-instances) | [Go](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network) | [Go](/load-balancer/how-to/use-with-private-network/) diff --git a/network/vpc/reference-content/understanding-routing.mdx b/network/vpc/reference-content/understanding-routing.mdx index f752bb5b70..2e23ee65e8 100644 --- a/network/vpc/reference-content/understanding-routing.mdx +++ b/network/vpc/reference-content/understanding-routing.mdx @@ -23,9 +23,9 @@ Managed routes are also automatically added to the VPC’s routing table when yo You can create your own custom routes to send traffic for defined IP ranges towards a specified resource in the VPC, for example if you want to route to a VPN installed on an Instance. -Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/network/vpc/how-to/manage-routing/#how-to-activate-routing). More routing features are planned for the future, such as ACLs and firewalling. +Routing is activated by default whenever you create a new VPC, and can be activated on pre-existing VPCs by [following these steps](/vpc/how-to/manage-routing/#how-to-activate-routing). More routing features are planned for the future, such as ACLs and firewalling. -The diagram below shows an example of how routing works across two Private Networks on a VPC. The route table is held on the VPC's virtual router ([VRouter](/network/vpc/concepts/#vrouter)), and synched to each resource as it joins a Private Network. +The diagram below shows an example of how routing works across two Private Networks on a VPC. The route table is held on the VPC's virtual router ([VRouter](/vpc/concepts/#vrouter)), and synched to each resource as it joins a Private Network. - An Elastic Metal server on Private Network A can send a packet to the public internet via a Public Gateway also attached to Private Network A. - An Instance also on Private Network A can send a packet to an Instance on Private Network B, via the vRouter. - The same Instance on Private Network A can send a packet to an IP destination at the other end of the VPN hosted on Instance XYZ on Private Network B, thanks to a custom route. diff --git a/network/vpc/reference-content/use-case-basic.mdx b/network/vpc/reference-content/use-case-basic.mdx index 658c19c616..ee8e9ff799 100644 --- a/network/vpc/reference-content/use-case-basic.mdx +++ b/network/vpc/reference-content/use-case-basic.mdx @@ -29,10 +29,10 @@ The architecture diagram below shows the infrastructure for this use-case. This is a basic infrastructure to leverage VPC isolation: -- [Instances](/compute/instances/concepts/#instance) are hosting the application without having their own [public/flexible IP addresses](/compute/instances/concepts/#flexible-ip). -- [Managed Database](/managed-databases/postgresql-and-mysql/concepts/#managed-database) is accessed by the Instances over the Private Network only, with no exposure to the public internet. -- [Load Balancer](/network/load-balancer/concepts/) distributes user traffic to the Instances over the Private Network. -- Administrators can access the Instances via the [Public Gateway](/network/public-gateways/concepts/#public-gateway). +- [Instances](/instances/concepts/#instance) are hosting the application without having their own [public/flexible IP addresses](/instances/concepts/#flexible-ip). +- [Managed Database](/managed-databases-for-postgresql-and-mysql/concepts/#managed-database) is accessed by the Instances over the Private Network only, with no exposure to the public internet. +- [Load Balancer](/load-balancer/concepts/) distributes user traffic to the Instances over the Private Network. +- Administrators can access the Instances via the [Public Gateway](/public-gateways/concepts/#public-gateway). - External services are accessed by the Instances via the Public Gateway. Full [Terraform templates](#terraform) are available for this infrastructure. @@ -74,22 +74,22 @@ This kind of infrastructure is appropriate for many applications, including but Follow the steps below to create this infrastructure using the [Scaleway console](https://console.scaleway.com/organization): -1. [Create a VPC](/network/vpc/how-to/create-vpc/) (or use the [default VPC](/network/vpc/how-to/create-vpc/#how-to-identify-your-default-vpcs) pre-created for each Scaleway Project in the appropriate [region](/network/vpc/concepts/#region-and-availability-zone)). -2. [Create a Private Network](/network/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generated subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. -3. [Create a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) (set it to advertise the [default route](/network/public-gateways/concepts/#default-route)) and [attach it to the Private Network](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network). -4. [Set up SSH bastion](/network/public-gateways/how-to/use-ssh-bastion/) on the Public Gateway, to allow administrator access. -5. [Create a Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). -6. [Detach the Managed Database's public endpoint](/managed-databases/postgresql-and-mysql/how-to/remove-public-endpoint/) and [attach it to the Private Network](/managed-databases/postgresql-and-mysql/how-to/connect-database-private-network/) you created in step 2. -7. Create and configure external services as required, e.g. [Object Storage](/storage/object/quickstart/), [Transactional Email](/managed-services/transactional-email/quickstart/) and [Secret Manager](/identity-and-access-management/secret-manager/quickstart/). -8. [Create your Instances](/compute/instances/how-to/create-an-instance/), using the configuration best-suited to your application. Do not assign public IPv4 or IPv6 addresses to the Instances. Add Block Storage volumes as required (or you can create and attach these [later](/storage/block/quickstart/).) +1. [Create a VPC](/vpc/how-to/create-vpc/) (or use the [default VPC](/vpc/how-to/create-vpc/#how-to-identify-your-default-vpcs) pre-created for each Scaleway Project in the appropriate [region](/vpc/concepts/#region-and-availability-zone)). +2. [Create a Private Network](/vpc/how-to/create-private-network/) inside the VPC. You can either let Scaleway create the network with an auto-generated subnet, which will provide the private IP addresses for attached resources, or specify a self-defined subnet. +3. [Create a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) (set it to advertise the [default route](/public-gateways/concepts/#default-route)) and [attach it to the Private Network](/public-gateways/how-to/configure-a-public-gateway/#how-to-attach-a-public-gateway-to-a-private-network). +4. [Set up SSH bastion](/public-gateways/how-to/use-ssh-bastion/) on the Public Gateway, to allow administrator access. +5. [Create a Managed Database](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). +6. [Detach the Managed Database's public endpoint](/managed-databases-for-postgresql-and-mysql/how-to/remove-public-endpoint/) and [attach it to the Private Network](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-private-network/) you created in step 2. +7. Create and configure external services as required, e.g. [Object Storage](/object-storage/quickstart/), [Transactional Email](/transactional-email/quickstart/) and [Secret Manager](/secret-manager/quickstart/). +8. [Create your Instances](/instances/how-to/create-an-instance/), using the configuration best-suited to your application. Do not assign public IPv4 or IPv6 addresses to the Instances. Add Block Storage volumes as required (or you can create and attach these [later](/block-storage/quickstart/).) - If you are creating several Instances with the exact same configuration running the exact same template, consider creating just one Instance, configuring and installing it to communicate with the other resources inside and outside the VPC as required, then [creating an image](/compute/instances/how-to/create-a-backup/) of this Instance and creating the remaining Instances [using this image](/compute/instances/how-to/create-a-backup/#how-to-create-or-restore-an-instance-from-an-image). + If you are creating several Instances with the exact same configuration running the exact same template, consider creating just one Instance, configuring and installing it to communicate with the other resources inside and outside the VPC as required, then [creating an image](/instances/how-to/create-a-backup/) of this Instance and creating the remaining Instances [using this image](/instances/how-to/create-a-backup/#how-to-create-or-restore-an-instance-from-an-image). -9. [Attach each Instance to the Private Network](/compute/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) you created at step 2. Either let Scaleway automatically choose an IP from the Private Network's subnet for each Instance, or use [reserved IPs](s/network/ipam/how-to/reserve-ip/) to specify the IP for each Instance on the network. -10. [Create a Load Balancer](/network/load-balancer/how-to/create-load-balancer/), ensuring you assign a public (flexible) IP address. Do not yet create the frontends and backends. -11. [Attach the Load Balancer to the Private Network](/network/load-balancer/how-to/use-with-private-network/#how-to-attach-a-private-network-to-your-load-balancer). As before, you can use an auto-selected IP, or a specific reserved IP from the subnet. -12. [Create a frontend and backend for the Load Balancer](/network/load-balancer/how-to/create-frontends-backends/). Choose the most appropriate configuration for your purpose and application, following advice and tips in the linked documentation. When configuring the Load Balancer's backend servers, enter the private IP addresses of the Instances on the Private Network. -13. [Create your domain](/network/domains-and-dns/how-to/register-internal-domain/) and [add a DNS record](/network/domains-and-dns/how-to/manage-dns-records/#how-to-add-dns-records) (e.g. an A record) to point it to the public IP of your Load Balancer. While instructions show how to do this with Scaleway's **Domains and DNS** product, you can also use an external domain and configure it with another provider. +9. [Attach each Instance to the Private Network](/instances/how-to/use-private-networks/#how-to-attach-instances-to-an-existing-private-network) you created at step 2. Either let Scaleway automatically choose an IP from the Private Network's subnet for each Instance, or use [reserved IPs](s/network/ipam/how-to/reserve-ip/) to specify the IP for each Instance on the network. +10. [Create a Load Balancer](/load-balancer/how-to/create-load-balancer/), ensuring you assign a public (flexible) IP address. Do not yet create the frontends and backends. +11. [Attach the Load Balancer to the Private Network](/load-balancer/how-to/use-with-private-network/#how-to-attach-a-private-network-to-your-load-balancer). As before, you can use an auto-selected IP, or a specific reserved IP from the subnet. +12. [Create a frontend and backend for the Load Balancer](/load-balancer/how-to/create-frontends-backends/). Choose the most appropriate configuration for your purpose and application, following advice and tips in the linked documentation. When configuring the Load Balancer's backend servers, enter the private IP addresses of the Instances on the Private Network. +13. [Create your domain](/domains-and-dns/how-to/register-internal-domain/) and [add a DNS record](/domains-and-dns/how-to/manage-dns-records/#how-to-add-dns-records) (e.g. an A record) to point it to the public IP of your Load Balancer. While instructions show how to do this with Scaleway's **Domains and DNS** product, you can also use an external domain and configure it with another provider. ## Terraform diff --git a/network/vpc/reference-content/vpc-migration.mdx b/network/vpc/reference-content/vpc-migration.mdx index 5129283974..e593baa9dd 100644 --- a/network/vpc/reference-content/vpc-migration.mdx +++ b/network/vpc/reference-content/vpc-migration.mdx @@ -27,10 +27,10 @@ As of July 12, 2023, VPC is now in general availability (GA). The arrival of VPC If you are unsure about some of the terminology in this document, refer to the sources below for more explanation before continuing. -- [What is a VPC?](/network/vpc/concepts/#vpc) -- [What is a Private Network?](/network/vpc/concepts/#private-networks) -- [What do the terms "region"/"regional" and "zoned"/"AZ" mean?](/network/vpc/concepts/#region-and-availability-zone) -- [What is DHCP?](/network/public-gateways/concepts/#dhcp) +- [What is a VPC?](/vpc/concepts/#vpc) +- [What is a Private Network?](/vpc/concepts/#private-networks) +- [What do the terms "region"/"regional" and "zoned"/"AZ" mean?](/vpc/concepts/#region-and-availability-zone) +- [What is DHCP?](/public-gateways/concepts/#dhcp) - [What is beta vs. general availability (GA)?](https://www.scaleway.com/en/betas/) ## VPC GA: What does it mean for Private Networks? @@ -40,7 +40,7 @@ As summarized in the [table](#overview) above, now that VPC is in general availa There is also an impact on pre-existing Private Networks. There are three aspects to this impact: - **Zoned > Regional**: All pre-existing zoned Private Networks have been automatically migrated by Scaleway, and are now regional Private Networks inside a VPC. -- **DHCP activation**: Prior to VPC GA, DHCP was not itself present on any pre-existing Private Networks. It was instead a feature of the [Public Gateway](/network/public-gateways/concepts/#public-gateway) which could optionally be attached to a Private Network and (if DHCP was activated), automatically assign private IP addresses to attached resources. When VPC went into GA, DHCP functionality was moved from Public Gateways to Private Networks themselves. **Whether or not DHCP has been automatically activated on your pre-existing Private Network depends on the specificities of your configuration**. +- **DHCP activation**: Prior to VPC GA, DHCP was not itself present on any pre-existing Private Networks. It was instead a feature of the [Public Gateway](/public-gateways/concepts/#public-gateway) which could optionally be attached to a Private Network and (if DHCP was activated), automatically assign private IP addresses to attached resources. When VPC went into GA, DHCP functionality was moved from Public Gateways to Private Networks themselves. **Whether or not DHCP has been automatically activated on your pre-existing Private Network depends on the specificities of your configuration**. - **Managed DNS**: All new Private Networks benefit from Managed DNS, to facilitate resource name resolution between different resources attached to the Private Network. **Private Networks attached to a legacy Public Gateway continue to use the Gateway's DNS**. Read on for more information about these three aspects. @@ -52,7 +52,7 @@ All newly created Private Networks going forward will be regional in scope. All - This was planned as a seamless migration with no downtime. - Private Networks in `PAR-1`, `PAR-2` or `PAR-3` became scoped to the whole `PAR` region, Private Networks from `AMS-1` or `AMS-2` became scoped to the whole `AMS` region, and Private Networks from `WAW-1` or `WAW-2` became scoped to the whole `WAW` region. - You can now attach resources from any of the AZs within the region of a Private Network. This gives you a Private Network where, for example, an Elastic Metal server in `PAR-2` can communicate with a Managed Database in `PAR-1`. -- One default VPC for each Scaleway region has been created per [Project](/identity-and-access-management/iam/concepts/#project), and your newly migrated Private Networks are accessible from within the default VPC for their region. +- One default VPC for each Scaleway region has been created per [Project](/iam/concepts/#project), and your newly migrated Private Networks are accessible from within the default VPC for their region. ## Aspect 2: DHCP on Private Networks @@ -87,9 +87,9 @@ Whether or not the managed DHCP server has been automatically activated on your If you fall into one of the cases where DHCP is not automatically activated for you, as well as seeing an **Activate DHCP** button in the Scaleway console, you can also activate via the API if you prefer. -See the dedicated documentation on [activating DHCP](/network/vpc/how-to/activate-dhcp/) +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 devtools 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](/network/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-gateway/) and other devtools 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 @@ -111,7 +111,7 @@ You may have observed the following behavior when during the period directly fol - For each Public Gateway (newly-created or pre-existing), a new VPC was automatically created to hold its subnets and route table. - When a Private Network is attached to a Public Gateway, it was moved to the gateway's VPC. -**Public Gateways created via the [Scaleway console](https://console.scaleway.com/) after October 17 2023 are IPAM-mode gateways, and the temporary behavior described above no longer applies.** These gateways are fully compatible with Scaleway's [IPAM](/network/vpc/concepts/#ipam) and no longer need to auto-create their own VPC for attached Private Networks to ensure IPAM compatibility. +**Public Gateways created via the [Scaleway console](https://console.scaleway.com/) after October 17 2023 are IPAM-mode gateways, and the temporary behavior described above no longer applies.** These gateways are fully compatible with Scaleway's [IPAM](/vpc/concepts/#ipam) and no longer need to auto-create their own VPC for attached Private Networks to ensure IPAM compatibility. **Public Gateways created before October 17 2023 are legacy gateways, and their attached Private Networks must stay in the gateway's auto-created VPC to ensure IPAM compatibility.** @@ -119,10 +119,10 @@ You can tell whether your Public Gateway is in legacy mode or IPAM mode, by refe -Find out more about legacy gateways versus IPAM-mode gateways in our [IPAM concept documentation](/network/public-gateways/concepts/#ipam). +Find out more about legacy gateways versus IPAM-mode gateways in our [IPAM concept documentation](/public-gateways/concepts/#ipam). -When creating a Kubernetes Kapsule cluster with [full isolation](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be fully integrated with IPAM. +When creating a Kubernetes Kapsule cluster with [full isolation](/kubernetes/reference-content/secure-cluster-with-private-network/#can-i-use-a-public-gateway-with-my-private-network-to-exit-all-outgoing-traffic-from-the-nodes) you are required to attach a Public Gateway to the cluster's Private Network, and this **cannot** be a legacy Public Gateway - it must be fully integrated with IPAM. ## Impacts on the rest of the Scaleway ecosystem @@ -161,7 +161,7 @@ Read our [blog post](https://www.scaleway.com/en/blog/virtual-private-cloud-publ ## Further resources -- [VPC Public Beta Documentation](/network/vpc/) +- [VPC Public Beta Documentation](/vpc/) - [VPC FAQ](/faq/vpc/) - [VPC API Documentation](https://www.scaleway.com/en/developers/api/vpc/) - [Scaleway Developers Tools](https://www.scaleway.com/en/developers/) diff --git a/network/vpc/troubleshooting/private-dns-dhcp-not-working.mdx b/network/vpc/troubleshooting/private-dns-dhcp-not-working.mdx index 3addabd06e..cfe24f5ba2 100644 --- a/network/vpc/troubleshooting/private-dns-dhcp-not-working.mdx +++ b/network/vpc/troubleshooting/private-dns-dhcp-not-working.mdx @@ -17,8 +17,8 @@ There are some cases when a Private Network's private DNS or DHCP may not work ' ## Basic steps to try first -- Make sure that [DHCP is activated](/network/vpc/how-to/activate-dhcp/) on your Private Network. -- Ensure that you have tried [detaching/reattaching](/network/vpc/troubleshooting/resource-attached-no-ip/#no-ip-address-is-displayed-but-i-have-activated-dhcp) the affected resources from/to the Private Network, particularly if they are older resources or you have [changed their name](/network/vpc/how-to/attach-resources-to-pn/#how-to-access-a-resource-on-a-private-network-via-its-hostname-dns). +- Make sure that [DHCP is activated](/vpc/how-to/activate-dhcp/) on your Private Network. +- Ensure that you have tried [detaching/reattaching](/vpc/troubleshooting/resource-attached-no-ip/#no-ip-address-is-displayed-but-i-have-activated-dhcp) the affected resources from/to the Private Network, particularly if they are older resources or you have [changed their name](/vpc/how-to/attach-resources-to-pn/#how-to-access-a-resource-on-a-private-network-via-its-hostname-dns). ## Resources with a dot in their hostname @@ -26,7 +26,7 @@ Issues may arise with internal addressing if you give your resource a name that ## Private Networks with a name that is also a TLD -See our [dedicated document](/network/vpc/troubleshooting/pn-name/) for a full explanation of this problem, and suggested solutions. +See our [dedicated document](/vpc/troubleshooting/pn-name/) for a full explanation of this problem, and suggested solutions. ## Distributions running Network Manager diff --git a/network/vpc/troubleshooting/resource-attached-no-ip.mdx b/network/vpc/troubleshooting/resource-attached-no-ip.mdx index 1cafa6930f..1d1db85bf8 100644 --- a/network/vpc/troubleshooting/resource-attached-no-ip.mdx +++ b/network/vpc/troubleshooting/resource-attached-no-ip.mdx @@ -13,10 +13,10 @@ categories: - network --- -When you attach a resource to a Private Network, the Private Network's built-in DHCP defines an IPv4 and IPv6 address for the resource on that network. This is managed via Scaleway's [internal IPAM](/network/vpc/concepts/#ipam). +When you attach a resource to a Private Network, the Private Network's built-in DHCP defines an IPv4 and IPv6 address for the resource on that network. This is managed via Scaleway's [internal IPAM](/vpc/concepts/#ipam). -- [Find out how to attach a resource to a Private Network](/network/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) -- [Find out how to view your resource's IP address on the Private Network](/network/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) +- [Find out how to attach a resource to a Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-attach-a-resource-to-a-private-network) +- [Find out how to view your resource's IP address on the Private Network](/vpc/how-to/attach-resources-to-pn/#how-to-view-the-resources-ip-address) IP addresses are allocated asynchronously from the attachment of the resource in most cases. The IP will therefore not be immediately returned upon attaching a resource via the API, and there may be a brief delay before it displays in the console, as shown below: @@ -26,13 +26,13 @@ However, in some cases even after waiting, an IP address may not be set for your ## No IP address is displayed and I have not activated DHCP -You may have attached a resource to an "old" Private Network on which you [have not activated DHCP](/network/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks). In this case, no IP address for the resource on the network is configured. +You may have attached a resource to an "old" Private Network on which you [have not activated DHCP](/vpc/reference-content/vpc-migration/#dhcp-activation-on-pre-existing-private-networks). In this case, no IP address for the resource on the network is configured. -You will need to carry out manual configuration to set the IP address on the resource or [activate](/network/vpc/how-to/activate-dhcp/) DHCP. +You will need to carry out manual configuration to set the IP address on the resource or [activate](/vpc/how-to/activate-dhcp/) DHCP. We strongly recommend that you activate DHCP on the Private Network to let us automatically handle IP address management. -Read our dedicated documentation about [VPC migration](/network/vpc/reference-content/vpc-migration/) for more information about how "old" Private Networks are migrated to the VPC, including DHCP activation. +Read our dedicated documentation about [VPC migration](/vpc/reference-content/vpc-migration/) for more information about how "old" Private Networks are migrated to the VPC, including DHCP activation. ## No IP address is displayed but I have activated DHCP @@ -42,6 +42,6 @@ To fix this problem, **detach your resource from the Private Network, and reatta ### Elastic Metal servers -Note that some manual configuration of the network interface is required for Elastic Metal servers. Follow the steps in our [dedicated documentation](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). +Note that some manual configuration of the network interface is required for Elastic Metal servers. Follow the steps in our [dedicated documentation](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks). -If you are running multiple virtual machines on an Elastic Metal server, you can reserve private IP addresses for them with IPAM, and attach a MAC address and resource name to these IPs. Follow our [dedicated documentation](/network/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file +If you are running multiple virtual machines on an Elastic Metal server, you can reserve private IP addresses for them with IPAM, and attach a MAC address and resource name to these IPs. Follow our [dedicated documentation](/ipam/how-to/reserve-ip/#how-to-reserve-a-private-ip-address-with-an-attached-mac-address). \ No newline at end of file diff --git a/observability/cockpit/api-cli/configuring-grafana-agent.mdx b/observability/cockpit/api-cli/configuring-grafana-agent.mdx index d52d9934cb..b9fbb39d09 100644 --- a/observability/cockpit/api-cli/configuring-grafana-agent.mdx +++ b/observability/cockpit/api-cli/configuring-grafana-agent.mdx @@ -16,12 +16,12 @@ categories: This page explains how to configure the Grafana agent and the Zipkin collector to push your metrics, logs, and traces. You can use it to **push your data from Scaleway resources or external resources**. - [The Grafana agent has been deprecated by Grafana](https://grafana.com/docs/agent/latest/). Find out [how to configure Grafana Alloy](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/#configuring-grafana-alloy) which is Grafana's new telemetry collector. + [The Grafana agent has been deprecated by Grafana](https://grafana.com/docs/agent/latest/). Find out [how to configure Grafana Alloy](/cockpit/how-to/send-metrics-with-grafana-alloy/#configuring-grafana-alloy) which is Grafana's new telemetry collector. - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A Scaleway account logged into the [console](https://console.scaleway.com) - Installed [Docker](https://www.docker.com/) and [Docker compose](https://docs.docker.com/compose/install/) @@ -36,7 +36,7 @@ This page explains how to configure the Grafana agent and the Zipkin collector t It is not currently possible to collect logs if you are using OSX. -1. [Create a token](/observability/cockpit/how-to/create-token/) and select the push permission for metrics, traces, and logs. +1. [Create a token](/cockpit/how-to/create-token/) and select the push permission for metrics, traces, and logs. 2. Create a folder where you will keep your configuration files. 3. Create a configuration file inside your folder and name it `config.yaml`. This file will contain the Grafana agent configuration. 4. Copy the following YAML template. @@ -166,7 +166,7 @@ This page explains how to configure the Grafana agent and the Zipkin collector t - filesystem - netdev ``` -5. You can also specify the [data source](/observability/cockpit/concepts/#data-sources) containing your [data types](/observability/cockpit/concepts/#data-types) by: +5. You can also specify the [data source](/cockpit/concepts/#data-sources) containing your [data types](/cockpit/concepts/#data-types) by: - Adding the ID of the data source to the endpoint. You can retrieve the ID of the data source you want to configure using the `ListDataSources` API command, or - Adding the `X-Datasource-Id` header in the `headers` section, under `X-Token`. @@ -236,7 +236,7 @@ This page explains how to configure the Grafana agent and the Zipkin collector t ## Visualizing metrics in Grafana -1. [Log into Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 2. Click the **Toggle menu** icon. 3. Click **Dashboards**. 4. Click **New** then click **Import** to import your Grafana dashboard. @@ -247,7 +247,7 @@ This page explains how to configure the Grafana agent and the Zipkin collector t ## Visualizing logs in Grafana -1. [Log into Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 2. Click **Explore**. 3. Select the **Scaleway logs** data source in the drop-down. @@ -257,7 +257,7 @@ This page explains how to configure the Grafana agent and the Zipkin collector t ## Visualizing traces in Grafana -1. [Log into Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 2. Click the **Toggle menu** icon. 3. Click **Explore** next to the compass icon. 4. Select the **Traces** data source from the drop-down. diff --git a/observability/cockpit/api-cli/querying-logs-with-logcli.mdx b/observability/cockpit/api-cli/querying-logs-with-logcli.mdx index a521628003..487fe7f9bf 100644 --- a/observability/cockpit/api-cli/querying-logs-with-logcli.mdx +++ b/observability/cockpit/api-cli/querying-logs-with-logcli.mdx @@ -20,9 +20,9 @@ Retrieving your logs programmatically can be useful in environments where automa - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Created a token](/observability/cockpit/how-to/create-token/) with the `query` permission for logs + - [Created a token](/cockpit/how-to/create-token/) with the `query` permission for logs - Custom and/or Scaleway logs to query - [Installed LogCLI](https://grafana.com/docs/loki/latest/query/logcli/#installation) diff --git a/observability/cockpit/concepts.mdx b/observability/cockpit/concepts.mdx index 2ef44bec2d..d42eb72576 100644 --- a/observability/cockpit/concepts.mdx +++ b/observability/cockpit/concepts.mdx @@ -21,7 +21,7 @@ Active series refer to [time series](#time-series) for which the latest [samples An agent is a software component that runs on your systems to gather [data types](#data-types) from the host system or applications running on it. The agent then forwards this data to Cockpit for analysis and visualization. - Find out how to [configure the Grafana Alloy agent to collect and send your data to Cockpit](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/). + Find out how to [configure the Grafana Alloy agent to collect and send your data to Cockpit](/cockpit/how-to/send-metrics-with-grafana-alloy/). ## Alerting @@ -50,7 +50,7 @@ Alerting rules allow you to define criteria that determine whether an alert is t ## Cockpit -A Cockpit is an instance of the Observability product that stores metrics, logs, and traces and provides a dedicated dashboarding system on Grafana to visualize them. A Scaleway Project can have only one Cockpit, which is automatically activated when you are using [Scaleway resources that are integrated into Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +A Cockpit is an instance of the Observability product that stores metrics, logs, and traces and provides a dedicated dashboarding system on Grafana to visualize them. A Scaleway Project can have only one Cockpit, which is automatically activated when you are using [Scaleway resources that are integrated into Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## Contact points @@ -58,11 +58,11 @@ Contact points define who is notified when an alert fires, according to the regi ## Data sources -Data sources are regionalized backends that allow you to store and fetch your metrics, logs, and traces. By default, **Scaleway data sources** are enabled if you are using [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) on your Project. +Data sources are regionalized backends that allow you to store and fetch your metrics, logs, and traces. By default, **Scaleway data sources** are enabled if you are using [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit) on your Project. Scaleway data sources are **read-only**. -You can [create](/observability/cockpit/how-to/create-external-data-sources/) additional **custom data sources** in the Paris, Amsterdam, and Warsaw regions, from your own external resources. +You can [create](/cockpit/how-to/create-external-data-sources/) additional **custom data sources** in the Paris, Amsterdam, and Warsaw regions, from your own external resources. ## Data types diff --git a/observability/cockpit/how-to/access-grafana-and-managed-dashboards.mdx b/observability/cockpit/how-to/access-grafana-and-managed-dashboards.mdx index 04e8aa5df6..f94ee2db2f 100644 --- a/observability/cockpit/how-to/access-grafana-and-managed-dashboards.mdx +++ b/observability/cockpit/how-to/access-grafana-and-managed-dashboards.mdx @@ -13,20 +13,20 @@ dates: posted: 2022-10-31 --- -Scaleway provides you with managed dashboards you can access in Grafana, for [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway provides you with managed dashboards you can access in Grafana, for [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). -This page shows you how to access [managed dashboards](/observability/cockpit/concepts/#managed-dashboards). +This page shows you how to access [managed dashboards](/cockpit/concepts/#managed-dashboards). - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - [Retrieved your Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Retrieved your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website. -3. Enter your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +3. Enter your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 4. Click **Log in**. The Grafana overview page displays. 5. Click the **Home** icon at the top left of your screen. 6. Click **Dashboard**. The Scaleway folder appears, with a list of all available managed dashboards for Scaleway resources. diff --git a/observability/cockpit/how-to/activate-managed-alerts.mdx b/observability/cockpit/how-to/activate-managed-alerts.mdx index 3de435a84d..9ba7a2e388 100644 --- a/observability/cockpit/how-to/activate-managed-alerts.mdx +++ b/observability/cockpit/how-to/activate-managed-alerts.mdx @@ -12,13 +12,13 @@ dates: posted: 2024-04-05 --- -This page shows you how to activate [preconfigured alerts](/observability/cockpit/concepts/#preconfigured-alerts) for your Cockpit resources using the [Scaleway console](https://console.scaleway.com/). +This page shows you how to activate [preconfigured alerts](/cockpit/concepts/#preconfigured-alerts) for your Cockpit resources using the [Scaleway console](https://console.scaleway.com/). - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Enabled](/observability/cockpit/how-to/enable-alert-manager/) the alert manager - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. diff --git a/observability/cockpit/how-to/activate-push-traces.mdx b/observability/cockpit/how-to/activate-push-traces.mdx index 9b7e519f54..8f2a5f9bb2 100644 --- a/observability/cockpit/how-to/activate-push-traces.mdx +++ b/observability/cockpit/how-to/activate-push-traces.mdx @@ -12,12 +12,12 @@ dates: posted: 2023-10-31 --- -This page shows you how to create [traces](/observability/cockpit/concepts/#traces) from the Scaleway console, retrieve traces push paths, configure the OpenTelemetry HTTP agent, and push traces. +This page shows you how to create [traces](/cockpit/concepts/#traces) from the Scaleway console, retrieve traces push paths, configure the OpenTelemetry HTTP agent, and push traces. - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Create a trace @@ -48,17 +48,17 @@ Alternatively, you can retrieve your trace's push path from the Scaleway console ## Push traces -1. [Create a token](/observability/cockpit/how-to/create-token/) with **Push** permissions for traces. +1. [Create a token](/cockpit/how-to/create-token/) with **Push** permissions for traces. Your token's secret key displays only once. Make sure that you copy and save it before you exit the page. -2. Configure your applications to send traces to your [preferred endpoint](/observability/cockpit/concepts/#endpoints) using your newly-created token to authenticate. +2. Configure your applications to send traces to your [preferred endpoint](/cockpit/concepts/#endpoints) using your newly-created token to authenticate. - You can also configure an agent to push your trace(s). Find out [how to configure the Grafana Alloy agent and push your data](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/) + You can also configure an agent to push your trace(s). Find out [how to configure the Grafana Alloy agent and push your data](/cockpit/how-to/send-metrics-with-grafana-alloy/) -3. [Create your Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). -4. [Log in to your Grafana account](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/). -5. Create your [Grafana dashboard](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data. +3. [Create your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). +4. [Log in to your Grafana account](/cockpit/how-to/access-grafana-and-managed-dashboards/). +5. Create your [Grafana dashboard](/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data. Find out more information about pushing traces and visualizing them in Grafana, in the [official documentation](https://grafana.com/docs/grafana/latest/panels-visualizations/visualizations/traces/#add-a-panel-with-tracing-visualizations) diff --git a/observability/cockpit/how-to/add-contact-points.mdx b/observability/cockpit/how-to/add-contact-points.mdx index 59b715de12..f1e57aadaa 100644 --- a/observability/cockpit/how-to/add-contact-points.mdx +++ b/observability/cockpit/how-to/add-contact-points.mdx @@ -12,13 +12,13 @@ dates: posted: 2024-04-05 --- -This page shows you how to associate [contact points](/observability/cockpit/concepts/#contact-points) with the default [receiver](/observability/cockpit/concepts/#receivers) using the [Scaleway console](https://console.scaleway.com/). +This page shows you how to associate [contact points](/cockpit/concepts/#contact-points) with the default [receiver](/cockpit/concepts/#receivers) using the [Scaleway console](https://console.scaleway.com/). - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - [Enabled](/observability/cockpit/how-to/enable-alert-manager/) the alert manager + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager ## Add contact points @@ -31,4 +31,4 @@ This page shows you how to associate [contact points](/observability/cockpit/con Make sure that you choose the same regions as the data sources for which you want to receive alerts. 6. Click **Add email address**. The email address appears in the list of your contact points. -7. Optionally, if you have [activated preconfigured alerts](/observability/cockpit/how-to/activate-managed-alerts/), click **Send test alert** to ensure that your alerts are sent to your contact points. +7. Optionally, if you have [activated preconfigured alerts](/cockpit/how-to/activate-managed-alerts/), click **Send test alert** to ensure that your alerts are sent to your contact points. diff --git a/observability/cockpit/how-to/change-data-retention.mdx b/observability/cockpit/how-to/change-data-retention.mdx index 261dc4d89a..f610f02c7f 100644 --- a/observability/cockpit/how-to/change-data-retention.mdx +++ b/observability/cockpit/how-to/change-data-retention.mdx @@ -13,20 +13,20 @@ dates: posted: 2024-11-25 --- -This page shows you how to change the [retention](/observability/cockpit/concepts/#retention) period for your data sources. +This page shows you how to change the [retention](/cockpit/concepts/#retention) period for your data sources. **Cockpit pricing plans were deprecated on January 1st 2025**

- The [retention](/observability/cockpit/concepts/#retention) period previously set for your Scaleway and custom logs, metrics and traces remains the same.

+ The [retention](/cockpit/concepts/#retention) period previously set for your Scaleway and custom logs, metrics and traces remains the same.

You can change the retention period for your metrics, logs, and traces for free during the retention period edition beta (starting January 1st 2025).

- A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click the **Data sources** tab. @@ -41,7 +41,7 @@ This page shows you how to change the [retention](/observability/cockpit/concept - Reducing the retention period of a data source will permanently delete all observability data in that data source beyond the selected timeframe. This deletion is irreversible and takes effect a few minutes after the retention period is reduced, even if the retention period is later increased. - - Find out about the [retention periods available for each data source type](/observability/cockpit/concepts/#retention). + - Find out about the [retention periods available for each data source type](/cockpit/concepts/#retention). 6. Click **Edit retention period** to confirm. diff --git a/observability/cockpit/how-to/configure-alerts-for-scw-resources.mdx b/observability/cockpit/how-to/configure-alerts-for-scw-resources.mdx index 83e22783ad..db79d0a1f2 100644 --- a/observability/cockpit/how-to/configure-alerts-for-scw-resources.mdx +++ b/observability/cockpit/how-to/configure-alerts-for-scw-resources.mdx @@ -17,14 +17,14 @@ This page shows you how to configure alerts for Scaleway resources in Grafana us - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Scaleway resources you can monitor - - [Created Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/) with the **Editor** role - - [Enabled](/observability/cockpit/how-to/enable-alert-manager/) the alert manager, and [activated preconfigured alerts](/observability/cockpit/how-to/activate-managed-alerts/) - - [Created](/observability/cockpit/how-to/add-contact-points/) at least one contact point + - [Created Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) with the **Editor** role + - [Enabled](/cockpit/how-to/enable-alert-manager/) the alert manager, and [activated preconfigured alerts](/cockpit/how-to/activate-managed-alerts/) + - [Created](/cockpit/how-to/add-contact-points/) at least one contact point - Selected the **Scaleway Alerting** alert manager in Grafana -1. [Log in to Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) using your credentials. +1. [Log in to Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your credentials. 2. Click the **Toggle menu** then click **Alerting**. 3. Click **Alert rules** and **+ New alert rule**. 4. Scroll down to the **Define query and alert condition** section and click **Switch to data source-managed alert rule**. diff --git a/observability/cockpit/how-to/create-external-data-sources.mdx b/observability/cockpit/how-to/create-external-data-sources.mdx index c2b658b3ba..10c119d1f6 100644 --- a/observability/cockpit/how-to/create-external-data-sources.mdx +++ b/observability/cockpit/how-to/create-external-data-sources.mdx @@ -12,18 +12,18 @@ dates: posted: 2024-04-05 --- -This page shows you how to create a **custom** [data source](/observability/cockpit/concepts/#data-sources) and its [data type](/observability/cockpit/concepts/#data-types), from the Scaleway console. +This page shows you how to create a **custom** [data source](/cockpit/concepts/#data-sources) and its [data type](/cockpit/concepts/#data-types), from the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click the **Data sources** tab. 3. Click **+ Create custom data source**. 4. Enter a name for the data source. -5. Choose the [data type](/observability/cockpit/concepts/#data-types) you want to create in the data source. +5. Choose the [data type](/cockpit/concepts/#data-types) you want to create in the data source. 6. Select the region for your data source. We recommend that you create your data sources in the same regions as the alert manager if you want to receive alerts for them. diff --git a/observability/cockpit/how-to/create-token.mdx b/observability/cockpit/how-to/create-token.mdx index 27a037a80c..af7ef0bae7 100644 --- a/observability/cockpit/how-to/create-token.mdx +++ b/observability/cockpit/how-to/create-token.mdx @@ -13,19 +13,19 @@ dates: posted: 2022-10-31 --- -This page shows you how to create [tokens](/observability/cockpit/concepts/#tokens), to grant other cloud providers’ services and platforms access to your [Cockpit](/observability/cockpit/concepts/#cockpit). +This page shows you how to create [tokens](/cockpit/concepts/#tokens), to grant other cloud providers’ services and platforms access to your [Cockpit](/cockpit/concepts/#cockpit). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click the **Tokens** tab. 3. Click **+ Create token**. A pop-up displays. 4. Choose a region to create the token in. - Make sure that you create your token in the same region as the [data sources](/observability/cockpit/concepts/#data-sources) you want to use it for. + Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for. 5. Choose a name for your token or use the already-generated name. 6. Select the permissions you wish to apply to your token. diff --git a/observability/cockpit/how-to/delete-external-data-sources.mdx b/observability/cockpit/how-to/delete-external-data-sources.mdx index c156acf7f7..29351c0469 100644 --- a/observability/cockpit/how-to/delete-external-data-sources.mdx +++ b/observability/cockpit/how-to/delete-external-data-sources.mdx @@ -12,13 +12,13 @@ dates: posted: 2024-04-13 --- -This page shows you how to delete a custom [data source](/observability/cockpit/concepts/#data-sources) from the Scaleway console. +This page shows you how to delete a custom [data source](/cockpit/concepts/#data-sources) from the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - [Created](/observability/cockpit/how-to/create-external-data-sources/) custom data sources + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Created](/cockpit/how-to/create-external-data-sources/) custom data sources 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click the **Data sources** tab. diff --git a/observability/cockpit/how-to/enable-alert-manager.mdx b/observability/cockpit/how-to/enable-alert-manager.mdx index 241c8ea1d2..382ff0c679 100644 --- a/observability/cockpit/how-to/enable-alert-manager.mdx +++ b/observability/cockpit/how-to/enable-alert-manager.mdx @@ -17,7 +17,7 @@ This page shows you how to enable Scaleway's regionalized alert manager to confi - A Scaleway account logged into the [Scaleway console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. @@ -25,6 +25,6 @@ This page shows you how to enable Scaleway's regionalized alert manager to confi 3. Click **Enable** under the **Alert manager** section. 4. Choose the regions where you want to enable the alert manager. - Make sure that you enable the alert manager in the same regions as the [data sources](/observability/cockpit/concepts/#data-sources) you want to be alerted for. + Make sure that you enable the alert manager in the same regions as the [data sources](/cockpit/concepts/#data-sources) you want to be alerted for. 5. Click **Enable alert manager** to confirm. diff --git a/observability/cockpit/how-to/retrieve-grafana-credentials.mdx b/observability/cockpit/how-to/retrieve-grafana-credentials.mdx index ff65433ad2..7be72086c1 100644 --- a/observability/cockpit/how-to/retrieve-grafana-credentials.mdx +++ b/observability/cockpit/how-to/retrieve-grafana-credentials.mdx @@ -13,19 +13,19 @@ dates: posted: 2022-10-31 --- -This page shows you how to retrieve your Grafana credentials to access your Grafana [dashboards](/observability/cockpit/concepts/#managed-dashboards) using the [Scaleway console](https://console.scaleway.com/). +This page shows you how to retrieve your Grafana credentials to access your Grafana [dashboards](/cockpit/concepts/#managed-dashboards) using the [Scaleway console](https://console.scaleway.com/). - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click the **Grafana users** tab. 3. Click **+ Add user**. 4. Enter a username. -5. Select a [role](/observability/cockpit/concepts/#grafana-users) for the user. +5. Select a [role](/cockpit/concepts/#grafana-users) for the user. 6. Click **Add user**. Your automatically generated password to log in to Grafana displays. Make sure to copy and save it before closing the pop-up. diff --git a/observability/cockpit/how-to/send-metrics-logs-to-cockpit.mdx b/observability/cockpit/how-to/send-metrics-logs-to-cockpit.mdx index 14d56a8166..bdf6f82f5b 100644 --- a/observability/cockpit/how-to/send-metrics-logs-to-cockpit.mdx +++ b/observability/cockpit/how-to/send-metrics-logs-to-cockpit.mdx @@ -13,15 +13,15 @@ dates: posted: 2022-10-31 --- -This page shows you how to send data such as [metrics](/observability/cockpit/concepts/#metric) and [logs](/observability/cockpit/concepts/#logs) to your [Cockpit](/observability/cockpit/concepts/#cockpit). You can push metrics with any `Prometheus Remote Write` compatible agent such as the [Prometheus](https://prometheus.io/docs/introduction/overview/), [Grafana](https://grafana.com/docs/agent/latest/) or [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) agents. +This page shows you how to send data such as [metrics](/cockpit/concepts/#metric) and [logs](/cockpit/concepts/#logs) to your [Cockpit](/cockpit/concepts/#cockpit). You can push metrics with any `Prometheus Remote Write` compatible agent such as the [Prometheus](https://prometheus.io/docs/introduction/overview/), [Grafana](https://grafana.com/docs/agent/latest/) or [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) agents. You can push logs with any Loki compatible agent such as the [Promtail](https://grafana.com/docs/loki/latest/clients/promtail/), [Fluentd](https://docs.fluentd.org/), [Fluent Bit](https://docs.fluentbit.io/manual/) or [Logstash](https://www.elastic.co/guide/en/logstash/current/introduction.html) agents. - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - Configured an agent. Read our dedicated [documentation](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure the Grafana Alloy agent - - [Created](/identity-and-access-management/iam/how-to/create-api-keys/) an API key and retrieved your API secret key + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - Configured an agent. Read our dedicated [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure the Grafana Alloy agent + - [Created](/iam/how-to/create-api-keys/) an API key and retrieved your API secret key @@ -32,18 +32,18 @@ You can push logs with any Loki compatible agent such as the [Promtail](https:// ## Send metrics and logs to your Cockpit 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. -2. [Create a token](/observability/cockpit/how-to/create-token/) with the **Push** permission for metrics and logs. +2. [Create a token](/cockpit/how-to/create-token/) with the **Push** permission for metrics and logs. - - Make sure that you create your token in the same region as the [data sources](/observability/cockpit/concepts/#data-sources) you want to use it for. + - Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for. - Make sure that you copy your token's secret key and save it before you exit the page. -3. Configure your applications to send metrics and logs to your Cockpit [endpoints](/observability/cockpit/concepts/#endpoints), using your token's secret key for authentication. +3. Configure your applications to send metrics and logs to your Cockpit [endpoints](/cockpit/concepts/#endpoints), using your token's secret key for authentication. Retrieve your metrics' and logs' push endpoints in the [Data sources tab](https://console.scaleway.com/cockpit/dataSource) of the Scaleway console. -4. [Log in to your Grafana account](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/). -5. Create your [Grafana dashboard](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data. +4. [Log in to your Grafana account](/cockpit/how-to/access-grafana-and-managed-dashboards/). +5. Create your [Grafana dashboard](/cockpit/how-to/access-grafana-and-managed-dashboards/) and start monitoring your data. --- @@ -51,11 +51,11 @@ You can push logs with any Loki compatible agent such as the [Promtail](https:// ## Sending Python logs to Cockpit - You need custom logs in the `fr-par` region to follow the procedure below. Find out [how to create custom logs](/observability/cockpit/how-to/create-external-data-sources/). + You need custom logs in the `fr-par` region to follow the procedure below. Find out [how to create custom logs](/cockpit/how-to/create-external-data-sources/). 1. Open a terminal and run `pip install python-logging-loki` or `pip3 install python-logging-loki` if you are using Python 3, to install the [logging_loki](https://pypi.org/project/python-logging-loki/) package to send your Python logs. - 2. [Create a token](/observability/cockpit/how-to/create-token/) with the **Push** permission for logs. + 2. [Create a token](/cockpit/how-to/create-token/) with the **Push** permission for logs. 3. Create a `python_logs.py` Python file and paste the following code snippet into it. Make sure that you replace `$SCW_SECRET_KEY` with your API secret key and `$COCKPIT_TOKEN_SECRET_KEY` with your Cockpit token's secret key. ``` @@ -94,7 +94,7 @@ You can push logs with any Loki compatible agent such as the [Promtail](https:// ### Creating a Grafana dashboard and visualizing your Python logs - 1. [Log into Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). + 1. [Log into Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) using your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 2. Click **Toggle menu**, then click **Dashboards**. 3. Click **New** in the top right corner of your screen, then **Import**. 4. Upload the JSON file of the [Grafana Log Viewer dashboard for Loki](https://grafana.com/grafana/dashboards/13639-logs-app/) or enter `13639` in the **Import via grafana.com** field. @@ -117,7 +117,7 @@ You can push logs with any Loki compatible agent such as the [Promtail](https:// - Read our more in depth-documentation on [how to configure the Grafana alloy agent](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/) to push your Scaleway metrics, and visualize them in a Grafana dashboard. + Read our more in depth-documentation on [how to configure the Grafana alloy agent](/cockpit/how-to/send-metrics-with-grafana-alloy/) to push your Scaleway metrics, and visualize them in a Grafana dashboard. diff --git a/observability/cockpit/how-to/send-metrics-with-grafana-alloy.mdx b/observability/cockpit/how-to/send-metrics-with-grafana-alloy.mdx index ec216fbddd..054db0fbb3 100644 --- a/observability/cockpit/how-to/send-metrics-with-grafana-alloy.mdx +++ b/observability/cockpit/how-to/send-metrics-with-grafana-alloy.mdx @@ -22,12 +22,12 @@ For the sake of this documentation, we are using Grafana Alloy on macOS. Refer t - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Retrieved your Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/) + - [Retrieved your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) - [Installed Grafana Alloy](https://grafana.com/docs/alloy/latest/get-started/install/) - - [Created a custom data source of the metrics type](/observability/cockpit/how-to/create-external-data-sources/) - - A [token](/observability/cockpit/how-to/create-token/) with push permissions for metrics in the **same region as your metrics** + - [Created a custom data source of the metrics type](/cockpit/how-to/create-external-data-sources/) + - A [token](/cockpit/how-to/create-token/) with push permissions for metrics in the **same region as your metrics** - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption and a high bill at the end of the month. @@ -93,7 +93,7 @@ For the sake of this documentation, we are using Grafana Alloy on macOS. Refer t 1. Click **Cockpit** in the Observability section of the [console](https://console.scaleway.com/) side menu. The **Cockpit** overview page displays. 2. Click **Open dashboards** to open your managed dashboards in Grafana. You are redirected to the Grafana website. -3. Enter your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/). +3. Enter your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/). 4. Click **Log in**. The Grafana overview page displays. 5. Click the **Toggle menu** icon in the top left corner of your screen. 6. Click **Dashboards**, then click **New** in the top right corner of your screen. A drop-down displays. diff --git a/observability/cockpit/index.mdx b/observability/cockpit/index.mdx index c9d673b66b..47f7b6f743 100644 --- a/observability/cockpit/index.mdx +++ b/observability/cockpit/index.mdx @@ -8,7 +8,7 @@ meta: productName="Cockpit" productLogo="cockpit" description="Cockpit offers powerful application and infrastructure monitoring, giving you insights and context. Visualize metrics, logs, and traces in your Grafana dashboards." - url="/observability/cockpit/quickstart/" + url="/cockpit/quickstart/" label="Cockpit Quickstart" /> @@ -21,28 +21,28 @@ meta: icon="rocket" description="Discover how to retrieve Grafana credentials and create a token in a few steps to start monitoring your data with Cockpit." label="View Quickstart" - url="/observability/cockpit/quickstart/" + url="/cockpit/quickstart/" /> @@ -58,7 +58,7 @@ meta: /> - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Having the default configuration on your agents might lead to more of your resources' metrics being sent, a high consumption, and a high bill at the end of the month. @@ -37,7 +37,7 @@ In this documentation, we show you how to retrieve your Grafana credentials to a 2. Click the **Grafana users** tab. 3. Click **Add user**. 4. Enter a username. -5. Select a [role](/observability/cockpit/concepts/#grafana-users) for the user. +5. Select a [role](/cockpit/concepts/#grafana-users) for the user. 6. Click **Add a user**. Your automatically generated password to log in to Grafana displays. Make sure to copy and save it before closing the pop-up. ## How to create a token to push your metrics and logs @@ -47,7 +47,7 @@ In this documentation, we show you how to retrieve your Grafana credentials to a 3. Click **Create token**. A pop-up displays prompting you to create a token. 4. Choose the region to create the token in. - Make sure that you create your token in the same region as the [data sources](/observability/cockpit/concepts/#data-sources) you want to use it for. + Make sure that you create your token in the same region as the [data sources](/cockpit/concepts/#data-sources) you want to use it for. 5. Choose a name for your token or use the already-generated name. 6. Select the permissions you wish to apply to your token. @@ -64,7 +64,7 @@ In this documentation, we show you how to retrieve your Grafana credentials to a **Going further**

- If you have not set up an agent yet, check out our [documentation](/observability/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure Grafana Alloy, push your metrics, and visualize them in Grafana. + If you have not set up an agent yet, check out our [documentation](/cockpit/how-to/send-metrics-with-grafana-alloy/) to find out how to configure Grafana Alloy, push your metrics, and visualize them in Grafana. You must have created resources to monitor to push your data to Cockpit. diff --git a/observability/cockpit/reference-content/cockpit-limitations.mdx b/observability/cockpit/reference-content/cockpit-limitations.mdx index 6a97af69e3..758f14752b 100644 --- a/observability/cockpit/reference-content/cockpit-limitations.mdx +++ b/observability/cockpit/reference-content/cockpit-limitations.mdx @@ -19,13 +19,13 @@ This page provides information about the capabilities and limits of Scaleway's O ## Retention period of your data -Scaleway offers several retention periods, depending on your [data types](/observability/cockpit/concepts/#data-types). +Scaleway offers several retention periods, depending on your [data types](/cockpit/concepts/#data-types). Find out more information about how Cockpit is billed depending on your data types in the [FAQ](/faq/cockpit/#how-am-i-billed-for-using-cockpit-with-my-scaleway-data). ## Limits for Loki -The following table provides information about [Loki](/observability/cockpit/concepts/#loki)'s limits. +The following table provides information about [Loki](/cockpit/concepts/#loki)'s limits. | Parameter | Default value | Value for the user | Description | |------------------------------------|---------------|--------------------|--------------------------------------------------------------------------------------| @@ -46,7 +46,7 @@ The following table provides information about [Loki](/observability/cockpit/con ## Limits for Mimir -The following table provides information about [Mimir](/observability/cockpit/concepts/#mimir)'s limits. +The following table provides information about [Mimir](/cockpit/concepts/#mimir)'s limits. | Parameter | Default value | Value for the user | Description | |------------------------------------|---------------|--------------------|-----------------------------------------------------------------------------------| diff --git a/observability/cockpit/reference-content/understanding-cockpit-usage.mdx b/observability/cockpit/reference-content/understanding-cockpit-usage.mdx index baa89fbc5f..cb42ed10c9 100644 --- a/observability/cockpit/reference-content/understanding-cockpit-usage.mdx +++ b/observability/cockpit/reference-content/understanding-cockpit-usage.mdx @@ -14,7 +14,7 @@ categories: --- -Cockpit allows you to [push custom metrics](/observability/cockpit/how-to/send-metrics-logs-to-cockpit/) for various resources. The pricing of our service is based on the number of samples that are ingested per month. +Cockpit allows you to [push custom metrics](/cockpit/how-to/send-metrics-logs-to-cockpit/) for various resources. The pricing of our service is based on the number of samples that are ingested per month. Using Cockpit costs €0.15 per million samples ingested per month. ## Importance of controlling the rate diff --git a/observability/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx b/observability/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx index f355e03af3..631cccca7f 100644 --- a/observability/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx +++ b/observability/cockpit/troubleshooting/pusher-does-not-support-custom-http-headers.mdx @@ -15,7 +15,7 @@ categories: - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization If your pusher does not support the `X-Token` header, there are other ways to pass it: diff --git a/observability/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx b/observability/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx index 7ca3c515b4..2e61cd09cc 100644 --- a/observability/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx +++ b/observability/cockpit/troubleshooting/resetting-grafana-password-via-the-api.mdx @@ -17,7 +17,7 @@ This page shows you how to reset your Grafana user's password through the Scalew - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Created](/identity-and-access-management/iam/how-to/create-api-keys/) an API key with sufficient [IAM permissions](/identity-and-access-management/iam/reference-content/permission-sets/) to perform the actions described on this page + - [Created](/iam/how-to/create-api-keys/) an API key with sufficient [IAM permissions](/iam/reference-content/permission-sets/) to perform the actions described on this page - [Installed](https://curl.se/download.html) curl diff --git a/package.json b/package.json index 10175040db..5d446ab3ca 100644 --- a/package.json +++ b/package.json @@ -31,6 +31,7 @@ "scripts": { "prepare": "husky install", "check-slugs": "bin/list-invalid-slugs", + "clean-categories": "bin/clean-categories", "format": "yarn run prettier --config .prettierrc --write \"**/*.json\"" } } diff --git a/partners/partner-space/how-to/edit-client-information.mdx b/partners/partner-space/how-to/edit-client-information.mdx index 74cf2fb9c3..1d4e7b9c61 100644 --- a/partners/partner-space/how-to/edit-client-information.mdx +++ b/partners/partner-space/how-to/edit-client-information.mdx @@ -17,7 +17,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) - Scaleway Partner status -- [Added a client](/partners/partner-space/how-to/add-client/) +- [Added a client](/partner-space/how-to/add-client/) 1. Go to the Partner Space. A list of your clients displays. 2. Locate the row corresponding to the client for whom you want to edit information. diff --git a/partners/partner-space/how-to/grant-access-to-partner-space.mdx b/partners/partner-space/how-to/grant-access-to-partner-space.mdx index f3686c3911..c66b78ad8f 100644 --- a/partners/partner-space/how-to/grant-access-to-partner-space.mdx +++ b/partners/partner-space/how-to/grant-access-to-partner-space.mdx @@ -44,13 +44,13 @@ categories: Now that you have created the Reseller policy, you can apply it to users who need access to the Partner Space. 1. Click the **Users** tab. - 2. Locate the user you want to grant access to. If the user is not yet part of the Organization, you will need to [invite them](/identity-and-access-management/iam/how-to/invite-user-to-orga/) first. + 2. Locate the user you want to grant access to. If the user is not yet part of the Organization, you will need to [invite them](/iam/how-to/invite-user-to-orga/) first. 3. Click to the right of the row. The overview of the user’s information displays. 4. Click the **Group & Policies** tab. 5. Click **Add to group**. 6. Select either **Administrator** or **Billing Administrator**, depending on the policy you created. - Refer to the [IAM documentation](/identity-and-access-management/iam/) for more details about user permission and access management. + Refer to the [IAM documentation](/iam/) for more details about user permission and access management. diff --git a/partners/partner-space/how-to/lock-client-organization.mdx b/partners/partner-space/how-to/lock-client-organization.mdx index 36c42b8889..5b0496730c 100644 --- a/partners/partner-space/how-to/lock-client-organization.mdx +++ b/partners/partner-space/how-to/lock-client-organization.mdx @@ -19,7 +19,7 @@ If you are confronted with a client who does not respect Scaleway’s Terms of S - A Scaleway account logged into the [console](https://console.scaleway.com) - Scaleway Partner status -- [Added a client](/partners/partner-space/how-to/add-client/) +- [Added a client](/partner-space/how-to/add-client/) Locking an Organization prevents its owner from ordering or managing resources. diff --git a/partners/partner-space/how-to/unlock-client-organization.mdx b/partners/partner-space/how-to/unlock-client-organization.mdx index 4b3bebc20e..75ed304bad 100644 --- a/partners/partner-space/how-to/unlock-client-organization.mdx +++ b/partners/partner-space/how-to/unlock-client-organization.mdx @@ -17,7 +17,7 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) - Scaleway Partner status -- [Added a client](/partners/partner-space/how-to/add-client/) +- [Added a client](/partner-space/how-to/add-client/) 1. Go to the Partner Space. A list of your clients displays. 2. Locate the row corresponding to the client whose Organization you want to unlock. diff --git a/partners/partner-space/index.mdx b/partners/partner-space/index.mdx index 3a445f84ab..178abc94ea 100644 --- a/partners/partner-space/index.mdx +++ b/partners/partner-space/index.mdx @@ -8,7 +8,7 @@ meta: productName="Partner Space" productLogo="iam" description="As a Scaleway Partner, you benefit from a dedicated interface within the console: the Partner Space. It empowers you to manage your clients efficiently, from creating their Organizations to monitoring their consumption for accurate billing." - url="/partners/partner-space/quickstart/" + url="/partner-space/quickstart/" label="Partner Space Quickstart" /> @@ -20,21 +20,21 @@ meta: icon="rocket" description="Learn how to add your first clients and follow their consumption." label="View Quickstart" - url="/partners/partner-space/quickstart/" + url="/partner-space/quickstart/" /> @@ -43,17 +43,17 @@ meta: diff --git a/serverless/containers/api-cli/deploy-container-api.mdx b/serverless/containers/api-cli/deploy-container-api.mdx index eda0fc0833..2b47bc5721 100644 --- a/serverless/containers/api-cli/deploy-container-api.mdx +++ b/serverless/containers/api-cli/deploy-container-api.mdx @@ -20,8 +20,8 @@ Refer to the [Scaleway Developers website](https://www.scaleway.com/en/developer - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [curl](https://curl.se/download.html) - Made your first [request](https://www.scaleway.com/en/developers/api/#quickstart:-first-request) using the Scaleway API diff --git a/serverless/containers/api-cli/deploy-container-cli.mdx b/serverless/containers/api-cli/deploy-container-cli.mdx index c4995feba3..91d7ac9457 100644 --- a/serverless/containers/api-cli/deploy-container-cli.mdx +++ b/serverless/containers/api-cli/deploy-container-cli.mdx @@ -20,10 +20,10 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Installed and configured the Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- [Installed and configured the Scaleway CLI](/scaleway-cli/quickstart/) ## Creating a container diff --git a/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry.mdx b/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry.mdx index e998a37b00..794ac45212 100644 --- a/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry.mdx +++ b/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry.mdx @@ -17,20 +17,20 @@ Serverless Containers rely on images that can be stored in the Scaleway Containe -This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/concepts/#container-registry). +This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/container-registry/concepts/#container-registry). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a [Container Registry namespace](/container-registry/how-to/create-namespace/) ## Import images using Docker 1. Install the Docker Engine by following the [official documentation](https://docs.docker.com/engine/install/). -2. Login to your Scaleway Container Registry namespace with the Docker CLI by following [this procedure](/containers/container-registry/how-to/connect-docker-cli/). +2. Login to your Scaleway Container Registry namespace with the Docker CLI by following [this procedure](/container-registry/how-to/connect-docker-cli/). 3. Run the command below to pull, tag, then push the public image to your Scaleway Registry namespace. Make sure to replace the namespace name, and the image name by the appropriate values: ``` diff --git a/serverless/containers/concepts.mdx b/serverless/containers/concepts.mdx index 68c16daa77..6dceafd001 100644 --- a/serverless/containers/concepts.mdx +++ b/serverless/containers/concepts.mdx @@ -27,7 +27,7 @@ Startup process steps are: Concurrency defines the number of simultaneous requests a single instance of your container can handle at the same time. Once the number of incoming requests exceeds this value, your container scales according to your parameters. -Refer to the [dedicated documentation](/serverless/containers/reference-content/containers-concurrency/) for more information on container concurrency. +Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-concurrency/) for more information on container concurrency. ## Container @@ -39,17 +39,17 @@ A container image is a file that includes all the requirements and instructions ## Container Registry -Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details. +Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details. ## CRON trigger A CRON trigger is a mechanism used to automatically invoke a Serverless Container at a specific time on a recurring schedule. -It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information. +It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless-containers/reference-content/cron-schedules/) for more information. ## Custom domain -By default, a generated endpoint is assigned to your Serverless resource. Custom domains allows you to use your own domain - see our [custom domain documentation](/serverless/containers/how-to/add-a-custom-domain-to-a-container) for full details. +By default, a generated endpoint is assigned to your Serverless resource. Custom domains allows you to use your own domain - see our [custom domain documentation](/serverless-containers/how-to/add-a-custom-domain-to-a-container) for full details. ## Deployment @@ -61,7 +61,7 @@ An endpoint is the URL generated to access your resource. It can be customized w ## Environment variables -Environment variables are key/value pairs injected in your container. They are useful to share information such as configurations with your container. Some names are reserved. [See details about reserved names](/serverless/containers/reference-content/containers-limitations/#configuration-restrictions). +Environment variables are key/value pairs injected in your container. They are useful to share information such as configurations with your container. Some names are reserved. [See details about reserved names](/serverless-containers/reference-content/containers-limitations/#configuration-restrictions). ## Ephemeral storage @@ -89,7 +89,7 @@ A Serverless Container instance handles incoming requests based on factors like ## JWT Token -JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your private container. [Find out how to secure a container](/serverless/containers/how-to/secure-a-container/#restrict-access-to-your-containers). +JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your private container. [Find out how to secure a container](/serverless-containers/how-to/secure-a-container/#restrict-access-to-your-containers). ## Load balancing @@ -97,7 +97,7 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik ## Logging -Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources: see [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/). +Serverless Containers offers a built-in logging system based on Cockpit to track the activity of your resources: see [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/). ## Max scale @@ -105,7 +105,7 @@ This parameter sets the maximum number of container instances. You should adjust ## Metrics -Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Containers](/serverless/containers/how-to/monitor-container/). +Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Containers](/serverless-containers/how-to/monitor-container/). ## Min scale @@ -117,13 +117,13 @@ A [vCPU](#vcpu) (Virtual Central Processing Unit) is equivalent to 1000 mvCPU. ## Namespace -A namespace is a project that allows you to [group your containers](/serverless/containers/how-to/create-manage-delete-containers-namespace/). +A namespace is a project that allows you to [group your containers](/serverless-containers/how-to/create-manage-delete-containers-namespace/). Containers in the same namespace can share environment variables, secrets and access tokens, defined at the namespace level. ## NATS trigger -A NATS trigger is a mechanism that connects a container to a [NATS](/serverless/messaging/concepts/#nats) subject and invokes the container automatically whenever a message is published to the subject. +A NATS trigger is a mechanism that connects a container to a [NATS](/messaging/concepts/#nats) subject and invokes the container automatically whenever a message is published to the subject. For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated container with the message as the input parameter. The container can then process the message and perform any required actions, such as updating a database or sending a notification. @@ -188,11 +188,11 @@ These functions automatically scale based on demand and are designed to be light ## Serverless Job -Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless/containers/reference-content/difference-jobs-functions-containers) for more information. +Serverless Jobs are similar to Serverless Containers but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless-containers/reference-content/difference-jobs-functions-containers) for more information. ## Queue trigger -A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue. +A queue trigger is a mechanism that connects a container to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the container automatically whenever a message is added to the queue. For each message that is sent to a queue, the trigger reads the message and invokes the associated container with the message as the input parameter. The container can then process the message and perform any required actions, such as updating a database or sending a notification. @@ -214,14 +214,14 @@ Refers to a system or application that does not maintain any persistent state be This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others. -To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/). +To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). ## Status A Serverless Container can have the following statuses: * **Ready**: your Serverless Container is operational to serve requests. * **Pending**: your resource is under deployment. -* **Error**: something went wrong during the deployment process. [Check our troubleshooting documentation](/serverless/containers/troubleshooting/cannot-deploy-image) to solve the issue. +* **Error**: something went wrong during the deployment process. [Check our troubleshooting documentation](/serverless-containers/troubleshooting/cannot-deploy-image) to solve the issue. ## Terraform diff --git a/serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx b/serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx index 722ce7bf64..5fbbecf4e0 100644 --- a/serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx +++ b/serverless/containers/how-to/add-a-custom-domain-to-a-container.mdx @@ -19,11 +19,11 @@ Each container comes with an automatically generated domain, on which it is avai - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A running [Serverless Container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A running [Serverless Container](/serverless-containers/how-to/deploy-container/) - Registered a domain name with the provider of your choice and have access to the domain name's DNS zone file -1. On your domain provider's platform (for example, [Scaleway's domains](/network/domains-and-dns/how-to/manage-dns-records/)), add a CNAME record pointing to your container default URL in the domain's DNS zone file. +1. On your domain provider's platform (for example, [Scaleway's domains](/domains-and-dns/how-to/manage-dns-records/)), add a CNAME record pointing to your container default URL in the domain's DNS zone file. diff --git a/serverless/containers/how-to/add-trigger-to-a-container.mdx b/serverless/containers/how-to/add-trigger-to-a-container.mdx index b8256323e6..6dc0f9abf0 100644 --- a/serverless/containers/how-to/add-trigger-to-a-container.mdx +++ b/serverless/containers/how-to/add-trigger-to-a-container.mdx @@ -23,11 +23,11 @@ A trigger can be an HTTP request, a message from a queue or stream, a CRON sched - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) -- Deployed a container from [Scaleway Container Registry](/serverless/containers/how-to/deploy-container/) or an [external registry](/serverless/containers/how-to/deploy-container/) -- [Created credentials](/serverless/messaging/how-to/create-credentials/) for Scaleway Queues -- [Created a queue](/serverless/messaging/how-to/create-manage-queues/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) +- Deployed a container from [Scaleway Container Registry](/serverless-containers/how-to/deploy-container/) or an [external registry](/serverless-containers/how-to/deploy-container/) +- [Created credentials](/messaging/how-to/create-credentials/) for Scaleway Queues +- [Created a queue](/messaging/how-to/create-manage-queues/) You can create triggers on private containers, but to update the privacy of a container from **public** to **private**, you must recreate the existing **Scaleway Queues** and **Scaleway NATS** triggers after the privacy change. We are actively working to make this operation as seamless as possible. @@ -39,11 +39,11 @@ You can create triggers on private containers, but to update the privacy of a co ## Queue triggers -[Queue triggers](/serverless/containers/concepts/#queue-trigger) allow you to automatically invoke a container using events stored in a [Scaleway queue](/serverless/messaging/concepts/#queues). +[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a container using events stored in a [Scaleway queue](/messaging/concepts/#queues). Only queues created with the Scaleway Queues product are compatible with Serverless Containers. -The configuration of the queue retention can affect the behavior of the trigger. Refer to the [Considerations to configure event retention for queue trigger inputs](/serverless/containers/reference-content/configure-trigger-inputs/) page for more information. +The configuration of the queue retention can affect the behavior of the trigger. Refer to the [Considerations to configure event retention for queue trigger inputs](/serverless-containers/reference-content/configure-trigger-inputs/) page for more information. 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. 2. Click the relevant containers namespace. @@ -61,9 +61,9 @@ When a message is pushed to the selected queues, the container will be triggered ## NATS triggers -[NATS triggers](/serverless/containers/concepts/#nats-trigger) allow you to automatically invoke a container using messages sent in a [NATS](/serverless/messaging/concepts/#nats) subject. +[NATS triggers](/serverless-containers/concepts/#nats-trigger) allow you to automatically invoke a container using messages sent in a [NATS](/messaging/concepts/#nats) subject. -[Scaleway NATS subjects](/serverless/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Containers. +[Scaleway NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Containers. 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. 2. Click the relevant containers namespace. @@ -79,7 +79,7 @@ When a message is pushed to the selected queues, the container will be triggered ## CRON triggers -[CRON triggers](/serverless/containers/concepts/#cron-trigger) allow you to invoke your containers based on a recurring schedule. The CRON triggers for Serverless Containers use the **UTC** time zone. +[CRON triggers](/serverless-containers/concepts/#cron-trigger) allow you to invoke your containers based on a recurring schedule. The CRON triggers for Serverless Containers use the **UTC** time zone. 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. 2. Click the relevant containers namespace. @@ -92,5 +92,5 @@ When a message is pushed to the selected queues, the container will be triggered The container will be invoked at the indicated time. - Refer to the [cron schedules reference](/serverless/containers/reference-content/cron-schedules/) for more information. + Refer to the [cron schedules reference](/serverless-containers/reference-content/cron-schedules/) for more information. diff --git a/serverless/containers/how-to/create-auth-token-from-console.mdx b/serverless/containers/how-to/create-auth-token-from-console.mdx index d02197e070..1c381fe8dc 100644 --- a/serverless/containers/how-to/create-auth-token-from-console.mdx +++ b/serverless/containers/how-to/create-auth-token-from-console.mdx @@ -19,9 +19,9 @@ This page shows you how to create and manage an authentication token from the Sc - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) -- [Deployed a container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) +- [Deployed a container](/serverless-containers/how-to/deploy-container/) ## Creating authentication tokens from the Scaleway console diff --git a/serverless/containers/how-to/create-manage-delete-containers-namespace.mdx b/serverless/containers/how-to/create-manage-delete-containers-namespace.mdx index af002ede13..e2bdc15adc 100644 --- a/serverless/containers/how-to/create-manage-delete-containers-namespace.mdx +++ b/serverless/containers/how-to/create-manage-delete-containers-namespace.mdx @@ -14,12 +14,12 @@ categories: - containers --- -This page shows you how to create and manage a Serverless Containers namespace. [Namespaces](/serverless/containers/concepts/#namespace) allow you to group your containers and share environment variables between them. +This page shows you how to create and manage a Serverless Containers namespace. [Namespaces](/serverless-containers/concepts/#namespace) allow you to group your containers and share environment variables between them. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Creating a Serverless Containers namespace @@ -31,7 +31,7 @@ This page shows you how to create and manage a Serverless Containers namespace. - Enter any **environment variables** required for your namespace. Environment variables configured in a namespace will be available in all containers/apps within the same namespace. For each environment variable, click **+Add new variable** and enter the key / value pair. - Set secret environment variables (optional). **Secrets** are environment variables that are injected into your container and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. - Verify the **estimated cost**. -4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless/containers/how-to/deploy-container/) next. +4. Click **Create namespace only** to finish, or click **Create namespace and add container** if you want to [deploy a container](/serverless-containers/how-to/deploy-container/) next. ## Managing a Serverless Containers namespace diff --git a/serverless/containers/how-to/delete-a-container.mdx b/serverless/containers/how-to/delete-a-container.mdx index 9ecf7bf051..7489567403 100644 --- a/serverless/containers/how-to/delete-a-container.mdx +++ b/serverless/containers/how-to/delete-a-container.mdx @@ -23,8 +23,8 @@ This page shows you how to delete a Scaleway container. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a container](/serverless-containers/how-to/deploy-container/) 1. Click **Containers** in the **Serverless** section of the side menu. The list of your containers displays. 2. Click the relevant Containers namespace. diff --git a/serverless/containers/how-to/deploy-container.mdx b/serverless/containers/how-to/deploy-container.mdx index b801ed6a89..0deb580d54 100644 --- a/serverless/containers/how-to/deploy-container.mdx +++ b/serverless/containers/how-to/deploy-container.mdx @@ -16,14 +16,14 @@ categories: This page shows you how to deploy Serverless Containers using the [Scaleway console](https://console.scaleway.com/). -You can deploy a container from the [Scaleway Container Registry](/containers/container-registry/quickstart/), or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. +You can deploy a container from the [Scaleway Container Registry](/container-registry/quickstart/), or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) -- [Created a Container Registry namespace](/containers/container-registry/how-to/create-namespace/) and [pushed a container image](/containers/container-registry/how-to/push-images/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) +- [Created a Container Registry namespace](/container-registry/how-to/create-namespace/) and [pushed a container image](/container-registry/how-to/push-images/) to it ## Deploy from the Scaleway Container Registry @@ -32,28 +32,28 @@ You can deploy a container from the [Scaleway Container Registry](/containers/co 3. Click **Deploy container**. The container creation wizard displays. 4. Complete the following steps in the wizard: - Select the **Scaleway** Container Registry. - - Choose an [image](/serverless/containers/concepts/#container-image) from your Container Registry. + - Choose an [image](/serverless-containers/concepts/#container-image) from your Container Registry. - Select the required Container Registry namespace from the drop-down list, and then select the container and tag. - - Choose the [port](/serverless/containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable. + - Choose the [port](/serverless-containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable. - Choose a **name** for your container and, optionally, a **description**. The name must only contain alphanumeric characters and dashes. - Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container. Available memory depends on allocated vCPU, and the maximum ephemeral storage value depends on allocated memory. - - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here. - - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair. - - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation. + - Set your [scaling](/serverless-containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here. + - Click **Advanced options** to define any [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair. + - Add [secrets](/serverless-containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation. Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns. - - Set the desired [privacy policy](/serverless/containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**). - - Set a custom [timeout](/serverless/containers/concepts/#timeout) for your container. + - Set the desired [privacy policy](/serverless-containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**). + - Set a custom [timeout](/serverless-containers/concepts/#timeout) for your container. - Verify the **estimated cost**. 5. Click **Deploy container** to finish. ## Deploy from an external container registry -Scaleway Serverless Containers allows you to deploy containers from external public [container registries](/containers/container-registry/concepts/#registry), such as Docker Hub, AWS container registries, GitLab container registry, etc. +Scaleway Serverless Containers allows you to deploy containers from external public [container registries](/container-registry/concepts/#registry), such as Docker Hub, AWS container registries, GitLab container registry, etc. Private external container registries are currently not supported. @@ -69,19 +69,19 @@ Private external container registries are currently not supported. - Enter the public container **image URL** provided by the external registry. For example: - `nginx:latest` to deploy the latest nginx image from [Docker Hub](https://hub.docker.com/) - `ghcr.io/namespace/image` to deploy an image from [GitHub Container Registry](https://github.com/features/packages) - - Choose the [port](/serverless/containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable. + - Choose the [port](/serverless-containers/concepts/#port) your container is listening on. We recommend configuring your container to listen on the `$PORT` environment variable. - Choose a **name** for your container and, optionally, a **description**. The name must only contain alphanumeric characters and dashes. - Choose the **resources** to be allocated to your container at runtime. These define the performance characteristics of your container. Available memory depends on allocated vCPU, and maximum ephemeral storage value depends on allocated memory. - - Set your [scaling](/serverless/containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here. - - Click **Advanced options** to define any [environment variables](/serverless/containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair. - - Add [secrets](/serverless/containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation. + - Set your [scaling](/serverless-containers/concepts/#scaling) preferences, or leave them at default values. The Scaleway platform automatically scales the number of available instances of your container to match the incoming load, depending on the settings you define here. + - Click **Advanced options** to define any [environment variables](/serverless-containers/concepts/#environment-variables) you want to inject into your container. For each environment variable, click **+Add variable** and enter the key/value pair. + - Add [secrets](/serverless-containers/concepts/#secrets) for your container. Secrets are environment variables that are injected into your container, but the values are not retained or displayed by Scaleway after initial validation. Encode your environment variables and secrets to `base64` if they are too large, and contain carriage returns. - - Set the desired [privacy policy](/serverless/containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**). - - Set a custom [timeout](/serverless/containers/concepts/#timeout) for your container. + - Set the desired [privacy policy](/serverless-containers/concepts/#privacy-policy) for your container. This defines whether container invocation may be done anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication) (**private**). + - Set a custom [timeout](/serverless-containers/concepts/#timeout) for your container. - Verify the **estimated cost**. 5. Click **Deploy container** to finish. diff --git a/serverless/containers/how-to/manage-a-container.mdx b/serverless/containers/how-to/manage-a-container.mdx index 15df2d4628..3610373142 100644 --- a/serverless/containers/how-to/manage-a-container.mdx +++ b/serverless/containers/how-to/manage-a-container.mdx @@ -14,13 +14,13 @@ categories: - containers --- -This page shows you how to manage a container, should you need to verify or edit its deployment parameters after creation. You can deploy a container from the [Scaleway Container Registry](/containers/container-registry/quickstart/) or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. +This page shows you how to manage a container, should you need to verify or edit its deployment parameters after creation. You can deploy a container from the [Scaleway Container Registry](/container-registry/quickstart/) or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Deployed a container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Deployed a container](/serverless-containers/how-to/deploy-container/) ## How to manage a container deployment diff --git a/serverless/containers/how-to/modify-container-privacy.mdx b/serverless/containers/how-to/modify-container-privacy.mdx index d1dbde2690..567b88b16e 100644 --- a/serverless/containers/how-to/modify-container-privacy.mdx +++ b/serverless/containers/how-to/modify-container-privacy.mdx @@ -14,13 +14,13 @@ categories: - containers --- -This page shows you how to modify a container's [privacy policy](/serverless/containers/concepts/#privacy-policy), if you wish to do so after creation. +This page shows you how to modify a container's [privacy policy](/serverless-containers/concepts/#privacy-policy), if you wish to do so after creation. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Deployed a container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Deployed a container](/serverless-containers/how-to/deploy-container/) Setting a container to private will not take care of the actual authentication, as token validation is done at runtime. For further information, refer to the [developers documentation](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication). diff --git a/serverless/containers/how-to/monitor-container.mdx b/serverless/containers/how-to/monitor-container.mdx index 1a57f0ae74..c042dee3d1 100644 --- a/serverless/containers/how-to/monitor-container.mdx +++ b/serverless/containers/how-to/monitor-container.mdx @@ -14,17 +14,17 @@ categories: - containers --- -Scaleway Serverless Containers is fully integrated into [Cockpit](/observability/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Containers. +Scaleway Serverless Containers is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Containers. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless Container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless Container](/serverless-containers/how-to/deploy-container/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to access the Grafana dashboard @@ -32,7 +32,7 @@ To view your Serverless Containers logs, use the Grafana dashboard which is acce - First you must create a user and their associated credentials (a username and password) for Grafana. - Then use these credentials to access the Grafana dashboard for all your Scaleway products, via the Scaleway console. -1. Create a Grafana user and retrieve their username and password by following [this procedure](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. Create a Grafana user and retrieve their username and password by following [this procedure](/cockpit/how-to/retrieve-grafana-credentials/). 2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. diff --git a/serverless/containers/how-to/secure-a-container.mdx b/serverless/containers/how-to/secure-a-container.mdx index 9ef4aea3e3..1c55ce587d 100644 --- a/serverless/containers/how-to/secure-a-container.mdx +++ b/serverless/containers/how-to/secure-a-container.mdx @@ -19,10 +19,10 @@ This page explains how to secure your container. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) -- [Deployed a container](/serverless/containers/how-to/deploy-container/) -- Created an [authentication token](/serverless/containers/how-to/create-auth-token-from-console/) for your container +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) +- [Deployed a container](/serverless-containers/how-to/deploy-container/) +- Created an [authentication token](/serverless-containers/how-to/create-auth-token-from-console/) for your container ## Use secrets to store access keys and sensitive information @@ -74,7 +74,7 @@ Unauthenticated calls will be rejected, and your container will not be triggered 3. Click the name of the container for which you want to define secrets. 4. Click the **Security** tab. 5. Set the **Privacy Policy** of the container to **Private**. -6. If required, [create an access token](/serverless/containers/how-to/create-auth-token-from-console/) for your container. +6. If required, [create an access token](/serverless-containers/how-to/create-auth-token-from-console/) for your container. Your container is now private, and requires an `X-Auth-Token` header to be called: @@ -92,7 +92,7 @@ Your container is now private, and requires an `X-Auth-Token` header to be calle curl -H "X-Auth-Token: " ``` -Refer to the [How to create an authentication token](/serverless/containers/how-to/create-auth-token-from-console/) documentation for more information. +Refer to the [How to create an authentication token](/serverless-containers/how-to/create-auth-token-from-console/) documentation for more information. ## Redirect HTTP to HTTPS @@ -116,7 +116,7 @@ Refer to our [dedicated repository](https://github.com/scaleway/serverless-scale ## Set up alerts in Observability Cockpit (upcoming feature) -Using Scaleway [Observability Cockpit](/observability/cockpit/quickstart/), a managed Grafana solution to which all your containers are connected, you can: +Using Scaleway [Observability Cockpit](/cockpit/quickstart/), a managed Grafana solution to which all your containers are connected, you can: * Monitor your containers using the default dashboard or create custom ones. * Set up notifications to be alerted in case of unexpected behavior. diff --git a/serverless/containers/how-to/test-a-container.mdx b/serverless/containers/how-to/test-a-container.mdx index 97dc2bbdf2..9a1136f7de 100644 --- a/serverless/containers/how-to/test-a-container.mdx +++ b/serverless/containers/how-to/test-a-container.mdx @@ -16,14 +16,14 @@ categories: This page shows you how to execute Serverless Containers from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a container allows you to run your code using a selection of methods to make sure it behaves as expected. -Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless/functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function. +Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a container](/serverless/containers/how-to/deploy-container/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a container](/serverless-containers/how-to/deploy-container/) 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. @@ -44,5 +44,5 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons The **Output** section displays the response from your container and the status code. -If you encounter a message error while testing your container, refer to the [dedicated troubleshooting](/serverless/containers/troubleshooting/tests-fail-on-container/) for more information. +If you encounter a message error while testing your container, refer to the [dedicated troubleshooting](/serverless-containers/troubleshooting/tests-fail-on-container/) for more information. \ No newline at end of file diff --git a/serverless/containers/index.mdx b/serverless/containers/index.mdx index ed4d7e8d5d..e9f78caff9 100644 --- a/serverless/containers/index.mdx +++ b/serverless/containers/index.mdx @@ -8,7 +8,7 @@ meta: productName="Serverless Containers" productLogo="containers" description="Scaleway Serverless Containers allows you to deploy containerized stateless web applications in the cloud to run short-lived, event-driven tasks." - url="/serverless/containers/quickstart" + url="/serverless-containers/quickstart" label="Serverless Containers Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create and deploy a Serverless Container in a few steps." label="View Quickstart" - url="/serverless/containers/quickstart/" + url="/serverless-containers/quickstart/" /> diff --git a/serverless/containers/quickstart.mdx b/serverless/containers/quickstart.mdx index 6c7e42ad77..2a23a967bb 100644 --- a/serverless/containers/quickstart.mdx +++ b/serverless/containers/quickstart.mdx @@ -16,14 +16,14 @@ categories: Scaleway Serverless Containers provides you with containerized stateless web applications deployed in the cloud. They are designed for short-lived, event-driven tasks. -Containers rely on the HTTP protocol, and must therefore include a web server to work properly. Refer to the [differences between Containers, Jobs, and Functions](/serverless/containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. +Containers rely on the HTTP protocol, and must therefore include a web server to work properly. Refer to the [differences between Containers, Jobs, and Functions](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. This page explains how to deploy a basic NGINX image in a Serverless Container using the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to deploy a Serverless Container @@ -34,7 +34,7 @@ You can deploy a container from the Scaleway Container Registry or any other pub If you have no existing Serverless Containers resources in your current Project, the creation process will guide you through the creation of a namespace, and then a container. - Make sure that you have [created a Container Registry namespace](/containers/container-registry/how-to/create-namespace/) and [pushed the latest NGINX Docker image](/containers/container-registry/how-to/push-images/) (or any other image with a web server) to it. + Make sure that you have [created a Container Registry namespace](/container-registry/how-to/create-namespace/) and [pushed the latest NGINX Docker image](/container-registry/how-to/push-images/) (or any other image with a web server) to it. 1. Click **Containers** in the **Serverless** section of the side menu. The containers page displays. @@ -45,7 +45,7 @@ If you have no existing Serverless Containers resources in your current Project, - Choose a **region**, which is the geographical location in which your namespace will be deployed. 4. Click **Create namespace and add container**. The container creation wizard displays. - Refer to the [How to create, manage and delete a Containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) documentation page for more information on the different parameters. + Refer to the [How to create, manage and delete a Containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) documentation page for more information on the different parameters. 5. Complete the following steps in the wizard: - Select the **Scaleway** Container Registry. @@ -58,7 +58,7 @@ If you have no existing Serverless Containers resources in your current Project, - In the **Advanced options**, set the **Container privacy policy** to **public**. - Verify the estimated cost. - Refer to [How to deploy a Container from the Scaleway Registry](/serverless/containers/how-to/deploy-container/) for more information on the different parameters. + Refer to [How to deploy a Container from the Scaleway Registry](/serverless-containers/how-to/deploy-container/) for more information on the different parameters. 6. Click **Deploy container** to finish. @@ -82,7 +82,7 @@ If you have no existing Serverless Containers resources in your current Project, - Choose a **region**, which is the geographical location in which your namespace will be deployed. 4. Click **Create namespace and add container**. The container creation wizard displays. - Refer to the [How to create, manage and delete a Containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) documentation page for more information on the different parameters. + Refer to the [How to create, manage and delete a Containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) documentation page for more information on the different parameters. 5. Complete the following steps in the wizard: - Select the **External** container registry. @@ -95,7 +95,7 @@ If you have no existing Serverless Containers resources in your current Project, - In the **Advanced options**, set the **Container privacy policy** to **public**. - Verify the estimated cost. - Refer to [How to deploy a Container from an external container registry](/serverless/containers/how-to/deploy-container/) for more information on the different parameters. + Refer to [How to deploy a Container from an external container registry](/serverless-containers/how-to/deploy-container/) for more information on the different parameters. 6. Click **Deploy container**. The deployment takes several minutes to complete. Check the **Overview** tab to see the container’s status. @@ -112,6 +112,6 @@ If you have no existing Serverless Containers resources in your current Project, ## Going further -For advanced usage, such as larger projects with dependencies, automation, multiple containers, and more, there are [several ways to deploy containers](/serverless/containers/reference-content/deploy-container/). +For advanced usage, such as larger projects with dependencies, automation, multiple containers, and more, there are [several ways to deploy containers](/serverless-containers/reference-content/deploy-container/). Check out our [GitHub repository](https://github.com/scaleway/serverless-examples) for real-world examples. \ No newline at end of file diff --git a/serverless/containers/reference-content/containers-concurrency.mdx b/serverless/containers/reference-content/containers-concurrency.mdx index 4f9891324e..b5ffed0617 100644 --- a/serverless/containers/reference-content/containers-concurrency.mdx +++ b/serverless/containers/reference-content/containers-concurrency.mdx @@ -18,7 +18,7 @@ categories: Concurrency determines the number of incoming requests a single instance of a container can process before scaling up. Serverless Containers automatically scale according to the number of instances needed to handle the incoming workload. -A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless/containers/concepts/#vcpu), and consequently a higher cost. +A higher number of instances processing requests at the same time implies a greater usage of memory and [vCPU](/serverless-containers/concepts/#vcpu), and consequently a higher cost. ``` Concurrency = 1 @@ -46,7 +46,7 @@ A higher number of instances processing requests at the same time implies a grea ## Concurrency setting -When [deploying a container](/serverless/containers/how-to/deploy-container/), Scaleway Serverless Containers allows you to configure the [concurrency](/serverless/containers/concepts/#concurrency), which is the maximum number of requests a single container instance can handle at the same time. The concurrency setting ranges from 1 to 1,000 simultaneous instances. +When [deploying a container](/serverless-containers/how-to/deploy-container/), Scaleway Serverless Containers allows you to configure the [concurrency](/serverless-containers/concepts/#concurrency), which is the maximum number of requests a single container instance can handle at the same time. The concurrency setting ranges from 1 to 1,000 simultaneous instances. By default, Serverless Containers allow **80 concurrent requests** per container instance. We recommend using the default value, as Serverless Containers are designed to efficiently function with it, but you can lower it to better fit specific requirements. diff --git a/serverless/containers/reference-content/containers-limitations.mdx b/serverless/containers/reference-content/containers-limitations.mdx index b92a99720d..824a5daabb 100644 --- a/serverless/containers/reference-content/containers-limitations.mdx +++ b/serverless/containers/reference-content/containers-limitations.mdx @@ -43,9 +43,9 @@ This section contains usage limits that apply when using Serverless Containers. \** Total container memory is the sum of the memory allocated to all your containers at their maximum Scale. -\*** Use [Serverless Jobs](/serverless/jobs/) for tasks up to 24h. +\*** Use [Serverless Jobs](/serverless-jobs/) for tasks up to 24h. -These limits are enforced as [Organization quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). +These limits are enforced as [Organization quotas](/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). During the execution of the container, if the limits are exceeded, a restart occurs. diff --git a/serverless/containers/reference-content/deploy-container.mdx b/serverless/containers/reference-content/deploy-container.mdx index 8098033a0d..001df56208 100644 --- a/serverless/containers/reference-content/deploy-container.mdx +++ b/serverless/containers/reference-content/deploy-container.mdx @@ -22,7 +22,7 @@ The [Scaleway console](https://console.scaleway.com/) is the easiest way to get The console lets you deploy containers from the Scaleway Container Registry or public repositories. -Refer to the [dedicated documentation](/serverless/containers/how-to/deploy-container/) for more information. +Refer to the [dedicated documentation](/serverless-containers/how-to/deploy-container/) for more information. ## Serverless framework diff --git a/serverless/containers/troubleshooting/cannot-create-namespace.mdx b/serverless/containers/troubleshooting/cannot-create-namespace.mdx index cfd5a7c025..7818a3be2a 100644 --- a/serverless/containers/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/containers/troubleshooting/cannot-create-namespace.mdx @@ -21,9 +21,9 @@ I cannot create a Serverless Containers namespace. This issue can happen for the following reasons: -- You have created too many Serverless Containers namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). +- You have created too many Serverless Containers namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#serverless-containers). -- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). +- You have created too many Registry namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#container-registry). ### Possible solutions diff --git a/serverless/containers/troubleshooting/cannot-deploy-image.mdx b/serverless/containers/troubleshooting/cannot-deploy-image.mdx index 4adb2b3a7e..086a72d5bb 100644 --- a/serverless/containers/troubleshooting/cannot-deploy-image.mdx +++ b/serverless/containers/troubleshooting/cannot-deploy-image.mdx @@ -25,9 +25,9 @@ I am unable to deploy my image using Serverless Containers. - Containers cannot start due to insufficient provisioned resources. Update your container's resources by provisioning more memory and more vCPU. -- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/containers/reference-content/containers-limitations/#architecture) documentation for more information. +- Make sure you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless-containers/reference-content/containers-limitations/#architecture) documentation for more information. -- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless/containers/reference-content/containers-limitations/). +- Make sure your deployment does not exceed the limitations of [Serverless Containers](/serverless-containers/reference-content/containers-limitations/). Run the [`docker inspect`](https://docs.docker.com/engine/reference/commandline/inspect/) command to get detailed information on your image: diff --git a/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx index 3dc80f6cad..20815fe150 100644 --- a/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx +++ b/serverless/containers/troubleshooting/cannot-retrieve-external-image.mdx @@ -23,6 +23,6 @@ Serverless products support external public registries (such as [Docker Hub](htt ## Solution -We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Containers at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). +We recommend using the [Scaleway Container Registry](/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Containers at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). -Refer to the [dedicated documentation](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. +Refer to the [dedicated documentation](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. diff --git a/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx index ac8b4da469..d9d64d141d 100644 --- a/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx +++ b/serverless/containers/troubleshooting/container-stopped-after-redeploy.mdx @@ -19,7 +19,7 @@ My Serverless Container stopped working (up to several hours) after a redeploy. ## Cause -The new deploy failed, and the [fallback mechanism has been triggered](/serverless/containers/reference-content/containers-limitations/#versioning-and-rollback). +The new deploy failed, and the [fallback mechanism has been triggered](/serverless-containers/reference-content/containers-limitations/#versioning-and-rollback). ## Possible solution diff --git a/serverless/containers/troubleshooting/tests-fail-on-container.mdx b/serverless/containers/troubleshooting/tests-fail-on-container.mdx index 701f2c16a0..9444fd7f8e 100644 --- a/serverless/containers/troubleshooting/tests-fail-on-container.mdx +++ b/serverless/containers/troubleshooting/tests-fail-on-container.mdx @@ -25,7 +25,7 @@ Testing **Private** Serverless Containers is not possible using the Scaleway con - Change the visibility of your function to **public**. Public containers can be executed anonymously. -- Make sure you have created an [authentication token](/serverless/containers/how-to/create-auth-token-from-console/) for your private function, then exexute a `curl` request from a terminal, as shown below: +- Make sure you have created an [authentication token](/serverless-containers/how-to/create-auth-token-from-console/) for your private function, then exexute a `curl` request from a terminal, as shown below: ```sh curl -H "X-Auth-Token: " \ ``` \ No newline at end of file diff --git a/serverless/functions/api-cli/deploy-function-api.mdx b/serverless/functions/api-cli/deploy-function-api.mdx index afb16d1ef0..49e930f8b2 100644 --- a/serverless/functions/api-cli/deploy-function-api.mdx +++ b/serverless/functions/api-cli/deploy-function-api.mdx @@ -21,8 +21,8 @@ Refer to the [Scaleway Developers website](https://www.scaleway.com/en/developer - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [curl](https://curl.se/download.html) - [Made your first request](https://www.scaleway.com/en/developers/api/#quickstart:-first-request) using the Scaleway API @@ -65,7 +65,7 @@ Refer to the [Scaleway Developers website](https://www.scaleway.com/en/developer {"id":"ef777a64-1f4e-4d43-8227-26927c7de057", "name":"your-function-name", "namespace_id":"example-fb93-43e3-a036-7be69f1af7a1", "status":"created", "environment_variables":{}, "min_scale":0, "max_scale":5, "runtime":"python310", "memory_limit":256, "cpu_limit":140, "timeout":"300s", "handler":"handler.handle", "error_message":null, "privacy":"public", "description":"", "domain_name":"namespaceg04rnwx-function-example.functions.fnc.fr-par.scw.cloud", "secret_environment_variables":[], "http_option":"enabled", "runtime_message":"", "build_message":null, "region":"fr-par"}% ``` -3. Create a zip file containing your function's code by following [this procedure](/serverless/functions/how-to/package-function-dependencies-in-zip/). +3. Create a zip file containing your function's code by following [this procedure](/serverless-functions/how-to/package-function-dependencies-in-zip/). For testing purposes, you can create a zip archive with a simple Python file named `handler.py` inside, that contains the following code: @@ -81,7 +81,7 @@ Refer to the [Scaleway Developers website](https://www.scaleway.com/en/developer ``` -4. Upload your zip file [using the Scaleway console or the Scaleway API](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file). +4. Upload your zip file [using the Scaleway console or the Scaleway API](/serverless-functions/how-to/package-function-dependencies-in-zip/#how-to-upload-your-zip-file). 5. Run the following command to deploy your function: diff --git a/serverless/functions/api-cli/deploy-function-cli.mdx b/serverless/functions/api-cli/deploy-function-cli.mdx index 1c7e258b0f..712f601dd8 100644 --- a/serverless/functions/api-cli/deploy-function-cli.mdx +++ b/serverless/functions/api-cli/deploy-function-cli.mdx @@ -20,10 +20,10 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Installed and configured the Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- [Installed and configured the Scaleway CLI](/scaleway-cli/quickstart/) ## Creating a function @@ -76,10 +76,10 @@ categories: ``` - Refer to [this page](/serverless/functions/reference-content/functions-lifecycle/#available-runtimes) to see all the available runtimes. + Refer to [this page](/serverless-functions/reference-content/functions-lifecycle/#available-runtimes) to see all the available runtimes. -3. Create a zip file containing your function's code by following [this procedure](/serverless/functions/how-to/package-function-dependencies-in-zip/). +3. Create a zip file containing your function's code by following [this procedure](/serverless-functions/how-to/package-function-dependencies-in-zip/). For testing purposes, you can create a zip archive with a simple Python file named `handler.py` inside, that contains the following code: diff --git a/serverless/functions/concepts.mdx b/serverless/functions/concepts.mdx index 658c27729b..45f0243ca2 100644 --- a/serverless/functions/concepts.mdx +++ b/serverless/functions/concepts.mdx @@ -35,11 +35,11 @@ Container Registry is the place where your images of your Serverless Functions a ## CRON trigger -A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless/functions/reference-content/cron-schedules/) for more information. +A CRON trigger is a mechanism used to automatically invoke a Serverless Function at a specific time on a recurring schedule. It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wiki/Cron), using the `* * * * *` format, and uses the **UTC** time zone. Refer to our [cron schedules reference](/serverless-functions/reference-content/cron-schedules/) for more information. ## Custom domain -By default, a generated endpoint is assigned to your Serverless resource. Custom domains allows you to use your own domain - see our [custom domain documentation](/serverless/functions/how-to/add-a-custom-domain-name-to-a-function/) for full details. +By default, a generated endpoint is assigned to your Serverless resource. Custom domains allows you to use your own domain - see our [custom domain documentation](/serverless-functions/how-to/add-a-custom-domain-name-to-a-function/) for full details. ## Endpoint @@ -47,7 +47,7 @@ An endpoint is the URL generated to access your resource. It can be customized w ## Environment variables -Environment variables are key/value pairs injected in your container. They are useful for sharing information such as configurations with your container. Some names are reserved. [See details on reserved names](/serverless/functions/reference-content/functions-limitations/#configuration-restrictions). +Environment variables are key/value pairs injected in your container. They are useful for sharing information such as configurations with your container. Some names are reserved. [See details on reserved names](/serverless-functions/reference-content/functions-limitations/#configuration-restrictions). ## GB-s @@ -55,11 +55,11 @@ Unit used to measure the resource consumption of a Serverless Function. It refle ## JWT Token -JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your private container. [Find out how to secure a Function](/serverless/functions/how-to/secure-a-function/#restrict-access-to-your-functions). +JWT (JSON Web Token) is an access token you can create from the console or API to enable an application to access your private container. [Find out how to secure a Function](/serverless-functions/how-to/secure-a-function/#restrict-access-to-your-functions). ## Handler -A handler is a routine/function/method that processes specific events. Upon invoking your function, the handler is executed and returns an output. Refer to our [dedicated documentation](/serverless/functions/reference-content/functions-handlers/) for more information on the structure of a handler. +A handler is a routine/function/method that processes specific events. Upon invoking your function, the handler is executed and returns an output. Refer to our [dedicated documentation](/serverless-functions/reference-content/functions-handlers/) for more information on the structure of a handler. ## Instance @@ -71,7 +71,7 @@ The Serverless infrastructure manages incoming request traffic. In scenarios lik ## Logging -Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/). +Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/). ## Max scale @@ -79,7 +79,7 @@ This parameter sets the maximum number of function instances. You should adjust ## Metrics -Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Functions](/serverless/functions/how-to/monitor-function/)). +Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Functions](/serverless-functions/how-to/monitor-function/)). ## Min scale @@ -87,13 +87,13 @@ Customizing the minimum scale for Serverless can help ensure that an instance re ## Namespace -A namespace is a project that allows you to [group your functions](/serverless/functions/how-to/create-manage-delete-functions-namespace/). +A namespace is a project that allows you to [group your functions](/serverless-functions/how-to/create-manage-delete-functions-namespace/). Functions in the same namespace can share environment variables and access tokens, defined at the namespace level. ## NATS trigger -A NATS trigger is a mechanism that connects a function to a [NATS](/serverless/messaging/concepts/#nats) subject and invokes the function automatically whenever a message is published to the subject. +A NATS trigger is a mechanism that connects a function to a [NATS](/messaging/concepts/#nats) subject and invokes the function automatically whenever a message is published to the subject. For each message that is sent to a NATS subject, the NATS trigger reads the message and invokes the associated function with the message as the input parameter. The function can then process the message and perform any required actions, such as updating a database or sending a notification. @@ -104,7 +104,7 @@ A function's privacy policy defines whether a function may be executed anonymous ## Queue trigger -A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/serverless/messaging/concepts/#queues), and invokes the function automatically whenever a message is added to the queue. +A queue trigger is a mechanism that connects a function to a queue created with [Scaleway Queues](/messaging/concepts/#queues), and invokes the function automatically whenever a message is added to the queue. For each message that is sent to a queue, the trigger reads the message and invokes the associated function with the message as the input parameter. The function can then process the message and perform any required actions, such as updating a database or sending a notification. @@ -166,7 +166,7 @@ These functions automatically scale based on demand and are designed to be light ## Serverless Job -Serverless Jobs are similar to Serverless Functions but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless/functions/reference-content/difference-jobs-functions-containers) for more information. +Serverless Jobs are similar to Serverless Functions but are better suited for running longer workloads. See [the comparaison between Serverless products](/serverless-functions/reference-content/difference-jobs-functions-containers) for more information. ## Stateless @@ -174,14 +174,14 @@ Refers to a system or application that does not maintain any persistent state be This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others. -To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/). +To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). ## Status A Serverless Function can have the following statuses: * **Ready**: your Serverless Function is operational to serve requests. * **Pending**: your resource is under deployment. -* **Error**: something went wrong during the deployment process or build of the source code to image. [Check our troubleshooting documentation](/serverless/functions/troubleshooting/function-in-error-state/) to solve the issue. +* **Error**: something went wrong during the deployment process or build of the source code to image. [Check our troubleshooting documentation](/serverless-functions/troubleshooting/function-in-error-state/) to solve the issue. ## Trigger diff --git a/serverless/functions/how-to/add-a-custom-domain-name-to-a-function.mdx b/serverless/functions/how-to/add-a-custom-domain-name-to-a-function.mdx index 8a9d086ab1..5ba927b452 100644 --- a/serverless/functions/how-to/add-a-custom-domain-name-to-a-function.mdx +++ b/serverless/functions/how-to/add-a-custom-domain-name-to-a-function.mdx @@ -18,13 +18,13 @@ Each function comes with an automatically generated domain, on which it is avail - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Serverless Function](/serverless/functions/how-to/create-a-function/) that is running +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Serverless Function](/serverless-functions/how-to/create-a-function/) that is running - Registered a domain name with the provider of your choice and have access to the domain name's DNS zone file If you are using **Cloudflare DNS**, see the note below regarding proxying. -1. On your domain provider's platform (for example, [Scaleway's domains](/network/domains-and-dns/how-to/manage-dns-records/)), add a CNAME record pointing to your function default URL in the domain's DNS zone file. +1. On your domain provider's platform (for example, [Scaleway's domains](/domains-and-dns/how-to/manage-dns-records/)), add a CNAME record pointing to your function default URL in the domain's DNS zone file. - All domains are supported. diff --git a/serverless/functions/how-to/add-trigger-to-a-function.mdx b/serverless/functions/how-to/add-trigger-to-a-function.mdx index 95c681a4ef..dd933ef2b2 100644 --- a/serverless/functions/how-to/add-trigger-to-a-function.mdx +++ b/serverless/functions/how-to/add-trigger-to-a-function.mdx @@ -23,11 +23,11 @@ A trigger can be an HTTP request, a message from a queue or stream, a CRON sched - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) -- Created a [function](/serverless/functions/how-to/create-a-function/) -- [Created credentials](/serverless/messaging/how-to/create-credentials/) for Scaleway Queues -- [Created a queue](/serverless/messaging/how-to/create-manage-queues/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) +- Created a [function](/serverless-functions/how-to/create-a-function/) +- [Created credentials](/messaging/how-to/create-credentials/) for Scaleway Queues +- [Created a queue](/messaging/how-to/create-manage-queues/) You can create triggers on private functions, but to update the privacy of a function from **public** to **private**, you must recreate the existing **Queues** and **NATS** triggers after the privacy change. We are actively working to make this operation as seamless as possible. @@ -39,11 +39,11 @@ You can create triggers on private functions, but to update the privacy of a fun ## Queue triggers -[Queue triggers](/serverless/containers/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/serverless/messaging/concepts/#queue). +[Queue triggers](/serverless-containers/concepts/#queue-trigger) allow you to automatically invoke a function using events stored in a [queue](/messaging/concepts/#queue). Only queues created with the Scaleway Queues product are compatible with Serverless Functions. -The configuration of the queue retention may affect the behavior of the trigger. Refer to the [Considerations to configure event retention for queue trigger inputs](/serverless/functions/reference-content/configure-trigger-inputs/) page for more information. +The configuration of the queue retention may affect the behavior of the trigger. Refer to the [Considerations to configure event retention for queue trigger inputs](/serverless-functions/reference-content/configure-trigger-inputs/) page for more information. 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. 2. Click the relevant functions namespace. @@ -59,9 +59,9 @@ The configuration of the queue retention may affect the behavior of the trigger. ## NATS triggers -[NATS triggers](/serverless/functions/concepts/#nats-trigger) allow you to automatically invoke a function using messages sent in a [NATS](/serverless/messaging/concepts/#nats) subject. +[NATS triggers](/serverless-functions/concepts/#nats-trigger) allow you to automatically invoke a function using messages sent in a [NATS](/messaging/concepts/#nats) subject. -Scaleway [NATS subjects](/serverless/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Functions. +Scaleway [NATS subjects](/messaging/quickstart/#quickstart-for-nats) are compatible with Serverless Functions. 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. 2. Click the relevant functions namespace. @@ -77,7 +77,7 @@ Scaleway [NATS subjects](/serverless/messaging/quickstart/#quickstart-for-nats) ## CRON triggers -[CRON triggers](/serverless/functions/concepts/#cron-trigger) allow you to invoke your functions based on a recurring schedule. The CRON triggers for Serverless Functions use the **UTC** time zone. +[CRON triggers](/serverless-functions/concepts/#cron-trigger) allow you to invoke your functions based on a recurring schedule. The CRON triggers for Serverless Functions use the **UTC** time zone. 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. 2. Click the relevant functions namespace. @@ -89,5 +89,5 @@ Scaleway [NATS subjects](/serverless/messaging/quickstart/#quickstart-for-nats) 8. Click **Create trigger** to launch trigger creation. - Refer to the [cron schedules reference](/serverless/functions/reference-content/cron-schedules/) for more information. + Refer to the [cron schedules reference](/serverless-functions/reference-content/cron-schedules/) for more information. diff --git a/serverless/functions/how-to/create-a-function.mdx b/serverless/functions/how-to/create-a-function.mdx index 7f072810dc..bfd38d9d8f 100644 --- a/serverless/functions/how-to/create-a-function.mdx +++ b/serverless/functions/how-to/create-a-function.mdx @@ -13,13 +13,13 @@ categories: - serverless --- -This page shows you how to deploy a [function](/serverless/functions/concepts/#function) using the Scaleway console. +This page shows you how to deploy a [function](/serverless-functions/concepts/#function) using the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. @@ -29,8 +29,8 @@ This page shows you how to deploy a [function](/serverless/functions/concepts/#f 4. Complete the following steps in the wizard: - Choose your function's runtime. - - Select **Deploy "Hello world"** to deploy a basic function, **Inline code editor** to enter your own function code, or **Upload a ZIP** to import a [packaged function](/serverless/functions/how-to/package-function-dependencies-in-zip/). - - If you used the code editor, enter the [handler](/serverless/functions/reference-content/functions-handlers/) of your function. + - Select **Deploy "Hello world"** to deploy a basic function, **Inline code editor** to enter your own function code, or **Upload a ZIP** to import a [packaged function](/serverless-functions/how-to/package-function-dependencies-in-zip/). + - If you used the code editor, enter the [handler](/serverless-functions/reference-content/functions-handlers/) of your function. - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Enter an optional **description**. - Select the **resources** to allocate to your function. @@ -47,13 +47,13 @@ This page shows you how to deploy a [function](/serverless/functions/concepts/#f - Set the desired **privacy policy** for your function. This defines whether a function can be executed anonymously (**public**) or only via an authentication mechanism provided by the [Scaleway API](https://www.scaleway.com/en/developers/api/serverless-functions/#authentication) (**private**). - Set the desired timeout for your function. - [Triggers](/serverless/functions/concepts/#trigger) can no longer be added from this screen. For more information, refer to the [How to add a trigger to a function](/serverless/functions/how-to/add-trigger-to-a-function/) documentation. + [Triggers](/serverless-functions/concepts/#trigger) can no longer be added from this screen. For more information, refer to the [How to add a trigger to a function](/serverless-functions/how-to/add-trigger-to-a-function/) documentation. - Verify the **estimated cost**. 6. Click **Create function** to finish. - There are different ways to deploy Serverless Functions. Refer to our detailed [deployment information](/serverless/functions/reference-content/deploy-function/) for more advanced options to deploy your functions. + There are different ways to deploy Serverless Functions. Refer to our detailed [deployment information](/serverless-functions/reference-content/deploy-function/) for more advanced options to deploy your functions. diff --git a/serverless/functions/how-to/create-auth-token-from-console.mdx b/serverless/functions/how-to/create-auth-token-from-console.mdx index ab346d829a..0957c68948 100644 --- a/serverless/functions/how-to/create-auth-token-from-console.mdx +++ b/serverless/functions/how-to/create-auth-token-from-console.mdx @@ -18,9 +18,9 @@ This page shows you how to create and manage an authentication token from the co - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [functions namespace](/serverless/functions/how-to/create-a-function/) -- A [function](/serverless/functions/how-to/create-a-function/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [functions namespace](/serverless-functions/how-to/create-a-function/) +- A [function](/serverless-functions/how-to/create-a-function/) ## Creating authentication tokens from the console diff --git a/serverless/functions/how-to/create-manage-delete-functions-namespace.mdx b/serverless/functions/how-to/create-manage-delete-functions-namespace.mdx index f2ec342f4b..b47aca698a 100644 --- a/serverless/functions/how-to/create-manage-delete-functions-namespace.mdx +++ b/serverless/functions/how-to/create-manage-delete-functions-namespace.mdx @@ -15,12 +15,12 @@ categories: This page shows you how to create, manage, and delete a Functions namespace using the Scaleway console. -[Namespaces](/serverless/functions/concepts/#namespace) allow you to group your [functions](/serverless/functions/concepts/#function) and share environment variables, secrets and tokens between them. +[Namespaces](/serverless-functions/concepts/#namespace) allow you to group your [functions](/serverless-functions/concepts/#function) and share environment variables, secrets and tokens between them. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Creating a Serverless Functions namespace @@ -34,7 +34,7 @@ This page shows you how to create, manage, and delete a Functions namespace usin - Choose a **region**, which is the geographical location in which your namespace will be deployed. - Click **+ Add advanced options** to define any **environment variables** you want to inject into your function. For each environment variable, click **+ Add variable** and enter the key/value pair. - Set optional secret environment variables. **Secrets** are environment variables which are injected into your function and stored securely, but not displayed in the console after initial validation. Add a **key** and a **value**. -4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless/functions/how-to/create-a-function/) next. +4. Click **Create namespace only** to finish, or click **Create namespace and add a function** if you want to [create a function](/serverless-functions/how-to/create-a-function/) next. ## Managing a Serverless Functions namespace diff --git a/serverless/functions/how-to/delete-a-function.mdx b/serverless/functions/how-to/delete-a-function.mdx index 3e0517a32f..855958c08d 100644 --- a/serverless/functions/how-to/delete-a-function.mdx +++ b/serverless/functions/how-to/delete-a-function.mdx @@ -19,8 +19,8 @@ This page shows you how to delete a function. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [function](/serverless/functions/how-to/create-a-function/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [function](/serverless-functions/how-to/create-a-function/) 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. 2. Click the relevant functions namespace. diff --git a/serverless/functions/how-to/manage-a-function.mdx b/serverless/functions/how-to/manage-a-function.mdx index 0c37dbeef8..18f18796d1 100644 --- a/serverless/functions/how-to/manage-a-function.mdx +++ b/serverless/functions/how-to/manage-a-function.mdx @@ -18,8 +18,8 @@ This page shows you how to manage a function, in order to edit it or verify/chan - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a function](/serverless/functions/how-to/create-a-function/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a function](/serverless-functions/how-to/create-a-function/) 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. 2. Click the relevant functions namespace. diff --git a/serverless/functions/how-to/monitor-function.mdx b/serverless/functions/how-to/monitor-function.mdx index 282b51b50c..4b6885c6a1 100644 --- a/serverless/functions/how-to/monitor-function.mdx +++ b/serverless/functions/how-to/monitor-function.mdx @@ -14,7 +14,7 @@ categories: - functions --- -Scaleway Serverless Functions is fully integrated into [Cockpit](/observability/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Functions. +Scaleway Serverless Functions is fully integrated into [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs and metrics. This page explains how to get started with Scaleway Cockpit to monitor your Serverless Functions. Use your Cockpit logs and metrics to fine-tune the resources allocated to your Serverless Functions to avoid bottlenecks and over-provisioning. @@ -23,12 +23,12 @@ Use your Cockpit logs and metrics to fine-tune the resources allocated to your S - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless Function](/serverless/functions/how-to/create-a-function/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless Function](/serverless-functions/how-to/create-a-function/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to access the Grafana dashboard @@ -36,7 +36,7 @@ To view your Serverless Functions logs, use the Grafana dashboard which is acces - First you must create a user and their associated credentials (a username and password) for Grafana. - Then use these credentials to access the Grafana dashboard for all your Scaleway products, via the Scaleway console. -1. Create a Grafana user and retrieve their username and password by following [this procedure](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. Create a Grafana user and retrieve their username and password by following [this procedure](/cockpit/how-to/retrieve-grafana-credentials/). 2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. diff --git a/serverless/functions/how-to/package-function-dependencies-in-zip.mdx b/serverless/functions/how-to/package-function-dependencies-in-zip.mdx index fb9f702a2c..08414e6bbe 100644 --- a/serverless/functions/how-to/package-function-dependencies-in-zip.mdx +++ b/serverless/functions/how-to/package-function-dependencies-in-zip.mdx @@ -20,13 +20,13 @@ This feature allows you to add your libraries or static files to your function. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) - installed [jq](https://jqlang.github.io/jq/download/) ## How to package a function into zip file -There are [different methods to deploy functions](/serverless/functions/reference-content/deploy-function/) and some of them require the function to be packaged into a `zip` file. +There are [different methods to deploy functions](/serverless-functions/reference-content/deploy-function/) and some of them require the function to be packaged into a `zip` file. To match the Scaleway build pipelines requirements, functions zip files must contain the content of the root folder you want to publish. @@ -46,7 +46,7 @@ The example above will create a `.zip` archive that contains the myFunction fold - 1. Package your dependencies on your local computer, as explained in the [Configure your package](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-package-a-function-into-zip-file) section. + 1. Package your dependencies on your local computer, as explained in the [Configure your package](/serverless-functions/how-to/package-function-dependencies-in-zip/#how-to-package-a-function-into-zip-file) section. 2. Create a **ZIP** archive containing the files and folders you need. 3. Go to the [Functions](https://console.scaleway.com/functions/namespaces) section of the Scaleway console and click on the functions namespace you want to configure. 4. Click **+ Create function**. The function creation page displays. @@ -58,7 +58,7 @@ The example above will create a `.zip` archive that contains the myFunction fold 10. Click **Create function** to finish. - Refer to our [dedicated documentation](/serverless/functions/how-to/create-a-function/) for more information on how to create Serverless Functions + Refer to our [dedicated documentation](/serverless-functions/how-to/create-a-function/) for more information on how to create Serverless Functions @@ -150,7 +150,7 @@ The example above will create a `.zip` archive that contains the myFunction fold 2. Upload the archive in the console. 3. Provide a custom handler name. Here, the handler is `handlers/hello.say_hello`. - By default, the handler path is `handler.handle` (def handle in handler.py). Refer to the [Functions handlers reference](/serverless/functions/reference-content/functions-handlers/) for more information. + By default, the handler path is `handler.handle` (def handle in handler.py). Refer to the [Functions handlers reference](/serverless-functions/reference-content/functions-handlers/) for more information. @@ -362,10 +362,10 @@ Example: └── myFuncB.lang (contains handlerC()) ``` -Like that, you can create 3 functions with the same zip file simply by changing the [handler](/serverless/functions/concepts/#handler) parameter to match the handler you want: +Like that, you can create 3 functions with the same zip file simply by changing the [handler](/serverless-functions/concepts/#handler) parameter to match the handler you want: - `myFuncA.handlerA` - `myFuncA.handlerB` - `myFuncB.handlerC` -You can also create a single Serverless Function with several handlers in the same zip file, and change the [handler](/serverless/functions/concepts/#handler) parameter according to your needs. +You can also create a single Serverless Function with several handlers in the same zip file, and change the [handler](/serverless-functions/concepts/#handler) parameter according to your needs. diff --git a/serverless/functions/how-to/secure-a-function.mdx b/serverless/functions/how-to/secure-a-function.mdx index 57e0b48b0e..21bc3c2ff8 100644 --- a/serverless/functions/how-to/secure-a-function.mdx +++ b/serverless/functions/how-to/secure-a-function.mdx @@ -18,17 +18,17 @@ This page explains how to secure your function. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) -- A [function](/serverless/functions/how-to/create-a-function/) -- Created an [authentication token](/serverless/functions/how-to/create-auth-token-from-console/) for your function +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) +- A [function](/serverless-functions/how-to/create-a-function/) +- Created an [authentication token](/serverless-functions/how-to/create-auth-token-from-console/) for your function ## Use secrets to store access keys and sensitive information Instead of using environment variables (which are stored in clear text) for your functions, use secrets. These are pieces of information that can be used via environment variables, but are encrypted in storage. - You can [create an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and store it with secrets to grant your functions access to the [Scaleway API](https://www.scaleway.com/en/developers/api/). + You can [create an API key](/iam/how-to/create-api-keys/) and store it with secrets to grant your functions access to the [Scaleway API](https://www.scaleway.com/en/developers/api/). ### Configure secrets from the Scaleway console @@ -77,7 +77,7 @@ Unauthenticated calls will be rejected, and your function will not be triggered. 3. Click the name of the function for which you want to define secrets. 4. Click the **Security** tab. 5. Set the **Privacy Policy** of the function to **Private**. -6. If required, [create an access token](/serverless/functions/how-to/create-auth-token-from-console/) for your function. +6. If required, [create an access token](/serverless-functions/how-to/create-auth-token-from-console/) for your function. ```bash curl -H "X-Auth-Token: " @@ -93,7 +93,7 @@ Your function is now private, and requires an `X-Auth-Token` header to be called curl -H "X-Auth-Token: " ``` -Refer to the [How to create an authentication token](/serverless/functions/how-to/create-auth-token-from-console/) documentation for more information. +Refer to the [How to create an authentication token](/serverless-functions/how-to/create-auth-token-from-console/) documentation for more information. ### Restrict access using Terraform @@ -103,7 +103,7 @@ You can generate access credentials to inject in other applications (containers, ## Set up alerts in Observability Cockpit (upcoming feature) -Using Scaleway [Observability Cockpit](/observability/cockpit/quickstart/), a managed Grafana solution to which all your functions are connected, you can: +Using Scaleway [Observability Cockpit](/cockpit/quickstart/), a managed Grafana solution to which all your functions are connected, you can: * Monitor your functions using the default dashboard or create custom ones. * Set up notifications to be alerted in case of unexpected behavior. diff --git a/serverless/functions/how-to/test-a-function.mdx b/serverless/functions/how-to/test-a-function.mdx index a5e69b03a9..03ce291142 100644 --- a/serverless/functions/how-to/test-a-function.mdx +++ b/serverless/functions/how-to/test-a-function.mdx @@ -16,14 +16,14 @@ categories: This page shows you how to execute Serverless Functions from the [Scaleway console](https://console.scaleway.com). The **Test** feature of a function allows you to run your code using a selection of methods to make sure it behaves as expected. -Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless/functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function. +Testing **Private** Serverless Functions is not possible using the Scaleway console due to CORS limitations. Refer to the [dedicated documentation](/serverless-functions/how-to/create-auth-token-from-console/) for more information on how to secure and test a private function. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a function](/serverless/functions/how-to/create-a-function/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a function](/serverless-functions/how-to/create-a-function/) 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. @@ -35,7 +35,7 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons 5. Select the **method** you want to use from the drop-down menu. -6. Enter the **path** to your function. Leave the default `/` value if your function is not located in a specific folder within a [Zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). +6. Enter the **path** to your function. Leave the default `/` value if your function is not located in a specific folder within a [Zip package](/serverless-functions/how-to/package-function-dependencies-in-zip/). 7. Click **+ Advanced options** to add any required HTTP header or parameter to your function. @@ -44,5 +44,5 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons The **Output** section displays the response from your function and the status code. -If you encounter a message error while testing your function, refer to the [dedicated troubleshooting](/serverless/functions/troubleshooting/tests-fail-on-function/) for more information. +If you encounter a message error while testing your function, refer to the [dedicated troubleshooting](/serverless-functions/troubleshooting/tests-fail-on-function/) for more information. \ No newline at end of file diff --git a/serverless/functions/index.mdx b/serverless/functions/index.mdx index 4a5baab212..4852f82fc1 100644 --- a/serverless/functions/index.mdx +++ b/serverless/functions/index.mdx @@ -8,7 +8,7 @@ meta: productName="Serverless Functions" productLogo="functions" description="Scaleway Serverless Functions allows you to execute your code directly in the cloud without managing infrastructure." - url="/serverless/functions/quickstart" + url="/serverless-functions/quickstart" label="Serverless Functions Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create and deploy a Serverless Function in a few steps." label="View Quickstart" - url="/serverless/functions/quickstart/" + url="/serverless-functions/quickstart/" /> diff --git a/serverless/functions/quickstart.mdx b/serverless/functions/quickstart.mdx index 8244070fc3..cafb6f659c 100644 --- a/serverless/functions/quickstart.mdx +++ b/serverless/functions/quickstart.mdx @@ -13,18 +13,18 @@ categories: - serverless --- -Scaleway Serverless Functions makes your [functions](/serverless/functions/concepts/#function) available, executes them on demand and manages resource allocation for you. +Scaleway Serverless Functions makes your [functions](/serverless-functions/concepts/#function) available, executes them on demand and manages resource allocation for you. -Functions are designed for lightweight and short-lived workloads, and are limited to [a selection of runtimes](/serverless/functions/reference-content/functions-lifecycle/#available-runtimes) for optimum performance. +Functions are designed for lightweight and short-lived workloads, and are limited to [a selection of runtimes](/serverless-functions/reference-content/functions-lifecycle/#available-runtimes) for optimum performance. -Refer to the [differences between Functions, Jobs, and Containers](/serverless/containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. +Refer to the [differences between Functions, Jobs, and Containers](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. This page explains how to deploy, invoke, and delete a basic Node, Python, or PHP function using the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed [cURL](https://everything.curl.dev/install/) ## How to create a function @@ -33,7 +33,7 @@ If you have no existing Serverless Functions resources in your current Project, 1. Click **Functions** in the **Serverless** section of the side menu. The functions page displays. -2. Click **+ Create a function**. The function [namespace](/serverless/functions/concepts/#namespace) creation wizard displays. +2. Click **+ Create a function**. The function [namespace](/serverless-functions/concepts/#namespace) creation wizard displays. 3. Complete the following steps in the wizard: - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. @@ -41,12 +41,12 @@ If you have no existing Serverless Functions resources in your current Project, - Choose a **region**, which is the geographical location in which your namespace will be deployed. 4. Click **Create namespace and add function**. The function creation wizard displays. - Refer to the [How to create, manage and delete a functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) documentation page for more information on the different parameters. + Refer to the [How to create, manage and delete a functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) documentation page for more information on the different parameters. 5. Complete the following steps in the wizard: - Choose either **Node**, **Python** or **PHP** as a runtime. - Select **Deploy "Hello world"** if you want to deploy a basic function, or select **Inline code editor** to enter your own function code. - - If you used the code editor, enter the [handler](/serverless/functions/concepts/#handler) of your function. + - If you used the code editor, enter the [handler](/serverless-functions/concepts/#handler) of your function. - Enter a **name** or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Enter an optional **description**. - Choose the smallest **resources** available to allocate to your function. @@ -54,7 +54,7 @@ If you have no existing Serverless Functions resources in your current Project, - In the **Advanced options**, set the **Function privacy policy** to **public**. - Verify the **estimated cost**. - Refer to the [How to create a function](/serverless/functions/how-to/create-a-function/) documentation page for more information on the different parameters. + Refer to the [How to create a function](/serverless-functions/how-to/create-a-function/) documentation page for more information on the different parameters. 6. Click **Create function**. The deployment takes several minutes to complete. Check the **Overview** tab to see the function's status. @@ -84,4 +84,4 @@ The **Output** section displays the response from your function and the status c ## Going further -If you require more advanced usage, such as large projects with dependencies, automation, and multiple functions, refer to our [deployment methods](/serverless/functions/reference-content/deploy-function/) documentation and check our [repository](https://github.com/scaleway/serverless-examples) for examples and use cases. \ No newline at end of file +If you require more advanced usage, such as large projects with dependencies, automation, and multiple functions, refer to our [deployment methods](/serverless-functions/reference-content/deploy-function/) documentation and check our [repository](https://github.com/scaleway/serverless-examples) for examples and use cases. \ No newline at end of file diff --git a/serverless/functions/reference-content/code-examples.mdx b/serverless/functions/reference-content/code-examples.mdx index fabe686091..754ed3369f 100644 --- a/serverless/functions/reference-content/code-examples.mdx +++ b/serverless/functions/reference-content/code-examples.mdx @@ -22,10 +22,10 @@ This page shows examples of functions in [Python](#python), [Node](#node), [Gola - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Serverless Functions namespace](/serverless/functions/how-to/create-manage-delete-functions-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Serverless Functions namespace](/serverless-functions/how-to/create-manage-delete-functions-namespace/) - A text editor/IDE (such as `vi` or [Visual Studio Code](https://code.visualstudio.com/)) -- Knowledge of [how to package your functions and their dependencies](/serverless/functions/how-to/package-function-dependencies-in-zip/) +- Knowledge of [how to package your functions and their dependencies](/serverless-functions/how-to/package-function-dependencies-in-zip/) ## Python @@ -138,7 +138,7 @@ def handle(event, context): You might need to get information or transmit data to an external service. The Scaleway Python runtime includes the `urllib` library which enables you to connect to HTTP services without adding external libraries. -Refer to our guide on [code packaging](/serverless/functions/how-to/package-function-dependencies-in-zip/) if you want to use requests. +Refer to our guide on [code packaging](/serverless-functions/how-to/package-function-dependencies-in-zip/) if you want to use requests. **`GET` request example** @@ -208,8 +208,8 @@ def handle(event, context): } ``` - To use other libraries like `request`, you need to upload your project [with advanced methods](/serverless/functions/reference-content/deploy-function/) (recommended) - or [use a ZIP file](/serverless/functions/how-to/package-function-dependencies-in-zip/). + To use other libraries like `request`, you need to upload your project [with advanced methods](/serverless-functions/reference-content/deploy-function/) (recommended) + or [use a ZIP file](/serverless-functions/how-to/package-function-dependencies-in-zip/). ### Advanced Python examples @@ -412,7 +412,7 @@ module.exports.myHandler = (event, context, callback) => { You might need to get information or transmit data to an external service. The following code snippets can be executed directly in Serverless Functions without adding external libraries. -Refer to our guide on [code packaging](/serverless/functions/how-to/package-function-dependencies-in-zip/), if you want to use `fetch`, `axios`, ... +Refer to our guide on [code packaging](/serverless-functions/how-to/package-function-dependencies-in-zip/), if you want to use `fetch`, `axios`, ... **`GET` request sample:** diff --git a/serverless/functions/reference-content/configure-trigger-inputs.mdx b/serverless/functions/reference-content/configure-trigger-inputs.mdx index 312a8f855e..5739222e4c 100644 --- a/serverless/functions/reference-content/configure-trigger-inputs.mdx +++ b/serverless/functions/reference-content/configure-trigger-inputs.mdx @@ -18,7 +18,7 @@ categories: This feature only allows a maximum of 10 in-flight requests. Functions that are configured with more than 10 replicas will not be used at full capacity. This limitation will be removed in the future. -Triggers get events from an input, such as a [Scaleway queue](/serverless/messaging/concepts/#queues), and forward them to a function, which will scale up according to its settings to accommodate the workload. This process uses back pressure, so that no new events are read if the function instances have not yet finished processing the previous ones. +Triggers get events from an input, such as a [Scaleway queue](/messaging/concepts/#queues), and forward them to a function, which will scale up according to its settings to accommodate the workload. This process uses back pressure, so that no new events are read if the function instances have not yet finished processing the previous ones. Triggers only keep a buffer of the messages that are in-flight, they do not drain all the messages of the input in advance. diff --git a/serverless/functions/reference-content/deploy-function.mdx b/serverless/functions/reference-content/deploy-function.mdx index 56da304c36..867e943127 100644 --- a/serverless/functions/reference-content/deploy-function.mdx +++ b/serverless/functions/reference-content/deploy-function.mdx @@ -22,9 +22,9 @@ The [Scaleway console](https://console.scaleway.com/) is the easiest way to get The console lets you deploy functions written in a single source file in your browser. -Refer to the [dedicated documentation](/serverless/functions/how-to/create-a-function/) for more information. +Refer to the [dedicated documentation](/serverless-functions/how-to/create-a-function/) for more information. -Deploying larger projects with dependencies and many files requires zipping your code before uploading it. Refer to the documentation on [packaging functions in a zip file](/serverless/functions/how-to/package-function-dependencies-in-zip/) for more information. +Deploying larger projects with dependencies and many files requires zipping your code before uploading it. Refer to the documentation on [packaging functions in a zip file](/serverless-functions/how-to/package-function-dependencies-in-zip/) for more information. ## Serverless framework @@ -52,7 +52,7 @@ The [Scaleway HTTP API](https://www.scaleway.com/en/developers/api/) lets you ma The HTTP API can be useful when integrating Function management into your automated tasks, continuous integration, and more custom use cases. -Refer to the [API procedure](/serverless/functions/api-cli/deploy-function-api/) for more information. +Refer to the [API procedure](/serverless-functions/api-cli/deploy-function-api/) for more information. Deploying a function requires multiple API calls (namespace creation, function creation, generating URL to push code, function deployment), hence will require more boilerplate code than some of the other methods listed here. diff --git a/serverless/functions/reference-content/functions-limitations.mdx b/serverless/functions/reference-content/functions-limitations.mdx index 70ea43c3c1..e4882458f6 100644 --- a/serverless/functions/reference-content/functions-limitations.mdx +++ b/serverless/functions/reference-content/functions-limitations.mdx @@ -41,9 +41,9 @@ This section contains usage limits that apply when using Serverless Functions. \** Total function memory is the sum of the memory allocated to all your functions at their maximum Scale. -\*** Use [Serverless Jobs](/serverless/jobs/) for tasks up to 24h. +\*** Use [Serverless Jobs](/serverless-jobs/) for tasks up to 24h. -These limits are enforced as [Organization quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). +These limits are enforced as [Organization quotas](/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). If the limits are exceeded during the execution of the function, a restart occurs. diff --git a/serverless/functions/reference-content/local-testing.mdx b/serverless/functions/reference-content/local-testing.mdx index d576920a47..58903e3e9d 100644 --- a/serverless/functions/reference-content/local-testing.mdx +++ b/serverless/functions/reference-content/local-testing.mdx @@ -48,7 +48,7 @@ The most significant difference is that, when running in Scaleway Serverless Fun This means that at runtime, your function may be launched in a different operating system, with different libraries available to your local development environment. -Performance during local testing can differ from the deployed Serverless Functions environment, and will involve [limitations](/serverless/functions/reference-content/functions-limitations/) around resource usage and quotas. +Performance during local testing can differ from the deployed Serverless Functions environment, and will involve [limitations](/serverless-functions/reference-content/functions-limitations/) around resource usage and quotas. CPU/memory settings do not apply when testing functions locally. diff --git a/serverless/functions/troubleshooting/cannot-create-namespace.mdx b/serverless/functions/troubleshooting/cannot-create-namespace.mdx index 55760c1959..025bd952e6 100644 --- a/serverless/functions/troubleshooting/cannot-create-namespace.mdx +++ b/serverless/functions/troubleshooting/cannot-create-namespace.mdx @@ -21,9 +21,9 @@ I cannot create a Serverless Functions namespace. This issue can happen for the following reasons: -- You have created too many Serverless Functions namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). +- You have created too many Serverless Functions namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#serverless-functions). -- You have created too many Registry namespaces and reached [your account's quota](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/#container-registry). +- You have created too many Registry namespaces and reached [your account's quota](/organizations-and-projects/additional-content/organization-quotas/#container-registry). ### Possible solutions diff --git a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx index bc29517c5c..70b9e294cf 100644 --- a/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx +++ b/serverless/functions/troubleshooting/function-stopped-after-redeploy.mdx @@ -19,7 +19,7 @@ My Serverless Function stopped working (up to several hours) after a redeploy. ## Cause -The new deploy failed, and the [fallback mechanism has been triggered](/serverless/functions/reference-content/functions-limitations/#versioning-and-rollback). +The new deploy failed, and the [fallback mechanism has been triggered](/serverless-functions/reference-content/functions-limitations/#versioning-and-rollback). ## Possible solution diff --git a/serverless/functions/troubleshooting/handler-not-found.mdx b/serverless/functions/troubleshooting/handler-not-found.mdx index 5a85404b2e..939d0921bf 100644 --- a/serverless/functions/troubleshooting/handler-not-found.mdx +++ b/serverless/functions/troubleshooting/handler-not-found.mdx @@ -35,7 +35,7 @@ The systems cannot find the function that should handle the request. It may be r - Make sure to provide the right handler path. -- If you have used a zip file, make sure the dependencies are present in your [zip package](/serverless/functions/how-to/package-function-dependencies-in-zip/). +- If you have used a zip file, make sure the dependencies are present in your [zip package](/serverless-functions/how-to/package-function-dependencies-in-zip/). - If you have used the Serverless framework, ensure the `.serverless` directory created with `serverless package` contains your zip file. diff --git a/serverless/functions/troubleshooting/tests-fail-on-function.mdx b/serverless/functions/troubleshooting/tests-fail-on-function.mdx index 42b5d4fa10..92149e3e1b 100644 --- a/serverless/functions/troubleshooting/tests-fail-on-function.mdx +++ b/serverless/functions/troubleshooting/tests-fail-on-function.mdx @@ -25,7 +25,7 @@ Testing **Private** Serverless Functions is not possible using the Scaleway cons - Change the visibility of your function to **public**. Public functions can be executed anonymously. -- Make sure you have created an [authentication token](/serverless/functions/how-to/create-auth-token-from-console/) for your private function, then exexute a `curl` request from a terminal, as shown below: +- Make sure you have created an [authentication token](/serverless-functions/how-to/create-auth-token-from-console/) for your private function, then exexute a `curl` request from a terminal, as shown below: ```sh curl -H "X-Auth-Token: " \ ``` \ No newline at end of file diff --git a/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry.mdx b/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry.mdx index 59a596f0a8..1ab2d9ee34 100644 --- a/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry.mdx +++ b/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry.mdx @@ -17,20 +17,20 @@ Serverless Jobs rely on container images. These images can be stored in the Scal -This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/containers/container-registry/concepts/#container-registry). +This page explains how to migrate images from public external container registries (such as Docker hub, Amazon container registries, GitHub Container registry, etc.) to the [Scaleway Container registry](/container-registry/concepts/#container-registry). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a [Container Registry namespace](/container-registry/how-to/create-namespace/) ## Import images using Docker 1. Install the Docker Engine by following the [official documentation](https://docs.docker.com/engine/install/). -2. Login to your Scaleway Container Registry namespace with the Docker CLI by following [this procedure](/containers/container-registry/how-to/connect-docker-cli/). +2. Login to your Scaleway Container Registry namespace with the Docker CLI by following [this procedure](/container-registry/how-to/connect-docker-cli/). 3. Run the command below to pull, tag, then push the public image to your Scaleway Registry namespace. Make sure to replace the namespace name, and the image name by the appropriate values: ``` diff --git a/serverless/jobs/concepts.mdx b/serverless/jobs/concepts.mdx index e6352edae2..4c6ce24ba7 100644 --- a/serverless/jobs/concepts.mdx +++ b/serverless/jobs/concepts.mdx @@ -14,7 +14,7 @@ categories: ## Container Registry -Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless/containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details. +Container Registry is the place where your images are stored before being deployed. We recommend using Scaleway Container Registry for optimal integration. See the [migration guide](/serverless-containers/api-cli/migrate-external-image-to-scaleway-registry/) for full details. ## Environment variables @@ -42,11 +42,11 @@ The name of a job is part of the [job definition](#job-definition) and is used f ## Job run -A job run is the execution of a job definition. It can be in a running, succeeded, canceled, or failed status. Each job run has a unique identifier and can be individually monitored using [Cockpit](/observability/cockpit/quickstart/). +A job run is the execution of a job definition. It can be in a running, succeeded, canceled, or failed status. Each job run has a unique identifier and can be individually monitored using [Cockpit](/cockpit/quickstart/). ## Logging -Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/). +Serverless offers a built-in logging system based on Scaleway Cockpit to track the activity of your resources: see [monitoring Serverless Jobs](/serverless-jobs/how-to/monitor-job/). ## Maximum duration @@ -54,15 +54,15 @@ The maximum duration option allows you to define the maximum execution time befo ## Metrics -Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Jobs](/serverless/jobs/how-to/monitor-job/). +Performance metrics for your Serverless resources are natively available: see [monitoring Serverless Jobs](/serverless-jobs/how-to/monitor-job/). ## Schedule (cron) -A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless/jobs/reference-content/cron-schedules/) for more information. +A schedule (cron) is a mechanism used to automatically start a Serverless Job at a specific time on a recurring schedule. It works similarly to a traditional Linux cron job, using the `* * * * *` format. Refer to our [cron schedules reference](/serverless-jobs/reference-content/cron-schedules/) for more information. ## Secrets reference -A secret reference is a mechanism that allows you to use a secret stored in [Secret Manager](/identity-and-access-management/secret-manager/) within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates. +A secret reference is a mechanism that allows you to use a secret stored in [Secret Manager](/secret-manager/) within Serverless Jobs. It allows you to securely reference sensitive data, such as API secret keys, passwords, tokens, or certificates. ## Startup command @@ -73,7 +73,7 @@ This optional field allows you to specify a custom command executed upon startin A Serverless Job run can have the following statuses: * **Succeeded**: your Serverless Job run finished in a successful state. * **Queued**: your Serverless Job run is waiting for resources to run. -* **Error**: your Serverless Job run finished with an error or timeout. [Check our troubleshooting documentation](/serverless/jobs/troubleshooting/job-in-error-state/) to solve the issue. +* **Error**: your Serverless Job run finished with an error or timeout. [Check our troubleshooting documentation](/serverless-jobs/troubleshooting/job-in-error-state/) to solve the issue. * **Canceled**: your Serverless Job run has been canceled by the user. ## Stateless @@ -82,7 +82,7 @@ Refers to a system or application that does not maintain any persistent state be This means that each request is treated as a new and isolated event, and there is no need for the system to remember previous states or data once a task is completed. Statelessness is commonly used in serverless architectures where each function execution is independent of others. -To store data you can use [Scaleway Object Storage](/storage/object/), [Scaleway Managed Databases](/managed-databases/postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless/sql-databases/). +To store data you can use [Scaleway Object Storage](/object-storage/), [Scaleway Managed Databases](/managed-databases-for-postgresql-and-mysql/), and [Scaleway Serverless Databases](/serverless-sql-databases/). ## vCPU-s diff --git a/serverless/jobs/how-to/create-job.mdx b/serverless/jobs/how-to/create-job.mdx index 98d48f0fb8..9b7ee169d8 100644 --- a/serverless/jobs/how-to/create-job.mdx +++ b/serverless/jobs/how-to/create-job.mdx @@ -16,17 +16,17 @@ categories: This page shows you how to create Serverless Jobs using the [Scaleway console](https://console.scaleway.com/). -You can create a job from the [Scaleway Container Registry](/containers/container-registry/quickstart/), or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. +You can create a job from the [Scaleway Container Registry](/container-registry/quickstart/), or any other public container registry, such as Docker Hub, AWS Container registries, GitLab container registry, etc. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Container Registry namespace](/containers/container-registry/how-to/create-namespace/) and [pushed a container image](/containers/container-registry/how-to/push-images/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Container Registry namespace](/container-registry/how-to/create-namespace/) and [pushed a container image](/container-registry/how-to/push-images/) to it ## Create a job from the Scaleway Container Registry -Scaleway's Serverless Jobs allows you to create jobs from several container [registries](/containers/container-registry/concepts/#registry), including the [Scaleway Container Registry](/containers/container-registry/concepts/#container-registry) which allows you to store, secure and manage all your custom container images effortlessly. +Scaleway's Serverless Jobs allows you to create jobs from several container [registries](/container-registry/concepts/#registry), including the [Scaleway Container Registry](/container-registry/concepts/#container-registry) which allows you to store, secure and manage all your custom container images effortlessly. 1. Click **Jobs** in the **Serverless** section of the side menu. The jobs page displays. @@ -38,12 +38,12 @@ Scaleway's Serverless Jobs allows you to create jobs from several container [reg - Enter a name or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Select the region in which your job will be created. - Choose the **resources** to be allocated to your job at runtime. These define the performance characteristics of your job. - - Add a **cron schedule** in the `* * * * *` format, and select your time zone to run your job periodically. Refer to the [cron schedules documentation](/serverless/jobs/reference-content/cron-schedules/) for more information. + - Add a **cron schedule** in the `* * * * *` format, and select your time zone to run your job periodically. Refer to the [cron schedules documentation](/serverless-jobs/reference-content/cron-schedules/) for more information. - Define any **environment variables** you want to inject into your job in the advanced options. For each environment variable, click **+Add new variable** and enter the key/value pair. Encode your environment variables to `base64` if they are too large, and contain carriage returns. - - Add the desired [secret references](/serverless/jobs/how-to/reference-secret-in-job/) to your job. + - Add the desired [secret references](/serverless-jobs/how-to/reference-secret-in-job/) to your job. - Add a **startup command** to your job. It will be executed every time your job is run. - Set a **maximum duration** to your job to stop it automatically if it does not complete within this limit. - Verify the **estimated cost**. @@ -56,12 +56,12 @@ Scaleway's Serverless Jobs allows you to create jobs from several container [reg The execution appears in the **Job runs** section of the **Overview** tab. - Refer to [How to monitor a job](/serverless/jobs/how-to/monitor-job/) to see the logs of the job you just executed. + Refer to [How to monitor a job](/serverless-jobs/how-to/monitor-job/) to see the logs of the job you just executed. ## Create a job from an external container registry -Scaleway Serverless Jobs allows you to create jobs from external public [container registries](/containers/container-registry/concepts/#registry), such as Docker Hub, AWS container registries, GitLab container registry, etc. +Scaleway Serverless Jobs allows you to create jobs from external public [container registries](/container-registry/concepts/#registry), such as Docker Hub, AWS container registries, GitLab container registry, etc. Private external container registries are currently not supported. @@ -79,12 +79,12 @@ Private external container registries are currently not supported. - Enter a name, or use the automatically generated one. The name can only contain lowercase alphanumeric characters and dashes. - Select the region in which your job will be created. - Choose the **resources** to be allocated to your job at runtime. These define the performance characteristics of your job. - - Optionally, add a **cron schedule** in the `* * * * *` format, and select your time zone to run your job periodically. Refer to the [cron schedules documentation](/serverless/jobs/reference-content/cron-schedules/) for more information. + - Optionally, add a **cron schedule** in the `* * * * *` format, and select your time zone to run your job periodically. Refer to the [cron schedules documentation](/serverless-jobs/reference-content/cron-schedules/) for more information. - Define any **environment variables** you want to inject into your job in the advanced options. For each environment variable, click **+Add new variable** and enter the key/value pair. Encode your environment variables to `base64` if they are too large, and contain carriage returns. - - Add the desired [secret references](/serverless/jobs/how-to/reference-secret-in-job/) to your job. + - Add the desired [secret references](/serverless-jobs/how-to/reference-secret-in-job/) to your job. - Add a **startup command** to your job. It will be executed every time your job is run. - Set a **maximum duration** to your job to stop it automatically if it does not complete within this limit. - Verify the **estimated cost**. @@ -97,5 +97,5 @@ Private external container registries are currently not supported. The execution appears in the **Job runs** section of the **Overview** tab. - Refer to [How to monitor a job](/serverless/jobs/how-to/monitor-job/) to see the logs of the job you just executed. + Refer to [How to monitor a job](/serverless-jobs/how-to/monitor-job/) to see the logs of the job you just executed. diff --git a/serverless/jobs/how-to/delete-job.mdx b/serverless/jobs/how-to/delete-job.mdx index df85038bec..d2a4944865 100644 --- a/serverless/jobs/how-to/delete-job.mdx +++ b/serverless/jobs/how-to/delete-job.mdx @@ -23,8 +23,8 @@ This page shows you how to delete a Serverless Job. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a job](/serverless/jobs/how-to/create-job/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a job](/serverless-jobs/how-to/create-job/) 1. Click **Jobs** in the **Serverless** section of the side menu. The Serverless Jobs page displays. 2. Click the icon next to the job you want to delete, and select **Delete** from the drop-down menu. diff --git a/serverless/jobs/how-to/manage-job-schedule.mdx b/serverless/jobs/how-to/manage-job-schedule.mdx index 8aee3163db..1c86ec3f96 100644 --- a/serverless/jobs/how-to/manage-job-schedule.mdx +++ b/serverless/jobs/how-to/manage-job-schedule.mdx @@ -13,13 +13,13 @@ categories: - jobs --- -Job scheduling allows you to execute a Serverless Job on a recurring schedule, based on a [cron expression](/serverless/jobs/reference-content/cron-schedules/), in the `* * * * *` format, using the desired time zone. +Job scheduling allows you to execute a Serverless Job on a recurring schedule, based on a [cron expression](/serverless-jobs/reference-content/cron-schedules/), in the `* * * * *` format, using the desired time zone. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless Job](/serverless/jobs/how-to/create-job/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless Job](/serverless-jobs/how-to/create-job/) 1. Click **Jobs** in the **Serverless** section of the side menu. The jobs page displays. @@ -28,5 +28,5 @@ Job scheduling allows you to execute a Serverless Job on a recurring schedule, b 3. Scroll down to the **Job scheduling** section, and edit the cron expression and the time zone. -Refer to the [dedicated documentation](/serverless/jobs/reference-content/cron-schedules/) for more information on cron scheduling and time zones. +Refer to the [dedicated documentation](/serverless-jobs/reference-content/cron-schedules/) for more information on cron scheduling and time zones. \ No newline at end of file diff --git a/serverless/jobs/how-to/monitor-job.mdx b/serverless/jobs/how-to/monitor-job.mdx index 5d9442bb59..cae16de0e1 100644 --- a/serverless/jobs/how-to/monitor-job.mdx +++ b/serverless/jobs/how-to/monitor-job.mdx @@ -14,20 +14,20 @@ categories: - jobs --- -You can monitor the activity of your Serverless Jobs using the [Scaleway console](https://console.scaleway.com) to check the current status, RAM, and CPU consumption of your runs. Also, Serverless Jobs is fully integrated into Scaleway’s Observability [Cockpit](/observability/cockpit/quickstart/), and allows you to quickly access your logs. +You can monitor the activity of your Serverless Jobs using the [Scaleway console](https://console.scaleway.com) to check the current status, RAM, and CPU consumption of your runs. Also, Serverless Jobs is fully integrated into Scaleway’s Observability [Cockpit](/cockpit/quickstart/), and allows you to quickly access your logs. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless Job](/serverless/jobs/how-to/create-job/) -- Retrieved your [Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/) with Scaleway Observability Cockpit +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless Job](/serverless-jobs/how-to/create-job/) +- Retrieved your [Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) with Scaleway Observability Cockpit ## How to monitor your Serverless Jobs from the Scaleway console Scaleway Cockpit allows you to monitor your applications and their infrastructure by giving you access to metrics, logs, and traces in Grafana dashboards. -Make sure that you have created a Grafana user and [retrieved their username and password](/observability/cockpit/how-to/retrieve-grafana-credentials/). +Make sure that you have created a Grafana user and [retrieved their username and password](/cockpit/how-to/retrieve-grafana-credentials/). ### Monitor the activity of a job diff --git a/serverless/jobs/how-to/reference-secret-in-job.mdx b/serverless/jobs/how-to/reference-secret-in-job.mdx index f27719cfce..2550283b7c 100644 --- a/serverless/jobs/how-to/reference-secret-in-job.mdx +++ b/serverless/jobs/how-to/reference-secret-in-job.mdx @@ -14,18 +14,18 @@ categories: - jobs --- -Serverless Jobs seamlessly integrates with [Secret Manager](/identity-and-access-management/secret-manager/), which allows you to store, manage, and access sensitive information, such as credentials, SSH keys, SSL/TLS certificates, or any key/value pairs you need to secure. +Serverless Jobs seamlessly integrates with [Secret Manager](/secret-manager/), which allows you to store, manage, and access sensitive information, such as credentials, SSH keys, SSL/TLS certificates, or any key/value pairs you need to secure. You can reference any secret stored in Secret Manager in a job, without having to hardcode any sensitive data. -A [job run](/serverless/jobs/concepts/#job-run) accesses each secret at startup, and each access generates a call to the Secret Manager API, which is billed accordingly. Refer to the [Secret Manager pricing](/identity-and-access-management/secret-manager) for more information. +A [job run](/serverless-jobs/concepts/#job-run) accesses each secret at startup, and each access generates a call to the Secret Manager API, which is billed accordingly. Refer to the [Secret Manager pricing](/secret-manager) for more information. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless Job](/serverless/jobs/how-to/create-job/) -- [Created a secret](/identity-and-access-management/secret-manager/how-to/create-secret/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless Job](/serverless-jobs/how-to/create-job/) +- [Created a secret](/secret-manager/how-to/create-secret/) ## Reference a secret in a job @@ -76,5 +76,5 @@ You cannot change the reference method of an existing secret. To modify it, firs The secret is no longer referenced in your Serverless Job. -Deleting a secret from the **Settings** tab of a job only deletes the secret reference, not the secret itself. To permanently delete a secret, follow [this procedure](/identity-and-access-management/secret-manager/how-to/delete-secret/). +Deleting a secret from the **Settings** tab of a job only deletes the secret reference, not the secret itself. To permanently delete a secret, follow [this procedure](/secret-manager/how-to/delete-secret/). \ No newline at end of file diff --git a/serverless/jobs/how-to/run-job.mdx b/serverless/jobs/how-to/run-job.mdx index 6f8085d531..898d6dbbc5 100644 --- a/serverless/jobs/how-to/run-job.mdx +++ b/serverless/jobs/how-to/run-job.mdx @@ -19,8 +19,8 @@ This page shows you how to manually run a Serverless Job from the Scaleway conso - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a job](/serverless/jobs/how-to/create-job/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a job](/serverless-jobs/how-to/create-job/) ## How to run a job @@ -34,7 +34,7 @@ The **Job runs** section contains basic monitoring information for your jobs: - A start date and an end date - The duration of the job execution - Use [Cockpit](/observability/cockpit/quickstart/) for in-depth monitoring of the activity of your serverless jobs. + Use [Cockpit](/cockpit/quickstart/) for in-depth monitoring of the activity of your serverless jobs. ## How to run a job with contextual options @@ -55,7 +55,7 @@ The **Job runs** section contains basic monitoring information for your jobs: - The duration of the job execution - Use [Cockpit](/observability/cockpit/quickstart/) for in-depth monitoring of the activity of your serverless jobs. + Use [Cockpit](/cockpit/quickstart/) for in-depth monitoring of the activity of your serverless jobs. diff --git a/serverless/jobs/how-to/stop-job.mdx b/serverless/jobs/how-to/stop-job.mdx index 6d4a6a694f..fd6e326e14 100644 --- a/serverless/jobs/how-to/stop-job.mdx +++ b/serverless/jobs/how-to/stop-job.mdx @@ -19,8 +19,8 @@ This page shows you how to manually stop a Serverless Job from the Scaleway cons - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [job currently running](/serverless/jobs/how-to/run-job/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [job currently running](/serverless-jobs/how-to/run-job/) 1. Click **Jobs** in the **Serverless** section of the side menu. The Serverless Jobs page displays. diff --git a/serverless/jobs/index.mdx b/serverless/jobs/index.mdx index a3e6533ef2..e2993bf7fd 100644 --- a/serverless/jobs/index.mdx +++ b/serverless/jobs/index.mdx @@ -8,7 +8,7 @@ meta: productName="Serverless Jobs" productLogo="serverlessJob" description="Scaleway Serverless Jobs allow you to run recurring and autonomous tasks in the cloud." - url="/serverless/jobs/quickstart" + url="/serverless-jobs/quickstart" label="Serverless Jobs Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create and run a Serverless Jobs in a few steps." label="View Quickstart" - url="/serverless/jobs/quickstart/" + url="/serverless-jobs/quickstart/" /> diff --git a/serverless/jobs/quickstart.mdx b/serverless/jobs/quickstart.mdx index cf78c291a2..4332565eb4 100644 --- a/serverless/jobs/quickstart.mdx +++ b/serverless/jobs/quickstart.mdx @@ -14,19 +14,19 @@ categories: - jobs --- -Scaleway Serverless Jobs allows you to run recurring tasks in the cloud. A [Job](/serverless/jobs/concepts/#job) is based on a job definition, which is used as a template to create job runs. +Scaleway Serverless Jobs allows you to run recurring tasks in the cloud. A [Job](/serverless-jobs/concepts/#job) is based on a job definition, which is used as a template to create job runs. Jobs are designed for autonomous and recurring tasks, and therefore do not offer automatic scaling or a web interface. -Refer to the [differences between Jobs, Containers, and Functions](/serverless/containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. +Refer to the [differences between Jobs, Containers, and Functions](/serverless-containers/reference-content/difference-jobs-functions-containers/) for more information on Scaleway's different Serverless products. This page explains how to create a job definition with the latest Alpine Linux image, how to execute it, and delete it. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Container Registry namespace](/containers/container-registry/how-to/create-namespace/) and [pushed a container image](/containers/container-registry/how-to/push-images/) to it +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Container Registry namespace](/container-registry/how-to/create-namespace/) and [pushed a container image](/container-registry/how-to/push-images/) to it ## How to create a job definition @@ -64,7 +64,7 @@ This page explains how to create a job definition with the latest Alpine Linux i 4. Click the icon next to the last execution in the **Job runs** section, then click **Logs** to access your job's logs. - Make sure that you [have retrieved your Grafana credentials](/observability/cockpit/how-to/retrieve-grafana-credentials/) before accessing your job's logs. + Make sure that you [have retrieved your Grafana credentials](/cockpit/how-to/retrieve-grafana-credentials/) before accessing your job's logs. ## How to delete a job diff --git a/serverless/jobs/reference-content/deploy-job.mdx b/serverless/jobs/reference-content/deploy-job.mdx index e67d62e784..ac82dd581d 100644 --- a/serverless/jobs/reference-content/deploy-job.mdx +++ b/serverless/jobs/reference-content/deploy-job.mdx @@ -20,7 +20,7 @@ Serverless Jobs can be deployed and managed using several tools. This page aims The [Scaleway console](https://console.scaleway.com/) is the easiest way to get started. -The console allows you to easily [create a job definition](/serverless/jobs/how-to/create-job/) and track your job runs. You can also monitor your jobs using [Scaleway Cockpit](/observability/cockpit/quickstart/). +The console allows you to easily [create a job definition](/serverless-jobs/how-to/create-job/) and track your job runs. You can also monitor your jobs using [Scaleway Cockpit](/cockpit/quickstart/). ## Terraform @@ -34,7 +34,7 @@ The HTTP API can be useful when integrating jobs management into your automated ## CLI -The [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) is a simple command line interface that allows you to create, update, delete and list your Serverless Jobs. +The [Scaleway CLI](/scaleway-cli/quickstart/) is a simple command line interface that allows you to create, update, delete and list your Serverless Jobs. The dedicated documentation is available in the [Scaleway CLI repository](https://github.com/scaleway/scaleway-cli). @@ -50,6 +50,6 @@ The Scaleway SDKs allow you to manage your resources directly using your favorit The available SDKs are: -- Go SDK ([documentation](/developer-tools/scaleway-sdk/go-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-go)) -- JS SDK ([documentation](/developer-tools/scaleway-sdk/js-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-js)) -- Python SDK ([documentation](/developer-tools/scaleway-sdk/python-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-python)) \ No newline at end of file +- Go SDK ([documentation](/scaleway-sdk/go-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-go)) +- JS SDK ([documentation](/scaleway-sdk/js-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-js)) +- Python SDK ([documentation](/scaleway-sdk/python-sdk/) - [repository](https://github.com/scaleway/scaleway-sdk-python)) \ No newline at end of file diff --git a/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx index cc53cc5394..322d83f326 100644 --- a/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx +++ b/serverless/jobs/troubleshooting/cannot-retrieve-external-image.mdx @@ -23,6 +23,6 @@ Serverless products support external public registries (such as [Docker Hub](htt ## Solution -We recommend using the [Scaleway Container Registry](/containers/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). +We recommend using the [Scaleway Container Registry](/container-registry/) instead, as it allows for a seamless integration with Serverless Containers and Jobs at a [competitive price](/faq/containerregistry/#how-am-i-billed-for-scaleway-container-registry). -Refer to the [dedicated documentation](/serverless/jobs/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. +Refer to the [dedicated documentation](/serverless-jobs/api-cli/migrate-external-image-to-scaleway-registry/) for more information on how to migrate images to the Scaleway Container Registry. diff --git a/serverless/jobs/troubleshooting/job-in-error-state.mdx b/serverless/jobs/troubleshooting/job-in-error-state.mdx index 558e940f36..ef6af3508c 100644 --- a/serverless/jobs/troubleshooting/job-in-error-state.mdx +++ b/serverless/jobs/troubleshooting/job-in-error-state.mdx @@ -19,6 +19,6 @@ My job run is in an error state. ## Possible solutions -- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless/jobs/reference-content/jobs-limitations/#architecture) documentation for more information. +- Make sure that you have built your image for an `amd64` architecture, as `arm64` is not supported. See the [Architecture](/serverless-jobs/reference-content/jobs-limitations/#architecture) documentation for more information. -- Make sure that your deployment does not exceed the limitations of [Serverless Jobs](/serverless/jobs/reference-content/jobs-limitations/). \ No newline at end of file +- Make sure that your deployment does not exceed the limitations of [Serverless Jobs](/serverless-jobs/reference-content/jobs-limitations/). \ No newline at end of file diff --git a/serverless/messaging/api-cli/connect-aws-cli.mdx b/serverless/messaging/api-cli/connect-aws-cli.mdx index 5a35e60da0..34f61a55d2 100644 --- a/serverless/messaging/api-cli/connect-aws-cli.mdx +++ b/serverless/messaging/api-cli/connect-aws-cli.mdx @@ -20,8 +20,8 @@ This guide shows you how to install the AWS-CLI and configure it to connect to S - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Valid [credentials](/serverless/messaging/how-to/create-credentials/) for Queues and/or Topics and Events +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Valid [credentials](/messaging/how-to/create-credentials/) for Queues and/or Topics and Events This page assumes you will use the AWS-CLI v1. @@ -105,7 +105,7 @@ Now you have installed the AWS-CLI, you need to configure it for use with Scalew aws configure ``` ** -4. Open the `~/.aws/credentials` file you just created, and for each product (out of **Queues** and **Topics and Events**) you want to use, add the access key and secret key you saved when you generated your [credentials](/serverless/messaging/how-to/create-credentials/): +4. Open the `~/.aws/credentials` file you just created, and for each product (out of **Queues** and **Topics and Events**) you want to use, add the access key and secret key you saved when you generated your [credentials](/messaging/how-to/create-credentials/): ``` [topics_events] aws_access_key_id= @@ -132,6 +132,6 @@ Now you have installed the AWS-CLI, you need to configure it for use with Scalew Check out our dedicated documentation to find more common commands for getting started with the AWS CLI: - - The [Queues guide](/serverless/messaging/api-cli/sqs-sns-aws-cli/#getting-started-with-scaleway-queues) walks you through creating and listing queues, sending messages to queues, and more. - - The [Topics and Events guide](/serverless/messaging/api-cli/sqs-sns-aws-cli/#getting-started-with-topics-and-events) shows you how to create and list topics and subscriptions, send messages to topics, and more. + - The [Queues guide](/messaging/api-cli/sqs-sns-aws-cli/#getting-started-with-scaleway-queues) walks you through creating and listing queues, sending messages to queues, and more. + - The [Topics and Events guide](/messaging/api-cli/sqs-sns-aws-cli/#getting-started-with-topics-and-events) shows you how to create and list topics and subscriptions, send messages to topics, and more. diff --git a/serverless/messaging/api-cli/nats-cli.mdx b/serverless/messaging/api-cli/nats-cli.mdx index 9846997cc6..f8c747f081 100644 --- a/serverless/messaging/api-cli/nats-cli.mdx +++ b/serverless/messaging/api-cli/nats-cli.mdx @@ -26,9 +26,9 @@ This page shows you how to get started with some basic actions via the NATS CLI. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A Scaleway [NATS account](/serverless/messaging/how-to/get-started/#how-to-create-a-nats-account) -- NATS [credentials](/serverless/messaging/how-to/create-credentials/) downloaded to your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A Scaleway [NATS account](/messaging/how-to/get-started/#how-to-create-a-nats-account) +- NATS [credentials](/messaging/how-to/create-credentials/) downloaded to your machine ## Installing the NATS CLI @@ -42,7 +42,7 @@ To simplify your interactions with NATS hosted on Scaleway, we recommend that yo The example below creates a context named `scaleway`. - Replace `{Scaleway NATS URL}` with the URL of your NATS account (find this in the console on your NATS account **Overview** tab). -- Replace `{path to your creds file}` with the path to the location where you [downloaded your `.creds` file](/serverless/messaging/how-to/create-credentials/#how-to-create-credentials-for-a-nats-account). +- Replace `{path to your creds file}` with the path to the location where you [downloaded your `.creds` file](/messaging/how-to/create-credentials/#how-to-create-credentials-for-a-nats-account). ```bash nats context save scaleway --server={Scaleway NATS URL} --creds={path to your creds file} @@ -58,12 +58,12 @@ nats context select scaleway ## Create a stream -To create a [stream](/serverless/messaging/concepts/#stream), use the command `nats stream add` and follow the CLI guidelines. +To create a [stream](/messaging/concepts/#stream), use the command `nats stream add` and follow the CLI guidelines. Bear in mind that: - Scaleway NATS does not support in-memory streams: choose `File` as storage backend. - - Some [system limits](/serverless/messaging/reference-content/limitations/) may apply by default. + - Some [system limits](/messaging/reference-content/limitations/) may apply by default. - If you choose a `Retention Policy` other than `Work Queue` you will be billed for the messages stored and retained. - Choosing three replicas has an impact on: - The stream storage limit (as data is replicated 3 times) diff --git a/serverless/messaging/api-cli/python-node-sns.mdx b/serverless/messaging/api-cli/python-node-sns.mdx index bbe9217a1b..acd87ce96e 100644 --- a/serverless/messaging/api-cli/python-node-sns.mdx +++ b/serverless/messaging/api-cli/python-node-sns.mdx @@ -13,7 +13,7 @@ dates: posted: 2023-01-04 --- -AWS provides a number of **S**oftware **D**evelopment **K**its (SDKs) which provide language-specific APIs for AWS services, including [SNS](/serverless/messaging/concepts/#sns), which is the protocol that Scaleway Topics and Events is based on. +AWS provides a number of **S**oftware **D**evelopment **K**its (SDKs) which provide language-specific APIs for AWS services, including [SNS](/messaging/concepts/#sns), which is the protocol that Scaleway Topics and Events is based on. - AWS provides a dedicated [SDK for Go](https://aws.amazon.com/sdk-for-go/). - The [AWS SDK for Python](https://aws.amazon.com/sdk-for-python/) is Boto3. @@ -24,8 +24,8 @@ This page provides code samples to show you how to get started using these SDKs - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Valid [credentials](/serverless/messaging/how-to/create-credentials/) for Topics and Events +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Valid [credentials](/messaging/how-to/create-credentials/) for Topics and Events - Installed the relevant AWS SDK [for Go](https://aws.amazon.com/sdk-for-go/), [Python](https://aws.amazon.com/sdk-for-python/) and/or [JavaScript](https://aws.amazon.com/sdk-for-javascript/) ## Go @@ -57,11 +57,11 @@ func main() { - The `Endpoint` for Scaleway Topics and Events is `https://sns.mnq.fr-par.scaleway.com`. The values for the access and secret keys should be the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Topics and Events. + The `Endpoint` for Scaleway Topics and Events is `https://sns.mnq.fr-par.scaleway.com`. The values for the access and secret keys should be the credentials you [generated](/messaging/how-to/create-credentials/) for Topics and Events. -Once connected, you can use any of the SDK's available functions. Be aware though that some functions are not [supported by Scaleway Topics and Events](/serverless/messaging/reference-content/sns-support/), so make sure to check the link for more details on these. See the [official SDK documentation](https://pkg.go.dev/github.com/aws/aws-sdk-go/service/sns) for more information on getting started with the SDK, or keep reading for some code examples. +Once connected, you can use any of the SDK's available functions. Be aware though that some functions are not [supported by Scaleway Topics and Events](/messaging/reference-content/sns-support/), so make sure to check the link for more details on these. See the [official SDK documentation](https://pkg.go.dev/github.com/aws/aws-sdk-go/service/sns) for more information on getting started with the SDK, or keep reading for some code examples. ### Create topic (Go) @@ -159,10 +159,10 @@ sns = boto3.resource('sns', ``` - The `endpoint_url` for Scaleway Topics and Events (based on SNS) is `https://sns.mnq.fr-par.scaleway.com`. The values for the access and secret keys should be the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Topics and Events. + The `endpoint_url` for Scaleway Topics and Events (based on SNS) is `https://sns.mnq.fr-par.scaleway.com`. The values for the access and secret keys should be the credentials you [generated](/messaging/how-to/create-credentials/) for Topics and Events. -Once connected to, you can use any of the SDK's available functions. However, some functions are not [supported by Scaleway Topics and Events](/serverless/messaging/reference-content/sns-support/), so do check the link to make sure. See the [official SDK documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more information, or keep reading for some code examples. +Once connected to, you can use any of the SDK's available functions. However, some functions are not [supported by Scaleway Topics and Events](/messaging/reference-content/sns-support/), so do check the link to make sure. See the [official SDK documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more information, or keep reading for some code examples. ### Create topic (Python) @@ -276,10 +276,10 @@ var snsClient = new SNSClient({ ``` - The `endpoint_url` for Scaleway Topics and Events is `https://sns.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Topics and Events. + The `endpoint_url` for Scaleway Topics and Events is `https://sns.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/messaging/how-to/create-credentials/) for Topics and Events. -Once connected, you can use any of the SDK's available functions. However, some functions are not [supported by Scaleway Topics and Events](/serverless/messaging/reference-content/sns-support), so do check the link to make sure. See the [official SDK documentation](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-sns/) for more information, or keep reading for some code examples. +Once connected, you can use any of the SDK's available functions. However, some functions are not [supported by Scaleway Topics and Events](/messaging/reference-content/sns-support), so do check the link to make sure. See the [official SDK documentation](https://docs.aws.amazon.com/AWSJavaScriptSDK/v3/latest/clients/client-sns/) for more information, or keep reading for some code examples. ### Create topic (NodeJS) diff --git a/serverless/messaging/api-cli/python-node-sqs.mdx b/serverless/messaging/api-cli/python-node-sqs.mdx index 1b88c93097..74d78d6b3b 100644 --- a/serverless/messaging/api-cli/python-node-sqs.mdx +++ b/serverless/messaging/api-cli/python-node-sqs.mdx @@ -14,7 +14,7 @@ dates: validation_frequency: 8 --- -AWS provides a number of SDKs (**S**oftware **D**evelopment **K**its) which provide language-specific APIs for AWS services, including [SQS](/serverless/messaging/concepts#sqs), which is the protocol Scaleway Queues is based on. +AWS provides a number of SDKs (**S**oftware **D**evelopment **K**its) which provide language-specific APIs for AWS services, including [SQS](/messaging/concepts#sqs), which is the protocol Scaleway Queues is based on. - AWS provides a dedicated [SDK for Go](https://aws.amazon.com/sdk-for-go/). - The [AWS SDK for Python](https://aws.amazon.com/sdk-for-python/) is Boto3 @@ -25,8 +25,8 @@ This guide provides code samples to show you how to start using these SDKs with - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Valid [credentials](/serverless/messaging/how-to/create-credentials/) for Scaleway Queues +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Valid [credentials](/messaging/how-to/create-credentials/) for Scaleway Queues - Installed the relevant AWS SDK [for Go](https://aws.amazon.com/sdk-for-go/), [Python](https://aws.amazon.com/sdk-for-python/) and/or [JavaScript](https://aws.amazon.com/sdk-for-javascript/) ## Go @@ -58,11 +58,11 @@ func main() { - The `Endpoint` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Queues. + The `Endpoint` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/messaging/how-to/create-credentials/) for Queues. -Once you are connected, you can use any functions available with the SDK. However, we recommend that you check they are [supported by Scaleway Queues](/serverless/messaging/reference-content/sqs-support/). See the [official documentation](https://pkg.go.dev/github.com/aws/aws-sdk-go/service/sqs) for more details on using the SDK, or read on to see some examples. +Once you are connected, you can use any functions available with the SDK. However, we recommend that you check they are [supported by Scaleway Queues](/messaging/reference-content/sqs-support/). See the [official documentation](https://pkg.go.dev/github.com/aws/aws-sdk-go/service/sqs) for more details on using the SDK, or read on to see some examples. ### Create queue (Go) @@ -115,10 +115,10 @@ sqs = boto3.resource('sqs', ``` - The `endpoint_url` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Queues. + The `endpoint_url` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/messaging/how-to/create-credentials/) for Queues. -Once connected, you can use any functions available with the SDK - just check that they are [supported by Scaleway Queues](/serverless/messaging/reference-content/sqs-support/). See the [official documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more details, or read on to see some examples. +Once connected, you can use any functions available with the SDK - just check that they are [supported by Scaleway Queues](/messaging/reference-content/sqs-support/). See the [official documentation](https://boto3.amazonaws.com/v1/documentation/api/latest/index.html) for more details, or read on to see some examples. ### Create queue (Python) @@ -172,10 +172,10 @@ var sqsClient = new SQSClient({ ``` - The `endpoint_url` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/serverless/messaging/how-to/create-credentials/) for Scaleway Queues. + The `endpoint_url` for Scaleway Queues is `https://sqs.mnq.fr-par.scaleway.com`. For the access and secret key values, use the credentials you [generated](/messaging/how-to/create-credentials/) for Scaleway Queues. -Once connected, you can use any of the SDK's functions as long as they're [supported by Scaleway Queues](/serverless/messaging/reference-content/sqs-support/). Refer to AWS's [official documentation](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/SQS.html)) for more information, or read on to see some examples. +Once connected, you can use any of the SDK's functions as long as they're [supported by Scaleway Queues](/messaging/reference-content/sqs-support/). Refer to AWS's [official documentation](https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/SQS.html)) for more information, or read on to see some examples. ### Create queue (NodeJS) diff --git a/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx b/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx index 735adf1464..ac152c9f78 100644 --- a/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx +++ b/serverless/messaging/api-cli/sqs-sns-aws-cli.mdx @@ -14,14 +14,14 @@ dates: validation_frequency: 8 --- -The AWS-CLI is an open-source tool built on top of the AWS SDK for Python (Boto) that provides commands for interacting with AWS services. Once you have [connected Scaleway Queues and/or Topics and Events to the AWS-CLI](/serverless/messaging/api-cli/connect-aws-cli/), you can start creating, listing and managing your queues and topics, sending messages and much more, all from your command line. +The AWS-CLI is an open-source tool built on top of the AWS SDK for Python (Boto) that provides commands for interacting with AWS services. Once you have [connected Scaleway Queues and/or Topics and Events to the AWS-CLI](/messaging/api-cli/connect-aws-cli/), you can start creating, listing and managing your queues and topics, sending messages and much more, all from your command line. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Valid [credentials](/serverless/messaging/how-to/create-credentials/) for Queues and/or Topics and Events -- [Connected Queues and/or Topics and Events to the AWS-CLI](/serverless/messaging/api-cli/connect-aws-cli/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Valid [credentials](/messaging/how-to/create-credentials/) for Queues and/or Topics and Events +- [Connected Queues and/or Topics and Events to the AWS-CLI](/messaging/api-cli/connect-aws-cli/) - [jq](https://stedolan.github.io/jq/download/) installed on your machine ## Getting started with Scaleway Queues @@ -117,7 +117,7 @@ The AWS-CLI is an open-source tool built on top of the AWS SDK for Python (Boto) ### Preparing and subscribing to a lambda (Scaleway Serverless Functions) target for Topics and Events messages -1. Create the function following the steps detailed in the [Scaleway Functions Quickstart](/serverless/functions/quickstart/). +1. Create the function following the steps detailed in the [Scaleway Functions Quickstart](/serverless-functions/quickstart/). 2. Get the function endpoint from the [Scaleway console](https://console.scaleway.com/functions) under "Functions" -> "[YOUR-FUNCTION-NAMESPACE]" -> "[YOUR-FUNCTION-NAME]" -> "Function Settings" tab -> "Function Endpoint" diff --git a/serverless/messaging/concepts.mdx b/serverless/messaging/concepts.mdx index ae1627067a..8005c58d51 100644 --- a/serverless/messaging/concepts.mdx +++ b/serverless/messaging/concepts.mdx @@ -19,11 +19,11 @@ Content-based messaging systems are a subset of the [publish/subscribe](#publish ## Content-based deduplication -Content-based deduplication is a setting available for [FIFO](#fifo) queues. Enable content-based deduplication if the message body is guaranteed to be unique for each message. A unique hash value is generated from the body of each message, which is used as its deduplication ID. This avoids the need to set a deduplication ID when sending messages. Read more in our dedicated documentation on [creating queues](/serverless/messaging/how-to/create-manage-queues/). +Content-based deduplication is a setting available for [FIFO](#fifo) queues. Enable content-based deduplication if the message body is guaranteed to be unique for each message. A unique hash value is generated from the body of each message, which is used as its deduplication ID. This avoids the need to set a deduplication ID when sending messages. Read more in our dedicated documentation on [creating queues](/messaging/how-to/create-manage-queues/). ## Credentials -Credentials give services and platforms access to Scaleway NATS, Queues, and Topics and Events, enabling them to connect to the host system. Credentials are product-specific: for **Queues** and **Topics ad Events**, different levels of permissions can be defined to write, read, or manage queues/topics. NATS credentials give full read-write-manage access. Refer to our [additional content](/serverless/messaging/reference-content/) for more information. +Credentials give services and platforms access to Scaleway NATS, Queues, and Topics and Events, enabling them to connect to the host system. Credentials are product-specific: for **Queues** and **Topics ad Events**, different levels of permissions can be defined to write, read, or manage queues/topics. NATS credentials give full read-write-manage access. Refer to our [additional content](/messaging/reference-content/) for more information. ## Dead Letter Queue @@ -51,7 +51,7 @@ A message broker is a piece of software that allows applications, systems and se ## Message retention period -The message retention period is a setting that can be configured for a queue. It represents the length of time (in seconds) that messages are kept in the queue before being deleted. Setting a longer message retention period allows for a longer interval between a message being sent and it being received. Read more in our dedicated documentation on [creating queues](/serverless/messaging/how-to/create-manage-queues/). +The message retention period is a setting that can be configured for a queue. It represents the length of time (in seconds) that messages are kept in the queue before being deleted. Setting a longer message retention period allows for a longer interval between a message being sent and it being received. Read more in our dedicated documentation on [creating queues](/messaging/how-to/create-manage-queues/). ## Messaging and Queuing @@ -65,7 +65,7 @@ A messaging protocol defines a structured way for users / platforms / services / The **N**eural **A**utonomic **T**ransport **S**ystem, or [NATS](https://nats.io/), is an open-source messaging system written in Go. It is part of the Cloud Native Computing Foundation (CNCF) and has more than 40 client language implementations. The application has been designed with performance, scalability, and ease of use in mind. -Check our our [NATS quickstart](/serverless/messaging/quickstart/#quickstart-for-nats) to get started with Scaleway NATS, or our [tutorial](/tutorials/large-messages/) on creating a serverless architecture to process large messages with NATS, to get an idea of how to go further. +Check our our [NATS quickstart](/messaging/quickstart/#quickstart-for-nats) to get started with Scaleway NATS, or our [tutorial](/tutorials/large-messages/) on creating a serverless architecture to process large messages with NATS, to get an idea of how to go further. ## NATS account @@ -81,7 +81,7 @@ Also known as "pub/sub", the publish/subscribe model provides a pattern or frame ## Queue -Creating a queue with [Scaleway Queues](#queue) facilitates asynchronous communication between different microservices, applications, and platforms. You can create a queue, configure its delivery and message parameters, and then start sending messages to it. Messages are stored in the queue until they are processed and delivered, and deleted once consumed. [Read more about creating and configuring queues](/serverless/messaging/how-to/create-manage-queues/), or check our [tutorial on creating a serverless scraping architecture using a queue](/tutorials/create-serverless-scraping/) to get an idea of what you can do with message queues. +Creating a queue with [Scaleway Queues](#queue) facilitates asynchronous communication between different microservices, applications, and platforms. You can create a queue, configure its delivery and message parameters, and then start sending messages to it. Messages are stored in the queue until they are processed and delivered, and deleted once consumed. [Read more about creating and configuring queues](/messaging/how-to/create-manage-queues/), or check our [tutorial on creating a serverless scraping architecture using a queue](/tutorials/create-serverless-scraping/) to get an idea of what you can do with message queues. ## Queues @@ -89,7 +89,7 @@ Scaleway Queues is a product for creating managed messaging queues based on the ## Queue types -When creating queues with Scaleway Queues, two queue types are available. [Standard](#standard) queues provide at-least-once delivery, while [FIFO](#fifo) queues offer first-in-first-out delivery, and (unlike Standard queues) guarantee that messages are delivered in order and without duplication. [Content-based deduplication](#content-based-deduplication) is only available for FIFO queue types. Find out more about creating queues with our [dedicated documentation](/serverless/messaging/how-to/create-manage-queues/). +When creating queues with Scaleway Queues, two queue types are available. [Standard](#standard) queues provide at-least-once delivery, while [FIFO](#fifo) queues offer first-in-first-out delivery, and (unlike Standard queues) guarantee that messages are delivered in order and without duplication. [Content-based deduplication](#content-based-deduplication) is only available for FIFO queue types. Find out more about creating queues with our [dedicated documentation](/messaging/how-to/create-manage-queues/). ## Queuing @@ -101,9 +101,9 @@ Queue volume is one of the factors affecting the billing of Scaleway Queues. Que ## Region -NATS, Queues, and Topics and Events are available in multiple regions. A region designates the geographical area where the service is hosted. Refer to the [product availability table](/console/account/reference-content/products-availability/) to check which regions are available for NATS, Queues, and Topics and Events. +NATS, Queues, and Topics and Events are available in multiple regions. A region designates the geographical area where the service is hosted. Refer to the [product availability table](/account/reference-content/products-availability/) to check which regions are available for NATS, Queues, and Topics and Events. -When [creating a NATS account](/serverless/messaging/how-to/get-started/#how-to-create-a-nats-account) or creating queues or topics, you need to do this on a region-by-region basis. The region drop-down in the console allows you to switch between available regions. +When [creating a NATS account](/messaging/how-to/get-started/#how-to-create-a-nats-account) or creating queues or topics, you need to do this on a region-by-region basis. The region drop-down in the console allows you to switch between available regions. ## Routing @@ -139,7 +139,7 @@ In [publish/subscribe](#publishsubscribe) systems such as [Topics and Events](#t ## Subscription -A subscription is a connection between a client or endpoint, and a topic. By creating a subscription, the subscribed endpoint receives messages and notifications published to the topic. You can [create subscriptions](/serverless/messaging/how-to/create-manage-subscriptions/) for HTTP/S endpoints, Scaleway queues, and Scaleway Serverless [Functions](/serverless/functions/quickstart/) and [Containers](/serverless/containers/quickstart/). +A subscription is a connection between a client or endpoint, and a topic. By creating a subscription, the subscribed endpoint receives messages and notifications published to the topic. You can [create subscriptions](/messaging/how-to/create-manage-subscriptions/) for HTTP/S endpoints, Scaleway queues, and Scaleway Serverless [Functions](/serverless-functions/quickstart/) and [Containers](/serverless-containers/quickstart/). ## Subscription protocols and endpoints @@ -147,10 +147,10 @@ A subscription protocol refers to the communication method used to deliver messa | Protocol | Endpoint / Client | Note | |-------------------------------------|--------------------------------------------------|-----------------------------------| -| HTTP | The URL of a service or web server that can receive notifications (HTTP POST requests) from Topics and Events, e.g. `http://example.fr` | - For security reasons, we recommend using the HTTPS protocol rather than HTTP.
- HTTP subscriptions must be [confirmed](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) after creation | -| HTTPS | The URL of a service or web server that can receive notifications (HTTPS POST requests) from Topics and Events, e.g. `https://example.fr` | - HTTPS subscriptions must be [confirmed](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) after creation | -| Serverless Functions and Containers | A Scaleway Serverless [Function](/serverless/functions/quickstart/) or [Container](/serverless/containers/quickstart/)
| - It must have a [public](/serverless/functions/concepts/#privacy-policy) privacy policy
- It must be in a [namespace](/serverless/functions/concepts/#namespace) from the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](#region) as the topic | -| Queues | A Scaleway [queue](#queue)
| - It must be in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](#region) as the topic | +| HTTP | The URL of a service or web server that can receive notifications (HTTP POST requests) from Topics and Events, e.g. `http://example.fr` | - For security reasons, we recommend using the HTTPS protocol rather than HTTP.
- HTTP subscriptions must be [confirmed](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) after creation | +| HTTPS | The URL of a service or web server that can receive notifications (HTTPS POST requests) from Topics and Events, e.g. `https://example.fr` | - HTTPS subscriptions must be [confirmed](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) after creation | +| Serverless Functions and Containers | A Scaleway Serverless [Function](/serverless-functions/quickstart/) or [Container](/serverless-containers/quickstart/)
| - It must have a [public](/serverless-functions/concepts/#privacy-policy) privacy policy
- It must be in a [namespace](/serverless-functions/concepts/#namespace) from the same [Project](/organizations-and-projects/concepts/#project) and [region](#region) as the topic | +| Queues | A Scaleway [queue](#queue)
| - It must be in the same [Project](/organizations-and-projects/concepts/#project) and [region](#region) as the topic | ## Topic @@ -158,7 +158,7 @@ A topic is a communication channel used to send messages and notifications to su ## Topic types -When creating topics with Scaleway Topics and Events, two topic types are available. [Standard](#standard) topics provide at-least-once delivery, while [FIFO](#fifo) topics offer first-in-first-out delivery, and (unlike Standard topics) guarantee that messages are delivered in order and without duplication. [Content-based deduplication](#content-based-deduplication) is only available for FIFO topic types. Find out more about creating topics with our [dedicated documentation](/serverless/messaging/how-to/create-manage-topics/). +When creating topics with Scaleway Topics and Events, two topic types are available. [Standard](#standard) topics provide at-least-once delivery, while [FIFO](#fifo) topics offer first-in-first-out delivery, and (unlike Standard topics) guarantee that messages are delivered in order and without duplication. [Content-based deduplication](#content-based-deduplication) is only available for FIFO topic types. Find out more about creating topics with our [dedicated documentation](/messaging/how-to/create-manage-topics/). ## Topic-based @@ -174,4 +174,4 @@ Scaleway Topics and Events is a product for creating managed messaging topics ba ## Visibility timeout -Visibility timeout is a setting that can be configured for a Scaleway queue. It represents the length of time (in seconds) during which, after a message is received, the queue hides it, so it cannot be received again by the same or other consumers. This is useful as the queue itself does not automatically delete messages once they are received, and so prevents consumers from receiving the same message many times before they have finished processing it. Read more in our dedicated documentation on [creating queues](/serverless/messaging/how-to/create-manage-queues/). +Visibility timeout is a setting that can be configured for a Scaleway queue. It represents the length of time (in seconds) during which, after a message is received, the queue hides it, so it cannot be received again by the same or other consumers. This is useful as the queue itself does not automatically delete messages once they are received, and so prevents consumers from receiving the same message many times before they have finished processing it. Read more in our dedicated documentation on [creating queues](/messaging/how-to/create-manage-queues/). diff --git a/serverless/messaging/how-to/create-credentials.mdx b/serverless/messaging/how-to/create-credentials.mdx index 522b1ba194..16ee57b0c8 100644 --- a/serverless/messaging/how-to/create-credentials.mdx +++ b/serverless/messaging/how-to/create-credentials.mdx @@ -13,14 +13,14 @@ dates: posted: 2022-08-11 --- -This page shows how to create [credentials](/serverless/messaging/concepts/#credentials) for Scaleway **NATS**, **Queues** and **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). Credentials give their bearer (e.g. services and platforms) access to your service. +This page shows how to create [credentials](/messaging/concepts/#credentials) for Scaleway **NATS**, **Queues** and **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). Credentials give their bearer (e.g. services and platforms) access to your service. You can create multiple sets of credentials for each of your NATS accounts, and for your Queues and Topics and Events services. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create credentials for a NATS account @@ -28,7 +28,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read 1. Click **NATS** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the NATS account for which you want to create credentials. The list of your NATS accounts in the pre-selected region displays. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the NATS account for which you want to create credentials. The list of your NATS accounts in the pre-selected region displays. 3. Click the NATS account you want to generate credentials for. The account's **Overview** page displays. diff --git a/serverless/messaging/how-to/create-manage-queues.mdx b/serverless/messaging/how-to/create-manage-queues.mdx index fe7773afe0..9ff931c1eb 100644 --- a/serverless/messaging/how-to/create-manage-queues.mdx +++ b/serverless/messaging/how-to/create-manage-queues.mdx @@ -13,12 +13,12 @@ dates: posted: 2022-08-11 --- -This page shows how to create and manage your Scaleway [Queues](/serverless/messaging/concepts/#queue) (formerly part of the **Messaging and Queuing** product). +This page shows how to create and manage your Scaleway [Queues](/messaging/concepts/#queue) (formerly part of the **Messaging and Queuing** product). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a queue @@ -27,7 +27,7 @@ This page shows how to create and manage your Scaleway [Queues](/serverless/mess 2. Click **Create queue**. The Queue creation wizard displays. -3. Select the [region](/serverless/messaging/concepts/#region) in which you want to create the queue. +3. Select the [region](/messaging/concepts/#region) in which you want to create the queue. 4. Enter a **name** for your queue. The name must be no more than 80 characters, and consist only of alphanumeric characters, hyphens, and underscores. Alternatively, you can go with the auto-generated name suggested for you. @@ -48,7 +48,7 @@ You are returned to the **Queues** tab, where your newly-created queue now displ Go further by clicking on the queue's name to access its **Settings** page and see additional information such as its ARN (Amazon Resource Name) and configuration parameters. -Remember that you need to [create credentials](/serverless/messaging/how-to/create-credentials/) in order to access your queues from an API or CLI. Sending messages to queues requires that credentials have the `can_publish` permission, while receiving messages from queues requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application. +Remember that you need to [create credentials](/messaging/how-to/create-credentials/) in order to access your queues from an API or CLI. Sending messages to queues requires that credentials have the `can_publish` permission, while receiving messages from queues requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application. ## How to modify a queue's configuration @@ -57,7 +57,7 @@ You can modify the visibility timeout, message retention period and maximum mess 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to modify. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the queue you want to modify. 3. Click the queue you wish to modify. The queue's **Settings** page displays: @@ -73,7 +73,7 @@ You can use the **Purge** feature to delete all messages from a queue. 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to configure. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the queue you want to configure. 3. Either: - Click the queue you wish to purge. The queue's **Settings** page displays. Click the **Purge** button in the top right corner. @@ -89,7 +89,7 @@ When you no longer want a queue, you can delete it. This action is irreversible 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to configure. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the queue you want to configure. 3. Either: - Click the queue you wish to delete. The queue's **Settings** page displays. Click the **Delete queue** button in the bottom right corner. diff --git a/serverless/messaging/how-to/create-manage-subscriptions.mdx b/serverless/messaging/how-to/create-manage-subscriptions.mdx index 7dcabe28eb..b8e05a5e43 100644 --- a/serverless/messaging/how-to/create-manage-subscriptions.mdx +++ b/serverless/messaging/how-to/create-manage-subscriptions.mdx @@ -13,19 +13,19 @@ dates: posted: 2024-02-06 --- -This page shows how to create and manage [subscriptions](/serverless/messaging/concepts/#subscription) with Scaleway Topics and Events (formerly part of the Messaging and Queuing product). When you create a subscription to a [topic](/serverless/messaging/concepts/#topic), you are effectively signing up an endpoint to receive all messages published to that topic. +This page shows how to create and manage [subscriptions](/messaging/concepts/#subscription) with Scaleway Topics and Events (formerly part of the Messaging and Queuing product). When you create a subscription to a [topic](/messaging/concepts/#topic), you are effectively signing up an endpoint to receive all messages published to that topic. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An existing [topic](/serverless/messaging/how-to/create-manage-topics/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An existing [topic](/messaging/how-to/create-manage-topics/) ## How to create a subscription 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. -2. Use the dropdown menu to select the [region](/serverless/messaging/concepts/#region) of the topic you want to create a subscription for. +2. Use the dropdown menu to select the [region](/messaging/concepts/#region) of the topic you want to create a subscription for. 3. Click the name of the topic you want to create a subscription for. @@ -45,7 +45,7 @@ This page shows how to create and manage [subscriptions](/serverless/messaging/c You are prompted to enter the URL of the HTTP endpoint to subscribe, e.g. `example.com`. Note that the scheme (`http://`) is not required. - After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). + After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). @@ -54,21 +54,21 @@ This page shows how to create and manage [subscriptions](/serverless/messaging/c You are prompted to enter the URL of the HTTP endpoint to subscribe, e.g. `example.com`. Note that the scheme (`https://`) is not required. - After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). + After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription).
Choose **Serverless Functions and Containers** to create a subscription for a Scaleway Serverless Function or Container that you have created. - You are prompted to select the **namespace** containing the Function or Container that you want to subscribe. Only namespaces in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](/serverless/messaging/concepts/#region) as the topic can be selected. + You are prompted to select the **namespace** containing the Function or Container that you want to subscribe. Only namespaces in the same [Project](/organizations-and-projects/concepts/#project) and [region](/messaging/concepts/#region) as the topic can be selected. - You are prompted to select the Serverless Function or Container to subscribe. Only Functions and Containers with a public [privacy policy](/serverless/functions/concepts/#privacy-policy) can subscribe to an topic. + You are prompted to select the Serverless Function or Container to subscribe. Only Functions and Containers with a public [privacy policy](/serverless-functions/concepts/#privacy-policy) can subscribe to an topic.
Choose **Queues** to create a subscription for a Scaleway queue that you have created. - You are prompted to select the **queue** to subscribe. Only queues in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](/serverless/messaging/concepts/#region) as the topic can be selected. + You are prompted to select the **queue** to subscribe. Only queues in the same [Project](/organizations-and-projects/concepts/#project) and [region](/messaging/concepts/#region) as the topic can be selected. @@ -100,7 +100,7 @@ When you no longer want a subscribed endpoint or service to receive messages fro 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the subscription you want to delete. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the subscription you want to delete. 3. Click the topic containing the subscription you want to delete. diff --git a/serverless/messaging/how-to/create-manage-topics.mdx b/serverless/messaging/how-to/create-manage-topics.mdx index 054f4cfb90..be9d69feda 100644 --- a/serverless/messaging/how-to/create-manage-topics.mdx +++ b/serverless/messaging/how-to/create-manage-topics.mdx @@ -13,12 +13,12 @@ dates: posted: 2023-12-27 --- -This page shows how to create and manage [topics](/serverless/messaging/concepts/#topic) with Scaleway Topics and Events (formerly part of the Messaging and Queuing product). +This page shows how to create and manage [topics](/messaging/concepts/#topic) with Scaleway Topics and Events (formerly part of the Messaging and Queuing product). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a topic @@ -34,14 +34,14 @@ This page shows how to create and manage [topics](/serverless/messaging/concepts 5. Choose a **topic type**. The following topic types are available: - **Standard**: Ensures at-least-once message delivery, where the order of messages is not preserved. Supports Serverless Functions, Serverless Containers and HTTP/S subscriptions. - - **FIFO**: Provides first-in-first-out delivery, where the order of messages is preserved without duplication. Supports Scaleway Queues subscriptions. [Content-based deduplication](/serverless/messaging/concepts/#content-based-deduplication) is only available for FIFO topics. + - **FIFO**: Provides first-in-first-out delivery, where the order of messages is preserved without duplication. Supports Scaleway Queues subscriptions. [Content-based deduplication](/messaging/concepts/#content-based-deduplication) is only available for FIFO topics. 6. Click **Create topic** to finish. You are returned to the **Topics** tab, where your newly-created topic now displays. The topic's URL is also displayed here, for use in your API/CLI operations. -Remember that you need to [create credentials](/serverless/messaging/how-to/create-credentials/) in order to access your Topics and Events service and its topics from an API or CLI. Sending messages to topics requires that credentials have the `can_publish` permission, while receiving messages from topics requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application. +Remember that you need to [create credentials](/messaging/how-to/create-credentials/) in order to access your Topics and Events service and its topics from an API or CLI. Sending messages to topics requires that credentials have the `can_publish` permission, while receiving messages from topics requires the `can_receive` permission. You can create separate credentials if you need to isolate these two roles in your application. ## How to delete a topic @@ -50,7 +50,7 @@ When you no longer want a topic, you can delete it. This action is irreversible 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the topic you want to delete. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the topic you want to delete. 3. Either: - Click the topic you wish to delete, and navigate to its **Settings** page. Click the **Delete topic** button in the bottom right corner, or diff --git a/serverless/messaging/how-to/deactivate-delete-messaging.mdx b/serverless/messaging/how-to/deactivate-delete-messaging.mdx index 8b186abd77..f8ef3f4fbe 100644 --- a/serverless/messaging/how-to/deactivate-delete-messaging.mdx +++ b/serverless/messaging/how-to/deactivate-delete-messaging.mdx @@ -20,14 +20,14 @@ Note that it is no longer necessary to deactivate services for **Queues** or **T - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one [NATS account](/serverless/messaging/how-to/get-started/), [queue](/serverless/messaging/how-to/create-manage-queues/), or [topic](/serverless/messaging/how-to/create-manage-topics/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one [NATS account](/messaging/how-to/get-started/), [queue](/messaging/how-to/create-manage-queues/), or [topic](/messaging/how-to/create-manage-topics/) ## How to delete a NATS account 1. Click **NATS** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the NATS account you want to delete. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the NATS account you want to delete. 3. Click the NATS account you want to delete. diff --git a/serverless/messaging/how-to/get-started.mdx b/serverless/messaging/how-to/get-started.mdx index 82f2db7284..8b8e7e58b2 100644 --- a/serverless/messaging/how-to/get-started.mdx +++ b/serverless/messaging/how-to/get-started.mdx @@ -15,15 +15,15 @@ dates: This page shows how to get started with Scaleway **NATS**, **Queues** or **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). -The process differs depending on the [messaging protocol](/serverless/messaging/concepts/#messaging-protocol) you want to use: +The process differs depending on the [messaging protocol](/messaging/concepts/#messaging-protocol) you want to use: - For NATS, you need to **create a NATS account**. -- For **Queues** and **Topics and Events**, you no longer need to activate the protocol, but can proceed directly to [creating queues](/serverless/messaging/how-to/create-manage-queues) and/or [topics](/serverless/messaging/how-to/create-manage-topics). +- For **Queues** and **Topics and Events**, you no longer need to activate the protocol, but can proceed directly to [creating queues](/messaging/how-to/create-manage-queues) and/or [topics](/messaging/how-to/create-manage-topics). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a NATS account @@ -51,4 +51,4 @@ To start using a NATS message broker, you must first create a NATS account. This ## How to activate Queues or Topics and Events -For **Queues** and **Topics and Events**, you no longer need to activate the individual protocols. Proceed directly to [creating queues](/serverless/messaging/how-to/create-manage-queues) or [topics](/serverless/messaging/how-to/create-manage-topics) directly. \ No newline at end of file +For **Queues** and **Topics and Events**, you no longer need to activate the individual protocols. Proceed directly to [creating queues](/messaging/how-to/create-manage-queues) or [topics](/messaging/how-to/create-manage-topics) directly. \ No newline at end of file diff --git a/serverless/messaging/how-to/manage-credentials.mdx b/serverless/messaging/how-to/manage-credentials.mdx index 3437c89276..4ea9a79652 100644 --- a/serverless/messaging/how-to/manage-credentials.mdx +++ b/serverless/messaging/how-to/manage-credentials.mdx @@ -15,15 +15,15 @@ categories: Credentials give their bearer (e.g. services and platforms) access to your service. -This page shows how to manage [credentials](/serverless/messaging/concepts/#credentials) for Scaleway **NATS**, **Queues** and **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). +This page shows how to manage [credentials](/messaging/concepts/#credentials) for Scaleway **NATS**, **Queues** and **Topics and Events** (previously grouped together as the **Messaging and Queuing** product). Credentials for **Queues** and **Topics and Events** can be updated to change their permissions, or revoked. **NATS** credentials can only be revoked, not updated. Once credentials are revoked, any user trying to use the credentials to connect to the service will be denied. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Valid [credentials](/serverless/messaging/how-to/create-credentials/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Valid [credentials](/messaging/how-to/create-credentials/) ## How to update Queues or Topics and Events credentials @@ -31,7 +31,7 @@ Credentials for **Queues** and **Topics and Events** can be updated to change th 2. Click the **Credentials** tab. -3. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the credentials you want to update. +3. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the credentials you want to update. 4. Click the button next to the credentials you want to update, and select **Update credentials**. A pop-up displays, such as the one below for Queues: @@ -49,7 +49,7 @@ Credentials for **Queues** and **Topics and Events** can be updated to change th 2. Click the **Credentials** tab. -3. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the credentials you want to revoke. +3. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the credentials you want to revoke. 4. Click the button next to the credentials you want to revoke and select **Revoke**. diff --git a/serverless/messaging/how-to/monitor-mnq-cockpit.mdx b/serverless/messaging/how-to/monitor-mnq-cockpit.mdx index 25bea41266..c957711a74 100644 --- a/serverless/messaging/how-to/monitor-mnq-cockpit.mdx +++ b/serverless/messaging/how-to/monitor-mnq-cockpit.mdx @@ -13,7 +13,7 @@ dates: posted: 2023-09-07 --- -You can view metrics for your NATS, Queues, and Topics and Events services via [Scaleway Cockpit](/observability/cockpit/quickstart/). This allows you to monitor your queues/streams and messages at a glance. There are two steps to complete to view your metrics for the first time with Cockpit: +You can view metrics for your NATS, Queues, and Topics and Events services via [Scaleway Cockpit](/cockpit/quickstart/). This allows you to monitor your queues/streams and messages at a glance. There are two steps to complete to view your metrics for the first time with Cockpit: 1. Generate your Grafana credentials 2. Access the product's metrics dashboard @@ -23,16 +23,16 @@ These steps are described below. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- At least one [NATS account](/serverless/messaging/how-to/get-started/), [queue](/serverless/messaging/how-to/create-manage-queues/), or [topic](/serverless/messaging/how-to/create-manage-topics/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- At least one [NATS account](/messaging/how-to/get-started/), [queue](/messaging/how-to/create-manage-queues/), or [topic](/messaging/how-to/create-manage-topics/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to generate Grafana credentials -To view your metrics with Cockpit, you will use a Grafana dashboard which is accessible from the Scaleway console. First, you must create a user and their associated credentials (a username and password) for Grafana. This can be done directly from the Scaleway console, [by following this procedure](/observability/cockpit/how-to/retrieve-grafana-credentials/). +To view your metrics with Cockpit, you will use a Grafana dashboard which is accessible from the Scaleway console. First, you must create a user and their associated credentials (a username and password) for Grafana. This can be done directly from the Scaleway console, [by following this procedure](/cockpit/how-to/retrieve-grafana-credentials/). ## How to access your NATS, Queues, or Topics and Events dashboard and view your metrics diff --git a/serverless/messaging/index.mdx b/serverless/messaging/index.mdx index fc8a61d8d6..5d9dc55412 100644 --- a/serverless/messaging/index.mdx +++ b/serverless/messaging/index.mdx @@ -8,7 +8,7 @@ meta: productName="NATS, Queues, and Topics and Events" productLogo="sqs" description="Transfer messages between microservices and platforms with our message broker tools, facilitating the development of highly scalable, reliable, distributed applications." - url="/serverless/messaging/quickstart/" + url="/messaging/quickstart/" label="NATS, Queues, and Topics and Events Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to start using NATS, Queues, and Topics and Events" label="View Quickstart" - url="/serverless/messaging/quickstart/" + url="/messaging/quickstart/" /> diff --git a/serverless/messaging/quickstart.mdx b/serverless/messaging/quickstart.mdx index 8ee76330ce..830a68418e 100644 --- a/serverless/messaging/quickstart.mdx +++ b/serverless/messaging/quickstart.mdx @@ -13,14 +13,14 @@ categories: - serverless --- -Scaleway NATS, Queues, and Topics and Events are [message broker](/serverless/messaging/concepts/#messaging-and-queuing) tools that allows you to transfer messages between different microservices and platforms. This enables them to "talk" to each other effectively even if they are not otherwise compatible. These brokers enable and simplify microservices application development and allows you to build highly scalable, reliable, distributed applications. +Scaleway NATS, Queues, and Topics and Events are [message broker](/messaging/concepts/#messaging-and-queuing) tools that allows you to transfer messages between different microservices and platforms. This enables them to "talk" to each other effectively even if they are not otherwise compatible. These brokers enable and simplify microservices application development and allows you to build highly scalable, reliable, distributed applications. NATS, Queues, and Topics and Events were previously grouped together as the Messaging and Queuing product, and have now become three separate products in their own right. Read on to learn how to get started with your product of choice - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Quickstart for NATS @@ -49,7 +49,7 @@ Credentials for NATS accounts are not granular: they necessarily give full read 1. Click **NATS** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the NATS account for which you want to create credentials. The list of your NATS accounts in the pre-selected region displays. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the NATS account for which you want to create credentials. The list of your NATS accounts in the pre-selected region displays. 3. Click the NATS account you want to generate credentials for. The account's **Overview** page displays. @@ -73,13 +73,13 @@ Credentials for NATS accounts are not granular: they necessarily give full read ### How to create and manage queues, messages and streams -All further actions related to publishing, processing and managing messages, subjects, queues and streams can be done via a supported CLI or SDK. See our documentation on [NATS CLI and SDKs](/serverless/messaging/reference-content/nats-overview/#further-actions-nats-cli-and-nats-sdk) for more information. You can also check out our tutorial on [creating a serverless architecture for handling large messages](/tutorials/large-messages/) with Scaleway Messaging and Queuing NATS. +All further actions related to publishing, processing and managing messages, subjects, queues and streams can be done via a supported CLI or SDK. See our documentation on [NATS CLI and SDKs](/messaging/reference-content/nats-overview/#further-actions-nats-cli-and-nats-sdk) for more information. You can also check out our tutorial on [creating a serverless architecture for handling large messages](/tutorials/large-messages/) with Scaleway Messaging and Queuing NATS. ### How to delete a NATS account 1. Click **NATS** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the NATS account you want to delete. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the NATS account you want to delete. 3. Click the NATS account you want to delete. @@ -129,7 +129,7 @@ Credentials for Queues are granular: you can define the level of access that the 2. Click **Create queue**. The queue creation wizard displays. -3. Select the [region](/serverless/messaging/concepts/#region) in which you want to create the queue. +3. Select the [region](/messaging/concepts/#region) in which you want to create the queue. 4. Enter a **name** for your queue. The name must be no more than 80 characters, and consist only of alphanumeric characters, hyphens, and underscores. Alternatively, you can go with the auto-generated name suggested for you. @@ -149,7 +149,7 @@ You are returned to the **Queues** tab, where your newly-created queue now displ ### How to send and receive messages -All further actions related to sending messages to queues can be done via a supported CLI or SDK. See our documentation on the [SQS CLI and SDKs](/serverless/messaging/reference-content/sqs-overview#further-actions) for more information. You can also check out [our tutorial](/tutorials/create-serverless-scraping/) on creating a serverless scraping architecture with Scaleway Queues. +All further actions related to sending messages to queues can be done via a supported CLI or SDK. See our documentation on the [SQS CLI and SDKs](/messaging/reference-content/sqs-overview#further-actions) for more information. You can also check out [our tutorial](/tutorials/create-serverless-scraping/) on creating a serverless scraping architecture with Scaleway Queues. ### How to delete a queue @@ -157,7 +157,7 @@ When you no longer want a queue, you can delete it. This action is irreversible 1. Click **Queues** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) of the queue you want to configure. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) of the queue you want to configure. 3. Either: - Click the queue you wish to delete. The queue's **Settings** page displays. Click the **Delete queue** button in the bottom right corner. @@ -213,7 +213,7 @@ Credentials for Topics and Events are granular: you can define the level of acce 5. Choose a **topic type**. The following topic types are available: - **Standard**: Ensures at-least-once message delivery, where the order of messages is not preserved. Supports Serverless Functions, Serverless Containers and HTTP/S subscriptions. - - **FIFO**: Provides first-in-first-out delivery, where the order of messages is preserved without duplication. Supports Scaleway Queues subscriptions. [Content-based deduplication](/serverless/messaging/concepts/#content-based-deduplication) is only available for FIFO topics. + - **FIFO**: Provides first-in-first-out delivery, where the order of messages is preserved without duplication. Supports Scaleway Queues subscriptions. [Content-based deduplication](/messaging/concepts/#content-based-deduplication) is only available for FIFO topics. 6. Click **Create topic** to finish. @@ -223,7 +223,7 @@ You are returned to the **Topics** tab, where your newly-created topic now displ 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. -2. Use the dropdown menu to select the [region](/serverless/messaging/concepts/#region) of the topic you want to create a subscription for. +2. Use the dropdown menu to select the [region](/messaging/concepts/#region) of the topic you want to create a subscription for. 3. Click the name of the topic you want to create a subscription for. @@ -243,7 +243,7 @@ You are returned to the **Topics** tab, where your newly-created topic now displ You are prompted to enter the URL of the HTTP endpoint to subscribe, e.g. `example.com`. Note that the scheme (`http://`) is not required. - After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). + After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). @@ -252,32 +252,32 @@ You are returned to the **Topics** tab, where your newly-created topic now displ You are prompted to enter the URL of the HTTP endpoint to subscribe, e.g. `example.com`. Note that the scheme (`https://`) is not required. - After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). + After your HTTP subscription is created, you must confirm it. Find out how in our [dedicated documentation](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription).
Choose **Serverless Functions and Containers** to create a subscription for a Scaleway Serverless Function or Container that you have created. - You are prompted to select the **namespace** containing the Function or Container that you want to subscribe. Only namespaces in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](/serverless/messaging/concepts/#region) as the topic can be selected. + You are prompted to select the **namespace** containing the Function or Container that you want to subscribe. Only namespaces in the same [Project](/organizations-and-projects/concepts/#project) and [region](/messaging/concepts/#region) as the topic can be selected. - You are prompted to select the Serverless Function or Container to subscribe. Only Functions and Containers with a public [privacy policy](/serverless/functions/concepts/#privacy-policy) can subscribe to a topic. + You are prompted to select the Serverless Function or Container to subscribe. Only Functions and Containers with a public [privacy policy](/serverless-functions/concepts/#privacy-policy) can subscribe to a topic.
Choose **Queues** to create a subscription for a Scaleway queue that you have created. - You are prompted to select the **queue** to subscribe. Only queues in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) and [region](/serverless/messaging/concepts/#region) as the topic can be selected. + You are prompted to select the **queue** to subscribe. Only queues in the same [Project](/organizations-and-projects/concepts/#project) and [region](/messaging/concepts/#region) as the topic can be selected. 7. Click **Create subscription** to finish. - The subscription is created. If you created an HTTP or HTTPS subscription, you will now need to [confirm it](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). + The subscription is created. If you created an HTTP or HTTPS subscription, you will now need to [confirm it](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription). ### How to publish messages -All further actions related to publishing messages to topics can be done via a supported CLI or SDK. See our documentation on the [SNS CLI and SDKs](/serverless/messaging/reference-content/sns-overview#further-actions)for more information. +All further actions related to publishing messages to topics can be done via a supported CLI or SDK. See our documentation on the [SNS CLI and SDKs](/messaging/reference-content/sns-overview#further-actions)for more information. ### How to delete a topic @@ -285,7 +285,7 @@ When you no longer want a topic, you can delete it. This action is irreversible 1. Click **Topics and Events** in the **Serverless** section of the Scaleway console side menu. -2. Use the drop-down menu to select the [region](/serverless/messaging/concepts/#region) containing the topic you want to delete. +2. Use the drop-down menu to select the [region](/messaging/concepts/#region) containing the topic you want to delete. 3. Either: - Click the topic you wish to delete, and navigate to its **Settings** page. Click the **Delete topic** button in the bottom right corner, or diff --git a/serverless/messaging/reference-content/limitations.mdx b/serverless/messaging/reference-content/limitations.mdx index 05f03cfb75..46e09224e4 100644 --- a/serverless/messaging/reference-content/limitations.mdx +++ b/serverless/messaging/reference-content/limitations.mdx @@ -16,8 +16,8 @@ categories: ## Usage limits -For the usage limits that apply when using Scaleway NATS, Queues, and Topics and Events, see the dedicated sections on our [Organization quotas](/identity-and-access-management/organizations-and-projects/additional-content/organization-quotas/) page. Limits (quotas) apply to, for example, the maximum number of queues, streams, topics and consumers/subscribers, as well as to message retention duration and storage. +For the usage limits that apply when using Scaleway NATS, Queues, and Topics and Events, see the dedicated sections on our [Organization quotas](/organizations-and-projects/additional-content/organization-quotas/) page. Limits (quotas) apply to, for example, the maximum number of queues, streams, topics and consumers/subscribers, as well as to message retention duration and storage. ## VPC -NATS, Queues, and Topics and Events are not currently compatible with [Scaleway VPC](https://www.scaleway.com/en/docs/network/vpc/quickstart/). +NATS, Queues, and Topics and Events are not currently compatible with [Scaleway VPC](https://www.scaleway.com/en/docs/vpc/quickstart/). diff --git a/serverless/messaging/reference-content/nats-overview.mdx b/serverless/messaging/reference-content/nats-overview.mdx index 6f0b576664..eeb9abb6e8 100644 --- a/serverless/messaging/reference-content/nats-overview.mdx +++ b/serverless/messaging/reference-content/nats-overview.mdx @@ -15,7 +15,7 @@ dates: ## What is NATS? -NATS (**N**eural **A**utonomic **T**ransport **S**ystem) is a messaging system that aims to be simple to use, scalable and provide high performance. It implements a [publish/subscribe](/serverless/messaging/concepts/#publishsubscribe) model as well as adding a [streaming](/serverless/messaging/concepts/#stream) service via [JetStream](https://docs.nats.io/nats-concepts/jetstream). A stream is a persistent, time-ordered list of messages which can be read sequentially by consumers. A consumer can be thought of as a "cursor" in the stream, consuming the stream's messages according to their "subject filter" or "replay policy". With NATS, you would typically implement a [queue](/serverless/messaging/concepts/#queuing) as a stream with a single consumer to read from. +NATS (**N**eural **A**utonomic **T**ransport **S**ystem) is a messaging system that aims to be simple to use, scalable and provide high performance. It implements a [publish/subscribe](/messaging/concepts/#publishsubscribe) model as well as adding a [streaming](/messaging/concepts/#stream) service via [JetStream](https://docs.nats.io/nats-concepts/jetstream). A stream is a persistent, time-ordered list of messages which can be read sequentially by consumers. A consumer can be thought of as a "cursor" in the stream, consuming the stream's messages according to their "subject filter" or "replay policy". With NATS, you would typically implement a [queue](/messaging/concepts/#queuing) as a stream with a single consumer to read from. NATS is a [Cloud Native Computing Foundation](https://www.cncf.io/) project supported by a strong community, and can also be integrated in a Kubernetes cluster. @@ -29,7 +29,7 @@ You can easily create a NATS account from the [Scaleway console](https://console ## NATS credentials -When you create your NATS account, you next need to [create credentials](/serverless/messaging/how-to/create-credentials/). On the NATS side, these credentials are the equivalent of a 'user'. We use the most secure connection type offered by NATS: [NKeys](https://docs.nats.io/running-a-nats-service/configuration/securing_nats/auth_intro/nkey_auth). NKeys are a public-key signature system based on [Ed25519](https://ed25519.cr.yp.to/). +When you create your NATS account, you next need to [create credentials](/messaging/how-to/create-credentials/). On the NATS side, these credentials are the equivalent of a 'user'. We use the most secure connection type offered by NATS: [NKeys](https://docs.nats.io/running-a-nats-service/configuration/securing_nats/auth_intro/nkey_auth). NKeys are a public-key signature system based on [Ed25519](https://ed25519.cr.yp.to/). Your credentials are provided in the form of a downloadable `.creds` file. Each set of credentials gives you full access to your NATS account, but does not enable you to generate new users with specific rights or fine-grained permissions. @@ -41,7 +41,7 @@ Note that the Scaleway NATS server is configured with TLS, and as such will requ ### NATS CLI -The [NATS CLI](https://docs.nats.io/using-nats/nats-tools/nats_cli) is a great tool for administrating or testing your subjects and streams. See our [dedicated documentation](/serverless/messaging/api-cli/nats-cli/) for help getting started with the NATS CLI. +The [NATS CLI](https://docs.nats.io/using-nats/nats-tools/nats_cli) is a great tool for administrating or testing your subjects and streams. See our [dedicated documentation](/messaging/api-cli/nats-cli/) for help getting started with the NATS CLI. ### NATS SDK diff --git a/serverless/messaging/reference-content/sns-overview.mdx b/serverless/messaging/reference-content/sns-overview.mdx index 7eea580145..d862ff1182 100644 --- a/serverless/messaging/reference-content/sns-overview.mdx +++ b/serverless/messaging/reference-content/sns-overview.mdx @@ -21,22 +21,22 @@ Scaleway Topics and Events is a managed messaging service that facilitates the s SNS is a managed messaging service developed by AWS and leveraged by Scaleway Topics and Events. -SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/serverless/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/serverless/messaging/concepts#topic), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Topics and Events makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway. +SNS (Simple Notification Service) was released in 2010. It enables users to interconnect their applications and systems using a [publish/subscribe](/messaging/concepts#publishsubscribe) pattern. Many publishers can send messages to [topics](/messaging/concepts#topic), while consumers, e.g. applications, can subscribe to topics to receive all (or a subset) of messages sent to this topic. Scaleway Topics and Events makes it easy to migrate your SNS-connected applications by providing a dedicated protocol gateway. Some SNS features are not yet available with Scaleway Topics and Events. Supported subscribers are currently limited to: - HTTP/S clients - [Serverless Functions](https://www.scaleway.com/en/serverless-functions/) - - Scaleway queues in the same [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) + - 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. ## Topics and Events credentials -You must [create credentials](/serverless/messaging/how-to/create-credentials/) that give your applications permission to connect to the Scaleway Topics and Events service. +You must [create credentials](/messaging/how-to/create-credentials/) that give your applications permission to connect to the Scaleway Topics and Events service. -Credentials are scoped to your Topics and Events service at [Project](/identity-and-access-management/organizations-and-projects/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions: +Credentials are scoped to your Topics and Events service at [Project](/organizations-and-projects/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions: - **Read**: receive messages from queues and topics. - **Write**: send messages to queues and publish in topics. @@ -44,11 +44,11 @@ Credentials are scoped to your Topics and Events service at [Project](/identity- ## Topics and subscriptions -You can [create topics](/serverless/messaging/how-to/create-manage-topics/) and [subscriptions](/serverless/messaging/how-to/create-manage-subscriptions/) via the Scaleway console. +You can [create topics](/messaging/how-to/create-manage-topics/) and [subscriptions](/messaging/how-to/create-manage-subscriptions/) via the Scaleway console. ## Further actions -All further actions such as sending messages etc. can be done using the AWS CLI or AWS SDKs. Check out our documentation to help you get started with the [AWS CLI](/serverless/messaging/api-cli/connect-aws-cli/) or [AWS SDKs](/serverless/messaging/api-cli/python-node-sqs/). +All further actions such as sending messages etc. can be done using the AWS CLI or AWS SDKs. Check out our documentation to help you get started with the [AWS CLI](/messaging/api-cli/connect-aws-cli/) or [AWS SDKs](/messaging/api-cli/python-node-sqs/). ## Topics and Events Resources @@ -56,7 +56,7 @@ The following resources may be helpful: - [Official SNS Documentation](https://docs.aws.amazon.com/sns/latest/dg/welcome.html) - Further information on supported API features: - - [SNS](/serverless/messaging/reference-content/sns-support/) + - [SNS](/messaging/reference-content/sns-support/) - [Creating a simulated CPU monitor notification system with Scaleway Topics and Events](/tutorials/sns-instances-notification-system/) - [Official AWS CLI Documentation](https://aws.amazon.com/cli/) - [Official AWS SDK Documentation](https://aws.amazon.com/developer/tools/) \ No newline at end of file diff --git a/serverless/messaging/reference-content/sqs-overview.mdx b/serverless/messaging/reference-content/sqs-overview.mdx index a640ff3e87..ea66b88507 100644 --- a/serverless/messaging/reference-content/sqs-overview.mdx +++ b/serverless/messaging/reference-content/sqs-overview.mdx @@ -21,17 +21,17 @@ Scaleway Queues is a managed message queuing service that enables decoupling of SQS is a managed messaging service developed by AWS and leveraged by Scaleway Queues. -SQS (Simple Queue Service) became generally available in 2006. It is a highly scalable [queuing](/serverless/messaging/concepts#queuing) service that facilitates the decoupling of software systems. Scaleway Queues provides a gateway that enables you to connect your existing applications without having to significantly modify your code baseline. +SQS (Simple Queue Service) became generally available in 2006. It is a highly scalable [queuing](/messaging/concepts#queuing) service that facilitates the decoupling of software systems. Scaleway Queues provides a gateway that enables you to connect your existing applications without having to significantly modify your code baseline. - Some SQS features are not yet supported. Refer to our [dedicated documentation page](/serverless/messaging/reference-content/sqs-support/) for more information. + Some SQS features are not yet supported. Refer to our [dedicated documentation page](/messaging/reference-content/sqs-support/) for more information. ## Scaleway Queues credentials -You must [create credentials](/serverless/messaging/how-to/create-credentials/) to give your applications permission to connect to the Scaleway Queues service. +You must [create credentials](/messaging/how-to/create-credentials/) to give your applications permission to connect to the Scaleway Queues service. -Credentials are scoped to your Scaleway Queues service at [Project](/identity-and-access-management/organizations-and-projects/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions: +Credentials are scoped to your Scaleway Queues service at [Project](/organizations-and-projects/concepts/#project)-level. You can choose to give each set of credentials the required level of permissions: - **Read**: receive messages from queues and topics. - **Write**: send messages to queues and publish in topics. @@ -39,11 +39,11 @@ Credentials are scoped to your Scaleway Queues service at [Project](/identity-an ## Queues -You can [create queues](/serverless/messaging/how-to/create-manage-queues/) via the Scaleway console. You can choose to create either a Standard or FIFO queue, and tweak parameters such as visibility timeout, message retention period, maximum message size and content based deduplication. +You can [create queues](/messaging/how-to/create-manage-queues/) via the Scaleway console. You can choose to create either a Standard or FIFO queue, and tweak parameters such as visibility timeout, message retention period, maximum message size and content based deduplication. ## Further actions -All further actions such as sending messages can be done using the AWS CLI or AWS SDKs. Check out our documentation to help you get started with the [AWS CLI](/serverless/messaging/api-cli/connect-aws-cli/) or [AWS SDKs](/serverless/messaging/api-cli/python-node-sqs/). +All further actions such as sending messages can be done using the AWS CLI or AWS SDKs. Check out our documentation to help you get started with the [AWS CLI](/messaging/api-cli/connect-aws-cli/) or [AWS SDKs](/messaging/api-cli/python-node-sqs/). ## Queue resources @@ -52,6 +52,6 @@ The following resources may be helpful: - [How to create a serverless scraping architecture, with Scaleway Queues, Serverless Functions and Managed Database](/tutorials/create-serverless-scraping/) - [Official SQS Documentation](https://docs.aws.amazon.com/sqs/index.html) - Further information on supported API features: - - [SQS](/serverless/messaging/reference-content/sqs-support/) + - [SQS](/messaging/reference-content/sqs-support/) - [Official AWS CLI Documentation](https://aws.amazon.com/cli/) - [Official AWS SDK Documentation](https://aws.amazon.com/developer/tools/) \ No newline at end of file diff --git a/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx b/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx index 7470259b4f..58663ecc4b 100644 --- a/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx +++ b/serverless/sql-databases/api-cli/import-data-to-serverless-sql-databases.mdx @@ -20,8 +20,8 @@ The methods listed below are best suited for database sizes below 100 GB (approx - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a target Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) to import your data into. +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a target Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) to import your data into. - Checked that the target database you are importing data into is empty, or contains data you can overwrite. The import procedure depends on your data source: @@ -70,10 +70,10 @@ To complete this procedure, you must have installed PostgreSQL 16 (or newer) wit 4. Enter the database password when prompted. - The password is the [IAM secret key](/identity-and-access-management/iam/concepts/#api-key) corresponding to the [IAM user](/identity-and-access-management/iam/concepts/#user) or [IAM application](/identity-and-access-management/iam/concepts/#application) you are connecting with. + The password is the [IAM secret key](/iam/concepts/#api-key) corresponding to the [IAM user](/iam/concepts/#user) or [IAM application](/iam/concepts/#application) you are connecting with. -5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. +5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless-sql-databases/how-to/connect-to-a-database/), and performing a query. ### Using pgAdmin @@ -103,7 +103,7 @@ To complete this procedure, you must have: #### Loading your data in your Serverless SQL Database -1. Register your new database in pgAdmin. Refer to the [How to connect to a Serverless SQL Database](/serverless/sql-databases/how-to/connect-to-a-database/#how-to-set-up-credentials) documentation page for more information. +1. Register your new database in pgAdmin. Refer to the [How to connect to a Serverless SQL Database](/serverless-sql-databases/how-to/connect-to-a-database/#how-to-set-up-credentials) documentation page for more information. 2. Connect to your database server by selecting it in the left-hand menu. @@ -123,7 +123,7 @@ To complete this procedure, you must have: 8. Click **Restore**. The restore process starts, and you can follow its progress by clicking **View processes**. -9. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. +9. When finished, make sure your data is stored in your new database by [connecting to it](/serverless-sql-databases/how-to/connect-to-a-database/), and performing a query. If the process fails and some data was already partly transferred, we suggest that you activate the **Clean before restore** option in the **Data options** tab to remove partly transferred data. @@ -146,10 +146,10 @@ To complete this procedure, you must have: ``` - You can find this information on the [overview page](https://console.scaleway.com/serverless-db/databases) of your database. The password is the [IAM secret Key](/identity-and-access-management/iam/concepts/#api-key) corresponding to the [IAM user](/identity-and-access-management/iam/concepts/#user) or [IAM application](/identity-and-access-management/iam/concepts/#application) you are connecting with. + You can find this information on the [overview page](https://console.scaleway.com/serverless-db/databases) of your database. The password is the [IAM secret Key](/iam/concepts/#api-key) corresponding to the [IAM user](/iam/concepts/#user) or [IAM application](/iam/concepts/#application) you are connecting with. -2. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. +2. When finished, make sure your data is stored in your new database by [connecting to it](/serverless-sql-databases/how-to/connect-to-a-database/), and performing a query. ## Import Data from a file (.csv, .txt, etc.) @@ -184,7 +184,7 @@ You can create a `.csv` file from an existing PostgreSQL table with the [psql \c ``` - You can find this information on the [overview page](https://console.scaleway.com/serverless-db/databases) of your database. The password is the [IAM secret key](/identity-and-access-management/iam/concepts/#api-key) corresponding to the [IAM user](/identity-and-access-management/iam/concepts/#user) or [IAM application](/identity-and-access-management/iam/concepts/#application) you are connecting with. + You can find this information on the [overview page](https://console.scaleway.com/serverless-db/databases) of your database. The password is the [IAM secret key](/iam/concepts/#api-key) corresponding to the [IAM user](/iam/concepts/#user) or [IAM application](/iam/concepts/#application) you are connecting with. 3. Create the table structure corresponding to your file column types: @@ -203,4 +203,4 @@ You can create a `.csv` file from an existing PostgreSQL table with the [psql \c The PostgreSQL [COPY command](https://www.postgresql.org/docs/current/sql-copy.html) cannot be used directly, as it requires the source file to be available on the PostgreSQL instance itself. -5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless/sql-databases/how-to/connect-to-a-database/), and performing a query. +5. When finished, make sure your data is stored in your new database by [connecting to it](/serverless-sql-databases/how-to/connect-to-a-database/), and performing a query. diff --git a/serverless/sql-databases/api-cli/postgrest-row-level-security.mdx b/serverless/sql-databases/api-cli/postgrest-row-level-security.mdx index 5b87e51272..a9f0f08994 100644 --- a/serverless/sql-databases/api-cli/postgrest-row-level-security.mdx +++ b/serverless/sql-databases/api-cli/postgrest-row-level-security.mdx @@ -22,12 +22,12 @@ Due to connection pooling, Serverless SQL Databases currently only support trans - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) ## How to add sample data and enable PostgreSQL Row Level Security -1. [Connect to your Serverless SQL Database](/serverless/sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client such as `psql`: +1. [Connect to your Serverless SQL Database](/serverless-sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client such as `psql`: ```bash psql "postgres://[user-or-application-id]:[api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require" ``` @@ -74,7 +74,7 @@ Due to connection pooling, Serverless SQL Databases currently only support trans ``` Where: - - `db-uri` must use credentials with an [application](/identity-and-access-management/iam/how-to/create-application/) having **ServerlessSQLDatabaseDataReadWrite** permissions (not **ServerlessSQLDatabaseReadWrite** or **ServerlessSQLDatabaseFullAccess**) + - `db-uri` must use credentials with an [application](/iam/how-to/create-application/) having **ServerlessSQLDatabaseDataReadWrite** permissions (not **ServerlessSQLDatabaseReadWrite** or **ServerlessSQLDatabaseFullAccess**) - `db-schemas` is your database schema. Use `public` as a default value. - `jwt-secret` is a token generated using the following command: ```sh diff --git a/serverless/sql-databases/concepts.mdx b/serverless/sql-databases/concepts.mdx index 53ac215746..4e5ffb2374 100644 --- a/serverless/sql-databases/concepts.mdx +++ b/serverless/sql-databases/concepts.mdx @@ -34,7 +34,7 @@ Connection pooling is the process of mutualizing client connections used to conn ## Credentials -Credentials are the login and password (also called "username" and "password" in PostgreSQL vocabulary) used by a user, or an application to connect to a database. With Scaleway Serverless SQL Databases, logins are [IAM principal IDs](/identity-and-access-management/iam/concepts/#principal) and passwords are [IAM secret keys](/identity-and-access-management/iam/concepts/#api-key). +Credentials are the login and password (also called "username" and "password" in PostgreSQL vocabulary) used by a user, or an application to connect to a database. With Scaleway Serverless SQL Databases, logins are [IAM principal IDs](/iam/concepts/#principal) and passwords are [IAM secret keys](/iam/concepts/#api-key). ## Database engine diff --git a/serverless/sql-databases/how-to/add-users.mdx b/serverless/sql-databases/how-to/add-users.mdx index 1febf18ec7..820befdd4e 100644 --- a/serverless/sql-databases/how-to/add-users.mdx +++ b/serverless/sql-databases/how-to/add-users.mdx @@ -18,10 +18,10 @@ Users and applications can connect to a database and access its data. Each one c - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) -- [Created a policy to manage users' permissions](/serverless/sql-databases/how-to/manage-permissions/) -- [Invited a user to your Organization](/identity-and-access-management/iam/how-to/invite-user-to-orga/) or [created an application](/identity-and-access-management/iam/how-to/create-application/) in IAM +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) +- [Created a policy to manage users' permissions](/serverless-sql-databases/how-to/manage-permissions/) +- [Invited a user to your Organization](/iam/how-to/invite-user-to-orga/) or [created an application](/iam/how-to/create-application/) in IAM ## How to add a user to a Serverless SQL Database @@ -36,7 +36,7 @@ Users and applications can connect to a database and access its data. Each one c 5. Choose **Select an unassigned policy**, then, select the previously created policy from the drop-down menu. - You can also [create a new policy](/serverless/sql-databases/how-to/manage-permissions/) or duplicate an existing one to manage the permissions of a user. + You can also [create a new policy](/serverless-sql-databases/how-to/manage-permissions/) or duplicate an existing one to manage the permissions of a user. 6. Click **Validate**. @@ -56,7 +56,7 @@ Users and applications can connect to a database and access its data. Each one c 6. Choose **Select an unassigned policy**, then, select the previously created policy from the drop-down menu. - You can also [create a new policy](/serverless/sql-databases/how-to/manage-permissions/) or duplicate an existing one to manage the permissions of an application. + You can also [create a new policy](/serverless-sql-databases/how-to/manage-permissions/) or duplicate an existing one to manage the permissions of an application. 7. Click **Validate**. diff --git a/serverless/sql-databases/how-to/configure-autoscaling.mdx b/serverless/sql-databases/how-to/configure-autoscaling.mdx index 00b1c6a2eb..dcc7194a28 100644 --- a/serverless/sql-databases/how-to/configure-autoscaling.mdx +++ b/serverless/sql-databases/how-to/configure-autoscaling.mdx @@ -18,8 +18,8 @@ This page shows you how to edit the autoscaling of a Serverless SQL Database usi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a database](/serverless-sql-databases/how-to/create-a-database/) 1. Click **SQL Databases** in the **Serverless** section of the side menu. The Serverless SQL Databases page displays. diff --git a/serverless/sql-databases/how-to/connect-to-a-database.mdx b/serverless/sql-databases/how-to/connect-to-a-database.mdx index 940d2aa14e..0cf181ea69 100644 --- a/serverless/sql-databases/how-to/connect-to-a-database.mdx +++ b/serverless/sql-databases/how-to/connect-to-a-database.mdx @@ -19,15 +19,15 @@ This page shows you how to set up the connection to a Serverless SQL Database us To connect to a Serverless SQL Database, you can either use a **connection string**, or **connection parameters**. - - A connection string provides the necessary information and parameters to establish a connection between an [IAM user](/identity-and-access-management/iam/concepts/#user) or [application](/identity-and-access-management/iam/concepts/#application) and the database. The string is written as follows: + - A connection string provides the necessary information and parameters to establish a connection between an [IAM user](/iam/concepts/#user) or [application](/iam/concepts/#application) and the database. The string is written as follows: ```sh postgres://[user-or-application-id]:[api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require ``` - The `?sslmode=require` is mandatory to connect to your database. Refer to the [dedicated documentation](/serverless/sql-databases/api-cli/secure-connection-ssl-tls/) for more information about SSL connection to Serverless SQL Databases. + The `?sslmode=require` is mandatory to connect to your database. Refer to the [dedicated documentation](/serverless-sql-databases/api-cli/secure-connection-ssl-tls/) for more information about SSL connection to Serverless SQL Databases. - - Connection parameters provide the necessary information and parameters to connect an [IAM user](/identity-and-access-management/iam/concepts/#user) or [application](/identity-and-access-management/iam/concepts/#application) to a database. The parameters are expressed in the `KEY="value"` format, as follows: + - Connection parameters provide the necessary information and parameters to connect an [IAM user](/iam/concepts/#user) or [application](/iam/concepts/#application) to a database. The parameters are expressed in the `KEY="value"` format, as follows: ```sh PGUSER="user-or-application-id" @@ -38,30 +38,30 @@ To connect to a Serverless SQL Database, you can either use a **connection strin ``` - The `PGSSLMODE="require"` parameter is required to connect to your database, but can be omitted as it is provided by default by most SQL clients. Refer to the [dedicated documentation](/serverless/sql-databases/api-cli/secure-connection-ssl-tls/) for more information about SSL connection to Serverless SQL Databases. + The `PGSSLMODE="require"` parameter is required to connect to your database, but can be omitted as it is provided by default by most SQL clients. Refer to the [dedicated documentation](/serverless-sql-databases/api-cli/secure-connection-ssl-tls/) for more information about SSL connection to Serverless SQL Databases. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) ## How to set up credentials 1. From the **Overview** tab of your database, click the **Set up credentials** button. The setup wizard displays. -2. Select the [principal](/identity-and-access-management/iam/concepts/#principal) to connect to the database, who can be either: - - Yourself, as an [IAM user](/identity-and-access-management/iam/concepts/#user), or - - An [IAM application](/identity-and-access-management/iam/concepts/#application) you [previously created](/identity-and-access-management/iam/how-to/create-application/) in the IAM section of the console. +2. Select the [principal](/iam/concepts/#principal) to connect to the database, who can be either: + - Yourself, as an [IAM user](/iam/concepts/#user), or + - An [IAM application](/iam/concepts/#application) you [previously created](/iam/how-to/create-application/) in the IAM section of the console. - Refer to the [IAM documentation](/identity-and-access-management/iam/reference-content/overview/) for more information on identities and access rights. + Refer to the [IAM documentation](/iam/reference-content/overview/) for more information on identities and access rights. 3. Set up the **connection string** or **connection parameters**.
- If you already have an [API secret key](/identity-and-access-management/iam/concepts/#api-key), replace the `[INSERT_SECRET_KEY_HERE]` placeholder with your **secret key** as shown below. + If you already have an [API secret key](/iam/concepts/#api-key), replace the `[INSERT_SECRET_KEY_HERE]` placeholder with your **secret key** as shown below. - Connection string: ``` postgresql://example-user-4052-8739-2017c3d9c0d9:example-secret-key-3fd8f53210ec@example-host-4d89-8e7d-g56vb754.pg.sdb.fr-par.scw.cloud:5432/serverless-sqldb-example-db?sslmode=require @@ -77,7 +77,7 @@ To connect to a Serverless SQL Database, you can either use a **connection strin
- If you do not have an [API secret key](/identity-and-access-management/iam/concepts/#api-key), click **Generate new secret key**. + If you do not have an [API secret key](/iam/concepts/#api-key), click **Generate new secret key**. A new secret key is created, and inserted directly into the connection string and parameters. @@ -122,9 +122,9 @@ You can now perform the authorized actions in the database. Use the connection parameters (host, port, user, password, and database name) previously saved to connect your application to the database. - Connection methods may vary depending on the framework or library used in your application. Refer to our [dedicated documentation](/serverless/sql-databases/api-cli/secure-connection-ssl-tls/) on securing connections with SSL/TLS, and to the corresponding official documentation for more information. + Connection methods may vary depending on the framework or library used in your application. Refer to our [dedicated documentation](/serverless-sql-databases/api-cli/secure-connection-ssl-tls/) on securing connections with SSL/TLS, and to the corresponding official documentation for more information. ## Troubleshooting -Refer to the [dedicated troubleshooting page](/serverless/sql-databases/troubleshooting/connection-errors/) to solve connection issues with Serverless SQL Databases. \ No newline at end of file +Refer to the [dedicated troubleshooting page](/serverless-sql-databases/troubleshooting/connection-errors/) to solve connection issues with Serverless SQL Databases. \ No newline at end of file diff --git a/serverless/sql-databases/how-to/create-a-database.mdx b/serverless/sql-databases/how-to/create-a-database.mdx index 10313a47b5..56681552a0 100644 --- a/serverless/sql-databases/how-to/create-a-database.mdx +++ b/serverless/sql-databases/how-to/create-a-database.mdx @@ -18,7 +18,7 @@ This page shows you how to create a Serverless SQL Database using the Scaleway c - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a database diff --git a/serverless/sql-databases/how-to/delete-a-database.mdx b/serverless/sql-databases/how-to/delete-a-database.mdx index 35f23ba236..0802cea190 100644 --- a/serverless/sql-databases/how-to/delete-a-database.mdx +++ b/serverless/sql-databases/how-to/delete-a-database.mdx @@ -18,8 +18,8 @@ This page shows you how to delete a Serverless SQL Database using the Scaleway c - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a database](/serverless-sql-databases/how-to/create-a-database/) ## How to delete a database diff --git a/serverless/sql-databases/how-to/manage-backups.mdx b/serverless/sql-databases/how-to/manage-backups.mdx index 9affadc11d..745bf6ae36 100644 --- a/serverless/sql-databases/how-to/manage-backups.mdx +++ b/serverless/sql-databases/how-to/manage-backups.mdx @@ -13,7 +13,7 @@ categories: - serverless --- -Serverless SQL Databases are automatically backed up every day at the same time. [Backups](/serverless/sql-databases/concepts/#backup) are stored for 7 days. They are useful when you need to restore a specific state of your Serverless SQL Database. You can restore a database to a previous state, create a new database from a specific backup, or export a backup in `.pg_dump` format. +Serverless SQL Databases are automatically backed up every day at the same time. [Backups](/serverless-sql-databases/concepts/#backup) are stored for 7 days. They are useful when you need to restore a specific state of your Serverless SQL Database. You can restore a database to a previous state, create a new database from a specific backup, or export a backup in `.pg_dump` format. The restore duration depends on the size of your database. Restore operations are considered as regular database activity, and are therefore billed the same way. Refer to our [dedicated FAQ](/faq/serverless-sql-databases/) for more information. @@ -22,8 +22,8 @@ Serverless SQL Databases are automatically backed up every day at the same time. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a database](/serverless-sql-databases/how-to/create-a-database/) ## How to restore a Serverless SQL Database from a backup diff --git a/serverless/sql-databases/how-to/manage-permissions.mdx b/serverless/sql-databases/how-to/manage-permissions.mdx index d682d51b6e..fd726f3b04 100644 --- a/serverless/sql-databases/how-to/manage-permissions.mdx +++ b/serverless/sql-databases/how-to/manage-permissions.mdx @@ -13,12 +13,12 @@ categories: - serverless --- -Permissions define the actions a user or an application can perform on a database. They are managed using Scaleway's [Identity and Access Management](/identity-and-access-management/iam/quickstart/) interface. +Permissions define the actions a user or an application can perform on a database. They are managed using Scaleway's [Identity and Access Management](/iam/quickstart/) interface. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization 1. Click **Identity and Access Management (IAM)** from the top-right of your [Organization Dashboard](https://console.scaleway.com/organization) in the Scaleway console. The **Users** tab of the [Identity and Access Management dashboard](https://console.scaleway.com/iam/users) displays. @@ -32,7 +32,7 @@ Permissions define the actions a user or an application can perform on a databas - Enter a **description** (optional). - - Select a **principal**, who will be the target of your policy. The [principal](/identity-and-access-management/iam/concepts/#principal) should be the user, application, or group you want to grant access to your database. + - Select a **principal**, who will be the target of your policy. The [principal](/iam/concepts/#principal) should be the user, application, or group you want to grant access to your database. - You can choose to create a policy without a principal for now, and attach the principal later. @@ -42,7 +42,7 @@ Permissions define the actions a user or an application can perform on a databas 5. Click **Add rules**. The second screen of the policy creation wizard. -6. Select **Access to resources**, then, select the [Project](/identity-and-access-management/iam/concepts/#project) in which you want the permissions to apply. +6. Select **Access to resources**, then, select the [Project](/iam/concepts/#project) in which you want the permissions to apply. 7. Click **Validate** to continue. diff --git a/serverless/sql-databases/how-to/use-row-level-security.mdx b/serverless/sql-databases/how-to/use-row-level-security.mdx index b379dfa494..ee5b347199 100644 --- a/serverless/sql-databases/how-to/use-row-level-security.mdx +++ b/serverless/sql-databases/how-to/use-row-level-security.mdx @@ -17,17 +17,17 @@ Row-Level Security is a database security mechanism that allows access only to s Row-Level Security can be activated with Serverless SQL Databases for a maximum of two different roles, having both read and write permissions. This can be used to restrict access to a subset of users with frameworks or tools such as [PostgREST](https://docs.postgrest.org/en/v12/). -This requires setting up different [IAM permissions sets](/identity-and-access-management/iam/reference-content/permission-sets/) for each role (**ServerlessSQLDatabaseFullAccess** or **ServerlessSQLDatabaseReadWrite** for one role, and **ServerlessSQLDatabaseDataReadWrite** for the other). +This requires setting up different [IAM permissions sets](/iam/reference-content/permission-sets/) for each role (**ServerlessSQLDatabaseFullAccess** or **ServerlessSQLDatabaseReadWrite** for one role, and **ServerlessSQLDatabaseDataReadWrite** for the other). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) ## How to add sample data and enable PostgreSQL Row Level Security -1. [Connect to your Serverless SQL Database](/serverless/sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client such as `psql`: +1. [Connect to your Serverless SQL Database](/serverless-sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client such as `psql`: ```bash psql "postgres://[user-or-application-id]:[api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require" ``` @@ -63,15 +63,15 @@ This requires setting up different [IAM permissions sets](/identity-and-access-m ## How to create an IAM application with Row Level Security enabled -1. Create a new [IAM application](/identity-and-access-management/iam/how-to/create-application/). +1. Create a new [IAM application](/iam/how-to/create-application/). -2. Create a new [IAM policy](/identity-and-access-management/iam/how-to/create-policy/), and add the **ServerlessSQLDatabaseDataReadWrite** permission set to the application you just created. +2. Create a new [IAM policy](/iam/how-to/create-policy/), and add the **ServerlessSQLDatabaseDataReadWrite** permission set to the application you just created. You must provide **ServerlessSQLDatabaseDataReadWrite** permission set and not **ServerlessSQLDatabaseReadWrite** permission set. Indeed, all connections to your database performed with the former permissions set will use `role_readwrite` in PostgreSQL, whereas all connections performed with the latter, or **ServerlessSQLDatabaseFullAccess** will use `role_admin` in PostgreSQL. -3. Create an [API Key](/identity-and-access-management/iam/how-to/create-api-keys/) for this application, and connect to your Serverless SQL Database with this application. +3. Create an [API Key](/iam/how-to/create-api-keys/) for this application, and connect to your Serverless SQL Database with this application. ```bash psql "postgres://[new-application-id]:[new-api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require" ``` diff --git a/serverless/sql-databases/index.mdx b/serverless/sql-databases/index.mdx index 1bf03b371a..c0086e6a90 100644 --- a/serverless/sql-databases/index.mdx +++ b/serverless/sql-databases/index.mdx @@ -8,7 +8,7 @@ meta: productName="Serverless SQL Databases" productLogo="serverlessDB" description="Serverless SQL Databases provides a fully-serverless database service for PostgreSQL with automatic backups, autoscaling, fully integrated in the Scaleway ecosystem." - url="/serverless/sql-databases/quickstart" + url="/serverless-sql-databases/quickstart" label="Serverless SQL Databases Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn how to create a Serverless SQL Database in a few steps." label="View Quickstart" - url="/serverless/sql-databases/quickstart/" + url="/serverless-sql-databases/quickstart/" /> diff --git a/serverless/sql-databases/quickstart.mdx b/serverless/sql-databases/quickstart.mdx index 1cde49fac7..ff14f298d3 100644 --- a/serverless/sql-databases/quickstart.mdx +++ b/serverless/sql-databases/quickstart.mdx @@ -20,7 +20,7 @@ This page explains how to create, access, and delete a Serverless SQL Database u - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed the [psql CLI tool](https://www.postgresql.org/docs/14/app-psql.html) (built-in with [PostgreSQL](https://www.postgresql.org/download/)). ## How to create a database @@ -44,10 +44,10 @@ This page explains how to create, access, and delete a Serverless SQL Database u 1. From the **Overview** tab of your database, click the **Set up credentials** button. The setup wizard displays. -2. Select yourself as the [principal](/identity-and-access-management/iam/concepts/#principal) to connect to the database. +2. Select yourself as the [principal](/iam/concepts/#principal) to connect to the database. - Refer to the [IAM documentation](/identity-and-access-management/iam/reference-content/overview/) for more information on identities and access rights. + Refer to the [IAM documentation](/iam/reference-content/overview/) for more information on identities and access rights. 3. Set up the **Connection string**: diff --git a/serverless/sql-databases/reference-content/known-differences.mdx b/serverless/sql-databases/reference-content/known-differences.mdx index 3e38a9b89d..d89f764b5d 100644 --- a/serverless/sql-databases/reference-content/known-differences.mdx +++ b/serverless/sql-databases/reference-content/known-differences.mdx @@ -15,11 +15,11 @@ categories: Serverless SQL Database is based on PostgreSQL engine and thus provides standard PostgreSQL compatibility for most PostgreSQL features and commands. Due to the nature of a managed service, autoscaling support and connection pooling support, some features are not currently supported. This means either the corresponding SQL command will not be authorized, or will not behave similarly to a standard PostgreSQL instance. -If you require strict compatibility with all PostgreSQL features, you can use [Managed Databases for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) instead. +If you require strict compatibility with all PostgreSQL features, you can use [Managed Databases for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) instead. ## Unsupported PostgreSQL extensions -Serverless SQL Databases support the most popular PostgreSQL extensions. Refer to the [dedicated documentation](/serverless/sql-databases/reference-content/supported-postgresql-extensions/) for more information. +Serverless SQL Databases support the most popular PostgreSQL extensions. Refer to the [dedicated documentation](/serverless-sql-databases/reference-content/supported-postgresql-extensions/) for more information. ## Unsupported SQL features diff --git a/serverless/sql-databases/reference-content/planned-maintenance.mdx b/serverless/sql-databases/reference-content/planned-maintenance.mdx index 650c31b07a..85658cb964 100644 --- a/serverless/sql-databases/reference-content/planned-maintenance.mdx +++ b/serverless/sql-databases/reference-content/planned-maintenance.mdx @@ -17,7 +17,7 @@ To add features, deploy security fixes or corrective patches, we perform regular However, **some maintenance operations may impact your database availability** or require actions on your side. In this case, **we will inform you beforehand**, so you can **follow the recommendations below** to ensure that the impact on your application is minimal. -The maintenance operations particularly concern our [connection pooler](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) for now, as we are working on making it as transparent as possible in future Serverless SQL Databases updates. +The maintenance operations particularly concern our [connection pooler](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) for now, as we are working on making it as transparent as possible in future Serverless SQL Databases updates. ## Impact on your application and recommendations diff --git a/serverless/sql-databases/reference-content/serverless-sql-databases-overview.mdx b/serverless/sql-databases/reference-content/serverless-sql-databases-overview.mdx index 16d18308ca..ec6dec920f 100644 --- a/serverless/sql-databases/reference-content/serverless-sql-databases-overview.mdx +++ b/serverless/sql-databases/reference-content/serverless-sql-databases-overview.mdx @@ -55,13 +55,13 @@ Automatic scaling operations may need to happen **between** atomic transactions. ## Compatibility -Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features relying on PostgreSQL sessions and temporary data storage are disabled or may not work as expected. Check out the [known differences](/serverless/sql-databases/reference-content/known-differences/) documentation. +Serverless SQL Database is compatible with most PostgreSQL-compatible clients and tools. Due to connection pooling support, some minor features relying on PostgreSQL sessions and temporary data storage are disabled or may not work as expected. Check out the [known differences](/serverless-sql-databases/reference-content/known-differences/) documentation. -If you require strict compatibility with all PostgreSQL features, you can use [Managed Databases for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) instead. +If you require strict compatibility with all PostgreSQL features, you can use [Managed Databases for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) instead. ## Authentication and access management -Authentication and access management are handled directly through [Scaleway IAM](/identity-and-access-management/iam/concepts/) so that you can easily manage all your users and applications accesses in a single place. Refer to [How to connect to a Serverless SQL Database](/serverless/sql-databases/how-to/connect-to-a-database/) for more information. +Authentication and access management are handled directly through [Scaleway IAM](/iam/concepts/) so that you can easily manage all your users and applications accesses in a single place. Refer to [How to connect to a Serverless SQL Database](/serverless-sql-databases/how-to/connect-to-a-database/) for more information. ## Configuration requiring manual actions diff --git a/serverless/sql-databases/reference-content/supported-postgresql-extensions.mdx b/serverless/sql-databases/reference-content/supported-postgresql-extensions.mdx index 8998daab0d..2d135e7a49 100644 --- a/serverless/sql-databases/reference-content/supported-postgresql-extensions.mdx +++ b/serverless/sql-databases/reference-content/supported-postgresql-extensions.mdx @@ -18,12 +18,12 @@ Serverless SQL Databases support the most popular [PostgreSQL extensions](#insta - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Serverless SQL Database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Serverless SQL Database](/serverless-sql-databases/how-to/create-a-database/) ## Install an extension -1. [Connect to your Serverless SQL Database](/serverless/sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client (such as `psql`): +1. [Connect to your Serverless SQL Database](/serverless-sql-databases/quickstart/#how-to-connect-to-a-database) with a PostgreSQL client (such as `psql`): ```bash psql "postgres://[user-or-application-id]:[api-secret-key]@[database-hostname]:5432/[database-name]?sslmode=require" ``` @@ -80,7 +80,7 @@ The following PostgreSQL extensions are available with Serverless SQL Databases: | pgcrypto | Provides cryptographic functions for data encryption, decryption, and hashing, essential for secure data storage. | | pgrouting | Extends PostgreSQL and PostGIS with geospatial routing capabilities, enabling the calculation of shortest paths and other routing operations. | | pgrowlocks | Displays information about row-level locking, helping in the diagnosis of concurrency issues. | -| pgvector | Supports vector similarity search, often used for storing and searching embeddings in machine learning applications. [Query options](https://github.com/pgvector/pgvector?tab=readme-ov-file#query-options) using `SET` command require [to be used in a single transaction](/serverless/sql-databases/reference-content/known-differences/#unsupported-configuration-commands) (i.e. between `BEGIN; (...) COMMIT;`) | +| pgvector | Supports vector similarity search, often used for storing and searching embeddings in machine learning applications. [Query options](https://github.com/pgvector/pgvector?tab=readme-ov-file#query-options) using `SET` command require [to be used in a single transaction](/serverless-sql-databases/reference-content/known-differences/#unsupported-configuration-commands) (i.e. between `BEGIN; (...) COMMIT;`) | | plpgsql | Enables the use of PL/pgSQL, a procedural language for PostgreSQL that allows complex control structures and query manipulation. | | postgis | Adds support for geographic objects, allowing location queries to be run in SQL, and is the foundation of the geographic information system (GIS) functionality in PostgreSQL. | | postgis_raster | Implements raster data support in PostGIS, enabling analysis and storage of raster images alongside vector data. | diff --git a/serverless/sql-databases/troubleshooting/connection-errors.mdx b/serverless/sql-databases/troubleshooting/connection-errors.mdx index c17a695418..cb5a9497f9 100644 --- a/serverless/sql-databases/troubleshooting/connection-errors.mdx +++ b/serverless/sql-databases/troubleshooting/connection-errors.mdx @@ -43,11 +43,11 @@ The error message below appears when trying to connect to the Serverless SQL Dat ### Cause -The [IAM principal](/identity-and-access-management/iam/concepts/#principal) (user or application) does not have the necessary permissions to connect the database. +The [IAM principal](/iam/concepts/#principal) (user or application) does not have the necessary permissions to connect the database. ### Solution -[Create a new IAM policy](/identity-and-access-management/iam/how-to/create-policy/) or [update an existing one](/identity-and-access-management/iam/how-to/manage-policies/#how-to-edit-a-policys-rules) to grant one of the following permissions sets to the user or application: +[Create a new IAM policy](/iam/how-to/create-policy/) or [update an existing one](/iam/how-to/manage-policies/#how-to-edit-a-policys-rules) to grant one of the following permissions sets to the user or application: - `ServerlessSQLDatabaseReadOnly` - `ServerlessSQLDatabaseReadWrite` - `ServerlessSQLDatabaseFullAccess` @@ -65,11 +65,11 @@ The error messages below appear when trying to create `TEMPORARY TABLES` or `SUB ### Cause -Serverless SQL Databases do not support `TEMPORARY TABLES` or `SUBSCRIPTION` yet. Refer to the [known differences](/serverless/sql-databases/reference-content/known-differences/#unsupported-sql-features) page for more information. +Serverless SQL Databases do not support `TEMPORARY TABLES` or `SUBSCRIPTION` yet. Refer to the [known differences](/serverless-sql-databases/reference-content/known-differences/#unsupported-sql-features) page for more information. ### Solution -If you (or a third party tool you are using, especially ETL tools such as Airbyte, Fivetran or Meltano) require `TEMPORARY TABLES`, we suggest you use a [Managed Database for PostgreSQL](https://www.scaleway.com/en/database/). `SUBSCRIPTION` is not supported by Managed Databases for PostgreSQL yet, but you can [import data with ETL tools](/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/#import-data-from-a-file-csv-txt-etc). +If you (or a third party tool you are using, especially ETL tools such as Airbyte, Fivetran or Meltano) require `TEMPORARY TABLES`, we suggest you use a [Managed Database for PostgreSQL](https://www.scaleway.com/en/database/). `SUBSCRIPTION` is not supported by Managed Databases for PostgreSQL yet, but you can [import data with ETL tools](/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/#import-data-from-a-file-csv-txt-etc). ## ERROR: prepared transactions are disabled @@ -83,11 +83,11 @@ The error message below appears when trying to use `PREPARE TRANSACTION` in a Se ### Cause -Serverless SQL Databases do not support `PREPARE TRANSACTION`. Refer to the [dedicated documentation](/serverless/sql-databases/reference-content/known-differences/#unsupported-sql-features) for more information. +Serverless SQL Databases do not support `PREPARE TRANSACTION`. Refer to the [dedicated documentation](/serverless-sql-databases/reference-content/known-differences/#unsupported-sql-features) for more information. ### Solution -If you require this feature, we suggest you use a [Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/). +If you require this feature, we suggest you use a [Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/). ## ERROR: cannot refresh materialized view concurrently @@ -101,11 +101,11 @@ The error message below appears when trying to connect to the Serverless SQL Dat ### Cause -Serverless SQL Databases do not support `REFRESH MATERIALIZED VIEW CONCURRENTLY`. However, the `REFRESH MATERIALIZED VIEW` command is supported, only the `CONCURRENTLY` keyword is not supported. Refer to the [dedicated documentation](/serverless/sql-databases/reference-content/known-differences/#unsupported-sql-features) for more information. +Serverless SQL Databases do not support `REFRESH MATERIALIZED VIEW CONCURRENTLY`. However, the `REFRESH MATERIALIZED VIEW` command is supported, only the `CONCURRENTLY` keyword is not supported. Refer to the [dedicated documentation](/serverless-sql-databases/reference-content/known-differences/#unsupported-sql-features) for more information. ### Solution -If you require this feature, we suggest you use a [Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/). +If you require this feature, we suggest you use a [Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/). ## Database hostname was not sent to server @@ -123,7 +123,7 @@ This error happens when the SQL client you are using does not support the TLS Se ### Solution -- If you are using a third-party tool or library which allows you to input a connection string or optional connection parameters, add `?options=databaseid%3D{databaseid}` at the end of your [connection string](/serverless/sql-databases/how-to/connect-to-a-database/#how-to-connect-to-a-database-as-a-user): +- If you are using a third-party tool or library which allows you to input a connection string or optional connection parameters, add `?options=databaseid%3D{databaseid}` at the end of your [connection string](/serverless-sql-databases/how-to/connect-to-a-database/#how-to-connect-to-a-database-as-a-user): ``` "postgresql://{username}:{password}@{host}:5432/{databasename}?sslmode=require&options=databaseid%3D{databaseid}" ``` diff --git a/serverless/sql-databases/troubleshooting/connection-timeout.mdx b/serverless/sql-databases/troubleshooting/connection-timeout.mdx index 6d71b83530..e1f45257c0 100644 --- a/serverless/sql-databases/troubleshooting/connection-timeout.mdx +++ b/serverless/sql-databases/troubleshooting/connection-timeout.mdx @@ -14,7 +14,7 @@ categories: --- Serverless SQL Databases is based on PostgreSQL engine, and thus provides standard PostgreSQL compatibility for most PostgreSQL features and commands. Due to autoscaling, the cold start can take a couple of seconds and be interpreted as an error by some drivers or third party libraries. -If you require strict compatibility with all PostgreSQL features, use [Managed Databases for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) instead. +If you require strict compatibility with all PostgreSQL features, use [Managed Databases for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) instead. ## Connection timeouts using Prisma diff --git a/storage/block/api-cli/identifying-volume-snapshot-api.mdx b/storage/block/api-cli/identifying-volume-snapshot-api.mdx index 55bbfa954e..99e31d24bc 100644 --- a/storage/block/api-cli/identifying-volume-snapshot-api.mdx +++ b/storage/block/api-cli/identifying-volume-snapshot-api.mdx @@ -19,8 +19,8 @@ This page shows you how to identify the API managing your Block Storage volumes - A Scaleway account logged into the [console](https://console.scaleway.com) -- Created [Block Storage volumes](/storage/block/how-to/create-a-volume/) -- [Created an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and set [your secret key as an environment variable](/developer-tools/scaleway-sdk/reference-content/environment-variables/#reserved-environment-variables) +- Created [Block Storage volumes](/block-storage/how-to/create-a-volume/) +- [Created an API key](/iam/how-to/create-api-keys/) and set [your secret key as an environment variable](/scaleway-sdk/reference-content/environment-variables/#reserved-environment-variables) - [Installed curl](https://curl.se/download.html) - Installed the [Scaleway CLI](https://cli.scaleway.com/) diff --git a/storage/block/api-cli/managing-a-volume.mdx b/storage/block/api-cli/managing-a-volume.mdx index 43f66cb3db..12c0263998 100644 --- a/storage/block/api-cli/managing-a-volume.mdx +++ b/storage/block/api-cli/managing-a-volume.mdx @@ -19,10 +19,10 @@ This documentation only explains how to mount **additional block volumes to your - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/concepts/#instance) -- [Attached](/storage/block/how-to/attach-a-volume/) an additional Block Storage volume to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/concepts/#instance) +- [Attached](/block-storage/how-to/attach-a-volume/) an additional Block Storage volume to your Instance ## Mounting and using a Block Storage volume @@ -195,14 +195,14 @@ The file is now transferred. You can connect to your Instance again, and use the ## Increasing the partition size of the volume with growpart - - We recommend that you make a backup of your data using the [snapshot](/storage/block/how-to/create-a-snapshot/) feature, before increasing the partition size of your volume. This helps you avoid any potential data loss. + - We recommend that you make a backup of your data using the [snapshot](/block-storage/how-to/create-a-snapshot/) feature, before increasing the partition size of your volume. This helps you avoid any potential data loss. - You need to have partitioned your volume to follow the procedure below - - If the partition you want to resize is mounted, you need to [unmount it](/storage/block/api-cli/unmounting-a-volume/) beforehand + - If the partition you want to resize is mounted, you need to [unmount it](/block-storage/api-cli/unmounting-a-volume/) beforehand `growpart` allows you to resize partitions. If you have increased the size of the partition's underlying volume, for example, you might want to increase the size of the partition to make use of the additional space. -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Use the `lsblk` command to identify your volume partition. Ensure that the partition is **not mounted before you resize it**. In the following example, we are resizing `sdb1`: ``` root@scw-festive-agnesi:~# lsblk diff --git a/storage/block/api-cli/unmounting-a-volume.mdx b/storage/block/api-cli/unmounting-a-volume.mdx index c0e17f0b74..939d2c5479 100644 --- a/storage/block/api-cli/unmounting-a-volume.mdx +++ b/storage/block/api-cli/unmounting-a-volume.mdx @@ -18,13 +18,13 @@ categories: ## Unmounting a Block Storage volume -Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/storage/block/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command. +Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created an [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Created an [Instance](/compute/instances/how-to/create-an-instance/) with an additional Block Storage volume +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created an [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume 1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console. @@ -49,8 +49,8 @@ Unmounting a volume means detaching it from the operating system so it is no lon sdb 8:0 0 18.6G 0 disk ``` - Remember to edit the `/etc/fstab` file and delete the line corresponding to your block volume if you have used [Persistent Mounting](/storage/block/api-cli/managing-a-volume/#using-fstab-for-persistent-mounting). + Remember to edit the `/etc/fstab` file and delete the line corresponding to your block volume if you have used [Persistent Mounting](/block-storage/api-cli/managing-a-volume/#using-fstab-for-persistent-mounting). -Refer to the [dedicated documentation](/storage/block/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. +Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. diff --git a/storage/block/concepts.mdx b/storage/block/concepts.mdx index ba1bb674a0..3f4ee08eb9 100644 --- a/storage/block/concepts.mdx +++ b/storage/block/concepts.mdx @@ -36,4 +36,4 @@ A Storage Area Network (SAN) consists of interconnected machines, network infras ## Volumes -A volume is a storage space used by your Instances. Several volumes can be [attached to an Instance](/storage/block/how-to/attach-a-volume/). In addition, they can be [snapshotted](/storage/block/how-to/create-a-snapshot/), [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) or [unmounted](/storage/block/api-cli/unmounting-a-volume/). \ No newline at end of file +A volume is a storage space used by your Instances. Several volumes can be [attached to an Instance](/block-storage/how-to/attach-a-volume/). In addition, they can be [snapshotted](/block-storage/how-to/create-a-snapshot/), [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume) or [unmounted](/block-storage/api-cli/unmounting-a-volume/). \ No newline at end of file diff --git a/storage/block/how-to/attach-a-volume.mdx b/storage/block/how-to/attach-a-volume.mdx index 6681b570b9..e13465979d 100644 --- a/storage/block/how-to/attach-a-volume.mdx +++ b/storage/block/how-to/attach-a-volume.mdx @@ -14,14 +14,14 @@ categories: - storage --- -You can attach a Block Storage volume to your Instance at any time, as long as they are both in the same [Availability Zone](/compute/instances/concepts/#availability-zone). +You can attach a Block Storage volume to your Instance at any time, as long as they are both in the same [Availability Zone](/instances/concepts/#availability-zone). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) -- At least one [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) +- At least one [Instance](/instances/how-to/create-an-instance/) 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. Your volumes display. @@ -41,8 +41,8 @@ Alternatively, you can attach a Block Storage volume the following way: You can attach up to 15 volumes at a time to a single Instance. - To use **[Block Storage Low Latency](/storage/block/) 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](/compute/instances/reference-content/instances-bandwidth-overview/) documentation. + To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. + You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. diff --git a/storage/block/how-to/create-a-snapshot.mdx b/storage/block/how-to/create-a-snapshot.mdx index fe9aa7d5fb..0d889058cd 100644 --- a/storage/block/how-to/create-a-snapshot.mdx +++ b/storage/block/how-to/create-a-snapshot.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Block Storage volume](/block-storage/how-to/create-a-volume/) 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. diff --git a/storage/block/how-to/create-a-volume.mdx b/storage/block/how-to/create-a-volume.mdx index b7456c4f49..e1c3869364 100644 --- a/storage/block/how-to/create-a-volume.mdx +++ b/storage/block/how-to/create-a-volume.mdx @@ -17,25 +17,25 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - This procedure refers to low latency block volumes. To create legacy block volumes, refer the [dedicated documentation](/compute/instances/how-to/create-a-block-volume/). + This procedure refers to low latency block volumes. To create legacy block volumes, refer the [dedicated documentation](/instances/how-to/create-a-block-volume/). 1. Click **Block Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com) side menu. The Block Storage page displays. 2. Click **+ Create volume**. 3. Follow the steps in the creation wizard: - - Choose an [Availability Zone](/compute/instances/concepts/#availability-zone). + - Choose an [Availability Zone](/instances/concepts/#availability-zone). - Configure the volume: - Enter a name for your volume or leave the automatically generated name. - - Select an [IOPS](/storage/block/concepts/#iops). + - Select an [IOPS](/block-storage/concepts/#iops). You cannot edit the IOPS after you create your volume. - To use **[Block Storage Low Latency](/storage/block/) 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](/compute/instances/reference-content/instances-bandwidth-overview/) documentation. + To use **[Block Storage Low Latency](/block-storage/) 15k**, your Instance must have at least **3 GiB/s of block bandwidth**. + You can verify if an Instance type meets this requirement by consulting the [Scaleway Instances internet and Block Storage bandwidth overview](/instances/reference-content/instances-bandwidth-overview/) documentation. Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. diff --git a/storage/block/how-to/create-volume-from-snapshot.mdx b/storage/block/how-to/create-volume-from-snapshot.mdx index 3817a7574d..08019da6b1 100644 --- a/storage/block/how-to/create-volume-from-snapshot.mdx +++ b/storage/block/how-to/create-volume-from-snapshot.mdx @@ -17,16 +17,16 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) -- Created a [snapshot](/storage/block/how-to/create-a-snapshot/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) +- Created a [snapshot](/block-storage/how-to/create-a-snapshot/) 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays. 2. Click the **Snapshots** tab. 3. Click > **Volume from snapshot** next to the snapshot of your choice. A pop-up displays. 4. Enter a name for the new volume, or leave the suggested name. -5. Select an [IOPS](/storage/block/concepts/#iops). +5. Select an [IOPS](/block-storage/concepts/#iops). You cannot edit the IOPS after you create your volume. diff --git a/storage/block/how-to/delete-a-snapshot.mdx b/storage/block/how-to/delete-a-snapshot.mdx index e54ce109fa..cf0e3f5e28 100644 --- a/storage/block/how-to/delete-a-snapshot.mdx +++ b/storage/block/how-to/delete-a-snapshot.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. A list of your volumes displays. diff --git a/storage/block/how-to/delete-a-volume.mdx b/storage/block/how-to/delete-a-volume.mdx index 36b16821e9..8f8057beca 100644 --- a/storage/block/how-to/delete-a-volume.mdx +++ b/storage/block/how-to/delete-a-volume.mdx @@ -17,12 +17,12 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) - - You must detach your volume from the Instance it is attached to before deleting the volume. Refer to our documentation to find out [how to do so](/storage/block/how-to/detach-a-volume/). - - We highly recommend that you [unmount](/storage/block/api-cli/unmounting-a-volume/) your volume from the operating system before detaching it, to avoid data loss. + - You must detach your volume from the Instance it is attached to before deleting the volume. Refer to our documentation to find out [how to do so](/block-storage/how-to/detach-a-volume/). + - We highly recommend that you [unmount](/block-storage/api-cli/unmounting-a-volume/) your volume from the operating system before detaching it, to avoid data loss. 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. A list of your volumes displays. diff --git a/storage/block/how-to/detach-a-volume.mdx b/storage/block/how-to/detach-a-volume.mdx index f60cfe382c..a00e0c970b 100644 --- a/storage/block/how-to/detach-a-volume.mdx +++ b/storage/block/how-to/detach-a-volume.mdx @@ -14,13 +14,13 @@ categories: - storage --- -You can detach a Block Storage volume from your Instance at any time. It is important to [unmount the volume](/storage/block/api-cli/unmounting-a-volume/) from the operating system before detaching it to avoid data loss. +You can detach a Block Storage volume from your Instance at any time. It is important to [unmount the volume](/block-storage/api-cli/unmounting-a-volume/) from the operating system before detaching it to avoid data loss. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) that is [attached](/storage/block/how-to/attach-a-volume/) to an Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) that is [attached](/block-storage/how-to/attach-a-volume/) to an Instance 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays. diff --git a/storage/block/how-to/increase-block-volume.mdx b/storage/block/how-to/increase-block-volume.mdx index 381cf459b0..e53b1c2a93 100644 --- a/storage/block/how-to/increase-block-volume.mdx +++ b/storage/block/how-to/increase-block-volume.mdx @@ -17,8 +17,8 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Block Storage volume](/storage/block/how-to/create-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Block Storage volume](/block-storage/how-to/create-a-volume/) 1. Click **Block Storage** in the **Storage** section of the Scaleway console side menu. The Block Storage page displays. @@ -30,7 +30,7 @@ categories: - Refer to our [dedicated documentation](/storage/block/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase your volume's partition size. + Refer to our [dedicated documentation](/block-storage/api-cli/managing-a-volume/#increasing-the-partition-size-of-the-volume-with-growpart) to find out how to increase your volume's partition size. diff --git a/storage/block/how-to/unmount-a-volume.mdx b/storage/block/how-to/unmount-a-volume.mdx index 23f8b7727f..1e37a869b3 100644 --- a/storage/block/how-to/unmount-a-volume.mdx +++ b/storage/block/how-to/unmount-a-volume.mdx @@ -14,14 +14,14 @@ categories: - storage --- -Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/storage/block/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command. +Unmounting a volume means detaching it from the operating system so it is no longer accessible. You can do this if you want to stop using it, prevent data corruption, or plan to [detach it](/block-storage/how-to/detach-a-volume/) from your Instance and attach it to another. This page shows you how to unmount a volume from the operating system using the `umount` command. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created an [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Created an [Instance](/compute/instances/how-to/create-an-instance/) with an additional Block Storage volume +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created an [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Created an [Instance](/instances/how-to/create-an-instance/) with an additional Block Storage volume 1. Open a terminal and use the following command to connect to your Instance. Make sure that you replace `` with your Instance's IP. You can also find the SSH command in your Instance's **Overview** tab in the Scaleway console. @@ -49,6 +49,6 @@ Unmounting a volume means detaching it from the operating system so it is no lon Do not forget to edit the `/etc/fstab` file and delete the line corresponding to your block volume. -Refer to the [dedicated documentation](/storage/block/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. +Refer to the [dedicated documentation](/block-storage/api-cli/managing-a-volume/) for more information about managing your Block Storage volumes. diff --git a/storage/block/index.mdx b/storage/block/index.mdx index 100567a678..fe074692b9 100644 --- a/storage/block/index.mdx +++ b/storage/block/index.mdx @@ -9,7 +9,7 @@ meta: productName="Block Storage Low Latency" productLogo="blockStorage" description="Block Storage Low Latency offers scalable, non-volatile disks for Scaleway Instances. Enhance performance with high IOPS, low latency, and scalability." - url="/storage/block/quickstart/" + url="/block-storage/quickstart/" label="Block Storage Quickstart" /> @@ -21,28 +21,28 @@ meta: icon="rocket" description="Learn to create Block Storage volumes, attach, and mount them to a Scaleway Instance in a few easy steps." label="View Quickstart" - url="/storage/block/quickstart/" + url="/block-storage/quickstart/" /> @@ -52,17 +52,17 @@ meta: diff --git a/storage/block/quickstart.mdx b/storage/block/quickstart.mdx index 576a49ab9d..534647fff7 100644 --- a/storage/block/quickstart.mdx +++ b/storage/block/quickstart.mdx @@ -14,27 +14,27 @@ categories: - storage --- -Scaleway [Block Storage](/storage/block/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/compute/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/compute/instances/concepts/#availability-zone). +Scaleway [Block Storage](/block-storage/concepts/#block-device) provides network-attached storage that can be plugged in and out of [Instances](/instances/concepts/#instance) like a virtual hard-drive. Block Storage devices are independent of the Local Storage of Instances, and the fact that they are accessed over a network connection makes it easy to move them between Instances in the same [Availability Zone](/instances/concepts/#availability-zone). -From the user's point of view, once [mounted](/storage/block/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk. +From the user's point of view, once [mounted](/block-storage/api-cli/managing-a-volume/#mounting-and-using-a-block-storage-volume), the block device behaves like a regular disk. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created an [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created an [Instance](/instances/how-to/create-an-instance/) ## How to create a Block Storage volume 1. Click **Block Storage** in the **Storage** section of the [Scaleway console](https://console.scaleway.com) side menu. The Block Storage page displays. 2. Click **+ Create volume**. 3. Follow the steps in the creation wizard: - - Choose an [Availability Zone](/compute/instances/concepts/#availability-zone). + - Choose an [Availability Zone](/instances/concepts/#availability-zone). - Configure the volume: - Enter a name for your volume or leave the automatically generated name. - - Select an [IOPS](/storage/block/concepts/#iops). + - Select an [IOPS](/block-storage/concepts/#iops). You cannot edit the IOPS after you create your volume. @@ -61,7 +61,7 @@ From the user's point of view, once [mounted](/storage/block/api-cli/managing-a- ## How to mount and use a Block Storage volume -In order to mount and use your Block Storage volume, you need to [connect to the Instance it is attached to via SSH](/compute/instances/how-to/connect-to-instance/#troubleshooting-connection-problems). +In order to mount and use your Block Storage volume, you need to [connect to the Instance it is attached to via SSH](/instances/how-to/connect-to-instance/#troubleshooting-connection-problems). Then, check that the volume is available, format it, and mount it, following the instructions below. ### How to verify device availability diff --git a/storage/block/reference-content/advantages-migrating-to-sbs.mdx b/storage/block/reference-content/advantages-migrating-to-sbs.mdx index 81582e6b90..ac09e40abc 100644 --- a/storage/block/reference-content/advantages-migrating-to-sbs.mdx +++ b/storage/block/reference-content/advantages-migrating-to-sbs.mdx @@ -29,7 +29,7 @@ Local volumes will remain exclusively supported by the Instance API. If you have created volumes and snapshots via the Instance API, you **must transition to the Block Storage API** to align with the latest management practices. -This entails [migrating your existing volumes and snapshots to the Block Storage API](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/), and **switching to using only the Block Storage API for Block Storage volumes and snapshots creation and management**. +This entails [migrating your existing volumes and snapshots to the Block Storage API](/instances/how-to/migrate-volumes-snapshots-to-sbs/), and **switching to using only the Block Storage API for Block Storage volumes and snapshots creation and management**. Unified volume creation and management will no longer be available via the Block Storage API and will no longer be supported by the Instance API at the end of the migration. For this reason, it is also necessary to convert your existing unified volumes and snapshots to either local or block volumes. @@ -86,13 +86,13 @@ By transitioning to the Block Storage API, you align with Scaleway's consolidate ## Impact on volume names in virtual machines -When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, refer to [our documentation on identifying devices on a Scaleway Instance](/compute/instances/reference-content/identify-devices/). +When transitioning to the Block Storage API, you may notice changes in how volumes are identified in your virtual machines (VMs). For more details on how devices are named and identified, refer to [our documentation on identifying devices on a Scaleway Instance](/instances/reference-content/identify-devices/). ## How to transition? -- For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/compute/instances/how-to/migrate-volumes-snapshots-to-sbs/). +- For a step-by-step guide to transitioning your block volumes and snapshots from the Instance API to the Block Storage API, refer to [our migration documentation](/instances/how-to/migrate-volumes-snapshots-to-sbs/). -- To identify which API manages your volumes and snapshots, refer to the [dedicated documentation](/storage/block/api-cli/identifying-volume-snapshot-api/). +- To identify which API manages your volumes and snapshots, refer to the [dedicated documentation](/block-storage/api-cli/identifying-volume-snapshot-api/). - To find out how to convert a Block Storage legacy volume into a Block Storage Low Latency volume, read [the dedicated documentation](/faq/blockstorage/#how-can-i-convert-a-block-storage-legacy-volume-into-a-block-storage-low-latency-volume). diff --git a/storage/block/reference-content/differences-between-5kiops-volumes.mdx b/storage/block/reference-content/differences-between-5kiops-volumes.mdx index 574ce9cf98..44779b2043 100644 --- a/storage/block/reference-content/differences-between-5kiops-volumes.mdx +++ b/storage/block/reference-content/differences-between-5kiops-volumes.mdx @@ -13,11 +13,11 @@ categories: - storage --- -When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/storage/block/) volumes, [block volumes (Block Storage)](/compute/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/compute/instances/concepts/#volumes). +When creating volumes from the Scaleway console, you are prompted to choose between [Block Storage Low Latency](/block-storage/) volumes, [block volumes (Block Storage)](/instances/concepts/#block-volumes), and [local volumes (Local Storage)](/instances/concepts/#volumes). -This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/storage/block/concepts/#iops) volumes. +This page provides information about the differences between Block Storage and Block Storage Low Latency 5K [IOPS](/block-storage/concepts/#iops) volumes. -Refer to the [dedicated documentation](/compute/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes. +Refer to the [dedicated documentation](/instances/concepts/#volumes) to learn about the differences between Block Storage and Local Storage volumes. ## Underlying hardware diff --git a/storage/object/api-cli/bucket-policy.mdx b/storage/object/api-cli/bucket-policy.mdx index 3fc9ec2aed..e46828cb51 100644 --- a/storage/object/api-cli/bucket-policy.mdx +++ b/storage/object/api-cli/bucket-policy.mdx @@ -18,7 +18,7 @@ categories: -The different elements of a bucket policy allow you to [configure fine-grained permissions](/storage/object/api-cli/combining-iam-and-object-storage/) when combined with [Identity and Access Management (IAM)](/identity-and-access-management/iam/concepts/#iam), as shown in the table below. +The different elements of a bucket policy allow you to [configure fine-grained permissions](/object-storage/api-cli/combining-iam-and-object-storage/) when combined with [Identity and Access Management (IAM)](/iam/concepts/#iam), as shown in the table below. @@ -35,7 +35,7 @@ Bucket policies behave like objects: they can be uploaded into buckets. Once you - The `2012-10-17` version is deprecated, and its usage is strongly discouraged. -- With the `2023-04-17` version, only actions explicitly **allowed** by the bucket policy are permitted, if the principal is also **allowed** by an [IAM policy](/identity-and-access-management/iam/how-to/create-policy/). **Deny** statements are therefore useless. +- With the `2023-04-17` version, only actions explicitly **allowed** by the bucket policy are permitted, if the principal is also **allowed** by an [IAM policy](/iam/how-to/create-policy/). **Deny** statements are therefore useless. ## Bucket policies description @@ -76,7 +76,7 @@ Bucket policies use a JSON-based access policy language, and are composed of str ``` - Refer to the [documentation on bucket policy versions](/storage/object/api-cli/bucket-policy/#bucket-policies-versions) for more information. + Refer to the [documentation on bucket policy versions](/object-storage/api-cli/bucket-policy/#bucket-policies-versions) for more information. ### Id @@ -274,7 +274,7 @@ Bucket policies use a JSON-based access policy language, and are composed of str ### Principal **Description** -: Defines the targets of the bucket policy, which can be a [user](/identity-and-access-management/iam/concepts#user) or an [application](/identity-and-access-management/iam/concepts#application). You must use `user_id` and/or `application_id`, or `*` to grant access to "everyone". +: Defines the targets of the bucket policy, which can be a [user](/iam/concepts#user) or an [application](/iam/concepts#application). You must use `user_id` and/or `application_id`, or `*` to grant access to "everyone". **Required** : Yes @@ -622,4 +622,4 @@ Bucket policies use a JSON-based access policy language, and are composed of str - `DateLessThan` - `DateLessThanEquals` -Refer to our [dedicated documentation](/storage/object/api-cli/manage-bucket-permissions-ip/) for more information on managing bucket permissions for IP addresses or ranges of IP. \ No newline at end of file +Refer to our [dedicated documentation](/object-storage/api-cli/manage-bucket-permissions-ip/) for more information on managing bucket permissions for IP addresses or ranges of IP. \ No newline at end of file diff --git a/storage/object/api-cli/bucket-website-api.mdx b/storage/object/api-cli/bucket-website-api.mdx index 207f63118e..330a7e7c01 100644 --- a/storage/object/api-cli/bucket-website-api.mdx +++ b/storage/object/api-cli/bucket-website-api.mdx @@ -16,16 +16,16 @@ categories: The bucket website feature allows you to host static websites using Scaleway [Object Storage](https://www.scaleway.com/en/object-storage/). -It is possible to enable and configure the bucket website feature via the [AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/). +It is possible to enable and configure the bucket website feature via the [AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/). -To enable and configure the bucket website using the Scaleway console, refer to our [dedicated documentation](/storage/object/how-to/use-bucket-website/). +To enable and configure the bucket website using the Scaleway console, refer to our [dedicated documentation](/object-storage/how-to/use-bucket-website/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Enabling the bucket website feature @@ -143,7 +143,7 @@ After setting up the basic bucket website configuration with `put-bucket-website You can also upload the rest of the static web page files that make up your website. -If this is your first time uploading objects into a bucket, you can follow the step-by-step on [this documentation page](/storage/object/how-to/upload-files-into-a-bucket/). +If this is your first time uploading objects into a bucket, you can follow the step-by-step on [this documentation page](/object-storage/how-to/upload-files-into-a-bucket/). ### Configuring access @@ -174,7 +174,7 @@ If you want your website to be accessible, you need to set up a bucket policy. - `"/*"` - Grants access to all objects inside a bucket, but not to the bucket itself. - `"//*"` - Grants access only to objects with the specified prefix inside a bucket, but not to the bucket itself. For example, if you apply a bucket policy that specifies `"my_files/movie/*"` under **Resource**, you would grant access to all objects with the `movie/` prefix, but not to other objects in `my_files/` bucket. -3. Use [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) or run the following command to implement the policy via the AWS-CLI: +3. Use [PutBucketPolicy](/object-storage/api-cli/bucket-operations/#putbucketpolicy) or run the following command to implement the policy via the AWS-CLI: ``` aws s3api put-bucket-policy --bucket --policy file://bucket-policy.json ``` diff --git a/storage/object/api-cli/combining-iam-and-object-storage.mdx b/storage/object/api-cli/combining-iam-and-object-storage.mdx index ea7dcf53ad..749fe71d83 100644 --- a/storage/object/api-cli/combining-iam-and-object-storage.mdx +++ b/storage/object/api-cli/combining-iam-and-object-storage.mdx @@ -14,9 +14,9 @@ categories: - object-storage --- -Scaleway Object Storage allows you to manage access to your resources with two features, [Identity and Access Management (IAM)](/identity-and-access-management/iam/concepts/#iam) and [Bucket policies](/storage/object/api-cli/bucket-policy/). +Scaleway Object Storage allows you to manage access to your resources with two features, [Identity and Access Management (IAM)](/iam/concepts/#iam) and [Bucket policies](/object-storage/api-cli/bucket-policy/). -You can use IAM when you do not need to configure access to specific buckets, and favor simplicity over granularity. IAM is central, and relies on policies to manage a [principal](/identity-and-access-management/iam/concepts/#principal)'s rights in the entire Scaleway ecosystem. +You can use IAM when you do not need to configure access to specific buckets, and favor simplicity over granularity. IAM is central, and relies on policies to manage a [principal](/iam/concepts/#principal)'s rights in the entire Scaleway ecosystem. Bucket policies operate at the bucket level, and enable you to state clearly who can do what in each bucket. @@ -26,9 +26,9 @@ To configure more granular access to your Object Storage buckets, you can combin ### IAM -[Identity and Access Management (IAM)](/identity-and-access-management/iam/concepts/#iam) allows you to control and manage access to your resources. For users of Scaleway Object Storage, this means that besides configuring access via bucket policies, you can use IAM policies to configure permissions at the Project level. +[Identity and Access Management (IAM)](/iam/concepts/#iam) allows you to control and manage access to your resources. For users of Scaleway Object Storage, this means that besides configuring access via bucket policies, you can use IAM policies to configure permissions at the Project level. -An [IAM policy](/identity-and-access-management/iam/concepts/#policy) is used to define the permissions of users, groups, and applications in a given Organization. A policy is composed of a [principal](/identity-and-access-management/iam/concepts/#principal) (the user, group or application to which it applies) and one or more IAM rules (which describe the permission sets the principal should have, and the scope of those permission sets). +An [IAM policy](/iam/concepts/#policy) is used to define the permissions of users, groups, and applications in a given Organization. A policy is composed of a [principal](/iam/concepts/#principal) (the user, group or application to which it applies) and one or more IAM rules (which describe the permission sets the principal should have, and the scope of those permission sets). If managing access to resources at the Project level is enough for your Object Storage use cases, use IAM only. @@ -40,7 +40,7 @@ If managing access to resources at the Project level is enough for your Object S -In order to perform actions on a bucket, a [principal](/storage/object/concepts/#principal) (user or application) must be granted access via an IAM policy, and optionally via a bucket policy. +In order to perform actions on a bucket, a [principal](/object-storage/concepts/#principal) (user or application) must be granted access via an IAM policy, and optionally via a bucket policy. By properly setting up IAM first, you can restrict access to Object Storage to the desired users and applications, and limit their allowed actions. By adding bucket policies to your critical resources, you can further restrain access and actions directly at the bucket-level, and achieve optimum security. @@ -48,32 +48,32 @@ To set up granular access to your Object Storage resources, you must: 1. List all the users and applications you want to grant access to Object Storage, what rights you want to give them, and which buckets they can access. -2. [Create an IAM group](/identity-and-access-management/iam/how-to/create-group/) that contains every user and application that must access Object Storage. +2. [Create an IAM group](/iam/how-to/create-group/) that contains every user and application that must access Object Storage. You can create several groups to assign different permission sets to your users and applications. -3. [Create an IAM policy](/identity-and-access-management/iam/how-to/create-policy/) for each group created, select the appropriate permission sets (e.g. `ObjectStorageReadOnly` or `ObjectStorageObjectsRead`), and [attach it to the group](/identity-and-access-management/iam/how-to/manage-groups/#attach-a-policy-to-a-group). +3. [Create an IAM policy](/iam/how-to/create-policy/) for each group created, select the appropriate permission sets (e.g. `ObjectStorageReadOnly` or `ObjectStorageObjectsRead`), and [attach it to the group](/iam/how-to/manage-groups/#attach-a-policy-to-a-group). -4. [Create and push a bucket policy](/storage/object/api-cli/create-bucket-policy/) in each bucket in which you want fine-grained access. +4. [Create and push a bucket policy](/object-storage/api-cli/create-bucket-policy/) in each bucket in which you want fine-grained access. ## IAM and bucket policy example -Consider an Organization in which a user and an application must perform specific tasks with Scaleway Object Storage in a [project](/identity-and-access-management/organizations-and-projects/concepts/#project) named `S3-project`. +Consider an Organization in which a user and an application must perform specific tasks with Scaleway Object Storage in a [project](/organizations-and-projects/concepts/#project) named `S3-project`. ### Defining authorizations -- The user must be able to read ([GET](/storage/object/api-cli/object-operations/#getobject)) and write ([PUT](/storage/object/api-cli/object-operations/#putobject)) objects in a bucket A. +- The user must be able to read ([GET](/object-storage/api-cli/object-operations/#getobject)) and write ([PUT](/object-storage/api-cli/object-operations/#putobject)) objects in a bucket A. -- The application must be able to read ([GET](/storage/object/api-cli/object-operations/#getobject)) objects in bucket A, and to write ([PUT](/storage/object/api-cli/object-operations/#putobject)) and [DELETE](/storage/object/api-cli/object-operations/#deleteobjects) objects in a bucket B. +- The application must be able to read ([GET](/object-storage/api-cli/object-operations/#getobject)) objects in bucket A, and to write ([PUT](/object-storage/api-cli/object-operations/#putobject)) and [DELETE](/object-storage/api-cli/object-operations/#deleteobjects) objects in a bucket B. ### Setting up access -1. [Create a group](/identity-and-access-management/iam/how-to/create-group/) named `S3-group` that contains the user and the application, so they are the only ones to have access to Object Storage. +1. [Create a group](/iam/how-to/create-group/) named `S3-group` that contains the user and the application, so they are the only ones to have access to Object Storage. -2. [Create an IAM policy](/identity-and-access-management/iam/how-to/create-policy/) named `S3-policy` in the [Scaleway console](https://console.scaleway.com/), with the previously created group as a [principal](/identity-and-access-management/iam/concepts/#principal). The members of this group will have the `ObjectStorageFullAccess` right. -3. [Create a bucket policy](/storage/object/api-cli/create-bucket-policy/) to manage access to bucket A. +2. [Create an IAM policy](/iam/how-to/create-policy/) named `S3-policy` in the [Scaleway console](https://console.scaleway.com/), with the previously created group as a [principal](/iam/concepts/#principal). The members of this group will have the `ObjectStorageFullAccess` right. +3. [Create a bucket policy](/object-storage/api-cli/create-bucket-policy/) to manage access to bucket A. ```json { "Version": "2023-04-17", @@ -110,7 +110,7 @@ Consider an Organization in which a user and an application must perform specifi ] } ``` -4. [Create a bucket policy](/storage/object/api-cli/create-bucket-policy/) to manage access to bucket B. +4. [Create a bucket policy](/object-storage/api-cli/create-bucket-policy/) to manage access to bucket B. ```json { "Version": "2023-04-17", @@ -136,12 +136,12 @@ Consider an Organization in which a user and an application must perform specifi } ``` -5. [Push the policies](/storage/object/api-cli/create-bucket-policy/) to the corresponding buckets. +5. [Push the policies](/object-storage/api-cli/create-bucket-policy/) to the corresponding buckets. - The user can now GET and PUT in bucket A, and the application can now GET in bucket A - The application can now PUT and DELETE in bucket B, and the user cannot perform any action as they are not **EXPLICITLY** allowed by the bucket policy. -Refer to the [Bucket policies overview](/storage/object/api-cli/bucket-policy/#bucket-policies-description) for more information on the different elements of a bucket policy. +Refer to the [Bucket policies overview](/object-storage/api-cli/bucket-policy/#bucket-policies-description) for more information on the different elements of a bucket policy. diff --git a/storage/object/api-cli/create-bucket-policy.mdx b/storage/object/api-cli/create-bucket-policy.mdx index 39c8f80e52..94b1024f00 100644 --- a/storage/object/api-cli/create-bucket-policy.mdx +++ b/storage/object/api-cli/create-bucket-policy.mdx @@ -16,15 +16,15 @@ categories: -To create and apply a bucket policy from the [Scaleway console](https://console/scaleway.com), refer to the [dedicated documentation](/storage/object/how-to/create-bucket-policy/). +To create and apply a bucket policy from the [Scaleway console](https://console/scaleway.com), refer to the [dedicated documentation](/object-storage/how-to/create-bucket-policy/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [IAM policy](/identity-and-access-management/iam/how-to/create-policy/) to grant access to your users and applications +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [IAM policy](/iam/how-to/create-policy/) to grant access to your users and applications ## How to create a bucket policy @@ -54,16 +54,16 @@ To create and apply a bucket policy from the [Scaleway console](https://console/ ] } ``` -3. Replace the `` placeholder with the ID of the user to which you want to grant access. You can also grant access to an [application](/storage/object/api-cli/bucket-policy/#principal). -4. Replace the `` placeholders with the name of the concerned bucket. Refer to the [resource documentation](/storage/object/api-cli/bucket-policy/#resource) for more information. +3. Replace the `` placeholder with the ID of the user to which you want to grant access. You can also grant access to an [application](/object-storage/api-cli/bucket-policy/#principal). +4. Replace the `` placeholders with the name of the concerned bucket. Refer to the [resource documentation](/object-storage/api-cli/bucket-policy/#resource) for more information. -Refer to the [Bucket policies description](/storage/object/api-cli/bucket-policy/#bucket-policies-description) for more details on each string. +Refer to the [Bucket policies description](/object-storage/api-cli/bucket-policy/#bucket-policies-description) for more details on each string. ## How to apply a bucket policy -Make sure that you have [installed the AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) before proceeding. +Make sure that you have [installed the AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) before proceeding. 1. Open a terminal and access the folder containing the previously created `bucket-policy.json` file. @@ -104,7 +104,7 @@ Make sure that you have [installed the AWS CLI](/storage/object/api-cli/object-s ## How to delete a bucket policy -To delete a bucket policy, you must have [Owner](/identity-and-access-management/iam/concepts/#owner) status, or the necessary [IAM permissions](/storage/object/reference-content/s3-iam-permissions-equivalence/). +To delete a bucket policy, you must have [Owner](/iam/concepts/#owner) status, or the necessary [IAM permissions](/object-storage/reference-content/s3-iam-permissions-equivalence/). Run the command below to delete the policy of a specific bucket. Replace `` with the name of your bucket. @@ -114,5 +114,5 @@ Run the command below to delete the policy of a specific bucket. Replace ` -Your objects will become accessible to all the users in your organization that have [IAM permissions](/storage/object/api-cli/combining-iam-and-object-storage/#combining-iam-and-bucket-policies) for Object Storage. +Your objects will become accessible to all the users in your organization that have [IAM permissions](/object-storage/api-cli/combining-iam-and-object-storage/#combining-iam-and-bucket-policies) for Object Storage. \ No newline at end of file diff --git a/storage/object/api-cli/enable-sse-c.mdx b/storage/object/api-cli/enable-sse-c.mdx index 80e38da80c..97ccd6a41f 100644 --- a/storage/object/api-cli/enable-sse-c.mdx +++ b/storage/object/api-cli/enable-sse-c.mdx @@ -33,9 +33,9 @@ Once the data has been copied, the encryption key is deleted. The digest of the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- Installed and initialized the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- Installed and initialized the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) ## Getting started with SSE-C diff --git a/storage/object/api-cli/generate-aws4-auth-signature.mdx b/storage/object/api-cli/generate-aws4-auth-signature.mdx index 17dc2867ed..c53d716eda 100644 --- a/storage/object/api-cli/generate-aws4-auth-signature.mdx +++ b/storage/object/api-cli/generate-aws4-auth-signature.mdx @@ -18,7 +18,7 @@ Requests sent to the Object Storage API require an HTTP Authorization header. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization Currently, the [AWS v4 signature type](https://docs.aws.amazon.com/general/latest/gr/signature-version-4.html) is supported. diff --git a/storage/object/api-cli/installing-minio-client.mdx b/storage/object/api-cli/installing-minio-client.mdx index ae6af94d76..126816ab78 100644 --- a/storage/object/api-cli/installing-minio-client.mdx +++ b/storage/object/api-cli/installing-minio-client.mdx @@ -18,7 +18,7 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) (`mc -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization. +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization. 1. Follow the instructions given in the [official MinIO documentation](hhttps://min.io/docs/minio/linux/reference/minio-mc.html#install-mc) to install the MinIO client (`mc`) for your OS. @@ -34,7 +34,7 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) (`mc mc alias set s3 https://s3.nl-ams.scw.cloud --api S3v4 ``` - You can create an alias for each [region](/storage/object/concepts/#region-and-availability-zone) in which you manage Object Storage resources. + You can create an alias for each [region](/object-storage/concepts/#region-and-availability-zone) in which you manage Object Storage resources. 4. You should now be able to run some basic commands, e.g.: - List all your buckets at the endpoint you configured in the previous step, via: diff --git a/storage/object/api-cli/installing-rclone.mdx b/storage/object/api-cli/installing-rclone.mdx index 3e85740fc3..82ee60d002 100644 --- a/storage/object/api-cli/installing-rclone.mdx +++ b/storage/object/api-cli/installing-rclone.mdx @@ -20,7 +20,7 @@ Follow the instructions given in the [official Rclone documentation here](https: For example, on Linux: -- Connect to your server as `root` via [SSH](/compute/instances/how-to/connect-to-instance/). +- Connect to your server as `root` via [SSH](/instances/how-to/connect-to-instance/). - Then, download and install Rclone with the following sequence of commands: ``` @@ -33,7 +33,7 @@ For example, on Linux: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Configuring Rclone @@ -128,7 +128,7 @@ For example, on Linux: Enter a string value. Press Enter for the default (""). access_key_id> ``` -6. Enter your [API access key](/identity-and-access-management/iam/how-to/create-api-keys/) and hit enter. The following output displays: +6. Enter your [API access key](/iam/how-to/create-api-keys/) and hit enter. The following output displays: ``` AWS Secret Access Key (password) Leave blank for anonymous access or runtime credentials. diff --git a/storage/object/api-cli/lifecycle-rules-api.mdx b/storage/object/api-cli/lifecycle-rules-api.mdx index f662e228cf..1a1cb424f3 100644 --- a/storage/object/api-cli/lifecycle-rules-api.mdx +++ b/storage/object/api-cli/lifecycle-rules-api.mdx @@ -16,8 +16,8 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) You can configure the lifecycle of a group of objects so that their storage costs can be effectively managed. A lifecycle configuration is a set of rules that defines actions applied to a group of objects stored on Object Storage. @@ -32,7 +32,7 @@ Currently, the **expiration**, **transition**, and **incomplete multipart upload - Standard -> Glacier - Onezone IA -> Glacier - Refer to our [dedicated documentation](/storage/object/how-to/edit-storage-class/) to manually change the storage class of your objects. + Refer to our [dedicated documentation](/object-storage/how-to/edit-storage-class/) to manually change the storage class of your objects. There might, for example, be a need to store log files for a week or a month, after which they become obsolete. It is possible to set a lifecycle rule to delete them automatically when they become obsolete. If you consider that a 3-month-old object is rarely used but still has a value, you might want to configure a rule to send it automatically to [Scaleway Glacier](/faq/objectstorage/#what-is-the-cold-storage-glacier-class), for example. @@ -62,7 +62,7 @@ Each `Rule` consists of the following: - Lifecycle transition(s) to perform on the selected objects - Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/storage/object/how-to/edit-storage-class/) or [delete](/storage/object/how-to/delete-an-object/) your objects manually. + Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) your objects manually. ## Available XML tokens @@ -202,16 +202,16 @@ The lifecycle configuration above translates to the following effective rules: - `mytagvalue2` is set to expire after one day. - To see examples of lifecycle rules API requests, refer to the Bucket Operations [documentation page](/storage/object/api-cli/bucket-operations/#putbucketlifecycleconfiguration). + To see examples of lifecycle rules API requests, refer to the Bucket Operations [documentation page](/object-storage/api-cli/bucket-operations/#putbucketlifecycleconfiguration). ## Setting rules for incomplete multipart uploads -When using the `awscli` to perform a [multipart upload](/storage/object/api-cli/multipart-uploads/), it is possible to set a bucket lifecycle rule that allows you to automate the *stoppage* of uploads if they are not completed. You can define a deadline for the expected completion with a lifecycle rule. If the multipart upload is incomplete by the end of the defined timeframe, it will be stopped and the parts associated with it will be deleted. +When using the `awscli` to perform a [multipart upload](/object-storage/api-cli/multipart-uploads/), it is possible to set a bucket lifecycle rule that allows you to automate the *stoppage* of uploads if they are not completed. You can define a deadline for the expected completion with a lifecycle rule. If the multipart upload is incomplete by the end of the defined timeframe, it will be stopped and the parts associated with it will be deleted. -You can automate the removal of incomplete multipart uploads by adding or uploading a lifecycle configuration to your bucket. The setup can be done via an API call or an [AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/) command. +You can automate the removal of incomplete multipart uploads by adding or uploading a lifecycle configuration to your bucket. The setup can be done via an API call or an [AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/) command. -Send a [putbucketlifecycleconfiguration](/storage/object/api-cli/bucket-operations/#putbucketlifecycleconfiguration) request with the following XML payload: +Send a [putbucketlifecycleconfiguration](/object-storage/api-cli/bucket-operations/#putbucketlifecycleconfiguration) request with the following XML payload: ```xml no-copy diff --git a/storage/object/api-cli/manage-bucket-permissions-ip.mdx b/storage/object/api-cli/manage-bucket-permissions-ip.mdx index 0f00b7e76e..c904f554f3 100644 --- a/storage/object/api-cli/manage-bucket-permissions-ip.mdx +++ b/storage/object/api-cli/manage-bucket-permissions-ip.mdx @@ -14,7 +14,7 @@ categories: - object-storage --- -You can stipulate which IP addresses or IP ranges have access or permission to perform operations on your buckets by creating a [bucket policy](/storage/object/api-cli/bucket-policy/) with the `IpAddress` or `NotIpAddress` conditions. +You can stipulate which IP addresses or IP ranges have access or permission to perform operations on your buckets by creating a [bucket policy](/object-storage/api-cli/bucket-policy/) with the `IpAddress` or `NotIpAddress` conditions. It is possible to `Allow` actions for a specific IP address or range of IPs, using the `IpAddress` condition and the `aws:SourceIp` condition key. @@ -25,9 +25,9 @@ It is possible to `Allow` actions for a specific IP address or range of IPs, usi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) In the example below, we allow the `192.0.2.0/24` IP range to perform the `s3:ListBucket` and `s3:GetObject` actions. @@ -80,5 +80,5 @@ Alternatively, you can block certain IP addresses or IP address ranges from perf ``` - Bucket policies use a JSON-based access policy language. Refer to the [dedicated documentation](/storage/object/api-cli/bucket-policy/) on bucket policies syntax for more information. + Bucket policies use a JSON-based access policy language. Refer to the [dedicated documentation](/object-storage/api-cli/bucket-policy/) on bucket policies syntax for more information. \ No newline at end of file diff --git a/storage/object/api-cli/managing-lifecycle-cliv2.mdx b/storage/object/api-cli/managing-lifecycle-cliv2.mdx index 5ebc95e354..cb48512345 100644 --- a/storage/object/api-cli/managing-lifecycle-cliv2.mdx +++ b/storage/object/api-cli/managing-lifecycle-cliv2.mdx @@ -14,19 +14,19 @@ categories: - object-storage --- -[Scaleway Object Storage](/storage/object/concepts/#object-storage) is a service based on the Amazon S3 protocol. It allows you to store different types of objects (documents, images, videos, etc.) and distribute them instantly, anywhere in the world. You can create and manage your Object Storage resources from the [console](https://console.scaleway.com/login), or via the [Scaleway Command Line Interface](/developer-tools/scaleway-cli/quickstart/) that uses external tools such as [S3cmd](https://github.com/s3tools/s3cmd), [Rclone](https://rclone.org/downloads/) or [MinIO Client (mc)](https://github.com/minio/mc). +[Scaleway Object Storage](/object-storage/concepts/#object-storage) is a service based on the Amazon S3 protocol. It allows you to store different types of objects (documents, images, videos, etc.) and distribute them instantly, anywhere in the world. You can create and manage your Object Storage resources from the [console](https://console.scaleway.com/login), or via the [Scaleway Command Line Interface](/scaleway-cli/quickstart/) that uses external tools such as [S3cmd](https://github.com/s3tools/s3cmd), [Rclone](https://rclone.org/downloads/) or [MinIO Client (mc)](https://github.com/minio/mc). ## Scaleway Command Line Interface Overview -[The Scaleway Command Line Interface (CLI)](/developer-tools/scaleway-cli/quickstart/) allows you to pilot your Scaleway infrastructure directly from your terminal, providing a faster way to administer and monitor your resources. Scaleway CLI is easy to set up and is an essential tool for operating efficiently in your cloud environment. +[The Scaleway Command Line Interface (CLI)](/scaleway-cli/quickstart/) allows you to pilot your Scaleway infrastructure directly from your terminal, providing a faster way to administer and monitor your resources. Scaleway CLI is easy to set up and is an essential tool for operating efficiently in your cloud environment. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- Installed and initialized the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- Installed and initialized the [Scaleway CLI](/scaleway-cli/quickstart/) - Downloaded [S3cmd](https://github.com/s3tools/s3cmd), [Rclone](https://rclone.org/downloads/) and [MinIO Client (mc)](https://github.com/minio/mc) ## Previewing an Object Storage configuration file for the Scaleway CLI @@ -100,7 +100,7 @@ Run the following command in a terminal to preview the configuration file for Mi ## Installing a configuration file for Amazon S3-compatible tools (s3cmd, rclone, and mc) -The `scw object config install` allows you to create a configuration file for the selected third party tool based on your [Scaleway CLI configuration](/developer-tools/scaleway-cli/quickstart/). +The `scw object config install` allows you to create a configuration file for the selected third party tool based on your [Scaleway CLI configuration](/scaleway-cli/quickstart/). Creating a new configuration file using `scw object config install` will overwrite the existing one for the specified third party tool. To update an existing configuration, [generate a preview](#previewing-an-object-storage-configuration-file-for-the-scaleway-cli) and manually edit the configuration file. diff --git a/storage/object/api-cli/migrating-buckets.mdx b/storage/object/api-cli/migrating-buckets.mdx index 601aaa1d57..8ef4a51838 100644 --- a/storage/object/api-cli/migrating-buckets.mdx +++ b/storage/object/api-cli/migrating-buckets.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed and initialized the [AWS CLI for Scaleway](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed and initialized the [AWS CLI for Scaleway](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) 1. Create a new bucket. ``` @@ -27,7 +27,7 @@ categories: ``` 2. Copy the objects between the Object Storage buckets. - If you have objects in the Scaleway `Glacier` storage class you must [restore](/storage/object/how-to/restore-an-object-from-glacier/) them before continuing. + If you have objects in the Scaleway `Glacier` storage class you must [restore](/object-storage/how-to/restore-an-object-from-glacier/) them before continuing. ``` diff --git a/storage/object/api-cli/multipart-uploads.mdx b/storage/object/api-cli/multipart-uploads.mdx index d8b0971f34..bac221e61f 100644 --- a/storage/object/api-cli/multipart-uploads.mdx +++ b/storage/object/api-cli/multipart-uploads.mdx @@ -31,9 +31,9 @@ The following technical specifications apply to multipart uploads: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Initiating a multipart upload @@ -80,7 +80,7 @@ During the lifecycle of a multipart upload, billing will occur for all storage a If a multipart upload is aborted, all parts already uploaded are deleted and billing for these resources stops. -Incomplete multipart uploads that have not been aborted are still subject to billing. For more information on how to view and abort incomplete MPUs, refer to the [dedicated documentation](/storage/object/how-to/abort-incomplete-mpu/). +Incomplete multipart uploads that have not been aborted are still subject to billing. For more information on how to view and abort incomplete MPUs, refer to the [dedicated documentation](/object-storage/how-to/abort-incomplete-mpu/). To upload a part of an object in an initiated multipart upload, send a POST request as follows: @@ -281,7 +281,7 @@ If the multipart upload is not completed, the parts will not be assembled and no In case these parts are no longer needed, it is possible to clear them by aborting the multipart upload session. -You can also [abort incomplete multipart uploads manually](/storage/object/how-to/abort-incomplete-mpu/) using the Scaleway console, or automatically using [lifecycle rules](/storage/object/how-to/manage-lifecycle-rules). +You can also [abort incomplete multipart uploads manually](/object-storage/how-to/abort-incomplete-mpu/) using the Scaleway console, or automatically using [lifecycle rules](/object-storage/how-to/manage-lifecycle-rules). To abort an active multipart upload session, send a `DELETE` request to the platform, as follows: diff --git a/storage/object/api-cli/object-lock.mdx b/storage/object/api-cli/object-lock.mdx index 8690edcb9c..9543b6ca4f 100644 --- a/storage/object/api-cli/object-lock.mdx +++ b/storage/object/api-cli/object-lock.mdx @@ -21,14 +21,14 @@ The feature uses a write-once-read-many (WORM) data protection model. This model Setting object lock can only be achieved upon the creation of a bucket. In addition, versioning is automatically enabled on the bucket and cannot be disabled. You must enable object lock if you wish to write a lock configuration. You can use the `PutObjectLockConfiguration` request with the object lock flag set. - Object Lock can be used with `Standard`, `One Zone - IA` (`fr-par`) and `Glacier` [storage classes](/storage/object/concepts/#storage-class). + Object Lock can be used with `Standard`, `One Zone - IA` (`fr-par`) and `Glacier` [storage classes](/object-storage/concepts/#storage-class). -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to configure bucket lock @@ -241,12 +241,12 @@ When the compliance mode is enabled, it is only possible to overwrite it or dele **Governance** -When this mode is set, all users with [permission](/identity-and-access-management/iam/concepts/#permission) can alter lock settings. +When this mode is set, all users with [permission](/iam/concepts/#permission) can alter lock settings. The **Governance** mode ensures extra protection before any alterations can be completed. An object can be permanently deleted only if: - A retention rule is applied, the governance retention date must be anterior to the present time - - The object does not have a legal hold in place. If it does, the legal hold [status token](/storage/object/api-cli/object-lock/#xml-legal-hold-configuration-token) must be set to OFF before deletion. + - The object does not have a legal hold in place. If it does, the legal hold [status token](/object-storage/api-cli/object-lock/#xml-legal-hold-configuration-token) must be set to OFF before deletion. When the above criteria are met, you will be able to use `delete-object --version-id` to permanently delete an object. diff --git a/storage/object/api-cli/object-operations.mdx b/storage/object/api-cli/object-operations.mdx index 667be0cee2..42cb4cc707 100644 --- a/storage/object/api-cli/object-operations.mdx +++ b/storage/object/api-cli/object-operations.mdx @@ -265,7 +265,7 @@ aws s3api head-object --bucket BucketName --key ObjectName Multipart uploads allow you to upload a single object as a set of parts. Each part is a contiguous portion of the object's data. You can upload these object parts independently and in any order. If transmission of any part fails, you can retransmit that part without affecting other parts. After all parts of your object are uploaded, Scaleway Object Storage assembles these parts and creates the object. - Check out our multipart uploads [documentation page](/storage/object/api-cli/multipart-uploads/) for more information. + Check out our multipart uploads [documentation page](/object-storage/api-cli/multipart-uploads/) for more information. **Sample request** @@ -329,7 +329,7 @@ Access-Control-Expose-Headers: x-amz-request-id This operation allows you to add an object to a specified bucket using HTML forms. POST is an alternate form of PUT that enables browser-based uploads as a way of putting objects in buckets. - If you want to learn more about this request, check out the POST Object [documentation page](/storage/object/api-cli/post-object/). + If you want to learn more about this request, check out the POST Object [documentation page](/object-storage/api-cli/post-object/). **Sample request** @@ -394,7 +394,7 @@ aws s3api put-object --bucket BucketName --key dir-1/ObjectName --body ObjectNam ``` -To define the [storage class](/storage/object/concepts/#storage-class) of the object directly upon creation, use the `--storage-class ` option with `awscli` or add the `x-amz-storage-class: ` header when using the Amazon S3 API. You can specify one of the following classes: `STANDARD`, `ONEZONE_IA`, `GLACIER`. Example: `x-amz-storage-class: ONEZONE_IA`. +To define the [storage class](/object-storage/concepts/#storage-class) of the object directly upon creation, use the `--storage-class ` option with `awscli` or add the `x-amz-storage-class: ` header when using the Amazon S3 API. You can specify one of the following classes: `STANDARD`, `ONEZONE_IA`, `GLACIER`. Example: `x-amz-storage-class: ONEZONE_IA`. If no class is specified, the object is created as STANDARD by default. diff --git a/storage/object/api-cli/object-storage-aws-cli.mdx b/storage/object/api-cli/object-storage-aws-cli.mdx index 2dd57bf70e..d105c02f87 100644 --- a/storage/object/api-cli/object-storage-aws-cli.mdx +++ b/storage/object/api-cli/object-storage-aws-cli.mdx @@ -19,8 +19,8 @@ The AWS-CLI is an open-source tool built on top of the [AWS SDK for Python (Boto - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) This page explains how to install the AWS-CLI v2. If you want to follow the installation procedure for v1, refer to the official [AWS-CLI documentation page](https://docs.aws.amazon.com/cli/v1/userguide/cli-chap-install.html) for more information. Furthermore, you must install the `awscli-plugin-endpoint` to allow the AWS-CLI v1 to interact with Scaleway Object Storage. diff --git a/storage/object/api-cli/post-object.mdx b/storage/object/api-cli/post-object.mdx index 14baafc1e4..0744b0dbd0 100644 --- a/storage/object/api-cli/post-object.mdx +++ b/storage/object/api-cli/post-object.mdx @@ -20,7 +20,7 @@ Parameters that are passed to PUT via HTTP Headers are instead passed as form fi -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization You must have WRITE access to a bucket to add an object to it. @@ -73,7 +73,7 @@ To allow wildcard on a field, use `["starts-with", "$field", ""]`. ## Signing request -POST object only supports [signature v4](/storage/object/concepts/#signature-v2-signature-v4). +POST object only supports [signature v4](/object-storage/concepts/#signature-v2-signature-v4). Here's how to sign an example policy in Python: diff --git a/storage/object/api-cli/setting-cors-rules.mdx b/storage/object/api-cli/setting-cors-rules.mdx index 32273ed5fd..71724cf19f 100644 --- a/storage/object/api-cli/setting-cors-rules.mdx +++ b/storage/object/api-cli/setting-cors-rules.mdx @@ -19,15 +19,15 @@ The [CORS standard](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## CORS overview Before CORS became standardized, it was not possible to call an API endpoint or other content under different domains for security reasons. This was (and to some degree still is) blocked by the Same-Origin Policy introduced with Netscape Navigator 2.0 in 1995. -An example of a cross-origin request: The frontend JavaScript code for a web application served from `http://webapplication.com` uses `XMLHttpRequest` to make a request for `http://customerapi.io/data.json`. Another example might be JavaScript that calls files in an Object Storage bucket, like web fonts, downloads, etc. It is possible to configure CORS for each bucket with the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/). +An example of a cross-origin request: The frontend JavaScript code for a web application served from `http://webapplication.com` uses `XMLHttpRequest` to make a request for `http://customerapi.io/data.json`. Another example might be JavaScript that calls files in an Object Storage bucket, like web fonts, downloads, etc. It is possible to configure CORS for each bucket with the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/). ## Setting CORS on an Object Storage bucket diff --git a/storage/object/api-cli/share-buckets-read-only.mdx b/storage/object/api-cli/share-buckets-read-only.mdx index c876756364..b827883caf 100644 --- a/storage/object/api-cli/share-buckets-read-only.mdx +++ b/storage/object/api-cli/share-buckets-read-only.mdx @@ -12,17 +12,17 @@ dates: --- - Bucket policy version `2012-10-17` is deprecated and its usage is not recommended. Refer to the [dedicated documentation](/storage/object/api-cli/bucket-policy/#bucket-policies-versions) for more information on bucket policy versions. + Bucket policy version `2012-10-17` is deprecated and its usage is not recommended. Refer to the [dedicated documentation](/object-storage/api-cli/bucket-policy/#bucket-policies-versions) for more information on bucket policy versions. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) -You can implement a [bucket policy](/storage/object/api-cli/bucket-policy/) to grant a Scaleway Organization or Project **Read** rights to a bucket in a different Project. +You can implement a [bucket policy](/object-storage/api-cli/bucket-policy/) to grant a Scaleway Organization or Project **Read** rights to a bucket in a different Project. For example, you are logged in to Organization A and you have a bucket (A1) inside Project A. You wish to share the bucket in read-only mode with users in Organization B, Project B. @@ -60,9 +60,9 @@ Specify which resources they can access under **Resource**: ] } ``` -Apply the policy using the [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) API call or run the following aws-cli command: +Apply the policy using the [PutBucketPolicy](/object-storage/api-cli/bucket-operations/#putbucketpolicy) API call or run the following aws-cli command: ``` aws s3api put-bucket-policy --bucket --profile default_project --policy file://bucket-policy.json ``` -You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/storage/object/api-cli/object-operations/#getobject). \ No newline at end of file +You can provide the user in Organization B with the name of your bucket. If the policy is correctly applied, they will be able to see bucket A1 included in their bucket list when running `List_Buckets`. If they know the name of an object, they can view their details by running [`Get_Object`](/object-storage/api-cli/object-operations/#getobject). \ No newline at end of file diff --git a/storage/object/api-cli/using-api-call-list.mdx b/storage/object/api-cli/using-api-call-list.mdx index 95746bf84c..011fe79deb 100644 --- a/storage/object/api-cli/using-api-call-list.mdx +++ b/storage/object/api-cli/using-api-call-list.mdx @@ -18,10 +18,10 @@ In this page we index all available Scaleway Object Storage API requests. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - When you use Object Storage directly with the API, you must generate an [Authentication Signature v4](/storage/object/api-cli/generate-aws4-auth-signature/) beforehand. + When you use Object Storage directly with the API, you must generate an [Authentication Signature v4](/object-storage/api-cli/generate-aws4-auth-signature/) beforehand. Status: @@ -33,44 +33,44 @@ Status: | Feature | Description | Status | | :------------ | :---- | :- | -| [GetService](/storage/object/api-cli/common-operations/#getservice) | Returns a list of all buckets | ✅ | +| [GetService](/object-storage/api-cli/common-operations/#getservice) | Returns a list of all buckets | ✅ | ## Bucket Operations | Feature | Description | Status | | :------------ | :---- | :---- | -| [CreateBucket](/storage/object/api-cli/bucket-operations/#createbucket) | Creates bucket | ✅ | -| [DeleteBucket](/storage/object/api-cli/bucket-operations/#deletebucket) | Deletes bucket | ✅ | -| [DeleteBucketCors](/storage/object/api-cli/bucket-operations/#deletebucketcors) | Deletes the [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) configuration of a bucket | ✅ | -| [DeleteBucketLifecycle](/storage/object/api-cli/bucket-operations/#deletebucketlifecycle)| Deletes the [lifecycle configuration](/storage/object/api-cli/lifecycle-rules-api/) of a bucket | ✅ | -| [DeleteBucketPolicy](/storage/object/api-cli/bucket-operations/#deletebucketpolicy) | Deletes the policy of a specified bucket | ✅ | -| [DeleteBucketTagging](/storage/object/api-cli/bucket-operations/#deletebuckettagging) | Deletes the tag(s) of a bucket | ✅ | -| [DeleteBucketWebsite](/storage/object/api-cli/bucket-operations/#deletebucketwebsite) | Deletes the bucket website configuration of a specified bucket | ✅ | -| [GetBucketAcl](/storage/object/api-cli/bucket-operations/#getbucketacl) | Returns the bucket ACL | ✅ | -| [GetBucketCors](/storage/object/api-cli/bucket-operations/#getbucketcors) | Returns the [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) configuration of a bucket | ✅ | +| [CreateBucket](/object-storage/api-cli/bucket-operations/#createbucket) | Creates bucket | ✅ | +| [DeleteBucket](/object-storage/api-cli/bucket-operations/#deletebucket) | Deletes bucket | ✅ | +| [DeleteBucketCors](/object-storage/api-cli/bucket-operations/#deletebucketcors) | Deletes the [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) configuration of a bucket | ✅ | +| [DeleteBucketLifecycle](/object-storage/api-cli/bucket-operations/#deletebucketlifecycle)| Deletes the [lifecycle configuration](/object-storage/api-cli/lifecycle-rules-api/) of a bucket | ✅ | +| [DeleteBucketPolicy](/object-storage/api-cli/bucket-operations/#deletebucketpolicy) | Deletes the policy of a specified bucket | ✅ | +| [DeleteBucketTagging](/object-storage/api-cli/bucket-operations/#deletebuckettagging) | Deletes the tag(s) of a bucket | ✅ | +| [DeleteBucketWebsite](/object-storage/api-cli/bucket-operations/#deletebucketwebsite) | Deletes the bucket website configuration of a specified bucket | ✅ | +| [GetBucketAcl](/object-storage/api-cli/bucket-operations/#getbucketacl) | Returns the bucket ACL | ✅ | +| [GetBucketCors](/object-storage/api-cli/bucket-operations/#getbucketcors) | Returns the [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) configuration of a bucket | ✅ | | GetBucketLifecycle | Returns the lifecycle configuration information set on the bucket | ❗ | -| [GetBucketLifecycleConfiguration](/storage/object/api-cli/bucket-operations/#getbucketlifecycleconfiguration) | Returns the lifecycle configuration information set on a bucket | ✅ | -| [GetBucketLocation](/storage/object/api-cli/bucket-operations/#getbucketlocation) | Returns the region where the bucket is | ✅ | +| [GetBucketLifecycleConfiguration](/object-storage/api-cli/bucket-operations/#getbucketlifecycleconfiguration) | Returns the lifecycle configuration information set on a bucket | ✅ | +| [GetBucketLocation](/object-storage/api-cli/bucket-operations/#getbucketlocation) | Returns the region where the bucket is | ✅ | | GetBucketNotification | Returns the notification configuration of a bucket | ⌛ | -| [GetBucketPolicy](/storage/object/api-cli/bucket-operations/#getbucketpolicy) | Returns the policy of a specified bucket | ✅ | +| [GetBucketPolicy](/object-storage/api-cli/bucket-operations/#getbucketpolicy) | Returns the policy of a specified bucket | ✅ | | GetBucketPolicyStatus | Retrieves the policy status for a bucket. The status indicates whether a bucket is public or not | ✅ | -| [GetBucketTagging](/storage/object/api-cli/bucket-operations/#getbuckettagging) | Returns the tag(s) of a bucket | ✅ | -| [GetBucketVersioning](/storage/object/api-cli/bucket-operations/#getbucketversioning) | Returns the versioning state of a bucket | ✅ | -| [GetBucketWebsite](/storage/object/api-cli/bucket-operations/#getbucketwebsite) | Returns the bucket website basic configuration | ✅ | -| [HeadBucket](/storage/object/api-cli/bucket-operations/#headbucket) | Checks if the bucket exists | ✅ | -| [ListObjects](/storage/object/api-cli/bucket-operations/#listobjects) | Lists objects in the bucket | ✅ | +| [GetBucketTagging](/object-storage/api-cli/bucket-operations/#getbuckettagging) | Returns the tag(s) of a bucket | ✅ | +| [GetBucketVersioning](/object-storage/api-cli/bucket-operations/#getbucketversioning) | Returns the versioning state of a bucket | ✅ | +| [GetBucketWebsite](/object-storage/api-cli/bucket-operations/#getbucketwebsite) | Returns the bucket website basic configuration | ✅ | +| [HeadBucket](/object-storage/api-cli/bucket-operations/#headbucket) | Checks if the bucket exists | ✅ | +| [ListObjects](/object-storage/api-cli/bucket-operations/#listobjects) | Lists objects in the bucket | ✅ | | ListObjectsV2 | Returns some or all (up to 1,000) of the objects in a bucket | ✅ | -| [ListObjectVersions](/storage/object/api-cli/bucket-operations/#listobjectversions) | Returns metadata about all the versions of objects in a bucket | ✅ | -| [PutBucketAcl](/storage/object/api-cli/bucket-operations/#putbucketacl) | Configures the Access Control List of a bucket | ✅ | -| [PutBucketCors](/storage/object/api-cli/bucket-operations/#putbucketcors) | Configures [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) on a bucket | ✅ | +| [ListObjectVersions](/object-storage/api-cli/bucket-operations/#listobjectversions) | Returns metadata about all the versions of objects in a bucket | ✅ | +| [PutBucketAcl](/object-storage/api-cli/bucket-operations/#putbucketacl) | Configures the Access Control List of a bucket | ✅ | +| [PutBucketCors](/object-storage/api-cli/bucket-operations/#putbucketcors) | Configures [CORS](https://en.wikipedia.org/wiki/Cross-origin_resource_sharing) on a bucket | ✅ | | PutBucketLifecycle | Creates a new lifecycle configuration or replaces an existing bucket lifecycle configuration | ❗ | | PutBucketLifecycleConfiguration| Creates a new lifecycle configuration or replaces an existing bucket lifecycle configuration | ✅ | | PutBucketNotification | Enables notifications of specified events for a bucket | ⌛ | -| [PutBucketPolicy](/storage/object/api-cli/bucket-operations/#putbucketpolicy) | Applies an Object Storage bucket policy to an Object Storage bucket. The key elements of bucket policy are [Version](/storage/object/api-cli/bucket-policy/#version), [ID](/storage/object/api-cli/bucket-policy/#id), [Statement](/storage/object/api-cli/bucket-policy/#statement), [Sid](/storage/object/api-cli/bucket-policy/#sid), [Principal](/storage/object/api-cli/bucket-policy/#principal), [Action](/storage/object/api-cli/bucket-policy/#action), [Effect](/storage/object/api-cli/bucket-policy/#effect), [Resource](/storage/object/api-cli/bucket-policy/#resource) and [Condition](/storage/object/api-cli/bucket-policy/#condition). You can find out more about each element by clicking the links, or consulting the full documentation | ✅ | -| [PutBucketTagging](/storage/object/api-cli/bucket-operations/#putbuckettagging) | Sets the tag(s) of a bucket | ✅ | -| [PutBucketVersioning](/storage/object/api-cli/bucket-operations/#putbucketversioning) | Sets the versioning state of an existing bucket | ✅ | -| [PutBucketWebsite](/storage/object/api-cli/bucket-operations/#putbucketwebsite) | Enables bucket website and sets the basic configuration for the website | ✅ | +| [PutBucketPolicy](/object-storage/api-cli/bucket-operations/#putbucketpolicy) | Applies an Object Storage bucket policy to an Object Storage bucket. The key elements of bucket policy are [Version](/object-storage/api-cli/bucket-policy/#version), [ID](/object-storage/api-cli/bucket-policy/#id), [Statement](/object-storage/api-cli/bucket-policy/#statement), [Sid](/object-storage/api-cli/bucket-policy/#sid), [Principal](/object-storage/api-cli/bucket-policy/#principal), [Action](/object-storage/api-cli/bucket-policy/#action), [Effect](/object-storage/api-cli/bucket-policy/#effect), [Resource](/object-storage/api-cli/bucket-policy/#resource) and [Condition](/object-storage/api-cli/bucket-policy/#condition). You can find out more about each element by clicking the links, or consulting the full documentation | ✅ | +| [PutBucketTagging](/object-storage/api-cli/bucket-operations/#putbuckettagging) | Sets the tag(s) of a bucket | ✅ | +| [PutBucketVersioning](/object-storage/api-cli/bucket-operations/#putbucketversioning) | Sets the versioning state of an existing bucket | ✅ | +| [PutBucketWebsite](/object-storage/api-cli/bucket-operations/#putbucketwebsite) | Enables bucket website and sets the basic configuration for the website | ✅ | @@ -78,31 +78,31 @@ Status: | Feature | Description | Status | | :------------ | :---- | :- | -| [AbortMultipartUpload](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) | Aborts a multipart upload| ✅ | -| [CompleteMultipartUpload](/storage/object/api-cli/multipart-uploads/#completing-a-multipart-upload) | Assembles previously uploaded parts to completes a multipart upload | ✅ | -| [CopyObject](/storage/object/api-cli/object-operations/#putobjectcopy) | Copies an object | ✅ | -| [CreateMultipart](/storage/object/api-cli/object-operations/#createmultipartupload) | Initiates a multipart upload and returns the upload ID | ✅ | -| [DeleteObjects](/storage/object/api-cli/object-operations/#deleteobjects) | Delete multiple objects in a single request (up to 1000) | ✅ | -| [DeleteObject](/storage/object/api-cli/object-operations/#deleteobject) | Deletes an object | ✅ | -| [DeleteObjectTagging](/storage/object/api-cli/object-operations/#deleteobjecttagging) | Deletes the tag(s) of an object | ✅ | -| [GetObject](/storage/object/api-cli/object-operations/#getobject) | Retrieves an object | ✅ | -| [GetObjectAcl](/storage/object/api-cli/object-operations/#getobjectacl) | Gets the ACL of an object | ✅ | -| [GetObjectLegalHold](/storage/object/api-cli/object-lock/#get-object-legal-hold) | Gets an object's current [Legal Hold configuration](/storage/object/api-cli/object-lock/#how-to-manage-object-legal-hold) | ✅ | -| [GetObjectLockConfiguration](/storage/object/api-cli/object-lock/#get-object-lock-configuration) | Gets an [object Lock configuration](/storage/object/api-cli/object-lock/) for a bucket. The specified rule will be applied by default to every new object placed in the bucket | ✅ | -| [GetObjectRetention](/storage/object/api-cli/object-lock/#get-object-retention) | Retrieves an object's [retention settings](/storage/object/api-cli/object-lock/#how-to-configure-object-retention) | ✅ | -| [GetObjectTagging](/storage/object/api-cli/object-operations/#getobjecttagging) | Get the tag(s) of an object | ✅ | -| [HeadObject](/storage/object/api-cli/object-operations/#headobject) | Gets object metadata | ✅ | -| [ListMultipart](/storage/object/api-cli/multipart-uploads/#listing-multipart-uploads) | Lists in-progress multipart uploads | ✅ | -| [OPTIONS object](/storage/object/api-cli/object-operations/#options-object) | Allows to send a preflight request to trigger an evaluation of the rules that are defined in the CORS configuration | ✅ | -| [POST object](/storage/object/api-cli/object-operations/#post-object) | Adds an object to a bucket by using HTML forms | ✅ | -| [PutObject](/storage/object/api-cli/object-operations/#putobject) | Adds an object to a bucket | ✅ | -| [PutObjectAcl](/storage/object/api-cli/object-operations/#putobjectacl) | Adds an ACL to an object | ✅ | -| [PutObjectTagging](/storage/object/api-cli/object-operations/#putobjecttagging) | Adds one or several tags to an object | ✅ | -| [PutObjectLegalHold](/storage/object/api-cli/object-lock/#put-object-legal-hold) | Applies a [Legal Hold configuration](/storage/object/api-cli/object-lock/#how-to-manage-object-legal-hold) to the specified object | ✅ | +| [AbortMultipartUpload](/object-storage/api-cli/multipart-uploads/#aborting-a-multipart-upload) | Aborts a multipart upload| ✅ | +| [CompleteMultipartUpload](/object-storage/api-cli/multipart-uploads/#completing-a-multipart-upload) | Assembles previously uploaded parts to completes a multipart upload | ✅ | +| [CopyObject](/object-storage/api-cli/object-operations/#putobjectcopy) | Copies an object | ✅ | +| [CreateMultipart](/object-storage/api-cli/object-operations/#createmultipartupload) | Initiates a multipart upload and returns the upload ID | ✅ | +| [DeleteObjects](/object-storage/api-cli/object-operations/#deleteobjects) | Delete multiple objects in a single request (up to 1000) | ✅ | +| [DeleteObject](/object-storage/api-cli/object-operations/#deleteobject) | Deletes an object | ✅ | +| [DeleteObjectTagging](/object-storage/api-cli/object-operations/#deleteobjecttagging) | Deletes the tag(s) of an object | ✅ | +| [GetObject](/object-storage/api-cli/object-operations/#getobject) | Retrieves an object | ✅ | +| [GetObjectAcl](/object-storage/api-cli/object-operations/#getobjectacl) | Gets the ACL of an object | ✅ | +| [GetObjectLegalHold](/object-storage/api-cli/object-lock/#get-object-legal-hold) | Gets an object's current [Legal Hold configuration](/object-storage/api-cli/object-lock/#how-to-manage-object-legal-hold) | ✅ | +| [GetObjectLockConfiguration](/object-storage/api-cli/object-lock/#get-object-lock-configuration) | Gets an [object Lock configuration](/object-storage/api-cli/object-lock/) for a bucket. The specified rule will be applied by default to every new object placed in the bucket | ✅ | +| [GetObjectRetention](/object-storage/api-cli/object-lock/#get-object-retention) | Retrieves an object's [retention settings](/object-storage/api-cli/object-lock/#how-to-configure-object-retention) | ✅ | +| [GetObjectTagging](/object-storage/api-cli/object-operations/#getobjecttagging) | Get the tag(s) of an object | ✅ | +| [HeadObject](/object-storage/api-cli/object-operations/#headobject) | Gets object metadata | ✅ | +| [ListMultipart](/object-storage/api-cli/multipart-uploads/#listing-multipart-uploads) | Lists in-progress multipart uploads | ✅ | +| [OPTIONS object](/object-storage/api-cli/object-operations/#options-object) | Allows to send a preflight request to trigger an evaluation of the rules that are defined in the CORS configuration | ✅ | +| [POST object](/object-storage/api-cli/object-operations/#post-object) | Adds an object to a bucket by using HTML forms | ✅ | +| [PutObject](/object-storage/api-cli/object-operations/#putobject) | Adds an object to a bucket | ✅ | +| [PutObjectAcl](/object-storage/api-cli/object-operations/#putobjectacl) | Adds an ACL to an object | ✅ | +| [PutObjectTagging](/object-storage/api-cli/object-operations/#putobjecttagging) | Adds one or several tags to an object | ✅ | +| [PutObjectLegalHold](/object-storage/api-cli/object-lock/#put-object-legal-hold) | Applies a [Legal Hold configuration](/object-storage/api-cli/object-lock/#how-to-manage-object-legal-hold) to the specified object | ✅ | | PutObjectLockConfiguration | Sets an object lock configuration on a specified bucket | ✅ | -| [PutObjectRetention](/storage/object/api-cli/object-lock/#put-object-retention) | Places an [object Retention configuration](/storage/object/api-cli/object-lock/#how-to-configure-object-retention) on an object | ✅ | -| [RestoreObject](/storage/object/api-cli/object-operations/#restoreobject) | Restores an object from `Glacier` | ✅ | -| [UploadPart](/storage/object/api-cli/multipart-uploads/#uploading-a-part) | Uploads a part in a multipart upload | ✅ | +| [PutObjectRetention](/object-storage/api-cli/object-lock/#put-object-retention) | Places an [object Retention configuration](/object-storage/api-cli/object-lock/#how-to-configure-object-retention) on an object | ✅ | +| [RestoreObject](/object-storage/api-cli/object-operations/#restoreobject) | Restores an object from `Glacier` | ✅ | +| [UploadPart](/object-storage/api-cli/multipart-uploads/#uploading-a-part) | Uploads a part in a multipart upload | ✅ | | UploadPartCopy | Copies data from an existing object as data source to upload a part | ✅ | diff --git a/storage/object/concepts.mdx b/storage/object/concepts.mdx index 8299ed89b0..2229a88cc9 100644 --- a/storage/object/concepts.mdx +++ b/storage/object/concepts.mdx @@ -21,21 +21,21 @@ control lists (ACL) are subresources attached to buckets and objects. They defin An Object Storage bucket is a scalable storage container used to store and organize [objects](#object). It allows users to manage large volumes of unstructured data, such as images, videos, and backups, with high durability and accessibility. -Buckets can contain as many objects as you want. Refer to our [dedicated documentation](/storage/object/how-to/create-a-bucket/) for more information. +Buckets can contain as many objects as you want. Refer to our [dedicated documentation](/object-storage/how-to/create-a-bucket/) for more information. ## Bucket policy -Bucket policies are assigned to [principals](#principal), who will be allowed or denied access to resources and actions. They can be created and applied using the [CLI](/storage/object/api-cli/create-bucket-policy/) or via the [Scaleway console](/storage/object/how-to/create-bucket-policy/). +Bucket policies are assigned to [principals](#principal), who will be allowed or denied access to resources and actions. They can be created and applied using the [CLI](/object-storage/api-cli/create-bucket-policy/) or via the [Scaleway console](/object-storage/how-to/create-bucket-policy/). ## Bucket website -A feature that allows you to [host static websites on buckets](/storage/object/how-to/use-bucket-website/). +A feature that allows you to [host static websites on buckets](/object-storage/how-to/use-bucket-website/). ## Edge Services -A feature that allows you to create a cache and a custom domain for your buckets. See our [dedicated documentation](/storage/object/how-to/get-started-edge-services/). +A feature that allows you to create a cache and a custom domain for your buckets. See our [dedicated documentation](/object-storage/how-to/get-started-edge-services/). ## Endpoint @@ -63,7 +63,7 @@ An endpoint represents one end of a communication channel. In the context of Obj A legal hold provides the same protection as a retention period, but it has no expiration date. It takes the form of an ON/OFF switch that can be applied to every object in a locked bucket, independently of the lock configuration, or the object retention or its age. It can be applied to objects which are locked. A legal hold remains in place until you explicitly remove it. -Refer to our [dedicated documentation](/storage/object/api-cli/object-lock/#how-to-manage-object-legal-hold) for more information. +Refer to our [dedicated documentation](/object-storage/api-cli/object-lock/#how-to-manage-object-legal-hold) for more information. ## Lifecycle configuration @@ -72,11 +72,11 @@ A lifecycle configuration is a set of rules that defines actions applied to a gr - **Expiration** defines when objects expire, to delete objects automatically on your behalf. - **Transition** defines when objects change their storage class. -Find out more in our how-to on [managing lifecycle rules from the console](/storage/object/how-to/manage-lifecycle-rules/). +Find out more in our how-to on [managing lifecycle rules from the console](/object-storage/how-to/manage-lifecycle-rules/). ## Metrics -A feature that allows you to [monitor your Object Storage consumption](/storage/object/how-to/monitor-consumption/) with a graphical interface from your Scaleway console. Object Storage Metrics provide information about: +A feature that allows you to [monitor your Object Storage consumption](/object-storage/how-to/monitor-consumption/) with a graphical interface from your Scaleway console. Object Storage Metrics provide information about: - the number of objects in a bucket - the storage used @@ -84,7 +84,7 @@ A feature that allows you to [monitor your Object Storage consumption](/storage/ ## Multipart uploads -Allows you to [upload large files to the Object Storage platform in multiple parts](/storage/object/api-cli/multipart-uploads/). It is possible to store objects up to 5 TB in size on the platform. +Allows you to [upload large files to the Object Storage platform in multiple parts](/object-storage/api-cli/multipart-uploads/). It is possible to store objects up to 5 TB in size on the platform. A multipart upload consists of three steps: @@ -102,7 +102,7 @@ An Amazon S3 API feature that allows users to lock objects to prevent them from The feature uses a write-once-read-many (WORM) data protection model. This model is generally used in cases where data cannot be altered once it has been written. It provides regulatory compliance and protection against ransomware and malicious or accidental deletion of objects. -Refer to our [dedicated documentation](/storage/object/api-cli/object-lock/#how-to-manage-object-legal-hold) for more information. +Refer to our [dedicated documentation](/object-storage/api-cli/object-lock/#how-to-manage-object-legal-hold) for more information. ## Object Storage @@ -127,7 +127,7 @@ As an example, consider the following objects: - `images/screenshot01.jpg` - `images/screenshot02.jpg` -Creating a [lifecycle rule](/storage/object/how-to/manage-lifecycle-rules/) based on the `images/` prefix will apply to all objects, whereas a rule based on `images/ph` will only apply to the first two objects. +Creating a [lifecycle rule](/object-storage/how-to/manage-lifecycle-rules/) based on the `images/` prefix will apply to all objects, whereas a rule based on `images/ph` will only apply to the first two objects. ## Principal @@ -160,13 +160,13 @@ A retention period specifies a fixed period for which an object remains [locked] ## Amazon S3 -Amazon S3 is the most widely known Object Storage protocol. Scaleway Object Storage officially supports a subset of Amazon S3. The list of supported features is described in the [Object Storage API documentation](/storage/object/api-cli/using-api-call-list/). +Amazon S3 is the most widely known Object Storage protocol. Scaleway Object Storage officially supports a subset of Amazon S3. The list of supported features is described in the [Object Storage API documentation](/object-storage/api-cli/using-api-call-list/). ## Signature V2, Signature V4 When you send HTTP requests to Object Storage, you sign the requests so that we can identify who sent them. You sign requests with your Scaleway access key, which consists of an access key and a secret key. The two main Amazon S3 protocols for authentication are Signature v2 and Signature v4. Signature v4 is more recent and it is the recommended version. -Refer to the [dedicated documentation](/storage/object/api-cli/generate-aws4-auth-signature/) for more information on v4 signature. +Refer to the [dedicated documentation](/object-storage/api-cli/generate-aws4-auth-signature/) for more information on v4 signature. ## Storage class @@ -188,4 +188,4 @@ Object visibility specifies whether an object is publicly visible or not. It is ## Versioning -Versioning allows you to keep multiple variants of an object in the same bucket. When [enabled](/storage/object/how-to/use-bucket-versioning/), you can list archived versions of an object or permanently delete an archived version. \ No newline at end of file +Versioning allows you to keep multiple variants of an object in the same bucket. When [enabled](/object-storage/how-to/use-bucket-versioning/), you can list archived versions of an object or permanently delete an archived version. \ No newline at end of file diff --git a/storage/object/how-to/abort-incomplete-mpu.mdx b/storage/object/how-to/abort-incomplete-mpu.mdx index 9daa184f68..65ab9d4bf5 100644 --- a/storage/object/how-to/abort-incomplete-mpu.mdx +++ b/storage/object/how-to/abort-incomplete-mpu.mdx @@ -20,14 +20,14 @@ The [Scaleway console](https://console.scaleway.com/) lists your Object Storage Incomplete multipart uploads are charged even though they are not finished as they use storage space. -You can automate the process of aborting incomplete multipart uploads using [lifecycle rules](/storage/object/how-to/manage-lifecycle-rules). +You can automate the process of aborting incomplete multipart uploads using [lifecycle rules](/object-storage/how-to/manage-lifecycle-rules). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- At least one incomplete [multipart upload](/storage/object/api-cli/multipart-uploads/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- At least one incomplete [multipart upload](/object-storage/api-cli/multipart-uploads/) ## How to view the information of an incomplete multipart upload @@ -44,7 +44,7 @@ From this page, you can consult the following elements of an incomplete multipar - Storage class - List of parts uploaded so far -Refer to the [dedicated documentation](/storage/object/api-cli/multipart-uploads/) for more information on how to create and manage multipart uploads. +Refer to the [dedicated documentation](/object-storage/api-cli/multipart-uploads/) for more information on how to create and manage multipart uploads. ## How to abort an incomplete multipart upload diff --git a/storage/object/how-to/access-objects-via-https.mdx b/storage/object/how-to/access-objects-via-https.mdx index 19c1a99044..22e7453611 100644 --- a/storage/object/how-to/access-objects-via-https.mdx +++ b/storage/object/how-to/access-objects-via-https.mdx @@ -16,14 +16,14 @@ categories: Scaleway Object Storage allows you to access your objects via HTTPS. -If an object is [private](/storage/object/how-to/manage-object-visibility/), you can create a temporary public link from the [Scaleway console](https://console.scaleway.com). +If an object is [private](/object-storage/how-to/manage-object-visibility/), you can create a temporary public link from the [Scaleway console](https://console.scaleway.com). If an object is public, you can retreive the link to access it from the [Scaleway console](https://console.scaleway.com). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Created an Object Storage bucket](/storage/object/how-to/create-a-bucket/) and have [uploaded objects](storage/object/how-to/upload-files-into-a-bucket/) to it +- [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) and have [uploaded objects](object-storage/how-to/upload-files-into-a-bucket/) to it 1. Click **Object Storage** on the side menu. The list of your buckets displays. 2. Click the bucket that contains the file you want to access. A list of your objects displays. @@ -33,5 +33,5 @@ If an object is public, you can retreive the link to access it from the [Scalewa 6. Click **Generate link**. Your temporary public link displays. - To make the link to an object permanent, [change its visibility](/storage/object/how-to/manage-object-visibility/) to **public**. The link will work as long as the object is public. + To make the link to an object permanent, [change its visibility](/object-storage/how-to/manage-object-visibility/) to **public**. The link will work as long as the object is public. diff --git a/storage/object/how-to/create-a-bucket.mdx b/storage/object/how-to/create-a-bucket.mdx index b43c756098..fdea8ec2ab 100644 --- a/storage/object/how-to/create-a-bucket.mdx +++ b/storage/object/how-to/create-a-bucket.mdx @@ -19,27 +19,27 @@ Object Storage allows you to store different types of objects (documents, images - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization To get started with Object Storage, you must first create a bucket. Objects are gathered into buckets. Each bucket represents a space where objects are stored. 1. Click **Object Storage** on the left side menu of the console. The Object Storage dashboard displays. 2. Click **+ Create bucket**. The bucket creation page displays. -3. Select the [region](/storage/object/concepts/#region-and-availability-zone) in which to create your bucket: +3. Select the [region](/object-storage/concepts/#region-and-availability-zone) in which to create your bucket: - Amsterdam, The Netherlands: - Region: `nl-ams` - Paris, France: - Region: `fr-par` - Warsaw, Poland: - Region: `pl-waw` -4. Check **Public** or **Private** to define the bucket visibility. The bucket visibility specifies whether everyone can see the list of objects in the bucket. It does not affect [object visibility](/storage/object/concepts/#visibility). +4. Check **Public** or **Private** to define the bucket visibility. The bucket visibility specifies whether everyone can see the list of objects in the bucket. It does not affect [object visibility](/object-storage/concepts/#visibility). A file uploaded to a public bucket is private by default. A private file stored in a public bucket is not publicly accessible. You can change the bucket visibility at any time from the **Bucket settings** tab. 5. Select a use case for your bucket. -6. Enable [bucket versioning](/storage/object/how-to/use-bucket-versioning/) if you want to store multiple versions of your objects (this may lead to higher storage costs). +6. Enable [bucket versioning](/object-storage/how-to/use-bucket-versioning/) if you want to store multiple versions of your objects (this may lead to higher storage costs). 7. If applicable, you can tick the **Activate 90-day free trial** to benefit from 750 GB of free [Multi-AZ class storage](/faq/objectstorage/#what-are-the-object-storage-classes-offered-by-scaleway) for buckets in your Organization, across all regions. Refer to our [dedicated FAQ](/faq/objectstorage/#how-can-i-benefit-from-the-object-storage-free-trial) for more information. 8. Enter a name for your bucket. 9. Optionally, you can use the cost estimator to simulate your Object Storage costs. diff --git a/storage/object/how-to/create-bucket-policy.mdx b/storage/object/how-to/create-bucket-policy.mdx index 00193bbc38..c50509173e 100644 --- a/storage/object/how-to/create-bucket-policy.mdx +++ b/storage/object/how-to/create-bucket-policy.mdx @@ -14,16 +14,16 @@ categories: - object-storage --- -Scaleway Object Storage allows you to create [bucket policies](/storage/object/concepts/#bucket-policy) directly from the [Scaleway console](https://console.scaleway.com). +Scaleway Object Storage allows you to create [bucket policies](/object-storage/concepts/#bucket-policy) directly from the [Scaleway console](https://console.scaleway.com). -To create and apply a bucket policy from the AWS CLI, refer to the [dedicated documentation](/storage/object/api-cli/create-bucket-policy/). +To create and apply a bucket policy from the AWS CLI, refer to the [dedicated documentation](/object-storage/api-cli/create-bucket-policy/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a bucket](/object-storage/how-to/create-a-bucket/) ## How to create a bucket policy @@ -36,39 +36,39 @@ To create and apply a bucket policy from the AWS CLI, refer to the [dedicated do 4. Select the bucket to which you want to apply the policy. - - You can only apply a policy to a single bucket, but you can [duplicate an existing policy](/storage/object/how-to/create-bucket-policy/#how-to-apply-an-existing-policy-to-another-bucket) and apply it to another bucket. + - You can only apply a policy to a single bucket, but you can [duplicate an existing policy](/object-storage/how-to/create-bucket-policy/#how-to-apply-an-existing-policy-to-another-bucket) and apply it to another bucket. - If you change the target bucket of an existing policy, the bucket policy will be removed from the original bucket, and applied to the selected bucket. 5. Select your preferred creation method: - - The **policy generator** to add [statements](/storage/object/api-cli/bucket-policy/#statement) using a form. + - The **policy generator** to add [statements](/object-storage/api-cli/bucket-policy/#statement) using a form. - The **JSON editor** to manually write or paste your bucket policy in a code editor. - Refer to the dedicated documentation on [bucket policies overview](/storage/object/api-cli/bucket-policy/) and [combining IAM and bucket policies](/storage/object/api-cli/combining-iam-and-object-storage/) for more information on how to build a bucket policy. + Refer to the dedicated documentation on [bucket policies overview](/object-storage/api-cli/bucket-policy/) and [combining IAM and bucket policies](/object-storage/api-cli/combining-iam-and-object-storage/) for more information on how to build a bucket policy. 6. Keep the **Maintain access to bucket** box ticked to prevent accidental lockout from your bucket. By default, the bucket policy contains a **secure statement** that allows every action to the user creating the policy. -7. Create a [statement](/storage/object/api-cli/bucket-policy/#statement) by entering the following information: +7. Create a [statement](/object-storage/api-cli/bucket-policy/#statement) by entering the following information: - - Enter a unique [statement ID](/storage/object/api-cli/bucket-policy/#sid) (also called **Sid**) describing the purpose of the statement. - - Select the types of [principals](/storage/object/api-cli/bucket-policy/#principal) of your bucket policy from the drop-down menu. + - Enter a unique [statement ID](/object-storage/api-cli/bucket-policy/#sid) (also called **Sid**) describing the purpose of the statement. + - Select the types of [principals](/object-storage/api-cli/bucket-policy/#principal) of your bucket policy from the drop-down menu. - Select the **users** and **applications** you want to grant access to. - - Select the [Actions](/storage/object/api-cli/bucket-policy/#action) to allow to the principal(s). + - Select the [Actions](/object-storage/api-cli/bucket-policy/#action) to allow to the principal(s). To allow different action sets to the different principals, create multiple statements. - - Select [resources](/storage/object/api-cli/bucket-policy/#resource) by entering the prefix of the objects, followed by `/*`. Enter `*` to select every object in the bucket. - - Add [conditions](/storage/object/api-cli/bucket-policy/#condition) by selecting by selecting them from the drop-down menu, and adding a supported key-value pair. + - Select [resources](/object-storage/api-cli/bucket-policy/#resource) by entering the prefix of the objects, followed by `/*`. Enter `*` to select every object in the bucket. + - Add [conditions](/object-storage/api-cli/bucket-policy/#condition) by selecting by selecting them from the drop-down menu, and adding a supported key-value pair. - - Enter a unique [statement ID](/storage/object/api-cli/bucket-policy/#sid) (also called **Sid**) describing the purpose of the statement. - - Enter the types of [principals](/storage/object/api-cli/bucket-policy/#principal) and the user/application ID you want to grant access as shown below: + - Enter a unique [statement ID](/object-storage/api-cli/bucket-policy/#sid) (also called **Sid**) describing the purpose of the statement. + - Enter the types of [principals](/object-storage/api-cli/bucket-policy/#principal) and the user/application ID you want to grant access as shown below: ```json "Principal":{ "SCW":[ @@ -77,7 +77,7 @@ To create and apply a bucket policy from the AWS CLI, refer to the [dedicated do ] }, ``` - - Enter the [Actions](/storage/object/api-cli/bucket-policy/#action) to allow to the principal(s) as shown below. Enter `s3:*` to allow all actions. + - Enter the [Actions](/object-storage/api-cli/bucket-policy/#action) to allow to the principal(s) as shown below. Enter `s3:*` to allow all actions. ```json "Action":[ "s3:ListBucket", @@ -87,7 +87,7 @@ To create and apply a bucket policy from the AWS CLI, refer to the [dedicated do To allow different action sets to the different principals, create multiple statements. - - Grant access to [resources](/storage/object/api-cli/bucket-policy/#resource) by entering the prefix of the objects as shown below. Enter `*` to select every object in the bucket. + - Grant access to [resources](/object-storage/api-cli/bucket-policy/#resource) by entering the prefix of the objects as shown below. Enter `*` to select every object in the bucket. ```json "Resource":[ "", @@ -97,7 +97,7 @@ To create and apply a bucket policy from the AWS CLI, refer to the [dedicated do Add the bucket as a resource to allow operations on the bucket, such as `s3:ListBucket`. - - Add [conditions](/storage/object/api-cli/bucket-policy/#condition) as shown below: + - Add [conditions](/object-storage/api-cli/bucket-policy/#condition) as shown below: ```json "Condition": { "DateGreaterThan": { @@ -124,7 +124,7 @@ To create and apply a bucket policy from the AWS CLI, refer to the [dedicated do ## Bucket policy example -Below is an example of a bucket policy generated using the console. For more information on each element of a bucket policy, refer to the [dedicated documentation](/storage/object/api-cli/bucket-policy/). +Below is an example of a bucket policy generated using the console. For more information on each element of a bucket policy, refer to the [dedicated documentation](/object-storage/api-cli/bucket-policy/). ```json { @@ -231,7 +231,7 @@ Alternatively, you can also delete a bucket policy by clicking - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) When you delete a bucket, every object stored inside it is deleted as well. diff --git a/storage/object/how-to/delete-an-object.mdx b/storage/object/how-to/delete-an-object.mdx index 3866a91b19..8fa9612cef 100644 --- a/storage/object/how-to/delete-an-object.mdx +++ b/storage/object/how-to/delete-an-object.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- An object in your [bucket](/storage/object/how-to/upload-files-into-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- An object in your [bucket](/object-storage/how-to/upload-files-into-a-bucket/) 1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. 2. Click the bucket name that contains the objects you want to delete. A list of the objects stored in the bucket displays. diff --git a/storage/object/how-to/download-files-from-a-bucket.mdx b/storage/object/how-to/download-files-from-a-bucket.mdx index e5e8f9d33c..928e1005e6 100644 --- a/storage/object/how-to/download-files-from-a-bucket.mdx +++ b/storage/object/how-to/download-files-from-a-bucket.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- An object in your [bucket](/storage/object/how-to/upload-files-into-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- An object in your [bucket](/object-storage/how-to/upload-files-into-a-bucket/) 1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. 2. Click the name of your selected bucket in the buckets list. A list of your objects displays. diff --git a/storage/object/how-to/edit-storage-class.mdx b/storage/object/how-to/edit-storage-class.mdx index 2acefac6bb..b1069818d9 100644 --- a/storage/object/how-to/edit-storage-class.mdx +++ b/storage/object/how-to/edit-storage-class.mdx @@ -14,22 +14,22 @@ categories: - object-storage --- -Scaleway Object Storage offers several [storage classes](/storage/object/concepts/#storage-class) to choose from depending on the performance, access, resiliency, and cost requirements of your workloads. The [Scaleway console](https://console/) allows you to edit the storage class of objects individually. +Scaleway Object Storage offers several [storage classes](/object-storage/concepts/#storage-class) to choose from depending on the performance, access, resiliency, and cost requirements of your workloads. The [Scaleway console](https://console/) allows you to edit the storage class of objects individually. -To change the storage class of several or all objects in a bucket, create a [lifecycle rule](/storage/object/how-to/manage-lifecycle-rules/). +To change the storage class of several or all objects in a bucket, create a [lifecycle rule](/object-storage/how-to/manage-lifecycle-rules/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) 1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. 2. Click the name of the bucket containing the object you want to edit. The list of objects displays. 3. Click next to the object that you want to transfer to another storage class. A pop-up displays. -5. Select a [storage class](/storage/object/concepts/#storage-class) from the drop-down menu. +5. Select a [storage class](/object-storage/concepts/#storage-class) from the drop-down menu. If you transfer objects to `Glacier` class, you might have to restore your data at a later date. To facilitate the steps of restoration and ensure fast restitution of your data, we recommend you use average-sized files (larger than 1 MB). diff --git a/storage/object/how-to/get-started-edge-services.mdx b/storage/object/how-to/get-started-edge-services.mdx index c0df717b8b..a671a1232f 100644 --- a/storage/object/how-to/get-started-edge-services.mdx +++ b/storage/object/how-to/get-started-edge-services.mdx @@ -23,14 +23,14 @@ Read on to learn how to create an Edge Services pipeline for your Object Storage - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to subscribe to Edge Services To use Edge Services, you must subscribe to a [pricing plan](https://www.scaleway.com/en/pricing/network/#edge-services). Within its monthly price, each pricing plan lets you create a certain number of pipelines and consume a certain amount of cache data. -Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/network/edge-services/how-to/subscribe-edge-services/). +Find out more about pricing plans and how to subscribe to Edge Services in our [dedicated documentation](/edge-services/how-to/subscribe-edge-services/). ## How to create an Edge Services pipeline @@ -59,19 +59,19 @@ You can create an Edge Services pipeline from the **Edge Services** section of t - Your bucket's [visibility](/storage/object/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/storage/object/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. + Your bucket's [visibility](/object-storage/concepts/#visibility) can be set to **private**, but any objects within it that you want to expose via Edge Services must be set to [**public** visibility](/object-storage/how-to/manage-object-visibility/). However, in the case that you are using Edge Services with bucket website, objects can remain private. ## How to access your bucket via Edge Services -Once you have created an Edge Services for your bucket, you can access your bucket and its content via its original Object Storage endpoint, and via its new customizable Edge Storage endpoint. Get full details in the [Edge Services](/network/edge-services/how-to/create-pipeline-bucket/#how-to-access-your-bucket-via-edge-services) section of the documentation. +Once you have created an Edge Services for your bucket, you can access your bucket and its content via its original Object Storage endpoint, and via its new customizable Edge Storage endpoint. Get full details in the [Edge Services](/edge-services/how-to/create-pipeline-bucket/#how-to-access-your-bucket-via-edge-services) section of the documentation. ## How to configure your pipeline See the dedicated Edge Services section of the documentation for help with: -- [Customizing your Edge Services endpoint](/network/edge-services/how-to/configure-custom-domain/) -- [Configuring your Edge Services cache](/network/edge-services/how-to/configure-cache/) +- [Customizing your Edge Services endpoint](/edge-services/how-to/configure-custom-domain/) +- [Configuring your Edge Services cache](/edge-services/how-to/configure-cache/) -To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/network/edge-services/) page. +To go further, browse our full range of Edge Services documentation on the [Edge Services Overview](/edge-services/) page. diff --git a/storage/object/how-to/manage-lifecycle-rules.mdx b/storage/object/how-to/manage-lifecycle-rules.mdx index 1599409a62..0c90c519da 100644 --- a/storage/object/how-to/manage-lifecycle-rules.mdx +++ b/storage/object/how-to/manage-lifecycle-rules.mdx @@ -14,15 +14,15 @@ categories: - object-storage --- -With the Scaleway console, you can use lifecycle rules to [manually](/storage/object/how-to/edit-storage-class/) or automatically change the storage class of your objects. These rules also allow users to set expiration dates for objects and their versions. +With the Scaleway console, you can use lifecycle rules to [manually](/object-storage/how-to/edit-storage-class/) or automatically change the storage class of your objects. These rules also allow users to set expiration dates for objects and their versions. -Lifecycle rules also allow you to automatically abort incomplete [multipart uploads](/storage/object/api-cli/multipart-uploads/). +Lifecycle rules also allow you to automatically abort incomplete [multipart uploads](/object-storage/api-cli/multipart-uploads/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to create a lifecycle rule 1. Click **Object Storage** in the **Storage** section of the side menu. The list of your buckets displays. @@ -33,19 +33,19 @@ Lifecycle rules also allow you to automatically abort incomplete [multipart uplo 6. Select the scope of the lifecycle rule: - Apply the rule to all the objects contained in the bucket. - Filter the objects you want the rule to be applied to by one or both of the following criteria: - - [**Prefix**](/storage/object/concepts/#prefix): based on the object name and path. The defined rule will be applied to all objects with the same name [prefix](/storage/object/concepts/#prefix). - - [**Tags**](/storage/object/concepts/#tags): comprised of a **key** and an associated **value**. These tags should be defined before rule creation, for either a bucket or an object. You can add one or more tags to your filter. + - [**Prefix**](/object-storage/concepts/#prefix): based on the object name and path. The defined rule will be applied to all objects with the same name [prefix](/object-storage/concepts/#prefix). + - [**Tags**](/object-storage/concepts/#tags): comprised of a **key** and an associated **value**. These tags should be defined before rule creation, for either a bucket or an object. You can add one or more tags to your filter. 7. Configure the behavior of the lifecycle rule: - Automatically transition the current version of your objects to another storage class after a specified number of days. - Automatically delete the current version of your objects after a specified number of days. - - Automatically abort [incomplete multipart uploads](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) after a specified number of days. + - Automatically abort [incomplete multipart uploads](/object-storage/api-cli/multipart-uploads/#aborting-a-multipart-upload) after a specified number of days. 8. Click **Next Step** to proceed. 9. Review the summary of your lifecycle rule, then click **Create lifecycle rule** to confirm. - - Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/storage/object/how-to/edit-storage-class/) or [delete](/storage/object/how-to/delete-an-object/) your objects manually. + - Lifecycle rules are limited to 500,000 jobs per day. Beyond this limit, you can [transition](/object-storage/how-to/edit-storage-class/) or [delete](/object-storage/how-to/delete-an-object/) your objects manually. - Lifecycle rules only allow the following transitions: - Standard -> Onezone IA diff --git a/storage/object/how-to/manage-object-visibility.mdx b/storage/object/how-to/manage-object-visibility.mdx index e83e23f9de..678fa58322 100644 --- a/storage/object/how-to/manage-object-visibility.mdx +++ b/storage/object/how-to/manage-object-visibility.mdx @@ -14,13 +14,13 @@ categories: - object-storage --- -Object visibility specifies whether your object is visible to others or not, independently from [bucket visibility](/storage/object/concepts/#visibility). +Object visibility specifies whether your object is visible to others or not, independently from [bucket visibility](/object-storage/concepts/#visibility). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) All objects are private by default, even if they are in a public bucket. A private file in a public bucket cannot be accessed publicly. @@ -36,12 +36,12 @@ Object visibility specifies whether your object is visible to others or not, ind 6. Click **Update object visibility** to confirm. -If you upload a file using the CLI, you can make it public by using the `--acl public-read` parameter. However, [bucket policies](/storage/object/api-cli/bucket-policy/) take precedence over ACLs. +If you upload a file using the CLI, you can make it public by using the `--acl public-read` parameter. However, [bucket policies](/object-storage/api-cli/bucket-policy/) take precedence over ACLs. ## Manage the visibility of multiple objects -You can manage the visibility of multiple ojects at a time using a [bucket policy](/storage/object/api-cli/bucket-policy/) as shown below. By allowing [GetObject](/storage/object/api-cli/object-operations/#getobject) operations to everyone, the desired objects can be accessed by any person with the link to the object. +You can manage the visibility of multiple ojects at a time using a [bucket policy](/object-storage/api-cli/bucket-policy/) as shown below. By allowing [GetObject](/object-storage/api-cli/object-operations/#getobject) operations to everyone, the desired objects can be accessed by any person with the link to the object. ```json { diff --git a/storage/object/how-to/monitor-consumption.mdx b/storage/object/how-to/monitor-consumption.mdx index dbaf7aa75a..1c5cdc32b9 100644 --- a/storage/object/how-to/monitor-consumption.mdx +++ b/storage/object/how-to/monitor-consumption.mdx @@ -14,19 +14,19 @@ categories: - object-storage --- -You can view your Object Storage's metrics and logs using [Scaleway Cockpit](/observability/cockpit/quickstart/). Scaleway Object Storage is fully integrated into Cockpit, and allows you to monitor your objects, storage usage, and bandwidth at a glance. This page explains how to get started with Scaleway Cockpit for viewing your Object Storage metrics and logs. +You can view your Object Storage's metrics and logs using [Scaleway Cockpit](/cockpit/quickstart/). Scaleway Object Storage is fully integrated into Cockpit, and allows you to monitor your objects, storage usage, and bandwidth at a glance. This page explains how to get started with Scaleway Cockpit for viewing your Object Storage metrics and logs. -Cockpit is available in all [regions](/storage/object/concepts/#region-and-availability-zone) for Object Storage. +Cockpit is available in all [regions](/object-storage/concepts/#region-and-availability-zone) for Object Storage. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to activate your Cockpit -Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/observability/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). +Scaleway Cockpit is activated by default if you have created [Scaleway resources integrated with Cockpit](/cockpit/reference-content/cockpit-limitations/#product-integration-into-cockpit). ## How to access the Grafana dashboard @@ -34,7 +34,7 @@ To view your Object Storage metrics and logs, use the Grafana dashboard, which i - First, you must create a user and their associated credentials (a username and password) for Grafana. - Then use these credentials to access the Grafana dashboard for all your Scaleway products via the Scaleway console. -1. Create a Grafana user and [retrieve your username and password](/observability/cockpit/how-to/retrieve-grafana-credentials/). +1. Create a Grafana user and [retrieve your username and password](/cockpit/how-to/retrieve-grafana-credentials/). 2. From the Scaleway console [Cockpit overview page](https://console.scaleway.com/cockpit/overview), click **Open dashboards** in the top right corner. diff --git a/storage/object/how-to/restore-an-object-from-glacier.mdx b/storage/object/how-to/restore-an-object-from-glacier.mdx index 3e51a8429f..360f937745 100644 --- a/storage/object/how-to/restore-an-object-from-glacier.mdx +++ b/storage/object/how-to/restore-an-object-from-glacier.mdx @@ -17,9 +17,9 @@ categories: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- An object in [Glacier storage class](/storage/object/how-to/edit-storage-class/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- An object in [Glacier storage class](/object-storage/how-to/edit-storage-class/) Objects in Glacier can only be restored to `Standard` class. @@ -46,7 +46,7 @@ categories: ## How to restore all objects in a bucket -If you have numerous files in a bucket that you would like to restore, we recommend using the command line interface, with a dedicated tool such as the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/). +If you have numerous files in a bucket that you would like to restore, we recommend using the command line interface, with a dedicated tool such as the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/). 1. Run the command below in a terminal to create a list of objects to restore, and store it as a text file. Make sure to replace `` with the name of your bucket. @@ -71,7 +71,7 @@ If you have numerous files in a bucket that you would like to restore, we recomm ## Restore time -The time it takes to restore an object depends on the size of the object and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for the restore to start. +The time it takes to restore an object depends on the size of the object and if [multipart](/object-storage/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for the restore to start. For multipart objects, each part is equivalent to one object. Consequently, the more parts your object has, the longer the restore time will be. diff --git a/storage/object/how-to/upload-files-into-a-bucket.mdx b/storage/object/how-to/upload-files-into-a-bucket.mdx index c7a839088c..4b97fe9e45 100644 --- a/storage/object/how-to/upload-files-into-a-bucket.mdx +++ b/storage/object/how-to/upload-files-into-a-bucket.mdx @@ -14,13 +14,13 @@ categories: - object-storage --- -This page explains how to upload files into an Object Storage bucket using the [Scaleway console](https://consol.scaleway.com). To upload an object using the Amazon S3 API, refer to the [dedicated documentation](/storage/object/api-cli/object-operations/#putobject). +This page explains how to upload files into an Object Storage bucket using the [Scaleway console](https://consol.scaleway.com). To upload an object using the Amazon S3 API, refer to the [dedicated documentation](/object-storage/api-cli/object-operations/#putobject). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) 1. Click **Object Storage** in the **Storage** section of the side menu. A list of your buckets displays. 2. Click the bucket name into which you want to upload your file. @@ -28,8 +28,8 @@ This page explains how to upload files into an Object Storage bucket using the [ Before uploading your files, make sure the file name is in accordance with the [AWS S3 Object key naming guidelines](https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html#object-key-guidelines). -4. Select the [storage class](/storage/object/concepts/#storage-class) of your object. Scaleway Object Storage allows you to associate storage classes with each of your objects. +4. Select the [storage class](/object-storage/concepts/#storage-class) of your object. Scaleway Object Storage allows you to associate storage classes with each of your objects. - Do not close your web browser during an upload, as it can result in an incomplete upload. If you want to upload files larger than 1 GB, we recommend [using the CLI](/storage/object/api-cli/object-operations/#putobject). + Do not close your web browser during an upload, as it can result in an incomplete upload. If you want to upload files larger than 1 GB, we recommend [using the CLI](/object-storage/api-cli/object-operations/#putobject). When the upload is completed, a list of the objects displays, including the newly uploaded objects. diff --git a/storage/object/how-to/use-bucket-versioning.mdx b/storage/object/how-to/use-bucket-versioning.mdx index f14c54ea6d..abb96888d5 100644 --- a/storage/object/how-to/use-bucket-versioning.mdx +++ b/storage/object/how-to/use-bucket-versioning.mdx @@ -21,8 +21,8 @@ Versioning allows you to easily recover your objects in case of unintended user - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to enable versioning diff --git a/storage/object/how-to/use-bucket-website.mdx b/storage/object/how-to/use-bucket-website.mdx index d4e7530ce2..2965745f9a 100644 --- a/storage/object/how-to/use-bucket-website.mdx +++ b/storage/object/how-to/use-bucket-website.mdx @@ -19,9 +19,9 @@ The Bucket Website feature allows you to host [static websites](https://en.wikip - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to enable the bucket website feature @@ -38,11 +38,11 @@ The Bucket Website feature allows you to host [static websites](https://en.wikip - The index and error files must be located at the root of your bucket, rather than in a folder. - - When Bucket Website is enabled, a default [bucket policy](/storage/object/concepts/#bucket-policy) is applied. All objects in the bucket then become publicly visible. You can create your own bucket policy to change the visibility settings [via CLI](/storage/object/api-cli/bucket-policy/). + - When Bucket Website is enabled, a default [bucket policy](/object-storage/concepts/#bucket-policy) is applied. All objects in the bucket then become publicly visible. You can create your own bucket policy to change the visibility settings [via CLI](/object-storage/api-cli/bucket-policy/). 6. Click **Save configuration** to confirm. The details of your website configuration display. - You can now [upload the **index** and **error** files](/storage/object/how-to/upload-files-into-a-bucket/) to your bucket, if you have not already done so, as well as the other files that make up your static website. + You can now [upload the **index** and **error** files](/object-storage/how-to/upload-files-into-a-bucket/) to your bucket, if you have not already done so, as well as the other files that make up your static website. Use the drag and drop area to upload several files and folders at the same time. diff --git a/storage/object/how-to/use-obj-stor-with-private-networks.mdx b/storage/object/how-to/use-obj-stor-with-private-networks.mdx index 3e6078d988..f0861791c3 100644 --- a/storage/object/how-to/use-obj-stor-with-private-networks.mdx +++ b/storage/object/how-to/use-obj-stor-with-private-networks.mdx @@ -14,19 +14,19 @@ categories: - object-storage --- -The [Public Gateway](/network/public-gateways/concepts/#public-gateway) feature of the [Private Networks](/network/vpc/concepts/#private-networks) allows Instances in your Private Network to reach resources on the internet without using a public IP address. +The [Public Gateway](/public-gateways/concepts/#public-gateway) feature of the [Private Networks](/vpc/concepts/#private-networks) allows Instances in your Private Network to reach resources on the internet without using a public IP address. This documentation shows how to create an Instance without a public IP address, create a Private Network with a Public Gateway, and a route from your Instance to an Object Storage bucket. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## How to create an Instance without a public IP -Follow the instructions for [creating an Instance](/compute/instances/how-to/create-an-instance/). +Follow the instructions for [creating an Instance](/instances/how-to/create-an-instance/). You must create an Instance without a flexible IP using the following specifications for our Instance: - **Availability Zone**: `nl-ams-1` (or another AZ of your choice). @@ -36,12 +36,12 @@ You must create an Instance without a flexible IP using the following specificat ## How to create a Private Network and attach the Instance -1. Follow the instructions for [creating a Private Network](/network/vpc/how-to/create-private-network/). Make sure you create it in the Region that encompasses the Availability Zone of the Instance you previously created. -2. Follow the instructions to [attach your Instance to the Private Network](/network/vpc/how-to/attach-resources-to-pn/). +1. Follow the instructions for [creating a Private Network](/vpc/how-to/create-private-network/). Make sure you create it in the Region that encompasses the Availability Zone of the Instance you previously created. +2. Follow the instructions to [attach your Instance to the Private Network](/vpc/how-to/attach-resources-to-pn/). ## How to create a Public Gateway and attach the Private Network -1. Follow the instructions for [creating a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/): +1. Follow the instructions for [creating a Public Gateway](/public-gateways/how-to/create-a-public-gateway/): - Select the same Availability Zone as for your previously created Instance. - Select a Public Gateway type according to your needs. - Select **Allocate a new IP**. diff --git a/storage/object/index.mdx b/storage/object/index.mdx index 1be77159fb..3a258a1587 100644 --- a/storage/object/index.mdx +++ b/storage/object/index.mdx @@ -8,7 +8,7 @@ meta: productName="Object Storage" productLogo="objectStorage" description="Object Storage allows you to store and access data from the Scaleway console and Amazon S3-compatible clients." - url="/storage/object/quickstart" + url="/object-storage/quickstart" label="Object Storage Quickstart" /> @@ -20,28 +20,28 @@ meta: icon="rocket" description="Learn the basics of Object Storage in a few simple steps." label="View Quickstart" - url="/storage/object/quickstart/" + url="/object-storage/quickstart/" /> @@ -51,7 +51,7 @@ meta: diff --git a/storage/object/quickstart.mdx b/storage/object/quickstart.mdx index 9c99c0ab0d..c9e1338271 100644 --- a/storage/object/quickstart.mdx +++ b/storage/object/quickstart.mdx @@ -14,12 +14,12 @@ categories: - object-storage --- -[Scaleway Object Storage](/storage/object/concepts/#object-storage) is an Object Storage service based on the Amazon S3 protocol. It allows you to store any objects (documents, images, videos, etc.) and access them anytime from anywhere in the world. You can manage your storage directly from the Scaleway console. On the control panel, you can easily upload, download, and visualize the objects in your buckets. In addition, you can integrate many existing libraries or CLI clients into your application or scripts. +[Scaleway Object Storage](/object-storage/concepts/#object-storage) is an Object Storage service based on the Amazon S3 protocol. It allows you to store any objects (documents, images, videos, etc.) and access them anytime from anywhere in the world. You can manage your storage directly from the Scaleway console. On the control panel, you can easily upload, download, and visualize the objects in your buckets. In addition, you can integrate many existing libraries or CLI clients into your application or scripts. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## How to create a bucket @@ -34,7 +34,7 @@ To get started with Object Storage, you must first create a bucket. Objects are - Region: `fr-par` - Warsaw, Poland: - Region: `pl-waw` -4. Check **Public** or **Private** to define the bucket visibility. The bucket visibility specifies whether everyone can see the list of objects in the bucket. It does not affect [object visibility](/storage/object/concepts/#visibility). +4. Check **Public** or **Private** to define the bucket visibility. The bucket visibility specifies whether everyone can see the list of objects in the bucket. It does not affect [object visibility](/object-storage/concepts/#visibility). A file uploaded to a public bucket is private by default. A private file stored in a public bucket is not publicly accessible. @@ -57,13 +57,13 @@ You can find more information about your bucket by clicking on its name in the * Before uploading your files, make sure the file name follows the [AWS S3 Object key naming guidelines](https://docs.aws.amazon.com/AmazonS3/latest/userguide/object-keys.html#object-key-guidelines). 5. Select the Storage Class of your object. Scaleway Object Storage allows you to associate storage classes with each of your objects. You can choose the storage class depending on your use case: - - [Standard](/storage/object/concepts/#storage-class): The `Standard` class is [Multi-AZ](/faq/objectstorage/#what-are-the-object-storage-classes-offered-by-scaleway), and is available in all regions. It is suitable for any use case, such as on-demand content, like streaming or CDN. - - [One Zone - IA](/storage/object/concepts/#storage-class): The `One Zone - IA` class is available in all regions, and is a good choice for storing secondary backup copies or easily re-creatable data. - - [Glacier](/storage/object/concepts/#storage-class): Archived storage. Your data needs to be restored first to be accessed. This class is available in the `fr-par` and `nl-ams` regions. + - [Standard](/object-storage/concepts/#storage-class): The `Standard` class is [Multi-AZ](/faq/objectstorage/#what-are-the-object-storage-classes-offered-by-scaleway), and is available in all regions. It is suitable for any use case, such as on-demand content, like streaming or CDN. + - [One Zone - IA](/object-storage/concepts/#storage-class): The `One Zone - IA` class is available in all regions, and is a good choice for storing secondary backup copies or easily re-creatable data. + - [Glacier](/object-storage/concepts/#storage-class): Archived storage. Your data needs to be restored first to be accessed. This class is available in the `fr-par` and `nl-ams` regions. - Pricing depends on the storage class you have selected. - - It is possible to [edit the storage classes](/storage/object/how-to/edit-storage-class/) at any time from the Object Storage bucket dashboard. + - It is possible to [edit the storage classes](/object-storage/how-to/edit-storage-class/) at any time from the Object Storage bucket dashboard. A list of the bucket's objects displays including the newly uploaded objects. diff --git a/storage/object/reference-content/cname-record.mdx b/storage/object/reference-content/cname-record.mdx index d5fdb9277f..32dc954c1a 100644 --- a/storage/object/reference-content/cname-record.mdx +++ b/storage/object/reference-content/cname-record.mdx @@ -12,4 +12,4 @@ categories: - network --- -This document has moved to the new [dedicated Edge Services section](/network/edge-services/reference-content/cname-record/). +This document has moved to the new [dedicated Edge Services section](/edge-services/reference-content/cname-record/). diff --git a/storage/object/reference-content/optimize-object-storage-performance.mdx b/storage/object/reference-content/optimize-object-storage-performance.mdx index 69994488d6..e04a82c0e7 100644 --- a/storage/object/reference-content/optimize-object-storage-performance.mdx +++ b/storage/object/reference-content/optimize-object-storage-performance.mdx @@ -14,7 +14,7 @@ categories: - object-storage --- -[Scaleway Object Storage](/storage/object/concepts/#object-storage) is a highly resilient and versatile service that guarantees the reliability and accessibility of your data, while being fully [Amazon S3-compatible](/storage/object/concepts/#amazon-s3) and user-friendly. +[Scaleway Object Storage](/object-storage/concepts/#object-storage) is a highly resilient and versatile service that guarantees the reliability and accessibility of your data, while being fully [Amazon S3-compatible](/object-storage/concepts/#amazon-s3) and user-friendly. Even though it is designed to provide best-in-class latency and throughput, user infrastructure plays a predominant role in achieving optimum efficiency, as many different factors can have an impact on performance, such as your hardware, your software stack, or the way you manage your objects. @@ -33,7 +33,7 @@ Adapt the throughput and latency of your bandwidth according to your most critic - Favor latency over throughput for smaller-size objects (less than 1 MB), such as logs or website assets. Avoid per-request connection to remove TCP slow starts and SSL handshakes on each request. A lower latency will also reduce your Time To First Byte (TTFB) for larger objects. The tradeoff is that `ListObject` operations will take longer to complete as they will return a greater number of objects. - [Prefixes](/storage/object/concepts/#prefix) and the `MaxKeys` parameter allow you to target smaller object batches. + [Prefixes](/object-storage/concepts/#prefix) and the `MaxKeys` parameter allow you to target smaller object batches. ### CPU @@ -50,7 +50,7 @@ For example, if the most CPU-intensive operation uses 20% of your CPU, you can e ### Geographic location -The physical distance to the hardware hosting your Object Storage can also have an impact on performance, especially on latency. Make sure to benchmark the different [regions](/storage/object/concepts/#region-and-availability-zone) where Object Storage is available to compare latency on your mission-critical operations. +The physical distance to the hardware hosting your Object Storage can also have an impact on performance, especially on latency. Make sure to benchmark the different [regions](/object-storage/concepts/#region-and-availability-zone) where Object Storage is available to compare latency on your mission-critical operations. For instance, media and content distribution are often heavily affected by the physical distance between the host and the client, as objects are usually large in this scenario. @@ -73,7 +73,7 @@ Multipart uploads must respect the following technical specifications: - Object size cannot exceed 5 TB - Consider using multipart uploads for objects larger than 50 MB. Refer to [our documentation on managing multipart uploads](/storage/object/api-cli/multipart-uploads/) for more information. + Consider using multipart uploads for objects larger than 50 MB. Refer to [our documentation on managing multipart uploads](/object-storage/api-cli/multipart-uploads/) for more information. Breaking your objects into very small parts is counter productive, as many operations are executed on each part, thus increasing the latency and reducing the throughput. @@ -90,7 +90,7 @@ Multipart upload allows you to leverage a significant concurrency capacity, beca - you can **request different parts simultaneously** using a single cURL request. `GetObject` requests allow you to know the number of parts of an object. -- you can [automate the removal of incomplete multipart uploads](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) to clear the parts that are no longer needed if an upload fails. +- you can [automate the removal of incomplete multipart uploads](/object-storage/api-cli/multipart-uploads/#aborting-a-multipart-upload) to clear the parts that are no longer needed if an upload fails. Use the `Range` header in `GET` requests (both for multipart and non-multipart objects) to create concurrent requests for a better throughput. @@ -98,13 +98,13 @@ Use the `Range` header in `GET` requests (both for multipart and non-multipart o ### Tools and features -Try benchmarking several clients to upload objects, such as [MinIO CLI](/storage/object/api-cli/installing-minio-client/), [awscli](/storage/object/api-cli/object-storage-aws-cli/), [Rclone](/storage/object/api-cli/installing-rclone/), or [s5cmd](https://github.com/peak/s5cmd). +Try benchmarking several clients to upload objects, such as [MinIO CLI](/object-storage/api-cli/installing-minio-client/), [awscli](/object-storage/api-cli/object-storage-aws-cli/), [Rclone](/object-storage/api-cli/installing-rclone/), or [s5cmd](https://github.com/peak/s5cmd). -Leverage the different [storage classes](/storage/object/concepts/#storage-class) offered by Scaleway, and benchmark them according to your needs to find the right configuration for your deployment. +Leverage the different [storage classes](/object-storage/concepts/#storage-class) offered by Scaleway, and benchmark them according to your needs to find the right configuration for your deployment. -Enable [Scaleway Cockpit](/observability/cockpit/quickstart/) to access detailed and in-depth monitoring and logs to identify potential bottlenecks in your Object Storage deployment. +Enable [Scaleway Cockpit](/cockpit/quickstart/) to access detailed and in-depth monitoring and logs to identify potential bottlenecks in your Object Storage deployment. -[Enable Scaleway Edge Services](/storage/object/how-to/get-started-edge-services/) to achieve better performance on `GET` +[Enable Scaleway Edge Services](/object-storage/how-to/get-started-edge-services/) to achieve better performance on `GET` operations by caching your objects closer to your users. This feature is particularly suited to CDN applications. Do not hesitate in reaching out or getting in contact with other Object Storage users on our [Community Slack](https://slack.scaleway.com/). \ No newline at end of file diff --git a/storage/object/reference-content/ssl-tls-certificate.mdx b/storage/object/reference-content/ssl-tls-certificate.mdx index 595cbc0efe..47d45d4377 100644 --- a/storage/object/reference-content/ssl-tls-certificate.mdx +++ b/storage/object/reference-content/ssl-tls-certificate.mdx @@ -12,4 +12,4 @@ categories: - network --- -This document has moved to the new [dedicated Edge Services section](/network/edge-services/reference-content/ssl-tls-certificate/). +This document has moved to the new [dedicated Edge Services section](/edge-services/reference-content/ssl-tls-certificate/). diff --git a/storage/object/troubleshooting/api-key-does-not-work.mdx b/storage/object/troubleshooting/api-key-does-not-work.mdx index 481131dd08..59f294dc8f 100644 --- a/storage/object/troubleshooting/api-key-does-not-work.mdx +++ b/storage/object/troubleshooting/api-key-does-not-work.mdx @@ -16,11 +16,11 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem -When using third-party API or CLI tools, such as the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/), [MinIO Client](/storage/object/api-cli/installing-minio-client/), or [Rclone](/storage/object/api-cli/installing-rclone/) to manage your Object Storage resources, you may experience one of the following issues connecting to the Scaleway API or listing your resources: +When using third-party API or CLI tools, such as the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/), [MinIO Client](/object-storage/api-cli/installing-minio-client/), or [Rclone](/object-storage/api-cli/installing-rclone/) to manage your Object Storage resources, you may experience one of the following issues connecting to the Scaleway API or listing your resources: - Listing your buckets with a third-party tool returns nothing, but you have at least one bucket created in the [Scaleway console](https://console.scaleway.com/object-storage/buckets). @@ -28,24 +28,24 @@ When using third-party API or CLI tools, such as the [AWS CLI](/storage/object/a ## Cause -The API key you used to configure the Amazon S3 third-party tool has a [preferred Project](/identity-and-access-management/iam/concepts/#preferred-project) assigned. +The API key you used to configure the Amazon S3 third-party tool has a [preferred Project](/iam/concepts/#preferred-project) assigned. -If you try to perform Object Storage operations in a Project that is **NOT** the [preferred Project](/identity-and-access-management/iam/concepts/#preferred-project) using a third-party tool, you will not be able to access your resources, resulting in an error message or an empty response. +If you try to perform Object Storage operations in a Project that is **NOT** the [preferred Project](/iam/concepts/#preferred-project) using a third-party tool, you will not be able to access your resources, resulting in an error message or an empty response. ## Solution You can change the preferred project of your API key: -- by editing it from the [Scaleway console](/identity-and-access-management/iam/how-to/manage-api-keys/#how-to-edit-an-api-key) -- by [overriding it while making an API call](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/#overriding-the-preferred-project-when-making-a-call) +- by editing it from the [Scaleway console](/iam/how-to/manage-api-keys/#how-to-edit-an-api-key) +- by [overriding it while making an API call](/iam/api-cli/using-api-key-object-storage/#overriding-the-preferred-project-when-making-a-call) You should now be able to list your buckets using a supported Amazon Amazon S3-compatible third-party tool. ## Going further -- Refer to the documentation on [using IAM API keys with Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) for more information. +- Refer to the documentation on [using IAM API keys with Object Storage](/iam/api-cli/using-api-key-object-storage/) for more information. -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/troubleshooting/cannot-access-data.mdx b/storage/object/troubleshooting/cannot-access-data.mdx index 82643cad8a..0db58a9faf 100644 --- a/storage/object/troubleshooting/cannot-access-data.mdx +++ b/storage/object/troubleshooting/cannot-access-data.mdx @@ -16,7 +16,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem @@ -32,13 +32,13 @@ I am experiencing issues while trying to access my buckets and objects stored on - [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc-admin/mc-admin-logs.html#mc-admin-logs) - [AWS CLI](https://docs.aws.amazon.com/cli/latest/reference/logs/get-log-events.html) -- Make sure there is no [bucket policy](/storage/object/concepts/#bucket-policy) that prevents you from deleting the bucket. If there is one, make sure that it [explicitly allows you](/storage/object/api-cli/bucket-policy/) to perform the desired action. +- Make sure there is no [bucket policy](/object-storage/concepts/#bucket-policy) that prevents you from deleting the bucket. If there is one, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. -- Make sure that [Object lock](/storage/object/api-cli/object-lock/) has not been enabled on the bucket you try to access. +- Make sure that [Object lock](/object-storage/api-cli/object-lock/) has not been enabled on the bucket you try to access. ## Going further -If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/troubleshooting/cannot-delete-bucket.mdx b/storage/object/troubleshooting/cannot-delete-bucket.mdx index c21b7917dc..b136f21815 100644 --- a/storage/object/troubleshooting/cannot-delete-bucket.mdx +++ b/storage/object/troubleshooting/cannot-delete-bucket.mdx @@ -16,7 +16,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem @@ -24,9 +24,9 @@ I cannot delete my Scaleway Object Storage bucket. ## Solution -- Make sure there is no [bucket policy](/storage/object/concepts/#bucket-policy) that prevents you from deleting the bucket. +- Make sure there is no [bucket policy](/object-storage/concepts/#bucket-policy) that prevents you from deleting the bucket. -- If there is a bucket policy, make sure that it [explicitly allows you](/storage/object/api-cli/bucket-policy/) to perform the desired action. +- If there is a bucket policy, make sure that it [explicitly allows you](/object-storage/api-cli/bucket-policy/) to perform the desired action. - The effective deletion of the bucket will start 24 hours after the deletion request. @@ -37,9 +37,9 @@ I cannot delete my Scaleway Object Storage bucket. ## Going further -- Refer to the documentation on [how to delete a bucket](/storage/object/how-to/delete-a-bucket/) for more information. +- Refer to the documentation on [how to delete a bucket](/object-storage/how-to/delete-a-bucket/) for more information. -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/troubleshooting/cannot-restore-glacier.mdx b/storage/object/troubleshooting/cannot-restore-glacier.mdx index 05c9b621c3..811aec69df 100644 --- a/storage/object/troubleshooting/cannot-restore-glacier.mdx +++ b/storage/object/troubleshooting/cannot-restore-glacier.mdx @@ -16,7 +16,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem @@ -24,7 +24,7 @@ I need to retrieve my data from Scaleway Glacier, but the restore operation does ## Cause -The time it takes to restore an object depends on the size of the object, and if [multipart](/storage/object/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for restore to start. +The time it takes to restore an object depends on the size of the object, and if [multipart](/object-storage/concepts/#multipart-uploads) is configured. If your object is larger than 1 MB, it can take anywhere from a few minutes to 24 hours for restore to start. ## Solution @@ -53,9 +53,9 @@ The `"Restore": "ongoing-request=\"true\"",` line indicates that the restore ope ## Going further -- Refer to the documentation on [how to restore objects from Glacier](/storage/object/how-to/restore-an-object-from-glacier/) for more information. +- Refer to the documentation on [how to restore objects from Glacier](/object-storage/how-to/restore-an-object-from-glacier/) for more information. -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx b/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx index cd200dd73c..7a641ccf67 100644 --- a/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx +++ b/storage/object/troubleshooting/lost-bucket-access-bucket-policy.mdx @@ -16,13 +16,13 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem -When [creating and applying a bucket policy](/storage/object/api-cli/create-bucket-policy/) to a bucket, you may lose access to the resources within the bucket if your bucket policy was not set properly. +When [creating and applying a bucket policy](/object-storage/api-cli/create-bucket-policy/) to a bucket, you may lose access to the resources within the bucket if your bucket policy was not set properly. -[Bucket policies](/storage/object/api-cli/bucket-policy/) automatically deny actions to users who are not explicitly allowed by a [statement](/storage/object/api-cli/bucket-policy/#statement). +[Bucket policies](/object-storage/api-cli/bucket-policy/) automatically deny actions to users who are not explicitly allowed by a [statement](/object-storage/api-cli/bucket-policy/#statement). @@ -51,30 +51,30 @@ If you have permission to apply a bucket policy, you can also edit it or delete 3. Click the name of the bucket policy applied to the lost bucket. -4. Either edit it to grant yourself access, or delete it and [create a new one](/storage/object/how-to/create-bucket-policy/) +4. Either edit it to grant yourself access, or delete it and [create a new one](/object-storage/how-to/create-bucket-policy/) If you have the permission to apply a bucket policy, you can also delete it. To regain access to the resources stored in your bucket, you can either: -- delete the current bucket policy using the command below. The bucket will become available to every user with [IAM permissions](/identity-and-access-management/iam/concepts/#permission). +- delete the current bucket policy using the command below. The bucket will become available to every user with [IAM permissions](/iam/concepts/#permission). ``` aws s3api delete-bucket-policy --bucket ``` -- [apply a new bucket policy](/storage/object/api-cli/create-bucket-policy/) in the bucket to allow yourself (or the desired principal) to perform the desired [storage operations](/storage/object/api-cli/using-api-call-list/). +- [apply a new bucket policy](/object-storage/api-cli/create-bucket-policy/) in the bucket to allow yourself (or the desired principal) to perform the desired [storage operations](/object-storage/api-cli/using-api-call-list/). - Refer to the [bucket policies overview](/storage/object/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. + Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. ## Going further -- Refer to the [bucket policies overview](/storage/object/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. +- Refer to the [bucket policies overview](/object-storage/api-cli/bucket-policy/) for more information on the different elements of a bucket policy. -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/troubleshooting/low-performance.mdx b/storage/object/troubleshooting/low-performance.mdx index 2a61b15fe8..a1b53f572a 100644 --- a/storage/object/troubleshooting/low-performance.mdx +++ b/storage/object/troubleshooting/low-performance.mdx @@ -16,7 +16,7 @@ categories: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Problem @@ -34,9 +34,9 @@ I am noticing decreased throughputs, timeouts, high latency, and overall instabi ## Going further -- Refer to the documentation on [how to optimize your Object Storage performance](/storage/object/reference-content/optimize-object-storage-performance/) for more information. +- Refer to the documentation on [how to optimize your Object Storage performance](/object-storage/reference-content/optimize-object-storage-performance/) for more information. -- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +- If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name - Object name (if the request concerns an object) diff --git a/storage/object/videos.mdx b/storage/object/videos.mdx index 44d845827a..2b7740a0fa 100644 --- a/storage/object/videos.mdx +++ b/storage/object/videos.mdx @@ -15,7 +15,7 @@ categories: --- -This video presents Scaleway Object Storage as of December, 2021, and does not reflect the current state of this product. Refer to the [Quickstart](/storage/object/quickstart/) page to discover Scaleway Object Storage. +This video presents Scaleway Object Storage as of December, 2021, and does not reflect the current state of this product. Refer to the [Quickstart](/object-storage/quickstart/) page to discover Scaleway Object Storage. ## What is Object Storage? Quickstart tutorial with use cases diff --git a/tutorials/abort-multipart-upload-minio/index.mdx b/tutorials/abort-multipart-upload-minio/index.mdx index 2f131a3593..5c052ce563 100644 --- a/tutorials/abort-multipart-upload-minio/index.mdx +++ b/tutorials/abort-multipart-upload-minio/index.mdx @@ -13,19 +13,19 @@ dates: hero: assets/scaleway_minio.webp --- -[Multipart Uploads](/storage/object/api-cli/multipart-uploads/) allows you to upload large files (up to 5 TB) to the Object Storage platform in multiple parts. This allows faster, more flexible uploads. +[Multipart Uploads](/object-storage/api-cli/multipart-uploads/) allows you to upload large files (up to 5 TB) to the Object Storage platform in multiple parts. This allows faster, more flexible uploads. -If you do not complete a multipart upload, all the uploaded parts will still be stored and counted as part of your storage usage. Multipart uploads can be aborted manually [via the API and CLI](/storage/object/api-cli/multipart-uploads/#aborting-a-multipart-upload) or automatically using a [Lifecycle rule](/storage/object/api-cli/lifecycle-rules-api/#setting-rules-for-incomplete-multipart-uploads). +If you do not complete a multipart upload, all the uploaded parts will still be stored and counted as part of your storage usage. Multipart uploads can be aborted manually [via the API and CLI](/object-storage/api-cli/multipart-uploads/#aborting-a-multipart-upload) or automatically using a [Lifecycle rule](/object-storage/api-cli/lifecycle-rules-api/#setting-rules-for-incomplete-multipart-uploads). If you use the API or the AWS CLI, you will have to abort each incomplete multipart upload independently. However, there is an easier and faster way to abort multipart uploads, using the open-source Amazon S3-compatible client [mc](https://github.com/minio/mc), from MinIO. In this tutorial, we show you how to use mc to abort and clean up all your incomplete multipart uploads at once. - A Scaleway account logged into the [console](https://console.scaleway.com) - - [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - [Generated your API keys](/identity-and-access-management/iam/how-to/create-api-keys/) - - [Created an Object Storage bucket](/storage/object/how-to/create-a-bucket/) - - [Started a multipart upload](/storage/object/api-cli/multipart-uploads/) + - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization + - [Generated your API keys](/iam/how-to/create-api-keys/) + - [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) + - [Started a multipart upload](/object-storage/api-cli/multipart-uploads/) ## Installing MinIO Client (mc) diff --git a/tutorials/access-mac-mini-with-reemo/index.mdx b/tutorials/access-mac-mini-with-reemo/index.mdx index 18aef1873d..53fb1a8e95 100644 --- a/tutorials/access-mac-mini-with-reemo/index.mdx +++ b/tutorials/access-mac-mini-with-reemo/index.mdx @@ -28,9 +28,9 @@ In this tutorial, you will learn how to launch your Mac mini development environ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) -- A working existing [remote desktop connection](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/) to your Mac mini +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) +- A working existing [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/) to your Mac mini ## Creating your Reemo account @@ -53,7 +53,7 @@ In this tutorial, you will learn how to launch your Mac mini development environ ## Installing the Reemo client -1. Log into your Mac mini using an exsiting [remote desktop connection](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/). +1. Log into your Mac mini using an exsiting [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/). 2. Open a terminal once logged into your Mac mini, open a terminal. 3. Run the following command to install the Reemo client on your machine: ```sh @@ -67,7 +67,7 @@ In this tutorial, you will learn how to launch your Mac mini development environ 4. Enter the **private key** of your Reemo account when prompted. Press Enter to validate. -5. Give Reemo access to screen recording (necessary for it to work). This needs to be done on macOS GUI using your existing [remote desktop connection](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/). Then, in **System Settings**, click **Privacy & Security** in the sidebar (you may need to scroll down). Turn on **Screen Recording** and **Accessibility** for the Reemo app. +5. Give Reemo access to screen recording (necessary for it to work). This needs to be done on macOS GUI using your existing [remote desktop connection](/apple-silicon/how-to/access-remote-desktop-mac-mini/). Then, in **System Settings**, click **Privacy & Security** in the sidebar (you may need to scroll down). Turn on **Screen Recording** and **Accessibility** for the Reemo app. Your remote computer is now displayed on your Reemo dashboard and ready to be streamed from any Chrome Browser (Desktop, Mobile etc.). ## Connecting to your Mac mini using Reemo diff --git a/tutorials/actility-lorawan-operator/index.mdx b/tutorials/actility-lorawan-operator/index.mdx index d9cf8ee353..7862b81415 100644 --- a/tutorials/actility-lorawan-operator/index.mdx +++ b/tutorials/actility-lorawan-operator/index.mdx @@ -29,11 +29,11 @@ This tutorial will guide you through: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An account logged into the [Actility Thingpark Enterprise console](https://community.thingpark.io/) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [IoT Hub](/managed-services/iot-hub/how-to/create-hub/) -- [Added](/managed-services/iot-hub/how-to/add-device/) a device to your IoT Hub with the **Deny Insecure** option enabled +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [IoT Hub](/iot-hub/how-to/create-hub/) +- [Added](/iot-hub/how-to/add-device/) a device to your IoT Hub with the **Deny Insecure** option enabled ## Configuring the Actility backend @@ -71,12 +71,12 @@ Your subscription will now be visible in the **Subscriptions** block, with messa Extend your capabilities by harnessing IoT Hub to construct a dashboard and visualize your data effortlessly: -1. [Create a Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) for PostgreSQL, add a `lora` table with fields such as `time` (timestamp type) and `data` (jsonb type). -2. Configure a [Database route](/managed-services/iot-hub/api-cli/cli-db-tips-tricks/) to push data into the database. Set the topic filter as: `my-app/things/+/uplink`. Your query will resemble: +1. [Create a Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) for PostgreSQL, add a `lora` table with fields such as `time` (timestamp type) and `data` (jsonb type). +2. Configure a [Database route](/iot-hub/api-cli/cli-db-tips-tricks/) to push data into the database. Set the topic filter as: `my-app/things/+/uplink`. Your query will resemble: ```sql INSERT INTO lora (time, data) VALUES (NOW(), $PAYLOAD) ``` -3. [Create an Instance](/compute/instances/how-to/create-an-instance/) and configure Grafana (Follow steps 1 to 14 of the tutorial, excluding enabling the TimescaleDB option). +3. [Create an Instance](/instances/how-to/create-an-instance/) and configure Grafana (Follow steps 1 to 14 of the tutorial, excluding enabling the TimescaleDB option). 4. Enhance your dashboard with widgets. 5. Experiment with creating a graph using the following query: ```sql @@ -87,4 +87,4 @@ Your dashboard will now provide insightful visualizations of your LoRaWAN© devi -Explore [Scaleway IoT Hub](/managed-services/iot-hub/concepts/) further, learn how to [add Devices to the hub](/managed-services/iot-hub/how-to/add-device/), and review [IoT Hub metrics](/managed-services/iot-hub/how-to/view-metrics/). \ No newline at end of file +Explore [Scaleway IoT Hub](/iot-hub/concepts/) further, learn how to [add Devices to the hub](/iot-hub/how-to/add-device/), and review [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/add-disk-configure-datastore-esxi/index.mdx b/tutorials/add-disk-configure-datastore-esxi/index.mdx index f1265455d1..3536e4a34c 100644 --- a/tutorials/add-disk-configure-datastore-esxi/index.mdx +++ b/tutorials/add-disk-configure-datastore-esxi/index.mdx @@ -35,7 +35,7 @@ This guide is designed to walk you through the process of ordering an additional - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Dedibox](https://www.scaleway.com/en/dedibox/) running [VMware ESXi](/tutorials/configure-virtual-machine-esxi/#installing-esxi) - Subscribed to the Business Service Level for the server diff --git a/tutorials/ansible-bionic-beaver/index.mdx b/tutorials/ansible-bionic-beaver/index.mdx index c3e25f3d93..31651c3714 100644 --- a/tutorials/ansible-bionic-beaver/index.mdx +++ b/tutorials/ansible-bionic-beaver/index.mdx @@ -24,9 +24,9 @@ Ansible works by configuring client machines from a computer that has the Ansibl - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Bionic +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Bionic ## Installing Ansible 2.6 on Ubuntu Bionic Beaver diff --git a/tutorials/ansible-galaxy/index.mdx b/tutorials/ansible-galaxy/index.mdx index c42e63f134..d49cd0e1b0 100644 --- a/tutorials/ansible-galaxy/index.mdx +++ b/tutorials/ansible-galaxy/index.mdx @@ -22,8 +22,8 @@ Ansible roles consist of playbooks that group multiple tasks into one container. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Linux +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Linux - Basic knowledge of [Ansible](/tutorials/ansible-bionic-beaver/) and [Ansible-Apache](/tutorials/install-apache-ansible/) - [Ansible-Apache](/tutorials/install-apache-ansible/) installed on your local computer diff --git a/tutorials/ark-server/index.mdx b/tutorials/ark-server/index.mdx index cc2698d557..6e4d02fa0d 100644 --- a/tutorials/ark-server/index.mdx +++ b/tutorials/ark-server/index.mdx @@ -39,24 +39,24 @@ In this tutorial, you will learn how to create an ARK server on a [Scaleway Inst - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Bionic Beaver (18.04) or Ubuntu Focal Fossa (20.04) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Bionic Beaver (18.04) or Ubuntu Focal Fossa (20.04) +- A valid [API key](/iam/how-to/create-api-keys/) - `sudo` privileges or access to the root user - A copy of [ARK: Survival Evolved](https://store.steampowered.com/app/346110/ARK_Survival_Evolved/) for your local computer - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). -Creating an ARK server can be done in a few steps on a [Scaleway Instance](https://www.scaleway.com/en/cost-optimized-instances/). If you do not have an Instance yet, start by [deploying your first Instance](/compute/instances/how-to/create-an-instance/). +Creating an ARK server can be done in a few steps on a [Scaleway Instance](https://www.scaleway.com/en/cost-optimized-instances/). If you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). The ARK: Survival Evolved game server application requires at least 6 GB of RAM to start. Memory requirements increase as the number of connected players increases, as well depending on the activated mods. We recommend that you use at minimum a **DEV1-L** Instance for smooth gameplay. -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/arqbackup-pc-mac/index.mdx b/tutorials/arqbackup-pc-mac/index.mdx index 646c3399f6..cf0114efb0 100644 --- a/tutorials/arqbackup-pc-mac/index.mdx +++ b/tutorials/arqbackup-pc-mac/index.mdx @@ -21,7 +21,7 @@ This tutorial guides you through backing up your PC or Mac computer to Scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An [Object Storage bucket](https://www.scaleway.com/en/object-storage/) ## Installing and configuring Arq Backup @@ -45,8 +45,8 @@ This tutorial guides you through backing up your PC or Mac computer to Scaleway - For FR-PAR (Paris, France) enter `https://s3.fr-par.scw.cloud` - For NL-AMS (Amsterdam, The Netherlands) enter `https://s3.nl-ams.scw.cloud` - For PL-WAW (Warsaw, Poland) enter `https://s3.pl-waw.scw.cloud` - - **Access key ID:** The [access key](/identity-and-access-management/iam/how-to/create-api-keys/) of the API key used for authentication - - **Secret key:** The [secret key](/identity-and-access-management/iam/how-to/create-api-keys/) of the API key used for authentication + - **Access key ID:** The [access key](/iam/how-to/create-api-keys/) of the API key used for authentication + - **Secret key:** The [secret key](/iam/how-to/create-api-keys/) of the API key used for authentication - **Region**: The region of your Object Storage bucket (`fr-par`, `nl-ams`, or `pl-waw`) diff --git a/tutorials/automate-tasks-using-cron/index.mdx b/tutorials/automate-tasks-using-cron/index.mdx index b6749c2d55..c4e036967e 100644 --- a/tutorials/automate-tasks-using-cron/index.mdx +++ b/tutorials/automate-tasks-using-cron/index.mdx @@ -20,9 +20,9 @@ These scheduled tasks, fondly called Cronjobs, work tirelessly to automate routi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04) - `sudo` privileges or access to the root user ## Installing Cron diff --git a/tutorials/back-up-postgresql-barman/index.mdx b/tutorials/back-up-postgresql-barman/index.mdx index 1a32f8aae6..e3c53c7697 100644 --- a/tutorials/back-up-postgresql-barman/index.mdx +++ b/tutorials/back-up-postgresql-barman/index.mdx @@ -21,9 +21,9 @@ Setting itself apart with its unique methodology, Barman uses PostgreSQL logs fo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Two [Instances](/compute/instances/how-to/create-an-instance/) running a [PostgreSQL database](/tutorials/install-postgresql/) on Ubuntu Bionic or a later version +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Two [Instances](/instances/how-to/create-an-instance/) running a [PostgreSQL database](/tutorials/install-postgresql/) on Ubuntu Bionic or a later version - `sudo` privileges or access to the root user ## Installing Barman diff --git a/tutorials/backup-dedicated-server-s3-duplicity/index.mdx b/tutorials/backup-dedicated-server-s3-duplicity/index.mdx index 04183a03c4..4317cc0827 100644 --- a/tutorials/backup-dedicated-server-s3-duplicity/index.mdx +++ b/tutorials/backup-dedicated-server-s3-duplicity/index.mdx @@ -13,7 +13,7 @@ dates: posted: 2018-10-13 --- -In this article, we will learn how to back up data from a Scaleway Instance, using [Scaleway's Object Storage](/storage/object/quickstart/) service and Duplicity. [Duplicity](https://duplicity.gitlab.io/) is a free and open-source tool that backs up folders to a remote server, in this case, an Object Storage bucket. Using libsync and GPG, Duplicity can make space-efficient encrypted backups. +In this article, we will learn how to back up data from a Scaleway Instance, using [Scaleway's Object Storage](/object-storage/quickstart/) service and Duplicity. [Duplicity](https://duplicity.gitlab.io/) is a free and open-source tool that backs up folders to a remote server, in this case, an Object Storage bucket. Using libsync and GPG, Duplicity can make space-efficient encrypted backups. Our objectives are to: @@ -33,13 +33,13 @@ Although this tutorial focuses on backing up an Instance, you can also back up a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu or Debian +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu or Debian ## Creating an Object Storage bucket -Follow the instructions to [create an Object Storage bucket](/storage/object/how-to/create-a-bucket/). This bucket will be used to back up your Instance's data. +Follow the instructions to [create an Object Storage bucket](/object-storage/how-to/create-a-bucket/). This bucket will be used to back up your Instance's data. ## Installing software requirements diff --git a/tutorials/backup-postgresql-pgbackrest-s3/index.mdx b/tutorials/backup-postgresql-pgbackrest-s3/index.mdx index 5da5115498..0a3902161e 100644 --- a/tutorials/backup-postgresql-pgbackrest-s3/index.mdx +++ b/tutorials/backup-postgresql-pgbackrest-s3/index.mdx @@ -23,11 +23,11 @@ pgBackRest can back up in three ways: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Instances](/compute/instances/how-to/create-an-instance/) running a [PostgreSQL database](/tutorials/install-postgresql/) on Ubuntu/Debian or RHEL/Rocky Linux +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Instances](/instances/how-to/create-an-instance/) running a [PostgreSQL database](/tutorials/install-postgresql/) on Ubuntu/Debian or RHEL/Rocky Linux - `sudo` privileges or access to the root user -- An [Object Storage bucket](/storage/object/quickstart/) +- An [Object Storage bucket](/object-storage/quickstart/) ## Installing pgBackRest diff --git a/tutorials/backup-synology-nas-s3-hyper-backup/index.mdx b/tutorials/backup-synology-nas-s3-hyper-backup/index.mdx index 3311811487..29efb4e7c8 100644 --- a/tutorials/backup-synology-nas-s3-hyper-backup/index.mdx +++ b/tutorials/backup-synology-nas-s3-hyper-backup/index.mdx @@ -23,8 +23,8 @@ As the NAS holds huge amounts of your personal data, a good backup strategy is i - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/quickstart/) - A NAS device supporting [Synology Hyper Backup](https://www.synology.com/en-us/dsm/feature/hyper_backup) ## Configuring Hyper Backup @@ -45,8 +45,8 @@ As the NAS holds huge amounts of your personal data, a good backup strategy is i - `s3.nl-ams.scw.cloud` for buckets in Amsterdam - `s3.pl-waw.scw.cloud` for buckets in Warsaw. - **Signature version**: Choose the value `v2` from the drop-down list - - **Access key**: The `access key` of your [API key](/identity-and-access-management/iam/how-to/create-api-keys/) - - **Secret key**: The `secret key` of your [API key](/identity-and-access-management/iam/how-to/create-api-keys/) + - **Access key**: The `access key` of your [API key](/iam/how-to/create-api-keys/) + - **Secret key**: The `secret key` of your [API key](/iam/how-to/create-api-keys/) - **Bucket name**: Choose the bucket for storing your backups from the drop-down list - **Directory**: The name of the directory for storing your backups. A default name is being generated from the name of your Synology device. That name can be changed if required. diff --git a/tutorials/bash-christmas-tree/index.mdx b/tutorials/bash-christmas-tree/index.mdx index d494ea5406..a60bdba68c 100644 --- a/tutorials/bash-christmas-tree/index.mdx +++ b/tutorials/bash-christmas-tree/index.mdx @@ -20,12 +20,12 @@ A bash script essentially constitutes a plain text file containing a sequence of Writing bash scripts does not require any special skills. You just write down the commands you want the computer to execute in a text file instead of individually typing them. This is handy for automating tasks, like managing files or folders. Bash scripts usually end with `*.sh`. - We recommend you follow this tutorial using a [Learning Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Learning Instance](/instances/reference-content/choosing-instance-type/). ## Writing the script -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/): +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/): ``` ssh root@ ``` diff --git a/tutorials/bind-dns-server/index.mdx b/tutorials/bind-dns-server/index.mdx index 4bfdfe32a0..ab4cdbac94 100644 --- a/tutorials/bind-dns-server/index.mdx +++ b/tutorials/bind-dns-server/index.mdx @@ -20,8 +20,8 @@ DNS (Domain Name System) is a service that translates the IP address of computer - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user ## Installing BIND diff --git a/tutorials/building-ai-application-function-calling/index.mdx b/tutorials/building-ai-application-function-calling/index.mdx index ec3032c1b6..e69ba8763e 100644 --- a/tutorials/building-ai-application-function-calling/index.mdx +++ b/tutorials/building-ai-application-function-calling/index.mdx @@ -23,8 +23,8 @@ This tutorial will guide you through creating a simple flight schedule assistant - A Scaleway account logged into the [console](https://console.scaleway.com) - Python 3.7 or higher -- An API key from Scaleway [Identity and Access Management](/identity-and-access-management/iam/) -- Access to Scaleway [Generative APIs](/ai-data/generative-apis/quickstart/) or to Scaleway [Managed Inference](/ai-data/managed-inference/quickstart/) +- An API key from Scaleway [Identity and Access Management](/iam/) +- Access to Scaleway [Generative APIs](/generative-apis/quickstart/) or to Scaleway [Managed Inference](/managed-inference/quickstart/) - The `openai` Python library installed ## Understanding function calling diff --git a/tutorials/ceph-cluster/index.mdx b/tutorials/ceph-cluster/index.mdx index 930fa7074d..0e8aa1f59e 100644 --- a/tutorials/ceph-cluster/index.mdx +++ b/tutorials/ceph-cluster/index.mdx @@ -23,7 +23,7 @@ This tutorial guides you through deploying a three-node [Ceph](https://www.ceph. - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - 3 Dedibox servers running Ubuntu Focal Fossa 20.04 LTS or later - An additional admin machine available to install `ceph-deploy` @@ -233,7 +233,7 @@ On the gateway instance (`ceph-node-a`), run the following command to create a n sudo radosgw-admin user create --uid=johndoe --display-name="John Doe" --email=john@example.com ``` -- Note the `access_key` and `user_key`. Proceed to configure your Object Storage client, e.g., [aws-cli](/storage/object/api-cli/object-storage-aws-cli/). +- Note the `access_key` and `user_key`. Proceed to configure your Object Storage client, e.g., [aws-cli](/object-storage/api-cli/object-storage-aws-cli/). ## Configuring AWS-CLI diff --git a/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx b/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx index 703a05036d..8cc5821e55 100644 --- a/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx +++ b/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx @@ -32,11 +32,11 @@ Cilicon uses the tart container format and integrates an OCI client to fetch ima - A Scaleway account logged into the [console](https://console.scaleway.com) -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) ## Installing Cilicon on macOS -1. Connect to your Mac Mini using [VNC](/bare-metal/apple-silicon/how-to/access-remote-desktop-mac-mini/). +1. Connect to your Mac Mini using [VNC](/apple-silicon/how-to/access-remote-desktop-mac-mini/). 2. Download the latest release of [Cilicon](https://github.com/traderepublic/Cilicon/releases/latest). 3. Move the file `Cilicon.app` to the applications folder of your OS. 4. Add `Cilicon.app` as a [launch item](https://support.apple.com/guide/mac-help/open-items-automatically-when-you-log-in-mh15189/13.0/mac/13.0) and set up [automatic login](https://support.apple.com/en-us/102316). diff --git a/tutorials/collecting-visualizing-logs-elastic-stack/index.mdx b/tutorials/collecting-visualizing-logs-elastic-stack/index.mdx index 4f59af3b93..da0e4c3d0b 100644 --- a/tutorials/collecting-visualizing-logs-elastic-stack/index.mdx +++ b/tutorials/collecting-visualizing-logs-elastic-stack/index.mdx @@ -26,9 +26,9 @@ Its components are: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) or an [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) with at least 4 GB of RAM +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) or an [Elastic Metal server](/elastic-metal/how-to/create-server/) with at least 4 GB of RAM ### Install Elasticsearch diff --git a/tutorials/configure-apache-kafka/index.mdx b/tutorials/configure-apache-kafka/index.mdx index a7feeef265..5e8eb8d5d1 100644 --- a/tutorials/configure-apache-kafka/index.mdx +++ b/tutorials/configure-apache-kafka/index.mdx @@ -23,8 +23,8 @@ Kafka has been implemented by many companies of any size because of its flexibil - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## What is a messaging system? diff --git a/tutorials/configure-apache-lets-encrypt/index.mdx b/tutorials/configure-apache-lets-encrypt/index.mdx index a1fd6f6dd8..8b9e157e20 100644 --- a/tutorials/configure-apache-lets-encrypt/index.mdx +++ b/tutorials/configure-apache-lets-encrypt/index.mdx @@ -22,15 +22,15 @@ We will walk you through the process of setting up a website on Apache and obtai - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) -- A [domain name](/network/domains-and-dns/quickstart/) pointing towards your Instance's IP address (via an A or AAAA record) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) +- A [domain name](/domains-and-dns/quickstart/) pointing towards your Instance's IP address (via an A or AAAA record) - `sudo` privileges or access to the root user ## Installing Apache -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/), and update the software already installed: +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/), and update the software already installed: ``` apt update apt upgrade -y diff --git a/tutorials/configure-chef-ubuntu-xenial/index.mdx b/tutorials/configure-chef-ubuntu-xenial/index.mdx index 0fb3a6363d..005ba7664f 100644 --- a/tutorials/configure-chef-ubuntu-xenial/index.mdx +++ b/tutorials/configure-chef-ubuntu-xenial/index.mdx @@ -22,12 +22,12 @@ You can easily manage up to 10,000 nodes using Chef. Chef also makes it easy to - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - One of the following remote machines running Ubuntu (this tutorial was validated for machines running Ubuntu Xenial or Ubuntu Focal Fossa): - - An [Instance](/compute/instances/how-to/create-an-instance/) - - An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) - - A [Dedibox dedicated server](/dedibox/dedicated-servers/how-to/order-a-server/) + - An [Instance](/instances/how-to/create-an-instance/) + - An [Elastic Metal server](/elastic-metal/how-to/create-server/) + - A [Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/) - A second machine (a local machine or a second remote machine) on which to install Chef SDK ## Core concepts @@ -40,7 +40,7 @@ You can easily manage up to 10,000 nodes using Chef. Chef also makes it easy to ### Accessing the server by hostname -1. Connect to your remote machine via SSH. Follow the instructions depending on your remote machine type: [Instance](/compute/instances/how-to/connect-to-instance/), [Elastic Metal](/bare-metal/elastic-metal/how-to/connect-to-server/), or [Dedibox](/dedibox/dedicated-servers/how-to/connect-to-server/). +1. Connect to your remote machine via SSH. Follow the instructions depending on your remote machine type: [Instance](/instances/how-to/connect-to-instance/), [Elastic Metal](/elastic-metal/how-to/connect-to-server/), or [Dedibox](/dedicated-servers/how-to/connect-to-server/). This tutorial assumes that you connect to your machine as root. If this is not the case, you may need to add `sudo` to the commands shown. diff --git a/tutorials/configure-dvc-with-object-storage/index.mdx b/tutorials/configure-dvc-with-object-storage/index.mdx index 4fc62ad60a..16aea60ae8 100644 --- a/tutorials/configure-dvc-with-object-storage/index.mdx +++ b/tutorials/configure-dvc-with-object-storage/index.mdx @@ -24,13 +24,13 @@ In this tutorial, you learn how to use [Scaleway Object Storage](https://www.sca - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) - A repository to store your metadata - Made your [first request with Scaleway API](https://www.scaleway.com/en/developers/api/#quickstart-first-request) - [Authenticated to the API](https://www.scaleway.com/en/developers/api/#how-to-authenticate) for the first time -- Installed the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/) +- Installed the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/) ## Setting up DVC diff --git a/tutorials/configure-failover-proxmox/index.mdx b/tutorials/configure-failover-proxmox/index.mdx index 92cf0e1de0..4eea369b9d 100644 --- a/tutorials/configure-failover-proxmox/index.mdx +++ b/tutorials/configure-failover-proxmox/index.mdx @@ -20,13 +20,13 @@ The software provides an intuitive web interface as well as a complete REST-API - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Scaleway Dedibox](http://www.scaleway.com/en/dedibox) -- At least one [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) +- At least one [failover IP](/dedibox-ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) This tutorial assumes that you have already installed Proxmox VE on your Scaleway Dedibox. The automatic installation of Proxmox VE is available from your [Dedibox console](https://console.online.net) - or manually using the [KVM-over-IP device](/dedibox/dedicated-servers/concepts/#ipmi) of your server. + or manually using the [KVM-over-IP device](/dedicated-servers/concepts/#ipmi) of your server. ## Connecting to Proxmox @@ -77,7 +77,7 @@ ISO files are archive files that contain identical copies of the data found on o 7. Configure the network for the container. Set the parameters as follows to ensure your container has network access: - **Name**: Set this value to `eth0` - - **MAC Address**: Set this value to the [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) associated to the failover IP of the container. + - **MAC Address**: Set this value to the [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) associated to the failover IP of the container. - **Bridge**: Set this value to `vmbr0`. - **IPv4**: Configure the IPv4 of the container as `Static`, enter the failover IP in [CIDR notation](https://en.wikipedia.org/wiki/Classless_Inter-Domain_Routing#CIDR_notation), and configure the unique gateway `62.210.0.1`. @@ -104,7 +104,7 @@ ISO files are archive files that contain identical copies of the data found on o 6. Choose the CPU settings for the virtual machine. You may set the number of **Sockets**, **Cores** and the **Type** based on your own requirements: 7. Set the amount of RAM for the virtual machine towards your requirements -8. Configure the network interface. Set the **bridge** to `vmbr0`, the model to `VirtIO (paravirtualized)`, and configure the [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) assigned to the failover IP of the virtual machine. The static [network configuration](/bare-metal/elastic-metal/how-to/configure-flexible-ip/) is done in a later step, during the installation of the operating system. +8. Configure the network interface. Set the **bridge** to `vmbr0`, the model to `VirtIO (paravirtualized)`, and configure the [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) assigned to the failover IP of the virtual machine. The static [network configuration](/elastic-metal/how-to/configure-flexible-ip/) is done in a later step, during the installation of the operating system. 9. A configuration summary displays. Click **Finish** if all settings are correct to launch the creation of the virtual machine. 10. Start the virtual machine from the Proxmox panel. It boots from the chosen ISO file. Connect to the virtual machine using the console and follow the steps of the operating systems' setup wizard to complete the installation: diff --git a/tutorials/configure-graphite/index.mdx b/tutorials/configure-graphite/index.mdx index 5cb62dfc6f..9ec0c12123 100644 --- a/tutorials/configure-graphite/index.mdx +++ b/tutorials/configure-graphite/index.mdx @@ -24,10 +24,10 @@ Throughout this tutorial, we will dive into the technical aspects of Graphite, a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu 20.04 LTS -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu 20.04 LTS +- A valid [API key](/iam/how-to/create-api-keys/) - `sudo` privileges or access to the root user ## Installing Graphite diff --git a/tutorials/configure-ipv6-virtual-machine-esxi/index.mdx b/tutorials/configure-ipv6-virtual-machine-esxi/index.mdx index 229e6768db..fcf9c5ee7c 100644 --- a/tutorials/configure-ipv6-virtual-machine-esxi/index.mdx +++ b/tutorials/configure-ipv6-virtual-machine-esxi/index.mdx @@ -23,14 +23,14 @@ This tutorial explains how to configure IPv6 on virtual machines on ESXi hypervi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A [Dedibox](https://www.scaleway.com/en/dedibox/) running ESXi 6.5 or later -- Enabled [SLAAC](/dedibox-network/ipv6/how-to/enable-ipv6-slaac/) for your Dedibox -- [Requested an IPv6 prefix](/dedibox-network/ipv6/how-to/request-prefix/) -- Installed a virtual machine running Ubuntu 20.04 or later and [configured a failover IPv4](/dedibox-network/ip-failover/how-to/configure-network-virtual-machine/#ubuntu) on it +- Enabled [SLAAC](/dedibox-ipv6/how-to/enable-ipv6-slaac/) for your Dedibox +- [Requested an IPv6 prefix](/dedibox-ipv6/how-to/request-prefix/) +- Installed a virtual machine running Ubuntu 20.04 or later and [configured a failover IPv4](/dedibox-ip-failover/how-to/configure-network-virtual-machine/#ubuntu) on it -1. Log into your virtual machine using [SSH](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). +1. Log into your virtual machine using [SSH](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh). 2. Run the command `ip a` to display your current network configuration. The command returns an output as follows: ``` 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 @@ -57,7 +57,7 @@ This tutorial explains how to configure IPv6 on virtual machines on ESXi hypervi } ``` - Edit the name of the internet interface to one of your VMs and replace `DUID` with the [DUID of your prefix](/dedibox-network/ipv6/how-to/request-prefix/). + Edit the name of the internet interface to one of your VMs and replace `DUID` with the [DUID of your prefix](/dedibox-ipv6/how-to/request-prefix/). 4. Open the file `/etc/systemd/system/dhclient.service` in a text editor and edit it as shown below. Then save and exit the editor. ``` @@ -112,7 +112,7 @@ This tutorial explains how to configure IPv6 on virtual machines on ESXi hypervi gateway4: 62.210.0.1 gateway6: LOCAL_IPv6 nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers) routes: - to: 0.0.0.0/0 @@ -122,7 +122,7 @@ This tutorial explains how to configure IPv6 on virtual machines on ESXi hypervi via: "LOCAL_IPv6" on-link: true nameservers: - addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/console/account/reference-content/scaleway-network-information/#dns-cache-servers/) + addresses: [ "51.159.47.28", "51.159.47.26" ] # Replace the IP of the DNS cache server with the one located in the same physical location as your machine for optimal performances (https://www.scaleway.com/en/docs/account/reference-content/scaleway-network-information/#dns-cache-servers/) accept-ra: no # Disable Router Advertisements to ignore SLAAC ``` 8. Apply the new network configuration with the following command: diff --git a/tutorials/configure-nagios-monitoring/index.mdx b/tutorials/configure-nagios-monitoring/index.mdx index 9ae76da743..920bd0b8f5 100644 --- a/tutorials/configure-nagios-monitoring/index.mdx +++ b/tutorials/configure-nagios-monitoring/index.mdx @@ -21,9 +21,9 @@ It is an open-source monitoring system that can automatically alert you in case - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- At least 2 [Instances](/compute/instances/how-to/create-an-instance/) or 2 [Elastic Metal servers](/bare-metal/elastic-metal/how-to/create-server/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- At least 2 [Instances](/instances/how-to/create-an-instance/) or 2 [Elastic Metal servers](/elastic-metal/how-to/create-server/) ## Installing Nagios diff --git a/tutorials/configure-netbox-managed-postgresql-database/index.mdx b/tutorials/configure-netbox-managed-postgresql-database/index.mdx index 2554e51bfb..36c9355799 100644 --- a/tutorials/configure-netbox-managed-postgresql-database/index.mdx +++ b/tutorials/configure-netbox-managed-postgresql-database/index.mdx @@ -21,10 +21,10 @@ In this tutorial, you learn how to install and configure NetBox on an Instance r - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) or later -- A [Database for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) or later +- A [Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) ## Configuring the database @@ -47,7 +47,7 @@ NetBox requires a PostgreSQL database. Configure your [Database for PostgreSQL]( ## Installing NetBox -1. Log into your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Log into your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance to the latest version available in Ubuntu's repositories: ``` apt update && apt upgrade -y diff --git a/tutorials/configure-nextcloud-ubuntu/index.mdx b/tutorials/configure-nextcloud-ubuntu/index.mdx index 34c5b53bc4..fd5352fd5d 100644 --- a/tutorials/configure-nextcloud-ubuntu/index.mdx +++ b/tutorials/configure-nextcloud-ubuntu/index.mdx @@ -20,9 +20,9 @@ It provides a large portfolio of [different applications](https://nextcloud.com/ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.04 LTS) - `sudo` privileges or access to the root user ## Installing Nextcloud diff --git a/tutorials/configure-nginx-lets-encrypt/index.mdx b/tutorials/configure-nginx-lets-encrypt/index.mdx index 834dd882f9..3236564895 100644 --- a/tutorials/configure-nginx-lets-encrypt/index.mdx +++ b/tutorials/configure-nginx-lets-encrypt/index.mdx @@ -19,14 +19,14 @@ These certificates are a key element in enabling secure HTTPS connections on web - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04) or later - A registered domain name pointed to your web server ### Installing the NGINX web server -1. Connect to your server as `root` via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your server as `root` via [SSH](/instances/how-to/connect-to-instance/). 2. Update the APT package cache and the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/configure-nodemcu-iot-hub/index.mdx b/tutorials/configure-nodemcu-iot-hub/index.mdx index a1ea8afc3c..57f4e9dcbf 100644 --- a/tutorials/configure-nodemcu-iot-hub/index.mdx +++ b/tutorials/configure-nodemcu-iot-hub/index.mdx @@ -18,8 +18,8 @@ Scaleway's IoT Hub lets your connected devices share messages. In this tutorial, - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - A [NodeMCU](https://en.wikipedia.org/wiki/NodeMCU) device - Downloaded and installed the [Arduino IDE](https://www.arduino.cc/en/software) @@ -458,4 +458,4 @@ You now have connected a NodeMCU device with IoT Hub, created a publish/subscrib --- -Learn more about [Scaleway IoT Hub](/managed-services/iot-hub/concepts/), discover how to add [Devices to the hub](/managed-services/iot-hub/how-to/add-device/), or check the [IoT Hub metrics](/managed-services/iot-hub/how-to/view-metrics/). \ No newline at end of file +Learn more about [Scaleway IoT Hub](/iot-hub/concepts/), discover how to add [Devices to the hub](/iot-hub/how-to/add-device/), or check the [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/configure-plex-s3/index.mdx b/tutorials/configure-plex-s3/index.mdx index 1658674588..7c723bb0c2 100644 --- a/tutorials/configure-plex-s3/index.mdx +++ b/tutorials/configure-plex-s3/index.mdx @@ -23,10 +23,10 @@ Plex is a client/server media player system comprising two main components: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) - `sudo` privileges or access to the root user ## Installing the required software diff --git a/tutorials/configure-realtime-alerting-slack/index.mdx b/tutorials/configure-realtime-alerting-slack/index.mdx index 5a5c95b35c..3a510e6e81 100644 --- a/tutorials/configure-realtime-alerting-slack/index.mdx +++ b/tutorials/configure-realtime-alerting-slack/index.mdx @@ -30,7 +30,7 @@ There are three steps to achieve this: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Creating a Slack workspace and application @@ -49,7 +49,7 @@ There are three steps to achieve this: Now that we have the Slack application ready, we need to create an IoT Hub. This will be where our simulated IoT Device will publish messages to be sent to our Slack workspace. -Follow [this procedure](/managed-services/iot-hub/how-to/create-hub/) to create an IoT Hub. Select your name and plan of choice, and click the `Create Hub and Add a Device` button. +Follow [this procedure](/iot-hub/how-to/create-hub/) to create an IoT Hub. Select your name and plan of choice, and click the `Create Hub and Add a Device` button. ## Setting up an IoT Route to our Slack application @@ -72,7 +72,7 @@ Now that we have everything set up, let's add a Device and send a message to tri - After you click **Add a device to your Hub**, you are taken to the credentials section. In this section, you can add a [Certificate Authority](/managed-services/iot-hub/concepts/#device-certificate) for your device. This step is not mandatory. + After you click **Add a device to your Hub**, you are taken to the credentials section. In this section, you can add a [Certificate Authority](/iot-hub/concepts/#device-certificate) for your device. This step is not mandatory. 3. Click **Back to devices**. Then, click the name of your device. The device information page displays. 4. Click **MQTT Webclient** on the device overview page. The client will open and automatically connect. @@ -92,10 +92,10 @@ Congratulations, you sent your first Slack message from a (simulated) device. When you use this tutorial in a production setting, we recommend that you: - store all alerts in a database to keep a history. - send the alerts to an on-premises real-time dashboard. - - for important alerts, depending on the content of the alert, notify the right Slack channel using a [Serverless Function](/serverless/functions/concepts/#serverless-functions) to make this choice. + - for important alerts, depending on the content of the alert, notify the right Slack channel using a [Serverless Function](/serverless-functions/concepts/#serverless-functions) to make this choice. You can set up your architecture in the following manner: -Learn more about [Scaleway IoT Hub](/managed-services/iot-hub/concepts/), discover how to add [Devices to the hub](/managed-services/iot-hub/how-to/add-device/), or check the [IoT Hub metrics](/managed-services/iot-hub/how-to/view-metrics/). \ No newline at end of file +Learn more about [Scaleway IoT Hub](/iot-hub/concepts/), discover how to add [Devices to the hub](/iot-hub/how-to/add-device/), or check the [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/configure-smtp-relay-tem/index.mdx b/tutorials/configure-smtp-relay-tem/index.mdx index 3e9b971006..9aae07f40f 100644 --- a/tutorials/configure-smtp-relay-tem/index.mdx +++ b/tutorials/configure-smtp-relay-tem/index.mdx @@ -23,12 +23,12 @@ For demonstration purposes, will walk through the configuration process on a Mac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) with the right [permissions](/identity-and-access-management/iam/reference-content/permission-sets/) -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) with the right [permissions](/iam/reference-content/permission-sets/) +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) - Installed [Postfix](https://ubuntu.com/server/docs/mail-postfix) on your local machine - Installed [stunnel](https://www.stunnel.org/downloads.html) on your local machine -- Opened [the mail ports on your Instance](/compute/instances/how-to/send-emails-from-your-instance/) +- Opened [the mail ports on your Instance](/instances/how-to/send-emails-from-your-instance/) - Configured your SMTP server ## Configuring Postfix with submission @@ -97,7 +97,7 @@ For demonstration purposes, will walk through the configuration process on a Mac Some providers do not let you access port 587. To solve this issue, Scaleway offers non-standard ports that are unlikely to be blocked: `2587` (SMTP) and `2465` (TLS). A workaround is to use `stunnel` to be able to use Postfix. - If you are sending emails from an Instance, you must [open your Instance's mail ports](/compute/instances/how-to/send-emails-from-your-instance/). + If you are sending emails from an Instance, you must [open your Instance's mail ports](/instances/how-to/send-emails-from-your-instance/). 1. Open a terminal and access the `smtp-wrapper.conf` file using the following command: diff --git a/tutorials/configure-tem-smtp-with-wordpress-plugin/index.mdx b/tutorials/configure-tem-smtp-with-wordpress-plugin/index.mdx index a4cbe73b91..b8b545e303 100644 --- a/tutorials/configure-tem-smtp-with-wordpress-plugin/index.mdx +++ b/tutorials/configure-tem-smtp-with-wordpress-plugin/index.mdx @@ -17,15 +17,15 @@ dates: - A Scaleway account logged into the [Scaleway console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/) -- [Added SPF, DKIM](/managed-services/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/managed-services/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/) +- [Added SPF, DKIM](/transactional-email/how-to/add-spf-dkim-records-to-your-domain/), [MX](/transactional-email/how-to/add-mx-record-to-your-domain/) and [DMARC](/transactional-email/how-to/add-mx-record-to-your-domain/) records to your domain ## Creating your resources -1. [Create an API key](/identity-and-access-management/iam/how-to/create-api-keys/) from the Scaleway console. Make sure that you take note of your secret key. -2. [Create an Instance](/compute/instances/how-to/create-an-instance/) with a **WordPress** image from the **InstantApps** tab. -3. [Create](/compute/instances/how-to/use-security-groups/#how-to-create-a-security-group) a security group, check the **Enable SMTP ports** box, click **+ Add Instance**, and select your Instance in the drop-down. +1. [Create an API key](/iam/how-to/create-api-keys/) from the Scaleway console. Make sure that you take note of your secret key. +2. [Create an Instance](/instances/how-to/create-an-instance/) with a **WordPress** image from the **InstantApps** tab. +3. [Create](/instances/how-to/use-security-groups/#how-to-create-a-security-group) a security group, check the **Enable SMTP ports** box, click **+ Add Instance**, and select your Instance in the drop-down. ## Configuring and logging in to your WordPress website diff --git a/tutorials/configure-virtual-machine-esxi/index.mdx b/tutorials/configure-virtual-machine-esxi/index.mdx index 21a5db5a7d..72315ea5d3 100644 --- a/tutorials/configure-virtual-machine-esxi/index.mdx +++ b/tutorials/configure-virtual-machine-esxi/index.mdx @@ -25,10 +25,10 @@ Management of the virtual machines can be done through an easy-to-use web interf - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Dedibox](http://www.scaleway.com/en/dedibox) server that fulfills the [VMware hardware requirements](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-DEB8086A-306B-4239-BF76-E354679202FC.html) - A [valid license](https://my.vmware.com/en/group/vmware/evalcenter?p=free-esxi7&lp=default) for ESXi (a 60-day free trial is available) -- At least one [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) +- At least one [failover IP](/dedibox-ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) ## Installing ESXi @@ -62,7 +62,7 @@ ESXi ISO images are available on VMware's ["Evaluate Products"](https://www.vmwa 4. Click the third button on the right. The model of the KVM over IP device is determined by the brand of your Dedibox chassis. For a Dell chassis, you will use **IDRAC**: -The process from this step forward may differ according to the KVM model being used. Refer to the Dedibox [KVM over IP documentation](/dedibox/kvm-over-ip/quickstart/) to conclude the installation. +The process from this step forward may differ according to the KVM model being used. Refer to the Dedibox [KVM over IP documentation](/dedibox-kvm-over-ip/quickstart/) to conclude the installation. ## Registering ESXi @@ -115,4 +115,4 @@ The VMware ESXi hypervisor uses full virtualization for virtual machines. They c 9. Double-click the console preview to launch the console of the virtual machine. You can now run the installation of your operating system: -The network configuration of the virtual machine is done during the installation. Refer to the [network configuration documentation](/dedibox-network/ip-failover/quickstart/) to learn more about how to configure the networking on your operating system. \ No newline at end of file +The network configuration of the virtual machine is done during the installation. Refer to the [network configuration documentation](/dedibox-ip-failover/quickstart/) to learn more about how to configure the networking on your operating system. \ No newline at end of file diff --git a/tutorials/configure-vm-hyperv/index.mdx b/tutorials/configure-vm-hyperv/index.mdx index 05ab04c25a..f2bc784b4e 100644 --- a/tutorials/configure-vm-hyperv/index.mdx +++ b/tutorials/configure-vm-hyperv/index.mdx @@ -19,9 +19,9 @@ It is available since the release of Windows Server 2012. - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Scaleway Dedibox](http://www.scaleway.com/en/dedibox) server that fulfills the hardware requirements of the [HyperV version](https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/system-requirements-for-hyper-v-on-windows) you have -- At least one [failover IP](/dedibox-network/ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-network/ip-failover/concepts/#virtual-mac-address) +- At least one [failover IP](/dedibox-ip-failover/concepts/#failover-ips) with a [virtual MAC address](/dedibox-ip-failover/concepts/#virtual-mac-address) - Microsoft has discontinued the free standalone Hyper-V Server product. The last version, Hyper-V Server 2019, reached the end of mainstream support in January 2024, with extended support continuing until January 2029. @@ -93,10 +93,10 @@ The process from this step forward may differ according to the KVM model being u 9. Click **Finish** to launch the creation of the virtual machine: -10. Assign a virtual MAC address to the failover IP from the [Dedibox console](https://console.online.net/) to make sure that the virtual machine is able to communicate on the internet. Refer to the [dedicated documentation](/dedibox-network/ip-failover/how-to/create-virtual-mac/) for more information about how to create a virtual MAC address. Click **Settings** in the VM section of the menu. +10. Assign a virtual MAC address to the failover IP from the [Dedibox console](https://console.online.net/) to make sure that the virtual machine is able to communicate on the internet. Refer to the [dedicated documentation](/dedibox-ip-failover/how-to/create-virtual-mac/) for more information about how to create a virtual MAC address. Click **Settings** in the VM section of the menu. 11. Click **Network Adapter** (1), **Advanced Features** (2), then on **Static** in the **MAC Address** section. Enter the virtual MAC address of the failover IP in the form and validate by clicking on **Apply**, then **OK** to leave the settings window. 12. Start the Virtual Machine by clicking on **Start** in the side menu. The virtual machine will boot from the ISO file and the installation wizard of the operating system displays. Follow the steps of the wizard to complete the installation. -13. Configure the virtual networking as described in our [documentation](/bare-metal/elastic-metal/how-to/configure-flexible-ip/) once the installation of the guest OS has been completed. Then, you may run a ping test to check the connectivity of the virtual machine: +13. Configure the virtual networking as described in our [documentation](/elastic-metal/how-to/configure-flexible-ip/) once the installation of the guest OS has been completed. Then, you may run a ping test to check the connectivity of the virtual machine: \ No newline at end of file diff --git a/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx b/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx index 1a82912425..4cf49cc58b 100644 --- a/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx +++ b/tutorials/configuring-gitlab-scaleway-elements-database/index.mdx @@ -19,21 +19,21 @@ Numerous major technology companies rely on GitLab to oversee their software dev For those seeking a dependable and high-performance hosting solution, Scaleway Cost-Optimized Instances present an ideal choice for your GitLab infrastructure. They provide a robust infrastructure for hosting your GitLab Instance, coupled with a Managed Database for PostgreSQL. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.04 LTS) - A domain or subdomain configured to point to the IP address of your Instance -- [Enabled the SMTP ports](/compute/instances/how-to/send-emails-from-your-instance/) to send emails from your Instance +- [Enabled the SMTP ports](/instances/how-to/send-emails-from-your-instance/) to send emails from your Instance ## Installing GitLab -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/) +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/) ``` ssh root@ ``` @@ -60,7 +60,7 @@ For those seeking a dependable and high-performance hosting solution, Scaleway C ## Creating a Database -1. [Create a Managed PostgreSQL Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) from the Scaleway console. You are taken to your Database's **Overview** page. +1. [Create a Managed PostgreSQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) from the Scaleway console. You are taken to your Database's **Overview** page. 2. Click the **Users** tab, then on **Add User**. 3. Enter the username (`gitlab`) and a secure password. In the permission tab, give `ALL` permissions for the user on the `rdb` database. 4. Retrieve the Database Instance **Endpoint** from the **Overview** tab, as it is required for the following steps. The first part, before the colon, is the IP address, and the second part is the port. diff --git a/tutorials/configuring-loadbalancer-wordpress/index.mdx b/tutorials/configuring-loadbalancer-wordpress/index.mdx index 5cf9fbcb04..4810e8884c 100644 --- a/tutorials/configuring-loadbalancer-wordpress/index.mdx +++ b/tutorials/configuring-loadbalancer-wordpress/index.mdx @@ -27,8 +27,8 @@ In this tutorial, you learn how to set up a Scaleway-managed Load Balancer with - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Prework - Setting up the backend Instances @@ -75,7 +75,7 @@ It is possible to check the status of the Load Balancer with an API call. It will provide you with information about the status of the Load Balancer and if the health check was successful. - Retrieve your organization ID and generate [API key](/identity-and-access-management/iam/how-to/create-api-keys/) from your [management console](https://console.scaleway.com/project/credentials) before you continue. + Retrieve your organization ID and generate [API key](/iam/how-to/create-api-keys/) from your [management console](https://console.scaleway.com/project/credentials) before you continue. 1. Set the required variables to make the API call easier: diff --git a/tutorials/create-deploy-staging-site-cpanel/index.mdx b/tutorials/create-deploy-staging-site-cpanel/index.mdx index 40cae9d053..834e4cd32c 100644 --- a/tutorials/create-deploy-staging-site-cpanel/index.mdx +++ b/tutorials/create-deploy-staging-site-cpanel/index.mdx @@ -29,7 +29,7 @@ Creating a staging website for your WordPress website is a smart move, allowing - A Scaleway account logged into the [console](https://console.scaleway.com) -- A [Web Hosting](/managed-services/webhosting/) account +- A [Web Hosting](/webhosting/) account ## Creating a WordPress staging website diff --git a/tutorials/create-esxi-cluster-dedibox/index.mdx b/tutorials/create-esxi-cluster-dedibox/index.mdx index f0c5f13ecd..8741b904dd 100644 --- a/tutorials/create-esxi-cluster-dedibox/index.mdx +++ b/tutorials/create-esxi-cluster-dedibox/index.mdx @@ -32,7 +32,7 @@ This tutorial consists of the following steps: - A Dedibox account logged into the [console](https://console.online.net/) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - 2 Dedibox [CORE-4-L SSD](https://www.scaleway.com/en/dedibox/core/core-4-l-ssd/) servers - An [RPN-SAN](https://www.scaleway.com/en/dedibox/storage/) - At least one [failover IP](https://www.scaleway.com/en/dedibox/ip-address/) @@ -93,7 +93,7 @@ Configure the RPN interface on both servers once the installation of both machin ``` vi vmknics.json ``` -10. Replace the MAC address of your RPN VMkernel NIC with your [Virtual MAC](/dedibox-network/ip-failover/how-to/create-virtual-mac/). +10. Replace the MAC address of your RPN VMkernel NIC with your [Virtual MAC](/dedibox-ip-failover/how-to/create-virtual-mac/). 11. Import the new configuration: ``` @@ -109,7 +109,7 @@ Configure the RPN interface on both servers once the installation of both machin ``` - You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-network/rpn/how-to/find-rpn-gateway/). + You can find the RPN gateway either on your server's overview page in the Dedibox console or by following [this guide](/dedibox-rpn/how-to/find-rpn-gateway/). 16. Ping the RPN-SAN to check if the RPN connection is working properly: ``` @@ -135,7 +135,7 @@ Repeat the steps above on the second Dedibox server. 1. Connect to the Dedibox console and click **Storage** > **RPN-SAN**. 2. Select the SAN you want to configure and click **Manage**. -3. Add the server(s) you want to permit to access your SAN services in the list. Optionally, you can add RPN subnet IPs. Note that if you use RPNv2, an [additional configuration](/dedibox-network/rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. +3. Add the server(s) you want to permit to access your SAN services in the list. Optionally, you can add RPN subnet IPs. Note that if you use RPNv2, an [additional configuration](/dedibox-rpn/how-to/configure-rpnv1-gateway/) is required to access the RPN-SAN. While it is technically possible, it is not recommended to allow more than one server at a time to communicate with the SAN. The iSCSI protocol does not handle concurrency, you may lose all your data if you allow more than one server to access this storage. @@ -169,7 +169,7 @@ We now have two ESXi hosts and an RPN-SAN but no possibility to manage both hype vCenter is a web-based tool for graphical management of the entire fabric of data center, clusters, networks, datastore, CPUs, and virtual machines in the form of a dynamic and seamless operating environment. - To proceed with these steps, you need to configure at least one [failover IP](/dedibox-network/ip-failover/quickstart/) with an associated [virtual MAC address](/dedibox-network/ip-failover/how-to/create-virtual-mac/). If you have not yet configured it, go to your [Dedibox console](https://console.online.net) before proceeding. + To proceed with these steps, you need to configure at least one [failover IP](/dedibox-ip-failover/quickstart/) with an associated [virtual MAC address](/dedibox-ip-failover/how-to/create-virtual-mac/). If you have not yet configured it, go to your [Dedibox console](https://console.online.net) before proceeding. diff --git a/tutorials/create-models-django/index.mdx b/tutorials/create-models-django/index.mdx index 623aca854a..ae52ead5d3 100644 --- a/tutorials/create-models-django/index.mdx +++ b/tutorials/create-models-django/index.mdx @@ -19,15 +19,15 @@ dates: To follow this tutorial, we assume that you completed the [first tutorial on Django installation and configuration](/tutorials/django-ubuntu-focal-fossa/). - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Focal Fossa (20.04 LTS) or later - `sudo` privileges or access to the root user - Completed the [Django installation and configuration tutorial](/tutorials/django-ubuntu-focal-fossa/) diff --git a/tutorials/create-openwrt-image-for-scaleway/index.mdx b/tutorials/create-openwrt-image-for-scaleway/index.mdx index d39963f48c..81a870d6a9 100644 --- a/tutorials/create-openwrt-image-for-scaleway/index.mdx +++ b/tutorials/create-openwrt-image-for-scaleway/index.mdx @@ -22,7 +22,7 @@ It introduces the basic needs and actions to create a custom image, but each ope The procedure introduced in this tutorial is specific to OpenWrt, an open-source project for embedded operating systems based on Linux. It is primarily used to route network traffic. -To create a custom image, you need to build a [QCOW2 image](https://www.linux-kvm.org/page/Qcow2) and [create a snapshot](/compute/instances/how-to/create-a-snapshot/) from it. +To create a custom image, you need to build a [QCOW2 image](https://www.linux-kvm.org/page/Qcow2) and [create a snapshot](/instances/how-to/create-a-snapshot/) from it. The following steps are required to create the image: @@ -36,9 +36,9 @@ The following steps are required to create the image: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) The following commands are done on an Ubuntu 22.04. @@ -294,7 +294,7 @@ In this tutorial, we do not set up cloud-init, but use the same magic IP mechani You can use the Scaleway console or your favorite Amazon S3-compatible CLI tool to upload objects into a bucket. -In this example, we use the [AWS CLI](/storage/object/api-cli/object-storage-aws-cli/). +In this example, we use the [AWS CLI](/object-storage/api-cli/object-storage-aws-cli/). 1. Import the image into your bucket: diff --git a/tutorials/create-serverless-scraping/index.mdx b/tutorials/create-serverless-scraping/index.mdx index b8364934cb..d307d9f348 100644 --- a/tutorials/create-serverless-scraping/index.mdx +++ b/tutorials/create-serverless-scraping/index.mdx @@ -80,7 +80,7 @@ We start by creating the scraper program, or the "data producer". body = json.dumps({'url': titleline.a["href"], 'title': titleline.a.get_text()}) response = sqs.send_message(QueueUrl=queue_url, MessageBody=body) ``` -As explained in the [Scaleway Functions documentation](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-configure-your-package), dependencies need to be installed in a `package` folder, and uploaded as an archive. This is done via Terraform, but if you decide to deploy using another system, you can create the archive as follows: +As explained in the [Scaleway Functions documentation](/serverless-functions/how-to/package-function-dependencies-in-zip/#how-to-configure-your-package), dependencies need to be installed in a `package` folder, and uploaded as an archive. This is done via Terraform, but if you decide to deploy using another system, you can create the archive as follows: ```bash cd scraper pip install -r requirements.txt --target ./package @@ -126,7 +126,7 @@ Next, let's create our consumer function. When receiving a message containing th if conn is not None: conn.close() ``` -As explained in the [Scaleway Functions documentation](/serverless/functions/how-to/package-function-dependencies-in-zip/#how-to-configure-your-package), dependencies need to be installed in a `package` folder, and uploaded as an archive. This is done via Terraform, but if you decide to deploy using another system, you can create the archive as follows: +As explained in the [Scaleway Functions documentation](/serverless-functions/how-to/package-function-dependencies-in-zip/#how-to-configure-your-package), dependencies need to be installed in a `package` folder, and uploaded as an archive. This is done via Terraform, but if you decide to deploy using another system, you can create the archive as follows: ```bash cd consumer pip install -r requirements.txt --target ./package @@ -140,10 +140,10 @@ For the purposes of this tutorial, we show how to provision all resources via Te If you do not want to use Terraform, 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](/serverless/messaging/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/messaging-and-queuing/sqs-api/) -- **Managed Database for PostgreSQL**: [console documentation](/managed-databases/postgresql-and-mysql/quickstart/) | [API documentation](https://www.scaleway.com/en/developers/api/managed-database-postgre-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) +- **Scaleway Queues resources**: [console documentation](/messaging/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/) +- **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) 1. Create a directory called `terraform` (at the same level as the `scraper` and `consumer` directories created in the previous steps). @@ -386,7 +386,7 @@ terraform apply Go to the [Scaleway console](https://console.scaleway.com/), and check the logs and metrics for Serverless Functions' execution and the queue's statistics. -To make sure the data is correctly stored in the database, you can [connect to it directly](/managed-databases/postgresql-and-mysql/how-to/connect-database-instance/) via a CLI tool such as `psql`. +To make sure the data is correctly stored in the database, you can [connect to it directly](/managed-databases-for-postgresql-and-mysql/how-to/connect-database-instance/) via a CLI tool such as `psql`. Retrieve the instance IP and port of your Managed Database from the console, under the [Managed Database section](https://console.scaleway.com/rdb/instances). Use the following command to connect to your database. When prompted for a password, you can find it by running `terraform output -json`. ``` @@ -407,5 +407,5 @@ While the volume of data processed in this example is quite small, thanks to rob Here are some possible extensions to this basic example: - Replace the simple proposed logic with your own. What about counting how many times some keywords (e.g: copilot, serverless, microservice) appear in Hacker News articles? - Define multiple cron triggers for different websites and pass the website as an argument to the function. Or, create multiple functions that feed the same queue. - - Use a [Serverless Container](/serverless/containers/quickstart/) instead of the consumer function, and use a command line tool such as `htmldoc` or `pandoc` to convert the scraped articles to PDF and upload the result to a [Scaleway Object Storage bucket](/storage/object/quickstart/). - - Replace the Managed Database for PostgreSQL with a [Scaleway Serverless Database](/serverless/sql-databases/quickstart/), so that all the infrastructure lives in the serverless ecosystem! *Note that at the moment there is no Terraform support for Serverless Database, hence the choice here to use Managed Database for PostgreSQL*. \ No newline at end of file + - Use a [Serverless Container](/serverless-containers/quickstart/) instead of the consumer function, and use a command line tool such as `htmldoc` or `pandoc` to convert the scraped articles to PDF and upload the result to a [Scaleway Object Storage bucket](/object-storage/quickstart/). + - Replace the Managed Database for PostgreSQL with a [Scaleway Serverless Database](/serverless-sql-databases/quickstart/), so that all the infrastructure lives in the serverless ecosystem! *Note that at the moment there is no Terraform support for Serverless Database, hence the choice here to use Managed Database for PostgreSQL*. \ No newline at end of file diff --git a/tutorials/create-valheim-server/index.mdx b/tutorials/create-valheim-server/index.mdx index 51141f5883..98606db926 100644 --- a/tutorials/create-valheim-server/index.mdx +++ b/tutorials/create-valheim-server/index.mdx @@ -24,8 +24,8 @@ At Scaleway, we offer a large range of Instances that will suit the gaming needs - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Deploying an Instance @@ -43,7 +43,7 @@ scw instance server create type=DEV1-L zone=fr-par-2 image=ubuntu_focal root-vol ## Installing SteamCMD -1. Log into your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Log into your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. The Valheim Server requires [SteamCMD](https://developer.valvesoftware.com/wiki/SteamCMD), a command line client of the Steam client. It requires the `i386` architecture available in the `apt` package manager. Add it with the following command: ``` dpkg --add-architecture i386 diff --git a/tutorials/create-wordpress-instances-cli/index.mdx b/tutorials/create-wordpress-instances-cli/index.mdx index 19917d2a35..3a7bc11daf 100644 --- a/tutorials/create-wordpress-instances-cli/index.mdx +++ b/tutorials/create-wordpress-instances-cli/index.mdx @@ -13,7 +13,7 @@ dates: posted: 2021-10-11 --- -This page shows you how to create WordPress Instances with the Scaleway CLI. Refer to our [tutorial on creating WordPress Instances from the Scaleway console](/tutorials/wordpress-instantapp/) to create an Instance from the [Scaleway console](https://console.scaleway.com/). By default, the WordPress image used in this tutorial [supports routed IPs](/compute/instances/api-cli/using-routed-ips/). +This page shows you how to create WordPress Instances with the Scaleway CLI. Refer to our [tutorial on creating WordPress Instances from the Scaleway console](/tutorials/wordpress-instantapp/) to create an Instance from the [Scaleway console](https://console.scaleway.com/). By default, the WordPress image used in this tutorial [supports routed IPs](/instances/api-cli/using-routed-ips/). WordPress is a popular, free, and open-source blogging tool and a content management system (CMS) based on PHP and MariaDB. @@ -24,8 +24,8 @@ The new WordPress image is updated regularly to be as close as possible to the l - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Downloaded and installed the [Scaleway CLI](https://github.com/scaleway/scaleway-cli#scaleway-cli-v2/) ## Auto-install functionality diff --git a/tutorials/dagster-serverless-jobs/index.mdx b/tutorials/dagster-serverless-jobs/index.mdx index 1d1d572830..1c1168f6a4 100644 --- a/tutorials/dagster-serverless-jobs/index.mdx +++ b/tutorials/dagster-serverless-jobs/index.mdx @@ -20,19 +20,19 @@ dates: It allows you to declare jobs that you want to run and the data assets that those jobs produce or update. Dagster then helps you run your jobs at the right time and keep your assets up-to-date. -In this tutorial, we will create a [Serverless Job](/serverless/jobs/quickstart/) using Dagster to scrape the content of the [Hacker News webstite](https://news.ycombinator.com/) to retrieve the title, author, and URL of the top articles. +In this tutorial, we will create a [Serverless Job](/serverless-jobs/quickstart/) using Dagster to scrape the content of the [Hacker News webstite](https://news.ycombinator.com/) to retrieve the title, author, and URL of the top articles. First, we will initialize the Dagster project locally and add the scraper's source code to it. Then, we will set up the environment, build the image and push it to the Scaleway registry. Finally, we will execute Dagster locally to scrape the Hacker News top stories through the Dagster UI. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) in the Paris region and have [signed in to it](/containers/container-registry/how-to/connect-docker-cli/) -- A [Serverless Database](/serverless/sql-databases/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [API key](/iam/how-to/create-api-keys/) +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) in the Paris region and have [signed in to it](/container-registry/how-to/connect-docker-cli/) +- A [Serverless Database](/serverless-sql-databases/how-to/create-a-database/) - Installed [Docker](https://docs.docker.com/engine/install/) locally to build and push the image -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) in the Paris region +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) in the Paris region ## Creating the Dagster project @@ -154,10 +154,10 @@ We will install Dagster using the `pip` package installer. Refer to the [Dagster ## Setting up the environment and creating the image 1. Retrieve the following elements: - - your [Serverless SQL Database connection string](/serverless/sql-databases/how-to/connect-to-a-database/#how-to-set-up-credentials) - - the project ID of the [Scaleway project](/identity-and-access-management/organizations-and-projects/how-to/create-a-project/) you want to use - - the [access key and secret key](/identity-and-access-management/iam/how-to/create-api-keys/) for your API key - - the name of the [Object Storage bucket](/storage/object/how-to/create-a-bucket/) you created + - your [Serverless SQL Database connection string](/serverless-sql-databases/how-to/connect-to-a-database/#how-to-set-up-credentials) + - the project ID of the [Scaleway project](/organizations-and-projects/how-to/create-a-project/) you want to use + - the [access key and secret key](/iam/how-to/create-api-keys/) for your API key + - the name of the [Object Storage bucket](/object-storage/how-to/create-a-bucket/) you created 2. Export the environment variables below: ```bash export PG_CONN_STRING= @@ -238,9 +238,9 @@ Dagster writes small chunks of data in the Serverless SQL Database as long as th - Refer to the [official Dagster documentation](https://docs.dagster.io/getting-started/what-why-dagster) for more information. -- You can automate your Dagster deployment using Terraform. Refer to our [Terraform Quickstart](/developer-tools/terraform/quickstart/) and to the [Scaleway Provider registry](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) for more information. +- You can automate your Dagster deployment using Terraform. Refer to our [Terraform Quickstart](/terraform/quickstart/) and to the [Scaleway Provider registry](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) for more information. -- You can replace the Serverless Database with a [Managed Database for postgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) to keep the Dagster UI running and reduce your database costs. Refer to the [Dagster documentation](https://docs.dagster.io/deployment/dagster-instance#dagster-storage) to connect a database using Postgres credentials. +- You can replace the Serverless Database with a [Managed Database for postgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) to keep the Dagster UI running and reduce your database costs. Refer to the [Dagster documentation](https://docs.dagster.io/deployment/dagster-instance#dagster-storage) to connect a database using Postgres credentials. ## Troubleshooting diff --git a/tutorials/deploy-angular-application/index.mdx b/tutorials/deploy-angular-application/index.mdx index 7432ad0951..feda7ec508 100644 --- a/tutorials/deploy-angular-application/index.mdx +++ b/tutorials/deploy-angular-application/index.mdx @@ -19,9 +19,9 @@ Angular 18 is the latest development platform that scales from single-developer - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Container Registry namespace](/container-registry/how-to/create-namespace/) - Installed [Angular 18](https://angular.dev/installation) and [Node.js](https://nodejs.org/en/learn/getting-started/how-to-install-nodejs) on your local machine - Installed [Docker](/tutorials/install-docker-ubuntu-jammy-jellyfish/) for building and pushing the Docker image @@ -90,7 +90,7 @@ Make sure `@angular/cli` version 18 or higher is installed on your local machine ### Building and Publishing the Docker Image -Ensure you have [connected your namespace](/containers/container-registry/how-to/connect-docker-cli/) to the Docker CLI before proceeding. +Ensure you have [connected your namespace](/container-registry/how-to/connect-docker-cli/) to the Docker CLI before proceeding. 1. Build the Docker image: diff --git a/tutorials/deploy-awstats/index.mdx b/tutorials/deploy-awstats/index.mdx index af2ec09fb1..1d0ac25ff9 100644 --- a/tutorials/deploy-awstats/index.mdx +++ b/tutorials/deploy-awstats/index.mdx @@ -22,13 +22,13 @@ AwStats leverages log file analysis to parse data from a wide range of web serve - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) - `sudo` privileges or access to the root user - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). ## Installing Apache diff --git a/tutorials/deploy-big-blue-button/index.mdx b/tutorials/deploy-big-blue-button/index.mdx index c6d57e4701..cc2cb9347a 100644 --- a/tutorials/deploy-big-blue-button/index.mdx +++ b/tutorials/deploy-big-blue-button/index.mdx @@ -35,12 +35,12 @@ This tutorial shows you how to deploy BigBlueButton on a Scaleway Elastic Metal - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Deploying BigBlueButton on a Scaleway Elastic Metal server -1. [Create an Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/), ensuring you select the **Big Blue Button 2.5** image at step 2 of the creation wizard. +1. [Create an Elastic Metal server](/elastic-metal/how-to/create-server/), ensuring you select the **Big Blue Button 2.5** image at step 2 of the creation wizard. The creation and installation of the server launches. This takes up to one hour. Once it finishes, you can see the URL to connect to your BigBlueButton interface in the description of the machine: diff --git a/tutorials/deploy-chatwoot-self-care/index.mdx b/tutorials/deploy-chatwoot-self-care/index.mdx index 957bd27045..38af194f06 100644 --- a/tutorials/deploy-chatwoot-self-care/index.mdx +++ b/tutorials/deploy-chatwoot-self-care/index.mdx @@ -24,13 +24,13 @@ Chatwoot is designed to enhance customer satisfaction and improve customer suppo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [Production-Optimized Instance](/compute/instances/how-to/create-an-instance/) with at least 8 GB RAM and 25 GB Block Storage, running on Ubuntu 20.04 LTS or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [Production-Optimized Instance](/instances/how-to/create-an-instance/) with at least 8 GB RAM and 25 GB Block Storage, running on Ubuntu 20.04 LTS or later - Installed [Ruby 3.2.2](/tutorials/ruby-on-rails/) on your Instance - A (sub-)domain pointed to the Instance's IP address -1. [Log into your Instance using SSH](/compute/instances/how-to/connect-to-instance/). +1. [Log into your Instance using SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance to the latest version available in the distribution repositories. ``` apt update && apy upgrade -y @@ -80,7 +80,7 @@ Chatwoot is designed to enhance customer satisfaction and improve customer suppo Whenever a newer version of Chatwoot is released, you can upgrade your installation to stay up-to-date with the latest developments and features added. -1. [Log into your Instance as root using SSH](/compute/instances/how-to/connect-to-instance/). +1. [Log into your Instance as root using SSH](/instances/how-to/connect-to-instance/). 2. From the root login, change to the Chatwoot user account to perform the upgrade. ```bsh diff --git a/tutorials/deploy-clickhouse-database/index.mdx b/tutorials/deploy-clickhouse-database/index.mdx index 988b25c0d9..d3ef07daff 100644 --- a/tutorials/deploy-clickhouse-database/index.mdx +++ b/tutorials/deploy-clickhouse-database/index.mdx @@ -19,13 +19,13 @@ ClickHouse® is an open-source column-oriented database management system that a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu or Debian +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu or Debian # Installing ClickHouse -1. [Log into your Instance using SSH](/compute/instances/how-to/connect-to-instance/). +1. [Log into your Instance using SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance to the latest version available in the distribution repositories. ``` apt update && apt upgrade -y diff --git a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx index e7f5c38c65..a129ce7f98 100644 --- a/tutorials/deploy-hasura-engine-database-postgresql/index.mdx +++ b/tutorials/deploy-hasura-engine-database-postgresql/index.mdx @@ -21,7 +21,7 @@ In this tutorial, you will learn how to get started with Hasura GraphQL Engine u - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Scaleway Database for PostgreSQL](https://www.scaleway.com/en/database/) - Installed [Docker](https://docs.docker.com/get-docker/) on your local computer - Basic understanding of Docker, PostgreSQL, and GraphQL @@ -124,4 +124,4 @@ Hasura provides a pre-configured [repository](https://github.com/hasura/graphql- You have successfully deployed Hasura GraphQL Engine 3.0 using Docker, linked it to a Scaleway Database for PostgreSQL, and run your first GraphQL queries. -For further learning, explore the [Hasura documentation](https://hasura.io/docs/latest/) or Scaleway’s [PostgreSQL resources](/managed-databases/postgresql-and-mysql/). \ No newline at end of file +For further learning, explore the [Hasura documentation](https://hasura.io/docs/latest/) or Scaleway’s [PostgreSQL resources](/managed-databases-for-postgresql-and-mysql/). \ No newline at end of file diff --git a/tutorials/deploy-instances-packer-terraform/index.mdx b/tutorials/deploy-instances-packer-terraform/index.mdx index 9e7029701a..182053b5eb 100644 --- a/tutorials/deploy-instances-packer-terraform/index.mdx +++ b/tutorials/deploy-instances-packer-terraform/index.mdx @@ -23,10 +23,10 @@ Both applications are available for Linux, macOS, Windows, FreeBSD, and NetBSD. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). ## Downloading and installing Packer @@ -52,7 +52,7 @@ Both applications are available for Linux, macOS, Windows, FreeBSD, and NetBSD. Packer builds images by taking a base image and installing additional software on it. -To use Packer with Scaleway, you must [generate an API key](/identity-and-access-management/iam/how-to/create-api-keys/) from the management console. +To use Packer with Scaleway, you must [generate an API key](/iam/how-to/create-api-keys/) from the management console. Packer uses JSON files for the configuration. diff --git a/tutorials/deploy-k3s-cluster-with-cilium/index.mdx b/tutorials/deploy-k3s-cluster-with-cilium/index.mdx index 33d310ee11..70956620a3 100644 --- a/tutorials/deploy-k3s-cluster-with-cilium/index.mdx +++ b/tutorials/deploy-k3s-cluster-with-cilium/index.mdx @@ -18,8 +18,8 @@ This step-by-step guide is designed to help you set up a highly efficient Kubern -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Installed and configured the [Scaleway CLI (v2)](https://github.com/scaleway/scaleway-cli) ## Choosing K3s and Cilium: A lightweight and efficient Kubernetes setup diff --git a/tutorials/deploy-laravel-on-serverless-containers/index.mdx b/tutorials/deploy-laravel-on-serverless-containers/index.mdx index e81853d23e..5c65f2ce8a 100644 --- a/tutorials/deploy-laravel-on-serverless-containers/index.mdx +++ b/tutorials/deploy-laravel-on-serverless-containers/index.mdx @@ -20,12 +20,12 @@ This tutorial provides a step-by-step guide for deploying a containerized Larave - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed [Docker](/tutorials/install-docker-ubuntu-bionic/) on your local computer ## Why Scaleway is suitable for deploying containerized applications -Scaleway provides a seamless environment for running and managing containers, offering features such as [Container Registry](https://www.scaleway.com/en/container-registry/), [Serverless Containers](https://www.scaleway.com/en/serverless-containers/), [Queues](/serverless/messaging/) and [Observability](https://www.scaleway.com/en/cockpit/). By combining the benefits of containerization with Scaleway's platform, developers should be able to easily deploy, scale, and manage their applications efficiently. +Scaleway provides a seamless environment for running and managing containers, offering features such as [Container Registry](https://www.scaleway.com/en/container-registry/), [Serverless Containers](https://www.scaleway.com/en/serverless-containers/), [Queues](/messaging/) and [Observability](https://www.scaleway.com/en/cockpit/). By combining the benefits of containerization with Scaleway's platform, developers should be able to easily deploy, scale, and manage their applications efficiently. [Serverless Containers](https://www.scaleway.com/en/serverless-containers/) offers significant advantages when deploying Laravel applications over [Serverless Functions](https://www.scaleway.com/en/serverless-functions/), as it provides the flexibility to customize the runtime environment according to your specific needs. @@ -33,7 +33,7 @@ Scaleway provides a seamless environment for running and managing containers, of ## Creating a queue -Laravel applications make use of [queues](https://laravel.com/docs/10.x/queues) to process long-running jobs in the background. As this feature of the Laravel framework is nearly always used, we will configure it and leverage the [Scaleway Queues](/serverless/messaging/) product from Scaleway. The [Scaleway documentation](/serverless/messaging/quickstart/) provides clear information on how this managed service works and can be configured. +Laravel applications make use of [queues](https://laravel.com/docs/10.x/queues) to process long-running jobs in the background. As this feature of the Laravel framework is nearly always used, we will configure it and leverage the [Scaleway Queues](/messaging/) product from Scaleway. The [Scaleway documentation](/messaging/quickstart/) provides clear information on how this managed service works and can be configured. 1. Create a queue. In this example, we create a `Standard` queue (At-least-once delivery, the order of messages is not preserved) with the default parameters. This queue will be the default queue used by our application. @@ -208,7 +208,7 @@ In this section, we will focus on building the containerized image. With Docker, ## Creating Container Registry -1. [Create a Scaleway Container Registry namespace](/containers/container-registry/how-to/create-namespace/) in the `PAR` region. Set the visibility to `Private` to avoid having your container retrieved without proper authentication and authorization. +1. [Create a Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/) in the `PAR` region. Set the visibility to `Private` to avoid having your container retrieved without proper authentication and authorization. @@ -230,13 +230,13 @@ In this section, we will focus on building the containerized image. With Docker, ## Deploying the Serverless Container -The Scaleway documentation website provides a Quickstart on how to [create and manage a Serverless Container Namespace](/serverless/containers/quickstart/). +The Scaleway documentation website provides a Quickstart on how to [create and manage a Serverless Container Namespace](/serverless-containers/quickstart/). 1. Create a Serverless Containers namespace. In this example, we create the `my-laravel-application` namespace and configure the environment variables and secrets necessary for our application. In particular, we must add all the variables needed to connect to the previously created SQS/SNS queue. By default, Laravel expects the following environment variables/secrets to be filled in for queues: `AWS_ACCESS_KEY_ID`, `AWS_SECRET_ACCESS_KEY`, `AWS_DEFAULT_REGION`, `QUEUE_CONNECTION`, `SQS_PREFIX` and `SQS_QUEUE`. -2. Deploy the application. Click **+ Deploy a Container** once the namespace is created, and follow the instructions of the creation wizard. Select the registry namespace and the previously uploaded Docker image and configure the listening port (the Nginx web server is listening on port 80). For the CPU and memory, define at least 560mVPCU and 256 MB respectively. To reduce the limitations due to [cold start](/serverless/containers/concepts/#cold-start), we will run at least 1 instance. +2. Deploy the application. Click **+ Deploy a Container** once the namespace is created, and follow the instructions of the creation wizard. Select the registry namespace and the previously uploaded Docker image and configure the listening port (the Nginx web server is listening on port 80). For the CPU and memory, define at least 560mVPCU and 256 MB respectively. To reduce the limitations due to [cold start](/serverless-containers/concepts/#cold-start), we will run at least 1 instance. diff --git a/tutorials/deploy-mdbooks-serverless-containers/index.mdx b/tutorials/deploy-mdbooks-serverless-containers/index.mdx index 2d3c1e9d6d..47a5d0700c 100644 --- a/tutorials/deploy-mdbooks-serverless-containers/index.mdx +++ b/tutorials/deploy-mdbooks-serverless-containers/index.mdx @@ -21,7 +21,7 @@ This tutorial uses `mdbook` to publish simple documentation but the main goal of - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Docker](https://docs.docker.com/engine/install/) installed on your local machine ## Why deploy on a Serverless infrastructure? @@ -54,7 +54,7 @@ With zero infrastructure management and many tools to integrate in CI/CD environ ## Preparing the Container Registry - We recommend using [Scaleway Container Registry](/containers/container-registry/) instead of external registries to avoid rate limiting errors, and risks linked to CGU and pricing changes. + We recommend using [Scaleway Container Registry](/container-registry/) instead of external registries to avoid rate limiting errors, and risks linked to CGU and pricing changes. 1. Create a file named `Dockerfile` in the previously created folder, and add the following code to it: @@ -82,12 +82,12 @@ With zero infrastructure management and many tools to integrate in CI/CD environ 2. Open the Scaleway console in a web browser, and navigate to the [Container Registry](https://console.scaleway.com/containers/). -3. Click **+ Create namespace**. [Namespaces](/containers/container-registry/concepts/#namespace) allow you to easily manage the images stored in your Container Registry. +3. Click **+ Create namespace**. [Namespaces](/container-registry/concepts/#namespace) allow you to easily manage the images stored in your Container Registry. 4. Enter a name for your namespace, or keep the automatically generated one, then click **Create namespace**. - For more information on creating a Container Registry namespace, refer to [the dedicated documentation](/containers/container-registry/how-to/create-namespace/). + For more information on creating a Container Registry namespace, refer to [the dedicated documentation](/container-registry/how-to/create-namespace/). ## Building and pushing the image @@ -140,6 +140,6 @@ Your Serverless Container is deployed and ready. You can access it via its **end ## Going further -* [Monitor logs and metrics](/serverless/containers/how-to/monitor-container/) of your container. -* [Add a custom domain](/serverless/containers/how-to/add-a-custom-domain-to-a-container/) to your container. -* Explore [other methods](/serverless/containers/reference-content/deploy-container/) to deploy your container. +* [Monitor logs and metrics](/serverless-containers/how-to/monitor-container/) of your container. +* [Add a custom domain](/serverless-containers/how-to/add-a-custom-domain-to-a-container/) to your container. +* Explore [other methods](/serverless-containers/reference-content/deploy-container/) to deploy your container. diff --git a/tutorials/deploy-meilisearch-instance/index.mdx b/tutorials/deploy-meilisearch-instance/index.mdx index f0a1d3453c..cd9707b04d 100644 --- a/tutorials/deploy-meilisearch-instance/index.mdx +++ b/tutorials/deploy-meilisearch-instance/index.mdx @@ -15,19 +15,19 @@ dates: Meilisearch is an open-source search engine that provides instant and relevant search results from large collections of data. [Meilisearch](https://www.meilisearch.com/) is particularly useful for applications that require fast and efficient search capabilities, such as e-commerce sites, documentation search, and any platform where users need to quickly find relevant information from a large dataset. -This tutorial shows you how to deploy a Meilisearch search engine on a [Scaleway Instance](/compute/instances/). +This tutorial shows you how to deploy a Meilisearch search engine on a [Scaleway Instance](/instances/). - A Scaleway account logged into the [console](https://console.scaleway.com/) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) (specifically **InstancesFullAccess**) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) with the [Docker InstantApp](/compute/instances/reference-content/images-and-instantapps/#instantapps) or with the [Docker Engine](https://docs.docker.com/engine/install/) installed +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) (specifically **InstancesFullAccess**) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) with the [Docker InstantApp](/instances/reference-content/images-and-instantapps/#instantapps) or with the [Docker Engine](https://docs.docker.com/engine/install/) installed ## Connecting to your Instance and starting Meilisearch -1. Open a terminal and connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). Replace `` with your Instance's IP (Instances > Overview > Flexible IP > the first IP address that displays in the list). +1. Open a terminal and connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). Replace `` with your Instance's IP (Instances > Overview > Flexible IP > the first IP address that displays in the list). ``` ssh root@ @@ -101,7 +101,7 @@ This tutorial shows you how to deploy a Meilisearch search engine on a [Scaleway You can also open your browser at `http://{INSTANCE_PUBLIC_DNS}:7700/health` since you do not need an API key to access the `/health` endpoint. -If you have created your Instance within a **Private Network** or if you are using a specific **security group** configuration, you must allow TCP traffic on port `7700` for your Instance to access your Meilisearch container remotely. See [our dedicated documentation on how to use security groups](/compute/instances/how-to/use-security-groups/) and [how to configure a Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/) for more information. +If you have created your Instance within a **Private Network** or if you are using a specific **security group** configuration, you must allow TCP traffic on port `7700` for your Instance to access your Meilisearch container remotely. See [our dedicated documentation on how to use security groups](/instances/how-to/use-security-groups/) and [how to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) for more information. ## Creating an index and adding data to it @@ -159,12 +159,12 @@ If you have created your Instance within a **Private Network** or if you are usi - **Secure** your deployment: - Encrypt traffic in transit to Meilisearch by [setting up SSL](https://www.meilisearch.com/docs/learn/configuration/instance_options#ssl-options) - - Move your Instance inside a [Private Network](/compute/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](/compute/instances/how-to/create-a-snapshot/) + - 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](/instances/how-to/create-a-snapshot/) -- **Fine-tune deployment configuration** such as [Instance type or disk size](/compute/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](/compute/instances/api-cli/cli-cheatsheet/) or [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/instance_server/). +- **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/) or [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs/resources/instance_server/). ## Troubleshooting -If you encounter any issues, check that you meet all the [requirements listed at the beginning of this page](#before-you-start). Also, verify that your Instance accepts connections from your computer. To do so, you can configure [security groups](/compute/instances/how-to/use-security-groups/) or a [Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/) on the [Private Network](/compute/instances/how-to/use-private-networks/) your Instance belongs to. +If you encounter any issues, check that you meet all the [requirements listed at the beginning of this page](#before-you-start). Also, verify that your Instance accepts connections from your computer. To do so, you can configure [security groups](/instances/how-to/use-security-groups/) or a [Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) on the [Private Network](/instances/how-to/use-private-networks/) your Instance belongs to. diff --git a/tutorials/deploy-nextcloud-s3/index.mdx b/tutorials/deploy-nextcloud-s3/index.mdx index 7165afd13f..3d7a1ed1f2 100644 --- a/tutorials/deploy-nextcloud-s3/index.mdx +++ b/tutorials/deploy-nextcloud-s3/index.mdx @@ -21,9 +21,9 @@ Combining NextCloud with Scaleway Object Storage gives you infinite storage spac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04) or later - Installed and configured [MariaDB](/tutorials/mariadb-ubuntu-bionic/) on your Instance - `sudo` privileges or access to the root user @@ -224,8 +224,8 @@ You can use NextCloud as a client for Object Storage while using the Local Stora - `Port` = The port for your bucket, leave this empty - `Region` = The geographical region of your bucket (Either: `nl-ams` for Amsterdam, The Netherlands, `pl-waw` for Warsaw, Poland, or `fr-par` for Paris, France) - `Enable SSL` = Activate this checkbox to encrypt the connection between your NextCloud and the Bucket - - `Access key` = Your [access key](/identity-and-access-management/iam/how-to/create-api-keys/) - - `Secret key` = Your [secret key](/identity-and-access-management/iam/how-to/create-api-keys/) + - `Access key` = Your [access key](/iam/how-to/create-api-keys/) + - `Secret key` = Your [secret key](/iam/how-to/create-api-keys/) Once you have entered all the details, click the checkmark to validate your configuration. If everything works well, a green dot will appear on the left. 6. Click the **file icon**, then on **External Storages** to access your bucket: diff --git a/tutorials/deploy-openproject-database-postgresql/index.mdx b/tutorials/deploy-openproject-database-postgresql/index.mdx index e6e143256c..f81dcb7f62 100644 --- a/tutorials/deploy-openproject-database-postgresql/index.mdx +++ b/tutorials/deploy-openproject-database-postgresql/index.mdx @@ -24,15 +24,15 @@ In this tutorial, you will learn how to install and configure OpenProject on an - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 22.04 (Jammy) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 22.04 (Jammy) - `sudo` privileges or access to the root user -- Configured an [A-record pointing to your Instance's IP address](/network/domains-and-dns/how-to/manage-dns-records/) +- Configured an [A-record pointing to your Instance's IP address](/domains-and-dns/how-to/manage-dns-records/) ## Installing OpenProject -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). 2. Update and upgrade the system to the latest version available in Ubuntus repositories. Then, install the `apt-transport-https` package, which allows the use of repositories accessed via the HTTP Secure protocol (HTTPS). ``` apt update && apt -y upgrade @@ -60,7 +60,7 @@ In this tutorial, you will learn how to install and configure OpenProject on an Since OpenProject requires a PostgreSQL database to run, we will be creating a Database for the PostgreSQL instance directly in the [Scaleway console](https://console.scaleway.com/rdb/instances/create). -Follow the instructions to [create a Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). Ensure that you select **PostgreSQL** as the database engine. +Follow the instructions to [create a Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). Ensure that you select **PostgreSQL** as the database engine. ## Configuring the stack diff --git a/tutorials/deploy-penpot-with-docker-instantapp/index.mdx b/tutorials/deploy-penpot-with-docker-instantapp/index.mdx index e9c6f3f81a..c2a23ea6e3 100644 --- a/tutorials/deploy-penpot-with-docker-instantapp/index.mdx +++ b/tutorials/deploy-penpot-with-docker-instantapp/index.mdx @@ -21,13 +21,13 @@ In this tutorial, you learn how to deploy your own Penpot Instance using the Doc - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Installing Penpot using Docker Compose -1. Click **Instances** in the **Compute** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. Then [deploy](/compute/instances/how-to/create-an-instance/) a new Instance using the [Docker InstantApp](https://console.scaleway.com/instance/servers/create?area=fr-par-1&imageKey=c1b530d8-0ca0-45c4-80db-ba06608287b2&offerName=PLAY2-MICRO). +1. Click **Instances** in the **Compute** section of the [Scaleway console](https://console.scaleway.com/organization) side menu. Then [deploy](/instances/how-to/create-an-instance/) a new Instance using the [Docker InstantApp](https://console.scaleway.com/instance/servers/create?area=fr-par-1&imageKey=c1b530d8-0ca0-45c4-80db-ba06608287b2&offerName=PLAY2-MICRO). -2. Connect to the Instance using [SSH](/compute/instances/how-to/connect-to-instance/): +2. Connect to the Instance using [SSH](/instances/how-to/connect-to-instance/): ``` ssh root@ ``` diff --git a/tutorials/deploy-phpmyadmin-with-docker/index.mdx b/tutorials/deploy-phpmyadmin-with-docker/index.mdx index 5cb474a0be..c822952b7d 100644 --- a/tutorials/deploy-phpmyadmin-with-docker/index.mdx +++ b/tutorials/deploy-phpmyadmin-with-docker/index.mdx @@ -22,8 +22,8 @@ In this tutorial, you learn how to deploy the tool on an [Instance](https://www. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A MySQL database ## Creating a Docker Instance @@ -40,7 +40,7 @@ In this tutorial, you learn how to deploy the tool on an [Instance](https://www. ## Deploying phpMyAdmin -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/): +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/): ```bash ssh root@ ``` @@ -57,7 +57,7 @@ In this tutorial, you learn how to deploy the tool on an [Instance](https://www. * Replace `$DB_PORT` with the port your MySQL server is listening on. - If you are using a [Database for MySQL](/managed-databases/postgresql-and-mysql/quickstart/) you can find the connection details on the Database information page: + If you are using a [Database for MySQL](/managed-databases-for-postgresql-and-mysql/quickstart/) you can find the connection details on the Database information page: diff --git a/tutorials/deploy-remote-desktop-ubuntu-2204/index.mdx b/tutorials/deploy-remote-desktop-ubuntu-2204/index.mdx index 33b60882f5..c6d44ff57a 100644 --- a/tutorials/deploy-remote-desktop-ubuntu-2204/index.mdx +++ b/tutorials/deploy-remote-desktop-ubuntu-2204/index.mdx @@ -32,9 +32,9 @@ This tutorial guides you through deploying a remote desktop on an Instance runni - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) - `sudo` privileges or access to the root user ## Preparing the remote machine diff --git a/tutorials/deploy-saas-application/index.mdx b/tutorials/deploy-saas-application/index.mdx index ccd4844d05..0bad69701e 100644 --- a/tutorials/deploy-saas-application/index.mdx +++ b/tutorials/deploy-saas-application/index.mdx @@ -28,18 +28,18 @@ You will learn how to store environment variables with Kubernetes secrets and us - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - A SaaS application using [Django Template](https://docs.djangoproject.com/en/4.0/topics/templates/). **Note**: you may still follow this tutorial if you have used another technology for your SaaS application, but you need to adapt the Django settings used throughout this tutorial -- A private [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- A [Scaleway Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) -- A private [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) -- Installed [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your local machine +- A private [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- A [Scaleway Database](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) +- A private [Container Registry namespace](/container-registry/how-to/create-namespace/) +- Installed [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your local machine - Installed [Docker](https://www.docker.com/) on your local machine ## Setting up Object Storage for your static files -In all applications, you have to define settings, usually based on environment variables, so that you can adapt the behavior of your application depending on their values. Having used Django to create your SaaS application, the settings you need can be found in a file called `settings.py`. In the following steps, we will modify `settings.py` to connect our private Object Storage bucket to our application. As noted in the requirements for this tutorial, you should have already [created a private Object Storage bucket](/storage/object/how-to/create-a-bucket/) before continuing. +In all applications, you have to define settings, usually based on environment variables, so that you can adapt the behavior of your application depending on their values. Having used Django to create your SaaS application, the settings you need can be found in a file called `settings.py`. In the following steps, we will modify `settings.py` to connect our private Object Storage bucket to our application. As noted in the requirements for this tutorial, you should have already [created a private Object Storage bucket](/object-storage/how-to/create-a-bucket/) before continuing. 1. Take a look at your Django application's `settings.py` file. Natively, Django does not manage the Amazon S3 protocol for storing static files, and it will provide you with a basic configuration at the end of this file: ``` @@ -88,8 +88,8 @@ In all applications, you have to define settings, usually based on environment v 'storages', ``` 5. Now we can take a look at the variables we added in step 2. Since there are so many variable imbrications it may seem a little overwhelming. However, once the setup is complete you won't need to worry about them anymore: - - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` are the [access key and secret key for your Scaleway account](/identity-and-access-management/iam/how-to/create-api-keys/) - - `AWS_STORAGE_BUCKET_NAME` is the name you gave your [Object Storage bucket](/storage/object/how-to/create-a-bucket/), e.g. `my_awesome_bucket` + - `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY` are the [access key and secret key for your Scaleway account](/iam/how-to/create-api-keys/) + - `AWS_STORAGE_BUCKET_NAME` is the name you gave your [Object Storage bucket](/object-storage/how-to/create-a-bucket/), e.g. `my_awesome_bucket` - `AWS_S3_REGION_NAME` is the region/zone of your Object Storage Bucket - `AWS_S3_HOST` and `AWS_S3_ENDPOINT_URL` are the URLs needed to access your Object Storage bucket. They are composed of the previously defined variables. - `AWS_LOCATION` is the folder that will be created in our Object Storage bucket for our static files @@ -126,7 +126,7 @@ Your Object Storage bucket is now all set, and your production environment knows ## Setting up Scaleway Database -We now need to configure our settings for our Scaleway Database. As noted in the requirements for this tutorial, you should already have [created a Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) before continuing. These come in various types, but for this tutorial we use a PostgreSQL database, which does not require much configuration. +We now need to configure our settings for our Scaleway Database. As noted in the requirements for this tutorial, you should already have [created a Database](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) before continuing. These come in various types, but for this tutorial we use a PostgreSQL database, which does not require much configuration. 1. Add the `psycopg2` package (or the equivalent for your chosen database type) to your Python requirements. 2. Back in your `settings.py` file, change the default database engine that Django will be using: @@ -160,7 +160,7 @@ We now need to configure our settings for our Scaleway Database. As noted in the ## Setting up Container Registry credentials -As noted in the requirements for this tutorial, you should already have [created a private Scaleway Container Registry namespace](/containers/container-registry/how-to/create-namespace/). For this tutorial, we use a namespace called `my_registry_namespace`. +As noted in the requirements for this tutorial, you should already have [created a private Scaleway Container Registry namespace](/container-registry/how-to/create-namespace/). For this tutorial, we use a namespace called `my_registry_namespace`. 1. Log into your Container Registry with docker. You can do this in your terminal by using the following command, as you already set up your `SECRET_ACCESS_KEY` environment variable in an earlier step. Just make sure to use your correct username, and namespace region (in this case `nl-ams`): ``` @@ -309,7 +309,7 @@ That's it! Your SaaS application is now deployed. If you want to go further by exposing your application outside the cluster, take a look at these tutorials: - [Setting up Traefik v2 and cert-manager on Kapsule](/tutorials/traefik-v2-cert-manager/) -- [Using a Load Balancer to expose your Kubernetes Kapsule ingress controller service](/containers/kubernetes/reference-content/lb-ingress-controller/) +- [Using a Load Balancer to expose your Kubernetes Kapsule ingress controller service](/kubernetes/reference-content/lb-ingress-controller/) By following them, you will learn how to: diff --git a/tutorials/deploy-static-website-with-hugo-and-github-runners-to-object-storage/index.mdx b/tutorials/deploy-static-website-with-hugo-and-github-runners-to-object-storage/index.mdx index 36f9e965a2..188db59bbe 100644 --- a/tutorials/deploy-static-website-with-hugo-and-github-runners-to-object-storage/index.mdx +++ b/tutorials/deploy-static-website-with-hugo-and-github-runners-to-object-storage/index.mdx @@ -20,8 +20,8 @@ This tutorial will guide you through the process of installing Hugo on your loca - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An Object Storage bucket with the [bucket website feature](/storage/object/how-to/use-bucket-website/) enabled +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An Object Storage bucket with the [bucket website feature](/object-storage/how-to/use-bucket-website/) enabled - A [GitHub](https://github.com/) account and an [empty repository](https://docs.github.com/en/get-started/quickstart/create-a-repo) for your Project - Installed `git` on your local computer diff --git a/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx b/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx index e3a80666ea..5ca441aa87 100644 --- a/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx +++ b/tutorials/deploy-ubuntu-20-04-instance-scaleway-elements/index.mdx @@ -22,9 +22,9 @@ In this tutorial, you will learn how to deploy an Instance with Ubuntu 20.04 LTS - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Basic knowledge of [Linux commands](/dedibox/dedicated-servers/reference-content/basic-linux-commands/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Basic knowledge of [Linux commands](/dedicated-servers/reference-content/basic-linux-commands/) ## Deploying your Ubuntu Linux Instance from the Scaleway console @@ -41,7 +41,7 @@ In this tutorial, you will learn how to deploy an Instance with Ubuntu 20.04 LTS * For the ease of this tutorial, leave the default storage options in place. * Enter a name and optional tags * Tags can help to organize your Instances - * Check your [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) displays in the list of keys authorized to access the Instance. + * Check your [SSH key](/organizations-and-projects/how-to/create-ssh-key/) displays in the list of keys authorized to access the Instance. * Click **Create Instance** to create the Instance. Once your Instance is ready, it displays in the list of your Instances. @@ -84,7 +84,7 @@ apt install packagename ``` - For more information about how to use the APT package manager, run the following command: `apt help`, or refer to our documentation on [how to manage packages](/dedibox/dedicated-servers/how-to/manage-packages/). + For more information about how to use the APT package manager, run the following command: `apt help`, or refer to our documentation on [how to manage packages](/dedicated-servers/how-to/manage-packages/). ## Adding regular users on Ubuntu @@ -106,5 +106,5 @@ As previously mentioned, we do not recommend always connecting to your Instance nano ~/.ssh/authorized_keys ``` - You can generate your SSH key pair on [Linux or macOS](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-osx-and-linux) directly from a terminal. On computers running [Windows](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-windows) you can use PuTTYgen to generate your key pair. + You can generate your SSH key pair on [Linux or macOS](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-osx-and-linux) directly from a terminal. On computers running [Windows](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-windows) you can use PuTTYgen to generate your key pair. \ No newline at end of file diff --git a/tutorials/deploy-ubuntu-22-04-instance/index.mdx b/tutorials/deploy-ubuntu-22-04-instance/index.mdx index 2182e91822..b26d8235b4 100644 --- a/tutorials/deploy-ubuntu-22-04-instance/index.mdx +++ b/tutorials/deploy-ubuntu-22-04-instance/index.mdx @@ -22,9 +22,9 @@ In this tutorial, you learn how to deploy an Instance with Ubuntu 22.04 LTS (Jam - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Basic knowledge of [Linux commands](/dedibox/dedicated-servers/reference-content/basic-linux-commands/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Basic knowledge of [Linux commands](/dedicated-servers/reference-content/basic-linux-commands/) ## Deploying your Ubuntu Linux Instance from the Scaleway console @@ -40,7 +40,7 @@ In this tutorial, you learn how to deploy an Instance with Ubuntu 22.04 LTS (Jam * For the ease of this tutorial, leave the default storage options in place. * Enter a name and optional tags * Tags can help to organize your Instances - * Check your [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) displays in the list of keys authorized to access the Instance + * Check your [SSH key](/organizations-and-projects/how-to/create-ssh-key/) displays in the list of keys authorized to access the Instance * Click **Create Instance** to create the Instance. Once your Instance is ready, it displays in the list of your Instances. @@ -84,7 +84,7 @@ apt install packagename ``` - For more information about how to use the APT package manager, run the following command: `apt help`, or refer to our documentation on [how to manage packages](/dedibox/dedicated-servers/how-to/manage-packages/). + For more information about how to use the APT package manager, run the following command: `apt help`, or refer to our documentation on [how to manage packages](/dedicated-servers/how-to/manage-packages/). ## Adding regular users on Ubuntu @@ -106,5 +106,5 @@ As previously mentioned, we do not recommend always connecting to your Instance nano ~/.ssh/authorized_keys ``` - You can generate your SSH key pair on [Linux or macOS](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-osx-and-linux) directly from a terminal. On computers running [Windows](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-windows) you can use PuTTYgen to generate your key pair. + You can generate your SSH key pair on [Linux or macOS](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-osx-and-linux) directly from a terminal. On computers running [Windows](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ssh-key-pair-on-windows) you can use PuTTYgen to generate your key pair. \ No newline at end of file diff --git a/tutorials/deploy-umami-on-serverless-containers/index.mdx b/tutorials/deploy-umami-on-serverless-containers/index.mdx index 29e6ead2cb..e81516fe54 100644 --- a/tutorials/deploy-umami-on-serverless-containers/index.mdx +++ b/tutorials/deploy-umami-on-serverless-containers/index.mdx @@ -21,16 +21,16 @@ Umami is a simple, easy-to-use, self-hosted web analytics solution. It provides - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Container Registry](/containers/container-registry/quickstart/) -- A [Database for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- A [Container Registry](/container-registry/quickstart/) +- A [Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) - Installed [Docker](/tutorials/install-docker-ubuntu-bionic/) on your local computer ## Preparating the database -1. Create a [database user](/managed-databases/postgresql-and-mysql/how-to/add-users/) and [grant permissions](/managed-databases/postgresql-and-mysql/how-to/manage-permissions/) to the PostgreSQL database you want to use for Umami. +1. Create a [database user](/managed-databases-for-postgresql-and-mysql/how-to/add-users/) and [grant permissions](/managed-databases-for-postgresql-and-mysql/how-to/manage-permissions/) to the PostgreSQL database you want to use for Umami. 2. Clone the Umami project locally and enter the project's directory: ``` git clone https://github.com/mikecao/umami.git diff --git a/tutorials/deploy-wordpress-from-application-library/index.mdx b/tutorials/deploy-wordpress-from-application-library/index.mdx index 3fca1e71d6..4757588eb8 100644 --- a/tutorials/deploy-wordpress-from-application-library/index.mdx +++ b/tutorials/deploy-wordpress-from-application-library/index.mdx @@ -15,16 +15,16 @@ dates: WordPress is a well-known CMS (**C**ontent **M**anagement **S**ystem) allowing you to create evolving websites. -This tutorial teaches you how to install WordPress on a Scaleway Kubernetes Kapsule or Kosmos cluster by using the [Application Library in the Easy-Deploy feature](/containers/kubernetes/how-to/enable-easy-deploy/). +This tutorial teaches you how to install WordPress on a Scaleway Kubernetes Kapsule or Kosmos cluster by using the [Application Library in the Easy-Deploy feature](/kubernetes/how-to/enable-easy-deploy/). You can perform most of these steps directly from the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A Scaleway [Kubernetes Kapsule or Kosmos cluster](/containers/kubernetes/how-to/create-cluster/) -- Installed [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your local computer +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A Scaleway [Kubernetes Kapsule or Kosmos cluster](/kubernetes/how-to/create-cluster/) +- Installed [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your local computer ## Creating a Kubernetes Kapsule cluster and deploying WordPress diff --git a/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx b/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx index 04af056426..66dc09118d 100644 --- a/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx +++ b/tutorials/deploy-wordpress-managed-database-mysql8/index.mdx @@ -23,9 +23,9 @@ With its customizable themes and extensive plugin ecosystem, WordPress provides - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04 LTS) or Focal Fossa (20.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04 LTS) or Focal Fossa (20.04 LTS) - A [Database](https://www.scaleway.com/en/database/) for MySQL v8 ## Preparing the managed database @@ -53,7 +53,7 @@ With its customizable themes and extensive plugin ecosystem, WordPress provides To host WordPress on our Instance, we need to install the required software on it. In this tutorial, we will use the Apache web server with PHP 7.4 to host our blog. -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). ``` ssh root@your_instance_ip ``` diff --git a/tutorials/deploying-a-documentation-website-with-docusaurus-on-scaleway/index.mdx b/tutorials/deploying-a-documentation-website-with-docusaurus-on-scaleway/index.mdx index 3adcec84f0..30bed38625 100644 --- a/tutorials/deploying-a-documentation-website-with-docusaurus-on-scaleway/index.mdx +++ b/tutorials/deploying-a-documentation-website-with-docusaurus-on-scaleway/index.mdx @@ -20,8 +20,8 @@ It builds a single-page application with fast client-side navigation, leveraging - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) with the [bucket website feature](/storage/object/how-to/use-bucket-website/) enabled +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) with the [bucket website feature](/object-storage/how-to/use-bucket-website/) enabled - A [GitHub](https://github.com/) account and an [empty repository](https://docs.github.com/en/get-started/quickstart/create-a-repo) for your Project - A local development environment with [Node.js](https://nodejs.org/en/download/) (version 16.14 or above) and `git` installed @@ -93,7 +93,7 @@ Docusaurus is available for most operating systems. In this tutorial, we describ ### Deploying to Scaleway Object Storage - You must configure an Object Storage bucket with the [bucket website feature](/storage/object/how-to/use-bucket-website/) enabled before you continue. + You must configure an Object Storage bucket with the [bucket website feature](/object-storage/how-to/use-bucket-website/) enabled before you continue. 1. Open a web browser and go to your project's repository on [GitHub.com](http://github.com). diff --git a/tutorials/deploying-qdrant-vectordb-kubernetes/index.mdx b/tutorials/deploying-qdrant-vectordb-kubernetes/index.mdx index 1495b57a7f..946bce0870 100644 --- a/tutorials/deploying-qdrant-vectordb-kubernetes/index.mdx +++ b/tutorials/deploying-qdrant-vectordb-kubernetes/index.mdx @@ -30,7 +30,7 @@ Key benefits of running Qdrant Hybrid Cloud on Scaleway include: - A Scaleway account logged into the [console](https://console.scaleway.com) - A Qdrant Hybrid Cloud account logged into the [management console](https://cloud.qdrant.io/) -- A [Kubernetes Kapsule](/containers/kubernetes/quickstart/) cluster +- A [Kubernetes Kapsule](/kubernetes/quickstart/) cluster ## Deploying Qdrant Hybrid Cloud on Scaleway Kubernetes Kapsule diff --git a/tutorials/dhclient-dedibox/index.mdx b/tutorials/dhclient-dedibox/index.mdx index 58254b6d91..8b06ffa778 100644 --- a/tutorials/dhclient-dedibox/index.mdx +++ b/tutorials/dhclient-dedibox/index.mdx @@ -22,11 +22,11 @@ categories: - A Dedibox account logged into the [console](https://console.online.net) -- A [Dedibox dedicated server](/dedibox/dedicated-servers/how-to/order-a-server/) -- Requested a [/48 IPv6 prefix](/dedibox-network/ipv6/how-to/request-prefix/) +- A [Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/) +- Requested a [/48 IPv6 prefix](/dedibox-ipv6/how-to/request-prefix/) - For servers supporting [IPv6 SLAAC](/dedibox-network/ipv6/how-to/enable-ipv6-slaac/), it is important to enable SLAAC to ensure the proper functioning of DHCPv6. If SLAAC is disabled, the server won't be able to learn its IPv6 default route. + For servers supporting [IPv6 SLAAC](/dedibox-ipv6/how-to/enable-ipv6-slaac/), it is important to enable SLAAC to ensure the proper functioning of DHCPv6. If SLAAC is disabled, the server won't be able to learn its IPv6 default route. ## How to set the DUID of your subnet diff --git a/tutorials/dhcpcd-dedibox/index.mdx b/tutorials/dhcpcd-dedibox/index.mdx index 9200c2ea2f..ec33e7c1de 100644 --- a/tutorials/dhcpcd-dedibox/index.mdx +++ b/tutorials/dhcpcd-dedibox/index.mdx @@ -51,7 +51,7 @@ In this tutorial, you will learn how to configure your IPv6 subnet with DHCPCD o - We assume you have already generated an [IPv6 prefix and its associated DUID](/dedibox-network/ipv6/how-to/request-prefix/). + We assume you have already generated an [IPv6 prefix and its associated DUID](/dedibox-ipv6/how-to/request-prefix/). 1. Open the DHCPCD configuration file located at `/etc/dhcpcd.conf` in a text editor of your choice and edit it as follows: @@ -160,4 +160,4 @@ In this tutorial, you will learn how to configure your IPv6 subnet with DHCPCD o Mar 15 15:30:16 sd-160847 dhcpcd[22368]: enp1s0: executing `/lib/dhcpcd/dhcpcd-run-hooks' ROUTERADVERT ``` -Your server is now ready to communicate with IPv6. For more information about IPv6 at Scaleway Dedibox, refer to our [dedicated documentation](/dedibox-network/ipv6/quickstart/). \ No newline at end of file +Your server is now ready to communicate with IPv6. For more information about IPv6 at Scaleway Dedibox, refer to our [dedicated documentation](/dedibox-ipv6/quickstart/). \ No newline at end of file diff --git a/tutorials/discourse-forum/index.mdx b/tutorials/discourse-forum/index.mdx index 56425a36ea..5e36360327 100644 --- a/tutorials/discourse-forum/index.mdx +++ b/tutorials/discourse-forum/index.mdx @@ -25,16 +25,16 @@ For those looking to set up Discourse, using the official [Docker image](https:/ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) - A domain name pointed to your Instance - Enabled the [SMTP ports](https://www.scaleway.com/en/faq/why-can-i-not-send-any-email/) - Configured a [mail server](/tutorials/setup-postfix-ubuntu-bionic/) or have an SMTP account available ## Installing Discourse -1. Log into your instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Log into your instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the instance to the latest version available in Ubuntu's Repositories: ``` apt update && apt ugprade -y diff --git a/tutorials/django-ubuntu-focal-fossa/index.mdx b/tutorials/django-ubuntu-focal-fossa/index.mdx index f56ef34e48..4397785949 100644 --- a/tutorials/django-ubuntu-focal-fossa/index.mdx +++ b/tutorials/django-ubuntu-focal-fossa/index.mdx @@ -26,15 +26,15 @@ There are many different ways to install Django on Ubuntu: In this tutorial, we install Django using `pip` in a virtual environment, as it is the most practical and most flexible way to install without affecting the larger system, along with other per-project customizations and packages. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 20.04 LTS (Focal Fossa) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 20.04 LTS (Focal Fossa) or later - `sudo` privileges or access to the root user ## Installing Django on Ubuntu with pip in a virtual environment diff --git a/tutorials/docker-instantapp/index.mdx b/tutorials/docker-instantapp/index.mdx index 77e14c8209..871296868c 100644 --- a/tutorials/docker-instantapp/index.mdx +++ b/tutorials/docker-instantapp/index.mdx @@ -13,18 +13,18 @@ dates: posted: 2019-05-13 --- -Docker is an open-source containerization platform. Docker allows developers to package their applications into containers, using OS-level virtualization. This page shows you how to create an Instance with Docker preinstalled using the Docker [InstantApp](/compute/instances/concepts/#instantapp) based on Ubuntu 22.04, and then how to start using Docker for your containerization projects. By default, this image supports [routed IPs](/compute/instances/api-cli/using-routed-ips/). +Docker is an open-source containerization platform. Docker allows developers to package their applications into containers, using OS-level virtualization. This page shows you how to create an Instance with Docker preinstalled using the Docker [InstantApp](/instances/concepts/#instantapp) based on Ubuntu 22.04, and then how to start using Docker for your containerization projects. By default, this image supports [routed IPs](/instances/api-cli/using-routed-ips/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Creating and connecting to your Docker InstantApp Instance -1. Create the Instance by [following our dedicated instructions](/compute/instances/how-to/create-an-instance/). When choosing your **Image**, click the **InstantApps** tab and select the **Docker** InstantApp. -2. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. Create the Instance by [following our dedicated instructions](/instances/how-to/create-an-instance/). When choosing your **Image**, click the **InstantApps** tab and select the **Docker** InstantApp. +2. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). ## Building your first container @@ -157,7 +157,7 @@ The application displays the internal hostname of the container and retrieves th Docker makes it easy to ship images to a registry to share with others. -In this example, the public Docker registry is used ("Docker Hub"), but it is also possible to set up a [private registry](https://docs.docker.com/registry/deploying/) to distribute the image on your infrastructure, or to use the [Scaleway Container Registry](/containers/container-registry/quickstart/). +In this example, the public Docker registry is used ("Docker Hub"), but it is also possible to set up a [private registry](https://docs.docker.com/registry/deploying/) to distribute the image on your infrastructure, or to use the [Scaleway Container Registry](/container-registry/quickstart/). You need a Docker account for this part of the tutorial. If you do not have one, you can create an account at [hub.docker.com](https://hub.docker.com). diff --git a/tutorials/easydeploy-argocd/index.mdx b/tutorials/easydeploy-argocd/index.mdx index e2653dbebc..82d184d659 100644 --- a/tutorials/easydeploy-argocd/index.mdx +++ b/tutorials/easydeploy-argocd/index.mdx @@ -22,9 +22,9 @@ This makes it ideal for managing complex Kubernetes environments with precision - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster ## Deploying the Argo CD application using Easy Deploy @@ -49,7 +49,7 @@ For example, your YAML configuration might create Block Storage volumes or Load ## Retrieving the Argo CD admin password -1. Access the [Kubernetes Dashboard](/containers/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. +1. Access the [Kubernetes Dashboard](/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. 2. Click `argocd-initial-admin-secret` to display the application metadata information. 3. Click the "eye" icon next to `password` to reveal the Argo CD admin password. Copy the password. diff --git a/tutorials/easydeploy-gitlab-runner/index.mdx b/tutorials/easydeploy-gitlab-runner/index.mdx index 438a5897aa..9feaee12ea 100644 --- a/tutorials/easydeploy-gitlab-runner/index.mdx +++ b/tutorials/easydeploy-gitlab-runner/index.mdx @@ -19,9 +19,9 @@ This setup enables you to optimize resource utilization, reduce overhead, and en - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster - A GitLab repository ## Deploying the GitLab Runner application using Easy Deploy diff --git a/tutorials/easydeploy-gitlab-server/index.mdx b/tutorials/easydeploy-gitlab-server/index.mdx index c15a291459..f762f46fa3 100644 --- a/tutorials/easydeploy-gitlab-server/index.mdx +++ b/tutorials/easydeploy-gitlab-server/index.mdx @@ -19,9 +19,9 @@ It outlines the prerequisites, step-by-step deployment instructions, and post-de - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster - A domain name and access to its DNS zone ## Deploying the GitLab Server application using Easy Deploy @@ -54,7 +54,7 @@ It outlines the prerequisites, step-by-step deployment instructions, and post-de ## Retrieving the GitLab Server root password -1. Access the [Kubernetes Dashboard](/containers/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. +1. Access the [Kubernetes Dashboard](/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. 2. Click `gitlab-server-gitlab-initial-root-password` to display the application metadata. 3. Click the eye icon next to `password` to reveal and copy the GitLab server root password. diff --git a/tutorials/easydeploy-grafana/index.mdx b/tutorials/easydeploy-grafana/index.mdx index 2f652d2d35..e1976eed89 100644 --- a/tutorials/easydeploy-grafana/index.mdx +++ b/tutorials/easydeploy-grafana/index.mdx @@ -20,9 +20,9 @@ Grafana's flexibility and ease of use make it a popular choice for managing appl - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster ## Deploying the Grafana application using Easy Deploy @@ -46,7 +46,7 @@ For example, your YAML configuration might create Block Storage volumes or Load ## Retrieving the Grafana admin password -1. Access the [Kubernetes Dashboard](/containers/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. +1. Access the [Kubernetes Dashboard](/kubernetes/how-to/access-kubernetes-dashboard/) of your cluster and navigate to **Secrets** under the **Config and Storage** section. 2. Select the name of your Grafana application to display its data. 3. Click the eye icon next to **admin-password** to reveal the Grafana admin password. Copy the password. diff --git a/tutorials/easydeploy-vault/index.mdx b/tutorials/easydeploy-vault/index.mdx index f8baa60b1c..20490a14b3 100644 --- a/tutorials/easydeploy-vault/index.mdx +++ b/tutorials/easydeploy-vault/index.mdx @@ -20,9 +20,9 @@ Vault is used to secure, store and protect secrets and other sensitive data usin - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a Scaleway Kubernetes [Kapsule](/containers/kubernetes/how-to/create-cluster/) or [Kosmos](/containers/kubernetes/how-to/create-kosmos-cluster/) cluster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a Scaleway Kubernetes [Kapsule](/kubernetes/how-to/create-cluster/) or [Kosmos](/kubernetes/how-to/create-kosmos-cluster/) cluster ## Deploying the Vault application using Easy Deploy diff --git a/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx b/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx index cd002ed0f1..a29e43f916 100644 --- a/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx +++ b/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx @@ -19,10 +19,10 @@ By default, Cilium is selected as the CNI when creating a cluster. We will confi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A functional [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule) cluster running **version 1.31**.- +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A functional [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule) cluster running **version 1.31**.- - `kubectl` installed and configured for your cluster. -- Cilium is selected as the [CNI](/containers/kubernetes/concepts/#container-network-interface-cni) in your cluster (default in Kapsule). +- Cilium is selected as the [CNI](/kubernetes/concepts/#container-network-interface-cni) in your cluster (default in Kapsule). ## Creating a CiliumNodeConfig resource for encryption diff --git a/tutorials/encode-videos-using-serverless-jobs/index.mdx b/tutorials/encode-videos-using-serverless-jobs/index.mdx index 043bfc64be..01e14d824f 100644 --- a/tutorials/encode-videos-using-serverless-jobs/index.mdx +++ b/tutorials/encode-videos-using-serverless-jobs/index.mdx @@ -20,9 +20,9 @@ This tutorial demonstrates the process of encoding videos retrieved from Object - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [Docker engine](https://docs.docker.com/engine/install/) @@ -71,7 +71,7 @@ The initial step involves defining a Docker image for interacting with the Objec This Dockerfile uses `linuxserver/ffmpeg` as a base image bundled with FFMPEG along with a variety of encoding codecs and installs [MinIO](https://min.io/) as a command-line client to copy files over Object Storage. -3. Build and [push the image](/containers/container-registry/how-to/push-images/) to your Container Registry: +3. Build and [push the image](/container-registry/how-to/push-images/) to your Container Registry: ```bash docker build . -t docker push @@ -118,7 +118,7 @@ Ensure that your Object Storage bucket contains at least one video that can be e 4. Click **Run job**. -The progress and details for your Job run can be viewed in the **Job runs** section of the job **Overview** tab in the [Scaleway console](https://console.scaleway.com). You can also access the detailed logs of your job in [Cockpit](/observability/cockpit/quickstart/). +The progress and details for your Job run can be viewed in the **Job runs** section of the job **Overview** tab in the [Scaleway console](https://console.scaleway.com). You can also access the detailed logs of your job in [Cockpit](/cockpit/quickstart/). Once the run status is **Succeeded**, the encoded video can be found in your Object Storage bucket under the folder and file name specified above in the environment variables. diff --git a/tutorials/encrypt-s3-data-rclone/index.mdx b/tutorials/encrypt-s3-data-rclone/index.mdx index 5b79243e56..43ddb3f13a 100644 --- a/tutorials/encrypt-s3-data-rclone/index.mdx +++ b/tutorials/encrypt-s3-data-rclone/index.mdx @@ -24,8 +24,8 @@ In this tutorial, we will explore the capabilities of the **Rclone crypt** modul - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Installing Rclone @@ -68,7 +68,7 @@ brew install rclone ## Configuring an Object Storage remote endpoint - You need to have your [API key](/identity-and-access-management/iam/how-to/create-api-keys/) ready for the `rclone` configuration. + You need to have your [API key](/iam/how-to/create-api-keys/) ready for the `rclone` configuration. Before encrypting your data, create a new remote Object Storage endpoint in Rclone using the `rclone config` command: @@ -305,7 +305,7 @@ For example, if you want to upload your personal photo album and want to protect rclone copy --progress --s3-chunk-size=20M /home/myuser/MyPhotoalbum secret:/encrypted/MyPhotoalbum ``` -It will transfer the directory `/home/myuser/MyPhotoalbum` to the endpoint `secret` and upload the data in the sub-directory `/encrypted/MyPhotoalbum`. The flags `--progress` display the status of the file transfer and `--s3-chunk-size=20` sets the maximum size for each part of a [multipart upload](/storage/object/api-cli/multipart-uploads/) to 20 MB. +It will transfer the directory `/home/myuser/MyPhotoalbum` to the endpoint `secret` and upload the data in the sub-directory `/encrypted/MyPhotoalbum`. The flags `--progress` display the status of the file transfer and `--s3-chunk-size=20` sets the maximum size for each part of a [multipart upload](/object-storage/api-cli/multipart-uploads/) to 20 MB. You can check if the data has been encrypted when running a `ls` command on the `scaleway` endpoint. It will return a list like the following: diff --git a/tutorials/encrypt-volumes/index.mdx b/tutorials/encrypt-volumes/index.mdx index c0ecc638ee..c83cab697d 100644 --- a/tutorials/encrypt-volumes/index.mdx +++ b/tutorials/encrypt-volumes/index.mdx @@ -23,15 +23,15 @@ This tutorial will walk you through the process of encrypting an additional volu - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) -- A [Block Storage volume connected to the Instance](/storage/block/how-to/attach-a-volume/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) +- A [Block Storage volume connected to the Instance](/block-storage/how-to/attach-a-volume/) - `sudo` privileges or access to the root user ## Installing Cryptsetup -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). 2. Update the apt sources and the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/erpnext-13/index.mdx b/tutorials/erpnext-13/index.mdx index a215df26bb..bc8b2304f3 100644 --- a/tutorials/erpnext-13/index.mdx +++ b/tutorials/erpnext-13/index.mdx @@ -23,12 +23,12 @@ This tutorial will show you how to deploy ERPNext 13 on a Scaleway machine runni - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - One of the following remote machines running Ubuntu Focal Fossa (20.04 LTS): - - An [Instance](/compute/instances/how-to/create-an-instance/) - - An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) - - A [Dedibox dedicated server](/dedibox/dedicated-servers/how-to/order-a-server/) + - An [Instance](/instances/how-to/create-an-instance/) + - An [Elastic Metal server](/elastic-metal/how-to/create-server/) + - A [Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/) - `sudo` privileges or access to the root user - Configured an A-record pointing to your server's IP address diff --git a/tutorials/erpnext/index.mdx b/tutorials/erpnext/index.mdx index f95f4d15ca..c6284a02c5 100644 --- a/tutorials/erpnext/index.mdx +++ b/tutorials/erpnext/index.mdx @@ -25,8 +25,8 @@ In this tutorial, you will learn how to install and configure ERPNext 12 on Ubun - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A Scaleway [Dedibox dedicated server](https://www.scaleway.com/en/dedibox/) running on Ubuntu 18.04 (Bionic Beaver) - `sudo` privileges or access to the root user - Configured an A-record pointing to your server's IP address diff --git a/tutorials/first-steps-linux-command-line/index.mdx b/tutorials/first-steps-linux-command-line/index.mdx index 884374f998..611f6e8810 100644 --- a/tutorials/first-steps-linux-command-line/index.mdx +++ b/tutorials/first-steps-linux-command-line/index.mdx @@ -21,7 +21,7 @@ You may be used to using a **G**raphical **U**ser **I**nterface (**GUI**) for yo -However, when you provision a virtual or remote machine such as a [Scaleway Instance](/compute/instances/how-to/create-an-instance/), [Dedibox](/dedibox/dedicated-servers/how-to/order-a-server/), or [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) it is more usual to use the text-based command line, rather than a GUI, to operate the machine. While GUIs are user-friendly, the command line is much more powerful, uses fewer of the machine's resources (leaving more compute power to be used elsewhere), is less laggy, and more efficient. +However, when you provision a virtual or remote machine such as a [Scaleway Instance](/instances/how-to/create-an-instance/), [Dedibox](/dedicated-servers/how-to/order-a-server/), or [Elastic Metal server](/elastic-metal/how-to/create-server/) it is more usual to use the text-based command line, rather than a GUI, to operate the machine. While GUIs are user-friendly, the command line is much more powerful, uses fewer of the machine's resources (leaving more compute power to be used elsewhere), is less laggy, and more efficient. Even if you are using a GUI on your own local machine, you can also choose to use the command line by opening a **terminal** application in your GUI, to start carrying actions via the command line instead of the graphical interface. @@ -37,7 +37,7 @@ If you are just looking for a quick recap and cheatsheet of Linux commands you a -- Provisioned a virtual/remote machine running a Linux OS and [connected to its command line via SSH](/compute/instances/how-to/connect-to-instance/) or you are using a physical machine running a Linux OS or MacOS, and have opened the terminal. +- Provisioned a virtual/remote machine running a Linux OS and [connected to its command line via SSH](/instances/how-to/connect-to-instance/) or you are using a physical machine running a Linux OS or MacOS, and have opened the terminal. ## The command prompt diff --git a/tutorials/flask/index.mdx b/tutorials/flask/index.mdx index eb277f3af5..66ef558209 100644 --- a/tutorials/flask/index.mdx +++ b/tutorials/flask/index.mdx @@ -17,13 +17,13 @@ Flask is a web application framework written in Python. Flask is easy to get sta - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (20.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (20.04 LTS) ## Setting up the environment -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) using SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) using SSH. 2. Update the APT package cache and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/focalboard-project-management/index.mdx b/tutorials/focalboard-project-management/index.mdx index 2d44240971..60e5f99616 100644 --- a/tutorials/focalboard-project-management/index.mdx +++ b/tutorials/focalboard-project-management/index.mdx @@ -21,15 +21,15 @@ Focalboard boasts a comprehensive array of functionalities as one of its standou In short, if you are seeking a robust and budget-friendly project management solution, Focalboard unquestionably merits exploration. Its impressive feature set coupled with a commitment to privacy positions it as a tool capable of fostering team organization and goal attainment. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/production-optimized/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/production-optimized/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) - A subdomain pointed to the IP address of your Instance (A-record) ## Installation of the required software diff --git a/tutorials/foreman-puppet/index.mdx b/tutorials/foreman-puppet/index.mdx index 279147459b..45b6b8f2aa 100644 --- a/tutorials/foreman-puppet/index.mdx +++ b/tutorials/foreman-puppet/index.mdx @@ -22,9 +22,9 @@ This tutorial assumes that Foreman is being installed on a fresh Instance, which - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) or later - Root access to all the servers you want to manage - A reachable port 8140 on the Puppet primary Instance - A working Puppet installation to perform the configuration management of hosts diff --git a/tutorials/get-started-containers-docker/index.mdx b/tutorials/get-started-containers-docker/index.mdx index e3e3dd923d..f4c3695b39 100644 --- a/tutorials/get-started-containers-docker/index.mdx +++ b/tutorials/get-started-containers-docker/index.mdx @@ -13,13 +13,13 @@ dates: posted: 2022-04-07 --- -This is the first in a series of tutorials accompanying our [video demonstrations on getting started with Kubernetes](https://www.youtube.com/watch?v=zgxcCcKnXR0). In this first tutorial, we focus on one of the fundamental concepts behind Kubernetes: the [container](/serverless/containers/concepts/#container). We use the popular containerization platform [Docker](https://www.docker.com/) to create and deploy a simple containerized "Hello World" application, before moving on to look at a slightly more complex application example. We finish by pushing the container images we have created to the Scaleway [Container Registry](/containers/container-registry/concepts/#container-registry). Future videos and tutorials in this series will show you how to then deploy your containerized application with Kubernetes, specifically with the Scaleway [Kubernetes Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule). +This is the first in a series of tutorials accompanying our [video demonstrations on getting started with Kubernetes](https://www.youtube.com/watch?v=zgxcCcKnXR0). In this first tutorial, we focus on one of the fundamental concepts behind Kubernetes: the [container](/serverless-containers/concepts/#container). We use the popular containerization platform [Docker](https://www.docker.com/) to create and deploy a simple containerized "Hello World" application, before moving on to look at a slightly more complex application example. We finish by pushing the container images we have created to the Scaleway [Container Registry](/container-registry/concepts/#container-registry). Future videos and tutorials in this series will show you how to then deploy your containerized application with Kubernetes, specifically with the Scaleway [Kubernetes Kapsule](/kubernetes/concepts/#kubernetes-kapsule). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Key concepts: containers, Docker and Kubernetes @@ -206,7 +206,7 @@ In this example, we look at a pre-built application called **whoami**, an HTTP s To finish, we push the Docker images we have created to a container registry. Container registries are designed to store container images and make them accessible to those who need them. There are many different container registry platforms, but here we use the [Scaleway Container Registry](https://www.scaleway.com/en/container-registry/). 1. Open a browser and go to the [Scaleway console's Container Registry page](https://console.scaleway.com/registry/namespaces). -2. Follow [these instructions](/containers/container-registry/how-to/create-namespace/) to create a namespace. Make sure that you set your privacy policy to **private**. +2. Follow [these instructions](/container-registry/how-to/create-namespace/) to create a namespace. Make sure that you set your privacy policy to **private**. The following steps should be carried out in the terminal of your local machine: 3. Log in to your Container Registry namespace: @@ -215,7 +215,7 @@ To finish, we push the Docker images we have created to a container registry. Co ``` - Ensure that you replace `` with the address of your own Container Registry namespace (e.g. `rg.fr-par.scw.cloud/mynamespace`) and that you have [created your API key](/identity-and-access-management/iam/how-to/create-api-keys/) and that you have saved the secret part of your API key as an environment variable e.g. with the command `export SCW_SECRET_TOKEN=a4db08b7-5723-4ba9-8c18-f2de493465a2`. + Ensure that you replace `` with the address of your own Container Registry namespace (e.g. `rg.fr-par.scw.cloud/mynamespace`) and that you have [created your API key](/iam/how-to/create-api-keys/) and that you have saved the secret part of your API key as an environment variable e.g. with the command `export SCW_SECRET_TOKEN=a4db08b7-5723-4ba9-8c18-f2de493465a2`. 4. Tag the image you want to push with the address of your Container Registry namespace: ```bash @@ -234,12 +234,12 @@ You have seen how to containerize an application by creating a Dockerfile, using ## Useful links - [Video tutorial: Getting started with Kubernetes: Part 1 - Containers & Docker](https://www.youtube.com/watch?v=zgxcCcKnXR0) -- [Kubernetes Concepts](/containers/kubernetes/concepts/) -- [Introduction to Kubernetes](/containers/kubernetes/reference-content/introduction-to-kubernetes/) +- [Kubernetes Concepts](/kubernetes/concepts/) +- [Introduction to Kubernetes](/kubernetes/reference-content/introduction-to-kubernetes/) - [What is a container? [Docker documentation]](https://www.docker.com/resources/what-container) - [What is a container? [VMware video]](https://www.youtube.com/watch?v=EnJ7qX9fkcU&t=185s) - [Containerization Explained [IBM video]](https://www.youtube.com/watch?v=0qotVMX-J5s) - [Understanding Docker & Kubernetes Visually [Aurelie Vache videos, FR]](https://www.youtube.com/c/AurelieVache/videos) - [Official Docker documentation](https://docs.docker.com/get-started/overview/) - [Docker Cheat Sheet](https://docs.docker.com/get-started/docker_cheatsheet.pdf) -- [Scaleway Container Registry documentation](/containers/container-registry/) \ No newline at end of file +- [Scaleway Container Registry documentation](/container-registry/) \ No newline at end of file diff --git a/tutorials/get-started-crossplane-kubernetes/index.mdx b/tutorials/get-started-crossplane-kubernetes/index.mdx index 6f9aeb2026..e1f8809fee 100644 --- a/tutorials/get-started-crossplane-kubernetes/index.mdx +++ b/tutorials/get-started-crossplane-kubernetes/index.mdx @@ -15,14 +15,14 @@ dates: Created by Upbound, [Crossplane](https://www.crossplane.io/) is a Kubernetes-based platform that allows you to manage resources through a unified control plane. `crossplane-provider-scaleway` is a Crossplane provider that helps you manage Scaleway cloud resources in Kubernetes. It is built using [Upjet](https://github.com/upbound/upjet) code generation tools and it exposes managed resources for Scaleway that adhere to Crossplane's eXtensible Resource Model (XRM). As a model, XRM ensures that users can easily and consistently manage cloud resources across different cloud providers. -In this tutorial, you will learn how to install Upbound Universal Crossplane (UXP) into your Kubernetes cluster, configure the provider to authenticate with Scaleway, and create a Scaleway [Kubernetes](/containers/kubernetes/quickstart/) managed resource directly from your cluster. +In this tutorial, you will learn how to install Upbound Universal Crossplane (UXP) into your Kubernetes cluster, configure the provider to authenticate with Scaleway, and create a Scaleway [Kubernetes](/kubernetes/quickstart/) managed resource directly from your cluster. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Kubernetes cluster](/containers/kubernetes/how-to/create-cluster/) and downloaded its [Kubeconfig file](/containers/kubernetes/concepts#kubeconfig) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- A [Kubernetes cluster](/kubernetes/how-to/create-cluster/) and downloaded its [Kubeconfig file](/kubernetes/concepts#kubeconfig) - Installed [curl](https://curl.se/download.html) - Installed [kubectl](https://github.com/kubernetes/kops/blob/master/docs/install.md) on your local computer @@ -116,7 +116,7 @@ Run the following `up uxp install` command to install the latest stable version The provider requires credentials to create and manage Scaleway resources. -1. Run the following command to create a `crossplane-system` [namespace](/containers/container-registry/concepts/#namespace): +1. Run the following command to create a `crossplane-system` [namespace](/container-registry/concepts/#namespace): ``` kubectl create namespace crossplane-system --dry-run=client -o yaml | kubectl apply -f - diff --git a/tutorials/get-started-deploy-kapsule/index.mdx b/tutorials/get-started-deploy-kapsule/index.mdx index 287e6f0ece..85f42e0df6 100644 --- a/tutorials/get-started-deploy-kapsule/index.mdx +++ b/tutorials/get-started-deploy-kapsule/index.mdx @@ -15,7 +15,7 @@ dates: This tutorial accompanies the second [video demonstration](https://www.youtube.com/watch?v=R5CwAq1a0Og) in our series to help users get started with Kubernetes. We walk you through Kubernetes fundamentals for beginners. In this installment, we show you how to deploy a containerized application with the [Scaleway Kubernetes Kapsule](https://www.scaleway.com/en/kubernetes-kapsule/). -First, we review some key Kubernetes terminology (including pools, nodes, and pods) and then demonstrate how to create a Kubernetes Kapsule via the [Scaleway console](https://console.scaleway.com/). Next, we show you how to install [`kubectl`](/containers/kubernetes/concepts/#kubectl) so you can connect to your cluster from the command line of your local machine, and how to create an [image pull secret](/containers/kubernetes/concepts/#image-pull-secret) for your cluster. +First, we review some key Kubernetes terminology (including pools, nodes, and pods) and then demonstrate how to create a Kubernetes Kapsule via the [Scaleway console](https://console.scaleway.com/). Next, we show you how to install [`kubectl`](/kubernetes/concepts/#kubectl) so you can connect to your cluster from the command line of your local machine, and how to create an [image pull secret](/kubernetes/concepts/#image-pull-secret) for your cluster. We then demonstrate how to deploy the containerized application (via the `whoami` image that we created in the [first video/tutorial](/tutorials/get-started-containers-docker/)) to our Kapsule cluster. Finally, we show how to use the Kubernetes NodePort service to expose a port, so we can test that the application is running at its endpoint. @@ -24,8 +24,8 @@ Future videos will cover topics like load balancing and storage for your Kuberne - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Followed the [first tutorial](/tutorials/get-started-containers-docker/) in this series, and pushed the `whoami` image to a Container Registry ## Why do we need Kubernetes? @@ -45,7 +45,7 @@ Before starting the practical steps of this tutorial, we review a few key Kubern Cluster: -* **Node**: A node may be a virtual or physical machine. In the case of Scaleway Kubernetes Kapsule, a node is an [Instance](/compute/instances/concepts/#instance). +* **Node**: A node may be a virtual or physical machine. In the case of Scaleway Kubernetes Kapsule, a node is an [Instance](/instances/concepts/#instance). * **Worker node**: Each worker node runs one or more containerized applications, which are grouped into pods. Each worker node is managed by the control plane and contains the services necessary to run pods. @@ -76,11 +76,11 @@ In both cases, Scaleway walks you through the setup of your cluster and manages ## Creating a Kubernetes Kapsule cluster -The first step in our tutorial is to create a Kubernetes Kapsule cluster. This can be achieved from the Scaleway console. [Follow our dedicated how-to on creating a cluster](/containers/kubernetes/how-to/create-cluster/), making sure to select Kapsule instead of Kosmos. You can leave all other settings at their default values. +The first step in our tutorial is to create a Kubernetes Kapsule cluster. This can be achieved from the Scaleway console. [Follow our dedicated how-to on creating a cluster](/kubernetes/how-to/create-cluster/), making sure to select Kapsule instead of Kosmos. You can leave all other settings at their default values. ## Installing kubectl and connecting to your cluster -The next step is to install `kubectl` on your local machine and configure it to connect to your cluster. To do this, [follow our dedicated how-to on connecting to a cluster with kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/). +The next step is to install `kubectl` on your local machine and configure it to connect to your cluster. To do this, [follow our dedicated how-to on connecting to a cluster with kubectl](/kubernetes/how-to/connect-cluster-kubectl/). ## Create an image pull secret @@ -91,7 +91,7 @@ In our previous tutorial, we saw how to containerize an application and create a kubectl create secret docker-registry registry-secret --docker-server=rg.fr-par.scw.cloud --docker-username=my-namespace --docker-password=$SCW_SECRET_KEY ``` - Make sure you replace `rg.fr-par.scw.cloud` with the endpoint of the container registry where you pushed the `whoami` image [from the first tutorial](/tutorials/get-started-containers-docker/#example-2-a-more-complex-app), and `my-namespace` with the relevant container registry namespace. You should also have [created an API key](/identity-and-access-management/iam/how-to/create-api-keys/) and exported it as an environment variable called `$SCW_SECRET_KEY`. + Make sure you replace `rg.fr-par.scw.cloud` with the endpoint of the container registry where you pushed the `whoami` image [from the first tutorial](/tutorials/get-started-containers-docker/#example-2-a-more-complex-app), and `my-namespace` with the relevant container registry namespace. You should also have [created an API key](/iam/how-to/create-api-keys/) and exported it as an environment variable called `$SCW_SECRET_KEY`. 2. Run the following command to display the generated secret and check that everything went well. ``` kubectl get secret registry-secret --output=yaml @@ -157,8 +157,8 @@ Now that we have created our cluster, connected to it with `kubectl`, and define ## Exposing the service for testing via NodePort (optional) - Kubernetes Kapsule clusters are deployed within a Virtual Private Cloud (VPC) for inherent [controlled isolation](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation). - The cluster automatically configures a [security group](/compute/instances/concepts/#security-group) with a default rule that blocks all incoming traffic. To enable external access to the NodePort service, it is necessary to [configure an inbound route for the service](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#how-can-i-access-my-cluster-via-my-nodes-public-ips-for-specific-use-cases). + Kubernetes Kapsule clusters are deployed within a Virtual Private Cloud (VPC) for inherent [controlled isolation](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation). + The cluster automatically configures a [security group](/instances/concepts/#security-group) with a default rule that blocks all incoming traffic. To enable external access to the NodePort service, it is necessary to [configure an inbound route for the service](/kubernetes/reference-content/secure-cluster-with-private-network/#how-can-i-access-my-cluster-via-my-nodes-public-ips-for-specific-use-cases). Our application is up and running, and we could just stop at this point. However, we can carry on and expose the port it is running on, so we can access the cluster's endpoint and check if the application is printing out its container ID as it should. We will achieve this via NodePort, a Kubernetes service that opens a port on every node of the cluster. Any traffic the cluster receives on this node is forwarded. @@ -197,8 +197,8 @@ You should see that the `whoami` application is printing the ID of the container - [Video tutorial: Getting started with Kubernetes: Part 1 - Containers & Docker](https://www.youtube.com/watch?v=zgxcCcKnXR0) - [Written tutorial: Getting started with Kubernetes: Part 1 - Containers & Docker](/tutorials/get-started-containers-docker/) - [Video tutorial: Getting started with Kubernetes: Part 2 - Deploying an app with Kapsule](https://www.youtube.com/watch?v=R5CwAq1a0Og) -- [Kubernetes Concepts](/containers/kubernetes/concepts/) -- [Introduction to Kubernetes](/containers/kubernetes/reference-content/introduction-to-kubernetes/) +- [Kubernetes Concepts](/kubernetes/concepts/) +- [Introduction to Kubernetes](/kubernetes/reference-content/introduction-to-kubernetes/) - [Kubernetes in 5 minutes](https://www.youtube.com/watch?v=PH-2FfFD2PU) - [Kubernetes Components](https://kubernetes.io/docs/concepts/overview/components/) - [Official Kubernetes documentation](https://kubernetes.io/docs/home/) \ No newline at end of file diff --git a/tutorials/get-started-kubernetes-loadbalancer/index.mdx b/tutorials/get-started-kubernetes-loadbalancer/index.mdx index 1e38f97cc1..6195a0458d 100644 --- a/tutorials/get-started-kubernetes-loadbalancer/index.mdx +++ b/tutorials/get-started-kubernetes-loadbalancer/index.mdx @@ -22,8 +22,8 @@ The next and final video in this series will look at the topic of persistent sto - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Followed the [first](/tutorials/get-started-containers-docker/) and [second](/tutorials/get-started-deploy-kapsule/) tutorials in this series - A Kubernetes Kapsule cluster running with the `whoami` application deployed on it. diff --git a/tutorials/get-started-kubernetes-storage/index.mdx b/tutorials/get-started-kubernetes-storage/index.mdx index c62e6588f2..7e2139c23e 100644 --- a/tutorials/get-started-kubernetes-storage/index.mdx +++ b/tutorials/get-started-kubernetes-storage/index.mdx @@ -22,10 +22,10 @@ Previous videos in this series covered the basics of [containers and Docker](/tu - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A [Kubernetes Kapsule](/containers/kubernetes/how-to/create-cluster/) -- [Kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) configured on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [API key](/iam/how-to/create-api-keys/) +- A [Kubernetes Kapsule](/kubernetes/how-to/create-cluster/) +- [Kubectl](/kubernetes/how-to/connect-cluster-kubectl/) configured on your machine ## Fundamental storage concepts @@ -63,7 +63,7 @@ What kind of applications need to use persistent volumes? To answer this, we mus Cloud providers such as Scaleway provide and default **StorageClasses** for their managed Kubernetes products. StorageClasses define the classes of storage the provider can offer for the cluster. The user can list the StorageClasses available by using the command `kubectl get storageclass`. -Scaleway provides [Block Storage](/storage/block/quickstart/) as its StorageClass, meaning that we offer persistent storage for Kapsule clusters via our Block Storage product. +Scaleway provides [Block Storage](/block-storage/quickstart/) as its StorageClass, meaning that we offer persistent storage for Kapsule clusters via our Block Storage product. Scaleway has upgraded the Block Storage used by our StorageClass, offering better performance. Our previous class was `scw-bss`, which has now been replaced by `sbs`, giving you faster read/write operations with lower latency. @@ -232,7 +232,7 @@ Next, we see what happens if we resize our cluster to scale the number of replic ## Going further - volume snapshots -Try creating [snapshots](/storage/block/how-to/create-a-snapshot/) for your volumes. A snapshot is a consistent, instantaneous copy of a Block Storage volume at a certain point in time. Snapshots are useful for backing up data and facilitating data recovery. +Try creating [snapshots](/block-storage/how-to/create-a-snapshot/) for your volumes. A snapshot is a consistent, instantaneous copy of a Block Storage volume at a certain point in time. Snapshots are useful for backing up data and facilitating data recovery. You can make snapshots by creating a manifest for a **VolumeSnapshot** object and applying it with kubectl. Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/storage/volume-snapshots/) for help with this. You can then check the creation of the snapshot in the Storage > Block Storage > Snapshots section of the console. diff --git a/tutorials/getting-started-with-kops-on-scaleway/index.mdx b/tutorials/getting-started-with-kops-on-scaleway/index.mdx index 640c656eeb..cdc8e1221b 100644 --- a/tutorials/getting-started-with-kops-on-scaleway/index.mdx +++ b/tutorials/getting-started-with-kops-on-scaleway/index.mdx @@ -25,11 +25,11 @@ With kOps, you can easily create, upgrade, and maintain highly available cluster - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Installed [kOps](https://github.com/kubernetes/kops/blob/master/docs/install.md) version >= 1.26 on your local computer - Installed [`kubectl`](https://github.com/kubernetes/kops/blob/master/docs/install.md) on your local computer -- An [Object Storage bucket](/storage/object/quickstart/) and its credentials +- An [Object Storage bucket](/object-storage/quickstart/) and its credentials ## Configuring environment variables diff --git a/tutorials/gitlab-instant-app/index.mdx b/tutorials/gitlab-instant-app/index.mdx index a44f31b652..936599dc88 100644 --- a/tutorials/gitlab-instant-app/index.mdx +++ b/tutorials/gitlab-instant-app/index.mdx @@ -15,13 +15,13 @@ dates: This guide explains the usage of the GitLab repository manager InstantApp, on a Scaleway Instance. GitLab is a web-based platform designed for managing Git repositories and provides a wide range of features, including code reviews, wikis, and issue tracking. -Scaleway provides a GitLab image that is built on Ubuntu 22.04 LTS (Jammy Jellyfish) and includes GitLab version 16.3.3. By default, this image includes support for [routed IPs](/compute/instances/api-cli/using-routed-ips/). +Scaleway provides a GitLab image that is built on Ubuntu 22.04 LTS (Jammy Jellyfish) and includes GitLab version 16.3.3. By default, this image includes support for [routed IPs](/instances/api-cli/using-routed-ips/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Creating a GitLab Instance @@ -35,7 +35,7 @@ Scaleway provides a GitLab image that is built on Ubuntu 22.04 LTS (Jammy Jellyf 8. Click **Create Instance** to launch your GitLab Instance. - For detailed information about Instance creation, refer to the [create an Instance](/compute/instances/how-to/create-an-instance/) documentation. + For detailed information about Instance creation, refer to the [create an Instance](/instances/how-to/create-an-instance/) documentation. ## Configuring GitLab @@ -76,7 +76,7 @@ GitLab can automatically fetch and renew [let's encrypt](https://letsencrypt.org ## Opening the mail ports to send emails - To prevent spam, our infrastructure does not allow access to remote mail ports by default. However, since GitLab requires the ability to send emails, you must enable access to these ports. Your account needs to undergo a validation process before you can enable the SMTP ports. [Learn more about identity verification](/console/account/how-to/verify-identity/). + To prevent spam, our infrastructure does not allow access to remote mail ports by default. However, since GitLab requires the ability to send emails, you must enable access to these ports. Your account needs to undergo a validation process before you can enable the SMTP ports. [Learn more about identity verification](/account/how-to/verify-identity/). 1. Click the **Security groups** tab on the Instances overview page. diff --git a/tutorials/glpi/index.mdx b/tutorials/glpi/index.mdx index 116933f773..0fc0873fba 100644 --- a/tutorials/glpi/index.mdx +++ b/tutorials/glpi/index.mdx @@ -29,9 +29,9 @@ The application disposes of several features to assist companies in managing the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) - A domain or subdomain pointed to your Instance ## Installing the stack @@ -55,7 +55,7 @@ In this tutorial, we will install and configure a [LEMP-Stack](https://lemp.io/) ### Creating a Database for MySQL -In this tutorial, we use a Scaleway Database for MySQL. To create the database, follow [this how-to](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). +In this tutorial, we use a Scaleway Database for MySQL. To create the database, follow [this how-to](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). Make sure you select MySQL as your database engine. diff --git a/tutorials/glusterfs/index.mdx b/tutorials/glusterfs/index.mdx index e5944f18d5..49cb497952 100644 --- a/tutorials/glusterfs/index.mdx +++ b/tutorials/glusterfs/index.mdx @@ -21,10 +21,10 @@ Each storage Instance will mirror the other, and files will automatically be rep - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Three Instances running Ubuntu 22.04 LTS -- Attached [Scaleway Block Storage](/storage/block/how-to/attach-a-volume/) to each GlusterFS Instance +- Attached [Scaleway Block Storage](/block-storage/how-to/attach-a-volume/) to each GlusterFS Instance ## Configuring the host file @@ -104,7 +104,7 @@ Before installing GlusterFS, ensure each Instance can resolve the others via the ### Attaching Scaleway Block Storage 1. Create and attach Scaleway Block Storage to each Instance: - - From the Scaleway Console, [create a new Block Storage volume](/storage/block/how-to/create-a-volume/) for each GlusterFS server. + - From the Scaleway Console, [create a new Block Storage volume](/block-storage/how-to/create-a-volume/) for each GlusterFS server. - Attach each volume to the respective Instance. - Once attached, log into each Instance and check if the Block Storage is recognized: ``` diff --git a/tutorials/gpu-super-resolution/index.mdx b/tutorials/gpu-super-resolution/index.mdx index 111e0b4f96..97e6a4b6a1 100644 --- a/tutorials/gpu-super-resolution/index.mdx +++ b/tutorials/gpu-super-resolution/index.mdx @@ -26,8 +26,8 @@ In this tutorial, we will show you how to prepare your data, construct the **sub - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [GPU Instance](/compute/instances/how-to/create-an-instance/) running on UbuntuML +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [GPU Instance](/instances/how-to/create-an-instance/) running on UbuntuML - Configured [Jupyter Notebook](/tutorials/setup-jupyter-notebook/) on your GPU Instance - `sudo` privileges or access to the root user diff --git a/tutorials/hadoop/index.mdx b/tutorials/hadoop/index.mdx index b2f35977a8..74556608fb 100644 --- a/tutorials/hadoop/index.mdx +++ b/tutorials/hadoop/index.mdx @@ -35,8 +35,8 @@ For more information, refer to the [official Apache Hadoop documentation.](http: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user ## Installing the default JRE/JDK diff --git a/tutorials/hestiacp/index.mdx b/tutorials/hestiacp/index.mdx index 9cb98aa13c..03d41c6b91 100644 --- a/tutorials/hestiacp/index.mdx +++ b/tutorials/hestiacp/index.mdx @@ -21,9 +21,9 @@ In this tutorial, you will learn how to install and configure HestiaCP on Ubuntu - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 18.04 (Bionic Beaver) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 18.04 (Bionic Beaver) - Configured an A-record pointing to the IP address of your Instance - `sudo` privileges or access to the root user diff --git a/tutorials/host-github-runner/index.mdx b/tutorials/host-github-runner/index.mdx index bed3dec35d..0f1e0034bd 100644 --- a/tutorials/host-github-runner/index.mdx +++ b/tutorials/host-github-runner/index.mdx @@ -17,18 +17,18 @@ GitHub Actions stands as a versatile tool, simplifying the automation of all you GitHub offers a limited range of complementary resources for constructing applications through GitHub Actions; however, proficient developers can swiftly encounter these constraints. Teams engaged in professional-grade projects might also want full authority over their build environment. GitHub extends the option to use runners on self-managed instances. A runner function is an application executing tasks from a GitHub Actions workflow. -In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of Production-Optimized Instances provides dedicated resources for enhanced performance. +In this guide, you will learn how to configure a GitHub Actions runner on a Scaleway Instance, effectively streamlining your project workflows. For typical workloads, opting for a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/) is recommended. For resource-intensive workloads, the use of Production-Optimized Instances provides dedicated resources for enhanced performance. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 20.04 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 20.04 - A [GitHub](https://www.github.com) account - `sudo` privileges or access to the root user @@ -42,7 +42,7 @@ In this guide, you will learn how to configure a GitHub Actions runner on a Scal ## Installing a GitHub runner -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Create a user for the GitHub runner. ```s adduser ghrunner diff --git a/tutorials/how-to-implement-rag-generativeapis/index.mdx b/tutorials/how-to-implement-rag-generativeapis/index.mdx index 2564728fd0..62c2991fe5 100644 --- a/tutorials/how-to-implement-rag-generativeapis/index.mdx +++ b/tutorials/how-to-implement-rag-generativeapis/index.mdx @@ -24,11 +24,11 @@ In this tutorial, you will learn how to implement RAG using LangChain, a leading - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Access to the [Generative APIs service](ai-data/generative-apis/quickstart/) -- An [Object Storage Bucket](/storage/object/how-to/create-a-bucket/) to store all the data you want to inject into your LLM model. -- A [Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) to securely store all your embeddings. +- An [Object Storage Bucket](/object-storage/how-to/create-a-bucket/) to store all the data you want to inject into your LLM model. +- A [Managed Database](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) to securely store all your embeddings. ## Configure your development environment @@ -359,16 +359,16 @@ Congratulations! You have built a custom RAG pipeline to improve LLM answers bas If you happen to encounter any issues, first ensure that you have: -- The necessary [IAM permissions](/identity-and-access-management/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** -- An [IAM API key capable of interacting with Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/) -- Stored the right credentials in your `.env` file allowing to connect to your [Managed Database Instance with admin rights](/managed-databases/postgresql-and-mysql/how-to/add-users/) +- The necessary [IAM permissions](/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** +- An [IAM API key capable of interacting with Object Storage](/iam/api-cli/using-api-key-object-storage/) +- Stored the right credentials in your `.env` file allowing to connect to your [Managed Database Instance with admin rights](/managed-databases-for-postgresql-and-mysql/how-to/add-users/) Below are some known error messages and their corresponding solutions: **Error**: `botocore.exceptions.ClientError: An error occurred (SignatureDoesNotMatch) when calling the ListObjectsV2 operation: The request signature we calculated does not match the signature you provided. Check your key and signing method.` -**Solution**: Ensure that your `SCW_BUCKET_NAME`, `SCW_REGION`, `SCW_BUCKET_ENDPOINT`, and `SCW_SECRET_KEY` are properly configured, the corresponding IAM Principal has the necessary rights, and that your [IAM API key can interact with Object Storage](/identity-and-access-management/iam/api-cli/using-api-key-object-storage/). +**Solution**: Ensure that your `SCW_BUCKET_NAME`, `SCW_REGION`, `SCW_BUCKET_ENDPOINT`, and `SCW_SECRET_KEY` are properly configured, the corresponding IAM Principal has the necessary rights, and that your [IAM API key can interact with Object Storage](/iam/api-cli/using-api-key-object-storage/). **Error**: `urllib.error.URLError: ` diff --git a/tutorials/how-to-implement-rag/index.mdx b/tutorials/how-to-implement-rag/index.mdx index 2512c9b477..b806a4b3a2 100644 --- a/tutorials/how-to-implement-rag/index.mdx +++ b/tutorials/how-to-implement-rag/index.mdx @@ -24,12 +24,12 @@ LangChain simplifies the process of enhancing language models with retrieval cap - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Inference Deployment](/ai-data/managed-inference/how-to/create-deployment/): set it up using [sentence-transformers/sentence-t5-xxl](/ai-data/managed-inference/reference-content/sentence-t5-xxl/) on an L4 instance to efficiently process embeddings. -- An [Inference Deployment](/ai-data/managed-inference/how-to/create-deployment/) with the large language model of your choice. -- An [Object Storage Bucket](/storage/object/how-to/create-a-bucket/) to store all the data you want to inject into your LLM model. -- A [Managed Database](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) to securely store all your embeddings. +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Inference Deployment](/managed-inference/how-to/create-deployment/): set it up using [sentence-transformers/sentence-t5-xxl](/managed-inference/reference-content/sentence-t5-xxl/) on an L4 instance to efficiently process embeddings. +- An [Inference Deployment](/managed-inference/how-to/create-deployment/) with the large language model of your choice. +- An [Object Storage Bucket](/object-storage/how-to/create-a-bucket/) to store all the data you want to inject into your LLM model. +- A [Managed Database](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) to securely store all your embeddings. ## Configure your development environment diff --git a/tutorials/install-apache-ansible/index.mdx b/tutorials/install-apache-ansible/index.mdx index 8655abdc0c..4135224631 100644 --- a/tutorials/install-apache-ansible/index.mdx +++ b/tutorials/install-apache-ansible/index.mdx @@ -16,7 +16,7 @@ dates: Apache is one of the most used open-source web servers globally. This tutorial explains how to deploy and configure Apache on Scaleway Instances with the power of Ansible automation. Before diving in, ensure you meet the prerequisites: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Familiarity with [Ansible](/tutorials/ansible-bionic-beaver/) for seamless execution ## Configuring Ansible for Apache diff --git a/tutorials/install-cassandra/index.mdx b/tutorials/install-cassandra/index.mdx index 109fceccd7..d4a9cf2788 100644 --- a/tutorials/install-cassandra/index.mdx +++ b/tutorials/install-cassandra/index.mdx @@ -19,9 +19,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) - `sudo` privileges or access to the root user ## Installing Cassandra diff --git a/tutorials/install-cockroachdb-scaleway-instances/index.mdx b/tutorials/install-cockroachdb-scaleway-instances/index.mdx index 0cfe442a0b..778e621df0 100644 --- a/tutorials/install-cockroachdb-scaleway-instances/index.mdx +++ b/tutorials/install-cockroachdb-scaleway-instances/index.mdx @@ -27,7 +27,7 @@ This article shows you how to install CockroachDB using three nodes on a Private - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed [CockroachDB](https://www.cockroachlabs.com/docs/v23.2/install-cockroachdb) locally - A network configuration allowing TCP communication on the following ports: - `26257` for intra-cluster and client-cluster communication @@ -451,7 +451,7 @@ Use the built-in SQL client locally as follows: Despite CockroachDB's various [built-in safeguards against failure](https://www.cockroachlabs.com/docs/v23.2/frequently-asked-questions#how-does-cockroachdb-survive-failures), it is critical to actively monitor the overall health and performance of a cluster running in production and to create alerting rules that promptly send notifications when there are events that require investigation or intervention. -You can leverage [Scaleway Cockpit](/observability/cockpit/how-to/send-metrics-logs-to-cockpit/) to set up monitoring and alerting using [CockroachDB Prometheus endpoint](https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html) via Prometheus Remote Write capabilities. This can be done by installing Prometheus as an agent on each node. +You can leverage [Scaleway Cockpit](/cockpit/how-to/send-metrics-logs-to-cockpit/) to set up monitoring and alerting using [CockroachDB Prometheus endpoint](https://www.cockroachlabs.com/docs/stable/monitor-cockroachdb-with-prometheus.html) via Prometheus Remote Write capabilities. This can be done by installing Prometheus as an agent on each node. For details about available monitoring options and the most important events and metrics to alert on, see [Monitoring and Alerting(https://www.cockroachlabs.com/docs/v23.2/monitoring-and-alerting). diff --git a/tutorials/install-configure-couchdb/index.mdx b/tutorials/install-configure-couchdb/index.mdx index 6c6e756f8d..29bfd94825 100644 --- a/tutorials/install-configure-couchdb/index.mdx +++ b/tutorials/install-configure-couchdb/index.mdx @@ -28,9 +28,9 @@ CouchDB also supports multi-primary replication which allows it to scale across - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- 3 [Instances](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic (18.04) or Ubuntu Focal (20.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- 3 [Instances](/instances/how-to/create-an-instance/) running on Ubuntu Bionic (18.04) or Ubuntu Focal (20.04) - `sudo` privileges or access to the root user ## Installing CouchDB on the Instances diff --git a/tutorials/install-docker-ubuntu-bionic/index.mdx b/tutorials/install-docker-ubuntu-bionic/index.mdx index 8081ad32ef..56a117309f 100644 --- a/tutorials/install-docker-ubuntu-bionic/index.mdx +++ b/tutorials/install-docker-ubuntu-bionic/index.mdx @@ -23,9 +23,9 @@ This ensures that an application can run on any Linux machine, regardless of the - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic - `sudo` privileges or access to the root user ## Installing Docker Community Edition diff --git a/tutorials/install-docker-ubuntu-jammy-jellyfish/index.mdx b/tutorials/install-docker-ubuntu-jammy-jellyfish/index.mdx index a174464731..a8d3ec4978 100644 --- a/tutorials/install-docker-ubuntu-jammy-jellyfish/index.mdx +++ b/tutorials/install-docker-ubuntu-jammy-jellyfish/index.mdx @@ -27,9 +27,9 @@ Docker Engine is the core component of the [Docker platform](https://docs.docker - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) - `sudo` privileges or access to the root user ## Installing Docker Engine on Ubuntu Jammy Jellyfish (22.04 LTS) diff --git a/tutorials/install-github-actions-runner-mac/index.mdx b/tutorials/install-github-actions-runner-mac/index.mdx index 2dce0c7c1d..c10ab9472c 100644 --- a/tutorials/install-github-actions-runner-mac/index.mdx +++ b/tutorials/install-github-actions-runner-mac/index.mdx @@ -18,8 +18,8 @@ GitHub Actions is a powerful CI/CD platform that allows users to automate their - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Mac mini](/apple-silicon/how-to/create-mac-mini/) - A GitHub repository with administrator rights - Installed a package manager, preferably [Homebrew](https://brew.sh/index) diff --git a/tutorials/install-golang-ubuntu-bionic/index.mdx b/tutorials/install-golang-ubuntu-bionic/index.mdx index c0855aa440..dba5798f6d 100644 --- a/tutorials/install-golang-ubuntu-bionic/index.mdx +++ b/tutorials/install-golang-ubuntu-bionic/index.mdx @@ -21,14 +21,14 @@ This tutorial will guide you through the download and installation of the Go pro - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) - `sudo` privileges or access to the root user ## Installing Go -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). ``` ssh root@your_server_ip ``` diff --git a/tutorials/install-ispconfig/index.mdx b/tutorials/install-ispconfig/index.mdx index 40f3a0baff..ca97400a52 100644 --- a/tutorials/install-ispconfig/index.mdx +++ b/tutorials/install-ispconfig/index.mdx @@ -21,16 +21,16 @@ It can be used to manage a single server, multiple servers for larger setups, or - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu For performance reasons, we recommend using an Instance with at least 4 GB of RAM. - A domain or subdomain pointed to your Instance -- Set the hostname and [reverse DNS](/compute/instances/how-to/configure-reverse-dns/) of your Instance to a valid FQDN +- Set the hostname and [reverse DNS](/instances/how-to/configure-reverse-dns/) of your Instance to a valid FQDN ## Installing ISPConfig -1. [Log into your Instance](/compute/instances/how-to/connect-to-instance/) via SSH using the root account. +1. [Log into your Instance](/instances/how-to/connect-to-instance/) via SSH using the root account. 2. Update and upgrade the software already installed on the Instance. ```bash apt update && apt upgrade -y diff --git a/tutorials/install-kvm-elastic-metal/index.mdx b/tutorials/install-kvm-elastic-metal/index.mdx index 077df2462b..b0e614d9da 100644 --- a/tutorials/install-kvm-elastic-metal/index.mdx +++ b/tutorials/install-kvm-elastic-metal/index.mdx @@ -25,9 +25,9 @@ Each virtual machine has virtualized devices such as: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Elastic Metal server](/elastic-metal/how-to/create-server/) running on Ubuntu Bionic Beaver (18.04) ## Installing the KVM hypervisor and a first guest diff --git a/tutorials/install-mattermost/index.mdx b/tutorials/install-mattermost/index.mdx index 3c80162963..e3c72b1e07 100644 --- a/tutorials/install-mattermost/index.mdx +++ b/tutorials/install-mattermost/index.mdx @@ -19,10 +19,10 @@ Mattermost is an open-source messaging tool for inter-team communication, releas - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic 20.04 or later -- A [Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic 20.04 or later +- A [Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) ## Installing Mattermost diff --git a/tutorials/install-medusa/index.mdx b/tutorials/install-medusa/index.mdx index 01621e6475..7a54e2aec5 100644 --- a/tutorials/install-medusa/index.mdx +++ b/tutorials/install-medusa/index.mdx @@ -20,14 +20,14 @@ This tutorial will show you how to install and use MedusaJS, create a new projec - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 22.04 or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 22.04 or later - Installed [PostgreSQL](/tutorials/install-postgresql/) on the Instance ## Installing MedusaJS -1. [Log into your Instance](/compute/instances/how-to/connect-to-instance/) using SSH. +1. [Log into your Instance](/instances/how-to/connect-to-instance/) using SSH. 2. Update the APT package cache and upgrade the software already installed on your Instance to the latest version available in Ubuntu's repository. ``` apt update && apt upgrade -y @@ -76,6 +76,6 @@ You can edit the files to adapt them to your requirements. For instance, if you This particular file comprises the components used for rendering your application's homepage. If you want to make changes to the backend of your application, you can edit the files in the `my-medusa-store/backend` to your specific requirements. -MedusaJS comes with a built-in SQLite database for development and testing purposes. However, if you want to deploy your application to production, the use of a PostgreSQL such as a [Managed Database for PostgreSQL](/managed-databases/postgresql-and-mysql/quickstart/) is highly recommended. +MedusaJS comes with a built-in SQLite database for development and testing purposes. However, if you want to deploy your application to production, the use of a PostgreSQL such as a [Managed Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/quickstart/) is highly recommended. The tool is designed to be customized to your specific needs, and a wide section of [Medusa Modules](https://docs.medusajs.com/modules/overview) is available to be integrated into your application. For more information on how to configure MedusaJS, refer to the [official Medusa documentation](https://docs.medusajs.com/) and the [Medusa development documentation](https://docs.medusajs.com/development/overview). \ No newline at end of file diff --git a/tutorials/install-openlitespeed-wordpress/index.mdx b/tutorials/install-openlitespeed-wordpress/index.mdx index 5c076e3098..9622df5961 100644 --- a/tutorials/install-openlitespeed-wordpress/index.mdx +++ b/tutorials/install-openlitespeed-wordpress/index.mdx @@ -20,9 +20,9 @@ The application provides a web-based administration interface, compatibility wit - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu or Debian Linux +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu or Debian Linux - A domain name configured and pointed to your Instance - `sudo` privileges or access to the root user diff --git a/tutorials/install-openvpn/index.mdx b/tutorials/install-openvpn/index.mdx index eadd7b2afc..fc97a3a857 100644 --- a/tutorials/install-openvpn/index.mdx +++ b/tutorials/install-openvpn/index.mdx @@ -18,9 +18,9 @@ Learn how to install and configure OpenVPN on Ubuntu 24.04 LTS with this compreh - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 24.04 LTS +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 24.04 LTS ## Installing OpenVPN and Easy-RSA diff --git a/tutorials/install-parse-server/index.mdx b/tutorials/install-parse-server/index.mdx index 1a6f290eab..868cb0702c 100644 --- a/tutorials/install-parse-server/index.mdx +++ b/tutorials/install-parse-server/index.mdx @@ -19,9 +19,9 @@ Parse provides a cloud-based backend service to build data-driven mobile applica - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa or later ## Installing MongoDB diff --git a/tutorials/install-pgbouncer/index.mdx b/tutorials/install-pgbouncer/index.mdx index 94c21d5140..5c3fe5c16d 100644 --- a/tutorials/install-pgbouncer/index.mdx +++ b/tutorials/install-pgbouncer/index.mdx @@ -26,9 +26,9 @@ In this tutorial, you can choose the pooling mode that best suits your workload. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu or Debian +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu or Debian - `sudo` privileges or access to the root user ## Installing PgBouncer diff --git a/tutorials/install-php-composer/index.mdx b/tutorials/install-php-composer/index.mdx index fcf58707c3..ce53a8475c 100644 --- a/tutorials/install-php-composer/index.mdx +++ b/tutorials/install-php-composer/index.mdx @@ -20,9 +20,9 @@ PHP Composer is a package dependency management tool for PHP similar to NPM for - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa - Installed PHP 7.4 or higher on your Instance ## Installing Composer diff --git a/tutorials/install-postgresql/index.mdx b/tutorials/install-postgresql/index.mdx index 7fa78cdd19..63845e7460 100644 --- a/tutorials/install-postgresql/index.mdx +++ b/tutorials/install-postgresql/index.mdx @@ -21,9 +21,9 @@ It runs on all major operating systems, including Linux, different Unix variants - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver or later - `sudo` privileges or access to the root user ## Installing PostgreSQL diff --git a/tutorials/install-rkhunter/index.mdx b/tutorials/install-rkhunter/index.mdx index acce63205a..3d92209515 100644 --- a/tutorials/install-rkhunter/index.mdx +++ b/tutorials/install-rkhunter/index.mdx @@ -18,14 +18,14 @@ The Rootkit Hunter (`rkhunter`) project provides an open-source tool to scan Uni - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) - `sudo` privileges or access to the root user ## Installing rkhunter -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Update the apt sources and the already installed software on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/install-wireguard/index.mdx b/tutorials/install-wireguard/index.mdx index a67e3e7239..f22589a367 100644 --- a/tutorials/install-wireguard/index.mdx +++ b/tutorials/install-wireguard/index.mdx @@ -22,9 +22,9 @@ It is compatible with various platforms, such as Windows, macOS, Linux, iOS, and - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) configured with [local boot](/compute/instances/how-to/use-boot-modes/#how-to-use-local-boot) and running on a Linux kernel ≥ 3.10 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) configured with [local boot](/instances/how-to/use-boot-modes/#how-to-use-local-boot) and running on a Linux kernel ≥ 3.10 WireGuard® is currently under development. @@ -38,7 +38,7 @@ The installation process is based on Ubuntu. Documentation regarding other platf WireGuard needs kernel modules that are not yet implemented in the kernel. The installation process will install new kernel modules via DKMS. -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Install Linux kernel headers and WireGuard. ```bash sudo apt update && apt upgrade -y diff --git a/tutorials/installation-jekyll/index.mdx b/tutorials/installation-jekyll/index.mdx index 5514cb9d46..937f2f27e8 100644 --- a/tutorials/installation-jekyll/index.mdx +++ b/tutorials/installation-jekyll/index.mdx @@ -21,9 +21,9 @@ In this guide, we'll dive into how Jekyll simplifies the process of creating sta - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Two [Instances](/compute/instances/how-to/create-an-instance/) running on [Ubuntu Jammy Jellyfish (22.04 LTS)](https://releases.ubuntu.com/jammy/), one for the development platform and the other to run the site in production +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Two [Instances](/instances/how-to/create-an-instance/) running on [Ubuntu Jammy Jellyfish (22.04 LTS)](https://releases.ubuntu.com/jammy/), one for the development platform and the other to run the site in production ## Installing Jekyll on the development server diff --git a/tutorials/installation-lemp-ubuntu-bionic/index.mdx b/tutorials/installation-lemp-ubuntu-bionic/index.mdx index 64afd0ad75..5bb41cb809 100644 --- a/tutorials/installation-lemp-ubuntu-bionic/index.mdx +++ b/tutorials/installation-lemp-ubuntu-bionic/index.mdx @@ -23,15 +23,15 @@ The LEMP-Stack references a group of software that can be used to serve dynamic - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 18.04 (Bionic Beaver) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 18.04 (Bionic Beaver) or later - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address - `sudo` privileges or access to the root user ## Installing the stack -1. [Connect to your Instance via SSH](/compute/instances/how-to/create-an-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/create-an-instance/). 2. Use the `apt` package manager of Ubuntu to install the required packages. Make sure that the system is up-to-date and has the latest bug fixes and updates installed by running the following command: ```bash apt update && apt -y upgrade diff --git a/tutorials/installation-lemp-ubuntu-focal/index.mdx b/tutorials/installation-lemp-ubuntu-focal/index.mdx index 62019364db..8b22d37058 100644 --- a/tutorials/installation-lemp-ubuntu-focal/index.mdx +++ b/tutorials/installation-lemp-ubuntu-focal/index.mdx @@ -23,15 +23,15 @@ The LEMP-Stack references a group of software that can be used to serve dynamic - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 20.04 (Focal Fossa) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 20.04 (Focal Fossa) - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address - `sudo` privileges or access to the root user ## Installing the stack -1. [Connect to your Instance via SSH](/compute/instances/how-to/create-an-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/create-an-instance/). 2. Use the `apt` package manager of Ubuntu to install the required packages. Make sure that the system is up-to-date and has the latest bug fixes and updates installed by running the following command: ```bash apt update && apt -y upgrade diff --git a/tutorials/installation-uncomplicated-firewall/index.mdx b/tutorials/installation-uncomplicated-firewall/index.mdx index 415a4cc82a..7f3c1a7c82 100644 --- a/tutorials/installation-uncomplicated-firewall/index.mdx +++ b/tutorials/installation-uncomplicated-firewall/index.mdx @@ -20,9 +20,9 @@ UFW, or **[Uncomplicated FireWall](https://en.wikipedia.org/wiki/Uncomplicated_F - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa or later -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa or later +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user ## Installing UFW diff --git a/tutorials/jitsi-debian-stretch/index.mdx b/tutorials/jitsi-debian-stretch/index.mdx index f23c7dcfd2..84daa8dab8 100644 --- a/tutorials/jitsi-debian-stretch/index.mdx +++ b/tutorials/jitsi-debian-stretch/index.mdx @@ -24,10 +24,10 @@ The tool provides features such as: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Debian Stretch (9.0) with **at least 4 GB of RAM**. -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Debian Stretch (9.0) with **at least 4 GB of RAM**. +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Installing Jitsi Meet diff --git a/tutorials/jitsi-debian/index.mdx b/tutorials/jitsi-debian/index.mdx index 4525f1a59e..7a0eda9512 100644 --- a/tutorials/jitsi-debian/index.mdx +++ b/tutorials/jitsi-debian/index.mdx @@ -26,10 +26,10 @@ The tool provides features such as: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Debian Buster with **at least 4 GB of RAM**. -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Debian Buster with **at least 4 GB of RAM**. +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance This tutorial shows the installation of Jitsi Meet on Debian Buster. If you prefer the installation of Jitsi Meet on Ubuntu Bionic Beaver, follow [this tutorial](/tutorials/jitsi-ubuntu-bionic/). diff --git a/tutorials/jitsi-docker/index.mdx b/tutorials/jitsi-docker/index.mdx index 17d01a15a2..a1d64ba067 100644 --- a/tutorials/jitsi-docker/index.mdx +++ b/tutorials/jitsi-docker/index.mdx @@ -20,14 +20,14 @@ This tutorial explains how to install the Jitsi Meet solution on an Instance usi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (or later) with **at least 4 GB of RAM** -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (or later) with **at least 4 GB of RAM** +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Setting up Docker -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Update the package cache and upgrade the software already installed on the Instance using the `apt` package manager: ```bash apt update && apt upgrade -y diff --git a/tutorials/jitsi-ubuntu-bionic/index.mdx b/tutorials/jitsi-ubuntu-bionic/index.mdx index 506dde1a56..94c35f5450 100644 --- a/tutorials/jitsi-ubuntu-bionic/index.mdx +++ b/tutorials/jitsi-ubuntu-bionic/index.mdx @@ -28,10 +28,10 @@ In summary, Jitsi Meet provides a competitive alternative to commercial solution - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver with **at least 4 GB of RAM**. -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver with **at least 4 GB of RAM**. +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance This tutorial describes the installation of Jitsi Meet on Ubuntu Bionic Beaver. If you prefer, you can [install Jitsi Meet on Debian Buster](/tutorials/jitsi-debian/), instead. @@ -39,7 +39,7 @@ In summary, Jitsi Meet provides a competitive alternative to commercial solution ## Installing Jitsi Meet -1. [Connect to your Instance via SSH](/compute/instances/how-to/create-an-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/create-an-instance/). 2. Configure the hostname of the server corresponding to your domain/subdomain name. Replace `jitsi.mydomain.tld` with the subdomain pointed to your Instance. ``` hostnamectl set-hostname jitsi diff --git a/tutorials/jitsi-ubuntu-focal-fossa/index.mdx b/tutorials/jitsi-ubuntu-focal-fossa/index.mdx index 34e511a786..6b0f7a06b9 100644 --- a/tutorials/jitsi-ubuntu-focal-fossa/index.mdx +++ b/tutorials/jitsi-ubuntu-focal-fossa/index.mdx @@ -26,10 +26,10 @@ It provides features like: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa with **at least 4 GB of RAM**. -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa with **at least 4 GB of RAM**. +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance This tutorial shows the installation of Jitsi Meet on Ubuntu Focal Fossa. If you prefer the installation of Jitsi Meet on Ubuntu Bionic Beaver, follow [this tutorial](/tutorials/jitsi-ubuntu-bionic/). diff --git a/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx b/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx index 7430401eda..3a9dfa5b4c 100644 --- a/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx +++ b/tutorials/jitsi-ubuntu-jammy-jellyfish/index.mdx @@ -29,10 +29,10 @@ Jitsi Meet provides users with a complete suite of tools, making virtual meeting - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish with **at least 4 GB of RAM**. -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish with **at least 4 GB of RAM**. +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance This tutorial shows the installation of Jitsi Meet on Ubuntu Jammy Jellyfish. If you would prefer to install Jitsi Meet on Ubuntu Bionic Beaver, follow [the tutorial for installing Jitsi Meet on Ubuntu Bionic Beaver](/tutorials/jitsi-ubuntu-bionic/). @@ -80,7 +80,7 @@ Jitsi Meet provides users with a complete suite of tools, making virtual meeting When asked: - - Enter the [FQDN](/network/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) of your Instance (for example `jitsi.mydomain.tld`), and press **Enter**. + - Enter the [FQDN](/domains-and-dns/concepts/#fully-qualified-domain-name-fqdn) of your Instance (for example `jitsi.mydomain.tld`), and press **Enter**. - Choose the `Let's Encrypt certificates` option as an SSL certificate and press **Enter**. - Enter your email address. - Enter your phone number (optional). diff --git a/tutorials/jump-desktop/index.mdx b/tutorials/jump-desktop/index.mdx index f4c1e2b79e..99cbe74bf8 100644 --- a/tutorials/jump-desktop/index.mdx +++ b/tutorials/jump-desktop/index.mdx @@ -22,8 +22,8 @@ In this tutorial, you will learn how to launch your Mac mini development environ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Mac mini](/apple-silicon/how-to/create-mac-mini/) - Installed a [VNC viewer](https://www.tightvnc.com/) on your local computer ## Downloading Jump Desktop on your local computer diff --git a/tutorials/k8s-gitlab/index.mdx b/tutorials/k8s-gitlab/index.mdx index 682b65e266..dae26f36ab 100644 --- a/tutorials/k8s-gitlab/index.mdx +++ b/tutorials/k8s-gitlab/index.mdx @@ -21,10 +21,10 @@ In this tutorial, you will learn how to use the `gitlab` Kubernetes integration - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - An Instance running the [`gitlab` InstantApp](/tutorials/gitlab-instant-app/) -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/). -- Downloaded the corresponding [kubeconfig](/containers/kubernetes/how-to/edit-cluster/) file and ensured [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) is working +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/). +- Downloaded the corresponding [kubeconfig](/kubernetes/how-to/edit-cluster/) file and ensured [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) is working - Installed [Helm client](https://helm.sh/docs/intro/install/) ## Configuring GitLab runner using Helm charts diff --git a/tutorials/k8s-kapsule-multi-az/index.mdx b/tutorials/k8s-kapsule-multi-az/index.mdx index 7b61a9df08..238cd95a6a 100644 --- a/tutorials/k8s-kapsule-multi-az/index.mdx +++ b/tutorials/k8s-kapsule-multi-az/index.mdx @@ -22,7 +22,7 @@ This configuration allows the system to withstand failures in one zone by replic - A Scaleway account logged into the [console](https://console.scaleway.com) -- A domain managed on the Scaleway [Domains and DNS service](/network/domains-and-dns/quickstart/) +- A domain managed on the Scaleway [Domains and DNS service](/domains-and-dns/quickstart/) - Installed [Terraform](/tutorials/terraform-quickstart/) on your local computer @@ -187,7 +187,7 @@ In this part, we will deploy an [ingress-nginx](https://github.com/kubernetes/in For this section you need, as a prerequisite, a domain managed on the Scaleway "Domains and DNS" service. -The domain used for this tutorial can be of type `internal` when bought with your Scaleway account, or of the `external` type if you want to re-use a domain bought with an external DNS registrar. If you choose the `external` method, you can follow the [How to add an external domain to DNS](/network/domains-and-dns/how-to/add-external-domain/) documentation. If you don't want to delegate all your domains to your Scaleway account, import your domain, but do not change the name servers in your registrar. Then you can create a "DNS zone" in Scaleway on your external domain, and declare two NS records in your registrar matching this zone. For example, with a domain "your-domain.tld" imported in Scaleway, you can create a DNS zone "scw", and delegate this zone to your registrar by adding those two records: +The domain used for this tutorial can be of type `internal` when bought with your Scaleway account, or of the `external` type if you want to re-use a domain bought with an external DNS registrar. If you choose the `external` method, you can follow the [How to add an external domain to DNS](/domains-and-dns/how-to/add-external-domain/) documentation. If you don't want to delegate all your domains to your Scaleway account, import your domain, but do not change the name servers in your registrar. Then you can create a "DNS zone" in Scaleway on your external domain, and declare two NS records in your registrar matching this zone. For example, with a domain "your-domain.tld" imported in Scaleway, you can create a DNS zone "scw", and delegate this zone to your registrar by adding those two records: ``` scw 600 IN NS ns0.dom.scw.cloud. scw 600 IN NS ns1.dom.scw.cloud. diff --git a/tutorials/k8s-velero-backup/index.mdx b/tutorials/k8s-velero-backup/index.mdx index fa43a23f4a..cdd7f50f1a 100644 --- a/tutorials/k8s-velero-backup/index.mdx +++ b/tutorials/k8s-velero-backup/index.mdx @@ -25,11 +25,11 @@ Velero seamlessly integrates with Kubernetes through custom resource definitions - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Created an Object Storage bucket](/storage/object/how-to/create-a-bucket/) -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Set up [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Set up [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your machine ## Installation of Velero diff --git a/tutorials/kubernetes-package-management-helm/index.mdx b/tutorials/kubernetes-package-management-helm/index.mdx index 90cdfd1045..6656df0c46 100644 --- a/tutorials/kubernetes-package-management-helm/index.mdx +++ b/tutorials/kubernetes-package-management-helm/index.mdx @@ -40,9 +40,9 @@ For a complete overview of Helm and its basic concepts, refer to this [Scaleway - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Set up [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Set up [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your machine ## Installing Helm @@ -51,7 +51,7 @@ For a complete overview of Helm and its basic concepts, refer to this [Scaleway ``` kubectl cluster-info ``` - You will see cluster information if `kubectl` is installed and configured correctly. If not, make sure to [deploy a Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) first. + You will see cluster information if `kubectl` is installed and configured correctly. If not, make sure to [deploy a Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) first. ### Installing Helm Client diff --git a/tutorials/large-messages/index.mdx b/tutorials/large-messages/index.mdx index 06734f66aa..6814bcfe11 100644 --- a/tutorials/large-messages/index.mdx +++ b/tutorials/large-messages/index.mdx @@ -15,7 +15,7 @@ dates: posted: 2024-01-22 --- -In this tutorial, we will build a simple architecture to store and automatically convert images to PDF. The focus is on transferring large messages using a messaging service, specifically the [Scaleway NATS](/serverless/messaging/quickstart/) server. Our setup involves using the [Object Storage](/storage/object/quickstart/) service for image storage and the [Serverless Functions](/serverless/functions/quickstart/) service for conversion. +In this tutorial, we will build a simple architecture to store and automatically convert images to PDF. The focus is on transferring large messages using a messaging service, specifically the [Scaleway NATS](/messaging/quickstart/) server. Our setup involves using the [Object Storage](/object-storage/quickstart/) service for image storage and the [Serverless Functions](/serverless-functions/quickstart/) service for conversion. We show how to provision all the required Scaleway resources via Terraform, but you can also use the [console](https://console.scaleway.com/login), the [API](https://www.scaleway.com/en/developers/api/) or one of our other supported [developer tools](https://www.scaleway.com/en/developers/). @@ -24,12 +24,12 @@ You can retrieve the full source code in [this repository](https://github.com/ro - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Installed [Terraform](/developer-tools/terraform/quickstart/) on your local machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Installed [Terraform](/terraform/quickstart/) on your local machine - [Set up authentication for the Terraform provider](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs#authentication) - Installed [Docker](/tutorials/install-docker-ubuntu-bionic/) on your local machine - Installed [NATS CLI](https://github.com/nats-io/natscli) on your local machine -- [AWS CLI configured with Scaleway credentials](/storage/object/api-cli/object-storage-aws-cli/#how-to-install-the-aws-cli) +- [AWS CLI configured with Scaleway credentials](/object-storage/api-cli/object-storage-aws-cli/#how-to-install-the-aws-cli) ## Architecture @@ -237,7 +237,7 @@ We continue using the Scaleway ecosystem and deploy the consumer using a Serverl depends_on = [null_resource.install_dependencies] } ``` - The `null_resource` is used to download and package the correct versions of the libraries that we use with the function. Refer to the [documentation on Python dependencies](/serverless/functions/how-to/package-function-dependencies-in-zip/#dependencies) for more information. + The `null_resource` is used to download and package the correct versions of the libraries that we use with the function. Refer to the [documentation on Python dependencies](/serverless-functions/how-to/package-function-dependencies-in-zip/#dependencies) for more information. 6. Create the function namespace. ```hcl diff --git a/tutorials/lb-firewall-haproxy-pfsense/index.mdx b/tutorials/lb-firewall-haproxy-pfsense/index.mdx index 94d1df1f1c..91986b20d0 100644 --- a/tutorials/lb-firewall-haproxy-pfsense/index.mdx +++ b/tutorials/lb-firewall-haproxy-pfsense/index.mdx @@ -25,17 +25,17 @@ This tutorial guides you through the installation of pfSense on a [Scaleway Dedi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A [Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) with KVM-over-IP access ## Installing pfSense - The installation of pfSense is done using the [KVM-over-IP device](/dedibox/kvm-over-ip/quickstart/) of the Elastic Metal server or the Scaleway Dedibox. + The installation of pfSense is done using the [KVM-over-IP device](/dedibox-kvm-over-ip/quickstart/) of the Elastic Metal server or the Scaleway Dedibox. -1. Connect to the [KVM-over-IP device](/dedibox/kvm-over-ip/quickstart/) of your Elastic Metal server or Scaleway Dedibox. +1. Connect to the [KVM-over-IP device](/dedibox-kvm-over-ip/quickstart/) of your Elastic Metal server or Scaleway Dedibox. 2. Depending on the type of the KVM-over-IP device, you can either mount a locally downloaded [pfSense ISO Image](https://www.pfsense.org/download/) or mount a virtual media from a [network share](https://virtualmedia.online.net/pfsense/). 3. Boot the server from the ISO file or the virtual CD-ROM drive. 4. The pfSense install wizard displays. Accept the copyright and distribution notice by pressing the **Enter** key on your keyboard: @@ -157,7 +157,7 @@ Once rebooted, the pfSense welcome screen displays: ### Configuring the interfaces Most [Scaleway Dedibox](https://www.scaleway.com/en/dedibox/) dedicated servers come with two physical network interfaces. In this configuration, the interface `igb0` is configured as a WAN (Internet) interface, and the interface `igb1` acts as a LAN (RPNv2) interface. -With [RPNv2](https://www.scaleway.com/en/dedibox/private-network-rpn/), it is possible to configure multiple private networks on the physical network interface. We suppose the [RPNv2 group](/dedibox-network/rpn/quickstart/#how-to-create-an-rpnv2-group) is already configured. +With [RPNv2](https://www.scaleway.com/en/dedibox/private-network-rpn/), it is possible to configure multiple private networks on the physical network interface. We suppose the [RPNv2 group](/dedibox-rpn/quickstart/#how-to-create-an-rpnv2-group) is already configured. In this tutorial, we will configure a cluster of two pfSense servers that are using the following VLANs: @@ -302,7 +302,7 @@ Before configuring High Availability, rules to allow `pfsync` traffic have to be ## Configuring failover IPs -Two [failover IPs](/dedibox-console/account/how-to/outsource-failover-ip/) are being used as an endpoint for HAProxy (one by each Instance). To automatize the configuration in case of unavailability of one of the servers, the following workflow is needed: +Two [failover IPs](/dedibox-account/how-to/outsource-failover-ip/) are being used as an endpoint for HAProxy (one by each Instance). To automatize the configuration in case of unavailability of one of the servers, the following workflow is needed: - In case of a failure of `pf1`, `pf2` calls the Scaleway Dedibox API to switch the failover IP to `lb1` - In case of a failure of `pf2`, `pf1` calls the Scaleway Dedibox API to switch the failover IP to `lb2` diff --git a/tutorials/librenms-monitoring/index.mdx b/tutorials/librenms-monitoring/index.mdx index 359ec9b727..183974a9fb 100644 --- a/tutorials/librenms-monitoring/index.mdx +++ b/tutorials/librenms-monitoring/index.mdx @@ -20,10 +20,10 @@ The software is based on PHP and MySQL (MariaDB) and is a community-based fork o - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04) -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04) +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Installing LibreNMS diff --git a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx index f459053a8a..ba9ed41893 100644 --- a/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx +++ b/tutorials/load-overflow-proxmox-and-elastic-metal/index.mdx @@ -18,12 +18,12 @@ dates: ## Overview -The [Private Network](/network/vpc/concepts/#private-networks) feature enables you to build a virtual L2 network between your cloud resources. The service is compatible with a wide range of resources including: -* [Instances](/compute/instances/quickstart/) -* [Elastic Metal servers](/bare-metal/elastic-metal/quickstart/) -* [Databases](/managed-databases/postgresql-and-mysql/quickstart/) -* [Load Balancers](/network/load-balancer/quickstart/) -* [Public Gateways](/network/public-gateways/concepts/#public-gateway), enabling their communication with the internet. +The [Private Network](/vpc/concepts/#private-networks) feature enables you to build a virtual L2 network between your cloud resources. The service is compatible with a wide range of resources including: +* [Instances](/instances/quickstart/) +* [Elastic Metal servers](/elastic-metal/quickstart/) +* [Databases](/managed-databases-for-postgresql-and-mysql/quickstart/) +* [Load Balancers](/load-balancer/quickstart/) +* [Public Gateways](/public-gateways/concepts/#public-gateway), enabling their communication with the internet. In this guide, we will establish a [Proxmox VE](https://www.proxmox.com/en/proxmox-ve) cluster on two Elastic Metal servers. Our goal is to enable the creation of multiple VMs on each of them, facilitating communication through a Private Network. @@ -36,12 +36,12 @@ Finally, we can introduce and configure a Load Balancer to evenly distribute tra - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- 2 [Elastic Metal servers](/compute/instances/how-to/create-an-instance/) running on Proxmox -- [Created a Private Network](/network/vpc/how-to/create-private-network/) and added your resources to it -- [Created a Public Gateway](/network/public-gateways/how-to/create-a-public-gateway/) -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- 2 [Elastic Metal servers](/instances/how-to/create-an-instance/) running on Proxmox +- [Created a Private Network](/vpc/how-to/create-private-network/) and added your resources to it +- [Created a Public Gateway](/public-gateways/how-to/create-a-public-gateway/) +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Preparing Proxmox @@ -64,12 +64,12 @@ Finally, we can introduce and configure a Load Balancer to evenly distribute tra Proxmox is capable of managing Linux Kernel Virtual Machines (KVM) as well as LXC containers. KVM provides full virtualization for complete Windows and Linux images whilst LXC containers are lightweight and perfect to run conflict-free Linux applications. Follow this guide for information on how to [configure virtual machines and LXC containers on Proxmox](/tutorials/configure-failover-proxmox/). -Create or clone your virtual machines on both servers of the cluster to distribute the load between them using a Load Balancer. Your virtual machines can use the Public Gateway and dynamic NAT to communicate with the internet for downloads and updates. If you want to expose certain ports of your VMs directly, configure [static NAT rules](/network/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) for them. +Create or clone your virtual machines on both servers of the cluster to distribute the load between them using a Load Balancer. Your virtual machines can use the Public Gateway and dynamic NAT to communicate with the internet for downloads and updates. If you want to expose certain ports of your VMs directly, configure [static NAT rules](/public-gateways/how-to/configure-a-public-gateway/#how-to-review-and-configure-nat) for them. Make sure to select the bridge `vmbr1`, automatic MAC address generation, and select DHCP for LXC network configuration. - We recommend that you use IPAM to assign an IP on the Private Network to each VM. You first need to [reserve](/network/ipam/how-to/reserve-ip/) an IP address for each machine, then use the IPAM API's [Attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-existing-ip-to-custom-resource) method to attach it by passing the VM's name and MAC address. + We recommend that you use IPAM to assign an IP on the Private Network to each VM. You first need to [reserve](/ipam/how-to/reserve-ip/) an IP address for each machine, then use the IPAM API's [Attach IP to custom resource](https://www.scaleway.com/en/developers/api/ipam/#path-ips-attach-existing-ip-to-custom-resource) method to attach it by passing the VM's name and MAC address. ## Configuring the Load Balancer @@ -93,5 +93,5 @@ Create or clone your virtual machines on both servers of the cluster to distribu * The IP addreses of your VM's inside the Private Network - For more information about the front and backend configuration, refer to the [Load Balancers documentation](/network/load-balancer/how-to/manage-frontends-and-backends/). + For more information about the front and backend configuration, refer to the [Load Balancers documentation](/load-balancer/how-to/manage-frontends-and-backends/). \ No newline at end of file diff --git a/tutorials/load-testing-vegeta/index.mdx b/tutorials/load-testing-vegeta/index.mdx index 7207659d35..c74e3b343e 100644 --- a/tutorials/load-testing-vegeta/index.mdx +++ b/tutorials/load-testing-vegeta/index.mdx @@ -27,19 +27,19 @@ Before transitioning an application to a production environment, load testing he - Identification of performance constraints attributed to technical specifications of employed Instances - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Linux +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Linux ## Downloading and installing Vegeta on Ubuntu Linux -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. [Download](https://github.com/tsenart/vegeta/releases) the latest binary version to install Vegeta on your Ubuntu Linux machine: ``` wget https://github.com/tsenart/vegeta/releases/download/v12.12.0/vegeta_12.12.0_linux_amd64.tar.gz diff --git a/tutorials/loriot-lorawan-network-server/index.mdx b/tutorials/loriot-lorawan-network-server/index.mdx index 9579afa2eb..8dd5ec5c47 100644 --- a/tutorials/loriot-lorawan-network-server/index.mdx +++ b/tutorials/loriot-lorawan-network-server/index.mdx @@ -28,15 +28,15 @@ In this tutorial we are going to: -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Create an IoT Hub -First, we need to create a Hub. Its role will be to distribute messages from your LoRaWAN© devices to the intended targets. Follow [this procedure](/managed-services/iot-hub/how-to/create-hub/) to create an IoT Hub if you do not have one already. The hub's name and plan does not matter for this tutorial. +First, we need to create a Hub. Its role will be to distribute messages from your LoRaWAN© devices to the intended targets. Follow [this procedure](/iot-hub/how-to/create-hub/) to create an IoT Hub if you do not have one already. The hub's name and plan does not matter for this tutorial. ## Create an IoT Device -The Loriot platform will connect as a MQTT device to exchange data on IoT Hub. This means that we need to add a Device to the IoT Hub. Follow [this procedure](/managed-services/iot-hub/how-to/add-device/) to create a device. +The Loriot platform will connect as a MQTT device to exchange data on IoT Hub. This means that we need to add a Device to the IoT Hub. Follow [this procedure](/iot-hub/how-to/add-device/) to create a device. - Use the `Allow Insecure` connections setting. @@ -89,9 +89,9 @@ This means that messages are flowing as expected. You could leverage the power of IoT Hub to build a dashboard to display your data in a few easy steps: -- [Start a PostgreSQL managed DB Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) and create a `lora` table with the following fields: `time` (timestamp type) and `data` (`jsonb` type) -- Configure a Database Route to push data in there, [see how to](/managed-databases/postgresql-and-mysql/how-to/create-a-database/). The topic filter should be `my-app/things/+/uplink`. Your query should look like `INSERT INTO lora (time, data) VALUES (NOW(), $PAYLOAD)`. -- Start a [new Scaleway Instance](/compute/instances/how-to/create-an-instance/) and setup Grafana, get inspiration from [this tutorial](/tutorials/visualize-timeseries-data-timescaledb-grafana/) (steps 1 to 14, do not enable the TimescaleDB option). +- [Start a PostgreSQL managed DB Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) and create a `lora` table with the following fields: `time` (timestamp type) and `data` (`jsonb` type) +- Configure a Database Route to push data in there, [see how to](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/). The topic filter should be `my-app/things/+/uplink`. Your query should look like `INSERT INTO lora (time, data) VALUES (NOW(), $PAYLOAD)`. +- Start a [new Scaleway Instance](/instances/how-to/create-an-instance/) and setup Grafana, get inspiration from [this tutorial](/tutorials/visualize-timeseries-data-timescaledb-grafana/) (steps 1 to 14, do not enable the TimescaleDB option). - Add widgets to your dashboard, for a graph your query could look like `SELECT time, data->'DevEUI_uplink'->'payload'->'batteryLevel' as batteryLevel FROM lora WHERE $__timeFilter(time)`. Your LoRaWAN© devices' data is now backed by a production-grade dashboard. @@ -100,4 +100,4 @@ Your LoRaWAN© devices' data is now backed by a production-grade dashboard. --- -Learn more about [Scaleway IoT Hub](/managed-services/iot-hub/concepts/), discover how to add [Devices to the hub](/managed-services/iot-hub/how-to/add-device/) or how to check the [IoT Hub metrics](/managed-services/iot-hub/how-to/view-metrics/). \ No newline at end of file +Learn more about [Scaleway IoT Hub](/iot-hub/concepts/), discover how to add [Devices to the hub](/iot-hub/how-to/add-device/) or how to check the [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/magento-ubuntu/index.mdx b/tutorials/magento-ubuntu/index.mdx index 8d9559ec13..d9975fea2c 100644 --- a/tutorials/magento-ubuntu/index.mdx +++ b/tutorials/magento-ubuntu/index.mdx @@ -22,9 +22,9 @@ In this tutorial, you will learn how to install the open-source version of Magen - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/compute/instances/how-to/create-an-instance/) and [connected to](/compute/instances/how-to/connect-to-instance/) a Scaleway Instance with at least 2 GB RAM -- Configured a domain name to point toward the IP address of your Instance ([A or AAAA record](/network/domains-and-dns/concepts/#resource-records)) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/instances/how-to/create-an-instance/) and [connected to](/instances/how-to/connect-to-instance/) a Scaleway Instance with at least 2 GB RAM +- Configured a domain name to point toward the IP address of your Instance ([A or AAAA record](/domains-and-dns/concepts/#resource-records)) - [Created a free Magento account](https://account.magento.com/customer/account/create/) ## Getting the Instance ready diff --git a/tutorials/manage-container-registry-images/index.mdx b/tutorials/manage-container-registry-images/index.mdx index 85d5d2c3d8..d62bc472ab 100644 --- a/tutorials/manage-container-registry-images/index.mdx +++ b/tutorials/manage-container-registry-images/index.mdx @@ -20,9 +20,9 @@ This tutorial will show you how to periodically remove older images with a speci - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Created a [Serverless Functions namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Created a [Serverless Functions namespace](/container-registry/how-to/create-namespace/) ## Deleting unused images diff --git a/tutorials/manage-database-instance-pgadmin4/index.mdx b/tutorials/manage-database-instance-pgadmin4/index.mdx index 5b3600c010..5c87c3e8d2 100644 --- a/tutorials/manage-database-instance-pgadmin4/index.mdx +++ b/tutorials/manage-database-instance-pgadmin4/index.mdx @@ -19,15 +19,15 @@ pgAdmin is an open-source management tool for PostgreSQL databases. It allows th - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Debian Buster +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Debian Buster - A [Database for PostgreSQL](https://www.scaleway.com/en/database/) - `sudo` privileges or access to the root user ## Installing pgAdmin -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Update the `apt` sources and the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/manage-instances-with-terraform-and-functions/index.mdx b/tutorials/manage-instances-with-terraform-and-functions/index.mdx index 3855bbe139..6a3c9e9ace 100644 --- a/tutorials/manage-instances-with-terraform-and-functions/index.mdx +++ b/tutorials/manage-instances-with-terraform-and-functions/index.mdx @@ -21,8 +21,8 @@ HashiCorp Terraform is an open-source software tool to deploy Infrastructure as - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [Python](https://www.python.org/) on your machine - Installed [Terraform](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs) on your machine diff --git a/tutorials/manage-k8s-logging-loki/index.mdx b/tutorials/manage-k8s-logging-loki/index.mdx index b4f614b13b..dc7077ba0c 100644 --- a/tutorials/manage-k8s-logging-loki/index.mdx +++ b/tutorials/manage-k8s-logging-loki/index.mdx @@ -14,21 +14,21 @@ dates: --- - Kubernetes Kapsule is fully integrated with Scaleway's [Observability Cockpit](/observability/cockpit/quickstart/). - You can [monitor your cluster](/containers/kubernetes/how-to/monitor-cluster/) directly from the cluster's dashboard, eliminating the need to set up your own monitoring solution. + Kubernetes Kapsule is fully integrated with Scaleway's [Observability Cockpit](/cockpit/quickstart/). + You can [monitor your cluster](/kubernetes/how-to/monitor-cluster/) directly from the cluster's dashboard, eliminating the need to set up your own monitoring solution. The following content is provided for informational purposes only. -In this tutorial, you will learn how to use **Loki** and **Grafana** to collect your Kubernetes logs on a [Kapsule cluster](/containers/kubernetes/how-to/create-cluster/). +In this tutorial, you will learn how to use **Loki** and **Grafana** to collect your Kubernetes logs on a [Kapsule cluster](/kubernetes/how-to/create-cluster/). Loki is a log aggregation system inspired by **Prometheus**. It is easy to operate, as it does not index the content of the Kubernetes logs but sets labels for log streams. Your metadata (object labels) can be used in Loki for scraping Kubernetes logs. If you use Grafana for metrics, Loki will allow you to have a single point of management for both logging and monitoring. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- Configured [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- Configured [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your machine - Installed `helm` (version 3.2+), the Kubernetes [packet manager](https://helm.sh/), on your local machine 1. Add the Grafana repository to Helm and update it. diff --git a/tutorials/manage-zigbee-devices-with-iot/index.mdx b/tutorials/manage-zigbee-devices-with-iot/index.mdx index ca2d9fd546..38b55b09da 100644 --- a/tutorials/manage-zigbee-devices-with-iot/index.mdx +++ b/tutorials/manage-zigbee-devices-with-iot/index.mdx @@ -15,11 +15,11 @@ dates: Privacy and security concerns should be at the forefront of any deployment of connected devices used to monitor or automate actions in our physical environment. Zigbee is a recognized protocol to create a mesh network of sensors and actuators in houses and apartments. However, a proprietary gateway is often used to send commands and receive information to and from this network. It results in a trade-off in control over the security level and the automation and monitoring capabilities. This tutorial aims to set the foundation of a fully configurable solution based on the open source [zigbee2mqtt](https://github.com/Koenkk/zigbee2mqtt) software and the IoT Hub managed service from Scaleway. -[Scaleway IoT Hub](/managed-services/iot-hub/quickstart/) is a resilient and MQTT message broker with export capabilities. The use of a message broker will enable us to increase the interoperability of the solution. +[Scaleway IoT Hub](/iot-hub/quickstart/) is a resilient and MQTT message broker with export capabilities. The use of a message broker will enable us to increase the interoperability of the solution. # Creating an IoT Hub -1. Create an **IoT Hub** (shared plan) for testing purposes, following the available [documentation](/managed-services/iot-hub/quickstart/). Dedicated and High availability plans remain recommended for more critical workloads. +1. Create an **IoT Hub** (shared plan) for testing purposes, following the available [documentation](/iot-hub/quickstart/). Dedicated and High availability plans remain recommended for more critical workloads. 2. Add a new device to the Hub, with the option "Deny insecure connection" selected. You need to download the device certificate and device private key, as well as the **Device ID**. 3. Download the certificate used to secure the MQTT endpoint in the **Networks** tabs. diff --git a/tutorials/mariadb-ubuntu-bionic/index.mdx b/tutorials/mariadb-ubuntu-bionic/index.mdx index 057e762f0f..03ceff6c01 100644 --- a/tutorials/mariadb-ubuntu-bionic/index.mdx +++ b/tutorials/mariadb-ubuntu-bionic/index.mdx @@ -29,14 +29,14 @@ Even the command line tools are similar to `mysqldump` and `mysqladmin` still ha - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver - `sudo` privileges or access to the root user ## Installing MariaDB -1. [Connect to your instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your instance](/instances/how-to/connect-to-instance/) via SSH. ``` ssh root@SERVER_IP ``` diff --git a/tutorials/mastodon-community/index.mdx b/tutorials/mastodon-community/index.mdx index cc50fd453b..b83fba389a 100644 --- a/tutorials/mastodon-community/index.mdx +++ b/tutorials/mastodon-community/index.mdx @@ -18,20 +18,20 @@ Mastodon is an open-source, self-hosted, social media and social networking serv As there is no central server, you can choose whether to join or leave an instance according to its policy without actually leaving Mastodon Social Network. Mastodon is a part of [Fediverse](https://fediverse.party/), allowing users to interact with users on other platforms that support the same protocol for example: [PeerTube](https://joinpeertube.org/en/), [Friendica](https://friendi.ca/) and [GNU Social](https://gnu.io/social/). -Mastodon provides the possibility of using [Amazon S3-compatible Object Storage](/storage/object/how-to/create-a-bucket/) to store media content uploaded to Instances, making it flexible and scalable. +Mastodon provides the possibility of using [Amazon S3-compatible Object Storage](/object-storage/how-to/create-a-bucket/) to store media content uploaded to Instances, making it flexible and scalable. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance - Enabled the SMTP ports to send out email notifications ## Installing Prework -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. 2. Update the APT package cache and the software already installed on the Instance. ``` apt update && apt upgrade -y @@ -332,7 +332,7 @@ Mastodon requires access to a PostgreSQL database to store its configuration and 4. Select **No** when asked if you want to use Docker. Most of the other values are already pre-filled with the correct settings. Edit them if required for your setup. -5. Select **Amazon S3** as a service provider to set up Mastodon with Object Storage. Valid [API keys](/identity-and-access-management/iam/how-to/create-api-keys/) are required in this step. +5. Select **Amazon S3** as a service provider to set up Mastodon with Object Storage. Valid [API keys](/iam/how-to/create-api-keys/) are required in this step. Enter the details as follows: diff --git a/tutorials/matomo-analytics/index.mdx b/tutorials/matomo-analytics/index.mdx index b93b56fbc2..0fd83010c3 100644 --- a/tutorials/matomo-analytics/index.mdx +++ b/tutorials/matomo-analytics/index.mdx @@ -22,9 +22,9 @@ The tool is written in PHP and stores its data in a MySQL/MariaDB database. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) or later - `sudo` privileges or access to the root user ## Installing the LEMP-stack diff --git a/tutorials/migrate-data-minio-client/index.mdx b/tutorials/migrate-data-minio-client/index.mdx index 273400d861..7e532f9df5 100644 --- a/tutorials/migrate-data-minio-client/index.mdx +++ b/tutorials/migrate-data-minio-client/index.mdx @@ -19,14 +19,14 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) prov - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) -- [Object Storage buckets](/storage/object/how-to/create-a-bucket/) in two different regions +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) +- [Object Storage buckets](/object-storage/how-to/create-a-bucket/) in two different regions ## Installing the MinIO client -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) as `root` via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) as `root` via SSH. 2. Update the APT package cache and the software already installed on the Instance: ``` apt update && apt upgrade -y @@ -49,7 +49,7 @@ The [MinIO Client](https://min.io/docs/minio/linux/reference/minio-mc.html) prov ``` - Replace `` and `` with the credentials of your [API key](/identity-and-access-management/iam/how-to/create-api-keys/). + Replace `` and `` with the credentials of your [API key](/iam/how-to/create-api-keys/). 2. Optionally, add other providers: diff --git a/tutorials/migrate-data-rclone/index.mdx b/tutorials/migrate-data-rclone/index.mdx index deecbe32b0..6ad92e0303 100644 --- a/tutorials/migrate-data-rclone/index.mdx +++ b/tutorials/migrate-data-rclone/index.mdx @@ -19,15 +19,15 @@ Rclone provides a modern alternative to `rsync`. The tool communicates with any - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa -- At least 2 [Object Storage buckets](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa +- At least 2 [Object Storage buckets](/object-storage/how-to/create-a-bucket/) ## Installing Rclone -1. Connect to your server as `root` via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your server as `root` via [SSH](/instances/how-to/connect-to-instance/). 2. Update the APT package cache and the software already installed on the Instance. ``` apt update && apt upgrade -y @@ -201,7 +201,7 @@ Rclone provides a modern alternative to `rsync`. The tool communicates with any Enter a string value. Press Enter for the default (""). access_key_id> ``` -6. Enter your [API access key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) and hit enter. +6. Enter your [API access key](/organizations-and-projects/how-to/create-ssh-key/) and hit enter. The following output displays: ``` diff --git a/tutorials/migrate-databases-instance/index.mdx b/tutorials/migrate-databases-instance/index.mdx index c92edbe34d..dfd50432e7 100644 --- a/tutorials/migrate-databases-instance/index.mdx +++ b/tutorials/migrate-databases-instance/index.mdx @@ -17,7 +17,7 @@ dates: [Managed Database for PostgreSQL and MySQL](https://www.scaleway.com/en/database/) product provides reliable high-performance managed SQL database engines, both for PostgreSQL and MySQL. Using the service allows you to stay focused on the development of your applications and to benefit from Scaleway's expertise in the management of your database engines. -To migrate or import a database without an Instance, or using third-party tools, refer to [this procedure](/managed-databases/postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/). +To migrate or import a database without an Instance, or using third-party tools, refer to [this procedure](/managed-databases-for-postgresql-and-mysql/api-cli/import-data-to-managed-postgresql-databases/). In this guide, you will learn how to migrate your existing databases on your Database Instances using an intermediate host. @@ -30,10 +30,10 @@ This guide consists of two parts, depending on which database Engine your Instan - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A [Database](https://www.scaleway.com/en/database/) for PostgreSQL or MySQL -- An [Instance](/compute/instances/how-to/create-an-instance/) available as an intermediate host for the migration +- An [Instance](/instances/how-to/create-an-instance/) available as an intermediate host for the migration If you run your database in a Private Network with no public endpoint, you have to create the intermediate Instance in your Private Network and attach a NAT gateway to be able to reach the public Internet, and then run the migration steps from there. @@ -78,7 +78,7 @@ This guide consists of two parts, depending on which database Engine your Instan ### Preparing the Database for PostgreSQL - If you do not have a Database for PostgreSQL yet, [create a new one](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) from your [Scaleway console](https://console.scaleway.com/rdb/instances). + If you do not have a Database for PostgreSQL yet, [create a new one](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) from your [Scaleway console](https://console.scaleway.com/rdb/instances). 1. Enter the Database section of the [Scaleway console](https://console.scaleway.com/rdb/instances). @@ -141,7 +141,7 @@ Once you have created both, the destination database and its users, import your ### Preparing the Database for MySQL - If you do not have a Database for MySQL yet, [create a new one](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) from your [Scaleway console](https://console.scaleway.com/rdb/instances). + If you do not have a Database for MySQL yet, [create a new one](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) from your [Scaleway console](https://console.scaleway.com/rdb/instances). 1. Enter the Database section of the [Scaleway console](https://console.scaleway.com/rdb/instances). @@ -177,4 +177,4 @@ Once you have created both, the destination database and its users, import your ## Conclusion -You now have exported your existing PostgreSQL or MySQL database and imported it into a Scaleway Managed Datatabase Instance. To finish the migration process of your database, update the credentials and server information in the configuration files of your existing application. Once this information is updated, your application will use your database on Instances managed by Scaleway. For more information about the Database product, refer to the [product information page](https://www.scaleway.com/en/database/) and the [product documentation](/managed-databases/postgresql-and-mysql/quickstart/). \ No newline at end of file +You now have exported your existing PostgreSQL or MySQL database and imported it into a Scaleway Managed Datatabase Instance. To finish the migration process of your database, update the credentials and server information in the configuration files of your existing application. Once this information is updated, your application will use your database on Instances managed by Scaleway. For more information about the Database product, refer to the [product information page](https://www.scaleway.com/en/database/) and the [product documentation](/managed-databases-for-postgresql-and-mysql/quickstart/). \ No newline at end of file diff --git a/tutorials/migrate-dedibox-to-elastic-metal/index.mdx b/tutorials/migrate-dedibox-to-elastic-metal/index.mdx index e79970218d..22b2560dc6 100644 --- a/tutorials/migrate-dedibox-to-elastic-metal/index.mdx +++ b/tutorials/migrate-dedibox-to-elastic-metal/index.mdx @@ -21,10 +21,10 @@ We use Duplicity to encrypt the backup and upload it to Object Storage. Then we - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A Dedibox server -- [Created](/bare-metal/elastic-metal/how-to/create-server/) and [installed](/bare-metal/elastic-metal/how-to/install-server/) an Elastic Metal server +- [Created](/elastic-metal/how-to/create-server/) and [installed](/elastic-metal/how-to/install-server/) an Elastic Metal server ## Creating an Object Storage bucket diff --git a/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx b/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx index 94a58fb11f..0177ffc3d7 100644 --- a/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx +++ b/tutorials/migrate-mysql-databases-postgresql-pgloader/index.mdx @@ -23,15 +23,15 @@ In this tutorial, you learn how to migrate an existing remote MySQL database to - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A [Database Instance](https://www.scaleway.com/en/database/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later - `sudo` privileges or access to the root user ## Setting up pgLoader to migrate your databases -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache, and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx b/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx index e9240a5694..05b9b5b1b3 100644 --- a/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx +++ b/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx @@ -19,13 +19,13 @@ Whether you are new to Kubernetes or have some experience, this guide aims to si - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Basic knowledge and familiarity with Docker and Kubernetes concepts. - Access to your Docker images (locally or in a registry). - The following tools installed: - [Docker](https://docs.docker.com/get-docker/) - [kubectl](https://kubernetes.io/docs/tasks/tools/) - - [Scaleway CLI (optional but recommended)](/developer-tools/scaleway-cli/quickstart/) + - [Scaleway CLI (optional but recommended)](/scaleway-cli/quickstart/) ## Overview of Steps @@ -52,7 +52,7 @@ Before you begin the migration, take some time to: Your Kubernetes cluster needs access to your Docker images. You can use: -- [Scaleway Container Registry](/containers/container-registry/quickstart/) (recommended) +- [Scaleway Container Registry](/container-registry/quickstart/) (recommended) - Other registries (e.g., Docker Hub or GitHub Container Registry) ### 2.1 Create a namespace in Scaleway Container Registry @@ -67,7 +67,7 @@ Your Kubernetes cluster needs access to your Docker images. You can use: * The namespace's **Privacy Policies** - A namespace can either be [public or private](/containers/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. + A namespace can either be [public or private](/container-registry/concepts/#namespace-privacy-policies). Anyone will be able to pull container images from a public namespace. Privacy policies may be set at image level. 4. Click **Create namespace** to create the namespace. @@ -114,7 +114,7 @@ docker push rg..scw.cloud/my-apps/my-app:latest * Choose the geographical **region** for the cluster. * Select the control plane offer for your cluster. Options include shared or dedicated control planes. - Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). + Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/kubernetes/reference-content/kubernetes-control-plane-offers/). * Specify the **Kubernetes version** for your cluster. 4. Enter the **cluster's details**. Provide a name for the cluster. Optionally, you can add a description and tags for better organization. @@ -134,17 +134,17 @@ This section outlines the settings for your cluster pools. You can configure as * Choose an **Availability Zone** for the pool's nodes. * Select the **node type** for the pool. - Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/containers/kubernetes/concepts/#node) + Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/kubernetes/concepts/#node) * Configure the **system volume**. This volume contains the operating system of the nodes in your pool. * Configure **pool options**, including node count and whether to enable autoscaling. Options also include enabling autoheal and linking to a placement group, or you can retain default settings. - - Unsure about the autoheal feature? [Learn more about autoheal.](/containers/kubernetes/concepts/#autoheal) - - Need more information about placement groups? [Learn more about placement groups.](/compute/instances/concepts/#placement-groups) + - Unsure about the autoheal feature? [Learn more about autoheal.](/kubernetes/concepts/#autoheal) + - Need more information about placement groups? [Learn more about placement groups.](/instances/concepts/#placement-groups) * Enable full isolation, if required. - Need more information on full isolation? [Learn more about full isolation.](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) + Need more information on full isolation? [Learn more about full isolation.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) 2. Click **Add pool** to integrate the pool into the cluster. 3. To add more pools, click **Expand** and repeat the steps above. @@ -162,7 +162,7 @@ This section outlines the settings for your cluster pools. You can configure as 2. Click **Create cluster** to deploy your cluster. Once deployment is complete, the cluster appears in the clusters list. - Refer to the [How to create a Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) for more information. + Refer to the [How to create a Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) for more information. ### 3.2 Wait for the cluster to be ready @@ -282,7 +282,7 @@ kubectl get service my-app-service #### Set up Ingress Controller (Optional) -For advanced routing and SSL termination, [deploy an ingress controller](/containers/kubernetes/how-to/deploy-ingress-controller/) like **NGINX Ingress**. +For advanced routing and SSL termination, [deploy an ingress controller](/kubernetes/how-to/deploy-ingress-controller/) like **NGINX Ingress**. ```sh kubectl apply -f ``` @@ -369,7 +369,7 @@ kubectl apply -f hpa.yaml ### 9.1 Set up monitoring - Deploy monitoring tools like **Prometheus** and **Grafana**. -- Use **[Scaleway Cockpit](/observability/cockpit/quickstart/)** for basic monitoring and metrics. +- Use **[Scaleway Cockpit](/cockpit/quickstart/)** for basic monitoring and metrics. ### 9.2 Logging @@ -378,7 +378,7 @@ kubectl apply -f hpa.yaml ### 9.3 Regular updates -- Keep your [Kubernetes cluster](/containers/kubernetes/how-to/upgrade-kubernetes-version/) and applications up to date. +- Keep your [Kubernetes cluster](/kubernetes/how-to/upgrade-kubernetes-version/) and applications up to date. - Regularly check for updates to dependencies and security patches. ## Troubleshooting tips @@ -391,8 +391,8 @@ kubectl apply -f hpa.yaml ## Additional resources - **Scaleway Documentation**: - - [Kubernetes Kapsule Documentation](/containers/kubernetes/) - - [Scaleway Container Registry](/containers/container-registry/) + - [Kubernetes Kapsule Documentation](/kubernetes/) + - [Scaleway Container Registry](/container-registry/) - **Kubernetes Documentation**: - [Kubernetes Concepts](https://kubernetes.io/docs/concepts/) - [Kubectl Cheat Sheet](https://kubernetes.io/docs/reference/kubectl/cheatsheet/) diff --git a/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx b/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx index 252943912c..6212a4400b 100644 --- a/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx +++ b/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx @@ -13,13 +13,13 @@ dates: posted: 2024-11-13 --- -This guide provides a step-by-step process to help you migrate your existing Kubernetes clusters from other managed services like GKE (Google Kubernetes Engine), EKS (Amazon Elastic Kubernetes Service), or AKS (Azure Kubernetes Service) to **[Scaleway Kapsule](/containers/kubernetes/quickstart/)**. The migration aims to minimize downtime and ensure a smooth transition of your workloads. +This guide provides a step-by-step process to help you migrate your existing Kubernetes clusters from other managed services like GKE (Google Kubernetes Engine), EKS (Amazon Elastic Kubernetes Service), or AKS (Azure Kubernetes Service) to **[Scaleway Kapsule](/kubernetes/quickstart/)**. The migration aims to minimize downtime and ensure a smooth transition of your workloads. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Access to an existing Kubernetes cluster - Basic knowledge and familiarity with Kubernetes concepts and tools. - Installed the following tools: `kubectl`, `helm` (if used), and `scaleway CLI` (optional but recommended). @@ -111,7 +111,7 @@ Your new cluster will need access to your container images. 5. Click **Create a Namespace**. - Refer to the dedicated documentation [How to create a namespace](/containers/container-registry/how-to/create-namespace/) for detailed information how to create a Scaleway Container Registry namespace. + Refer to the dedicated documentation [How to create a namespace](/container-registry/how-to/create-namespace/) for detailed information how to create a Scaleway Container Registry namespace. ### 3.2 Authenticate Docker with Scaleway Registry @@ -167,7 +167,7 @@ To create and configure a new Kapsule Kubernetes cluster, follow the steps below * Choose the geographical **region** for the cluster. * Select the control plane offer for your cluster. Options include shared or dedicated control planes. - Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/containers/kubernetes/reference-content/kubernetes-control-plane-offers/). + Need help deciding on a control plane offer? Learn more about our [Kubernetes control plane offers](/kubernetes/reference-content/kubernetes-control-plane-offers/). * Specify the **Kubernetes version** for your cluster. 4. Enter the **cluster's details**. Provide a name for the cluster. Optionally, you can add a description and tags for better organization. @@ -185,17 +185,17 @@ To create and configure a new Kapsule Kubernetes cluster, follow the steps below * Choose an **Availability Zone** for the pool's nodes. * Select the **node type** for the pool. - Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/containers/kubernetes/concepts/#node) + Need advice on choosing a node type? [Learn more about Kubernetes nodes.](/kubernetes/concepts/#node) * Configure the **system volume**. This volume contains the operating system of the nodes in your pool. * Configure **pool options**, including node count and whether to enable autoscaling. Options also include enabling autoheal and linking to a placement group, or you can retain default settings. - - Unsure about the autoheal feature? [Learn more about autoheal.](/containers/kubernetes/concepts/#autoheal) - - Need more information about placement groups? [Learn more about placement groups.](/compute/instances/concepts/#placement-groups) + - Unsure about the autoheal feature? [Learn more about autoheal.](/kubernetes/concepts/#autoheal) + - Need more information about placement groups? [Learn more about placement groups.](/instances/concepts/#placement-groups) * Enable full isolation, if required. - Need more information on full isolation? [Learn more about full isolation.](/containers/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) + Need more information on full isolation? [Learn more about full isolation.](/kubernetes/reference-content/secure-cluster-with-private-network/#what-is-the-difference-between-controlled-isolation-and-full-isolation) 2. Click **Add pool** to integrate the pool into the cluster. 3. To add more pools, click **Expand** and repeat the steps above. @@ -279,12 +279,12 @@ Your existing manifests may contain cloud-provider-specific settings that need a #### Load Balancers -- Modify Service definitions of type `LoadBalancer` to use [Scaleway's Load Balancers](/network/load-balancer/quickstart/). Refer to our [annotations documentation](/containers/kubernetes/reference-content/using-load-balancer-annotations/). +- Modify Service definitions of type `LoadBalancer` to use [Scaleway's Load Balancers](/load-balancer/quickstart/). Refer to our [annotations documentation](/kubernetes/reference-content/using-load-balancer-annotations/). - Ensure annotations specific to other cloud providers are removed or replaced. #### Ingress controllers -- [Deploy an Ingress controller](/containers/kubernetes/how-to/deploy-ingress-controller/) compatible with Kapsule (e.g., NGINX Ingress Controller). +- [Deploy an Ingress controller](/kubernetes/how-to/deploy-ingress-controller/) compatible with Kapsule (e.g., NGINX Ingress Controller). #### Networking policies @@ -420,7 +420,7 @@ Conduct functional, performance, and end-to-end testing to verify the applicatio ### 12.1 Resource usage -- Monitor CPU, memory, and storage usage in [Scaleway Cockpit](/observability/cockpit/quickstart/). +- Monitor CPU, memory, and storage usage in [Scaleway Cockpit](/cockpit/quickstart/). - Adjust node pool sizes or autoscaling settings as needed. ### 12.2 Security @@ -460,15 +460,15 @@ Conduct functional, performance, and end-to-end testing to verify the applicatio - **Resource Quotas**: Check for any limitations in Scaleway that may affect deployments. - **Persistent Volume Issues**: Ensure storage classes and PVCs are correctly configured. - **Networking Problems**: Verify VPC configurations, network policies, and firewall rules. -- **Image Pull Errors**: Confirm that images are correctly tagged and accessible in [Scaleway Container Registry](/containers/container-registry/quickstart/). +- **Image Pull Errors**: Confirm that images are correctly tagged and accessible in [Scaleway Container Registry](/container-registry/quickstart/). ## Additional considerations ### Leveraging Scaleway features -- **Elastic Metal nodes**: For workloads requiring dedicated resources, consider adding [Production-Optimized or Workload-Optimized nodes](/compute/instances/reference-content/choosing-instance-type/) to your cluster. -- **Autoscaling**: Use cluster and [pod autoscaling](/containers/kubernetes/concepts/#autoscale) to handle variable workloads efficiently. -- **Private Networking**: Use [VPC and Private Networks](/network/vpc/quickstart/) for enhanced security. +- **Elastic Metal nodes**: For workloads requiring dedicated resources, consider adding [Production-Optimized or Workload-Optimized nodes](/instances/reference-content/choosing-instance-type/) to your cluster. +- **Autoscaling**: Use cluster and [pod autoscaling](/kubernetes/concepts/#autoscale) to handle variable workloads efficiently. +- **Private Networking**: Use [VPC and Private Networks](/vpc/quickstart/) for enhanced security. ### Cost management @@ -477,16 +477,16 @@ Conduct functional, performance, and end-to-end testing to verify the applicatio ### Security best practices -- **IAM policies**: Set up proper [access controls](/identity-and-access-management/iam/how-to/create-policy/). +- **IAM policies**: Set up proper [access controls](/iam/how-to/create-policy/). - **Regular updates**: Keep Kubernetes and applications up to date with security patches. - **Secrets management**: Use Kubernetes Secrets securely, and consider external secret management solutions if necessary. ## Additional resources - **Scaleway Documentation**: - - [Kubernetes Kapsule](/containers/kubernetes/) - - [Scaleway Container Registry](/containers/container-registry/) - - [Block Storage](/storage/block/) + - [Kubernetes Kapsule](/kubernetes/) + - [Scaleway Container Registry](/container-registry/) + - [Block Storage](/block-storage/) - **Kubernetes Documentation**: - [Kubernetes Official Documentation](https://kubernetes.io/docs/home/) - [Storage Classes](https://kubernetes.io/docs/concepts/storage/storage-classes/) diff --git a/tutorials/minikube-elastic-metal/index.mdx b/tutorials/minikube-elastic-metal/index.mdx index e5570aabb2..c7241f1dab 100644 --- a/tutorials/minikube-elastic-metal/index.mdx +++ b/tutorials/minikube-elastic-metal/index.mdx @@ -39,9 +39,9 @@ Minikube provides support for various essential Kubernetes features, including: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Elastic Metal server](/elastic-metal/how-to/create-server/) running on Ubuntu Bionic Beaver (18.04) ## Downloading and Installing Minikube diff --git a/tutorials/mist-streaming-server/index.mdx b/tutorials/mist-streaming-server/index.mdx index 9f7031c9eb..5b03495a38 100644 --- a/tutorials/mist-streaming-server/index.mdx +++ b/tutorials/mist-streaming-server/index.mdx @@ -19,14 +19,14 @@ MistServer is one of the leading OTT (internet streaming) toolkits with an open - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Installing Mist Server -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. ``` ssh root@your.instance.ip.address ``` diff --git a/tutorials/mlx-array-framework-apple-silicon/index.mdx b/tutorials/mlx-array-framework-apple-silicon/index.mdx index 238f5faa1c..78d9e66e30 100644 --- a/tutorials/mlx-array-framework-apple-silicon/index.mdx +++ b/tutorials/mlx-array-framework-apple-silicon/index.mdx @@ -31,8 +31,8 @@ Key features of MLX include: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Mac mini](/apple-silicon/how-to/create-mac-mini/) - Installed native Python >= 3.8 on the Mac (preinstalled by default) diff --git a/tutorials/mongodb-ubuntu-1604/index.mdx b/tutorials/mongodb-ubuntu-1604/index.mdx index 4566ae915c..88828d1eb2 100644 --- a/tutorials/mongodb-ubuntu-1604/index.mdx +++ b/tutorials/mongodb-ubuntu-1604/index.mdx @@ -20,13 +20,13 @@ In contrast to relational databases, MongoDB® does not require a deep predefine - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 24.O4 or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 24.O4 or later - `sudo` privileges or access to the root user - If you want to set up a MongoDB® Instance without worrying about the upkeep of compute resources, you can [create a Managed Databases for MongoDB® Instance](/managed-databases/mongodb/how-to/create-a-database-instance). These are powerful Database Instances managed by Scaleway. + If you want to set up a MongoDB® Instance without worrying about the upkeep of compute resources, you can [create a Managed Databases for MongoDB® Instance](/managed-mongodb-databases/how-to/create-a-database-instance). These are powerful Database Instances managed by Scaleway. ## Setting up MongoDB @@ -37,7 +37,7 @@ In contrast to relational databases, MongoDB® does not require a deep predefine You should always use the official MongoDB® `mongodb-org` packages, which are kept up-to-date with the most recent major and minor MongoDB® releases. -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. ``` ssh root@your.instance.ip.address ``` diff --git a/tutorials/monitor-gpu-instance-cockpit/index.mdx b/tutorials/monitor-gpu-instance-cockpit/index.mdx index 7ccde487ad..3e793385f3 100644 --- a/tutorials/monitor-gpu-instance-cockpit/index.mdx +++ b/tutorials/monitor-gpu-instance-cockpit/index.mdx @@ -13,14 +13,14 @@ dates: posted: 2024-10-21 --- -This tutorial guides you through the process of monitoring your [GPU Instances](/compute/instances/concepts/#gpu-instance) using Cockpit and the [NVIDIA Data Center GPU Manager (DCGM) Exporter](https://docs.nvidia.com/datacenter/cloud-native/gpu-telemetry/latest/dcgm-exporter.html). Visualize your GPU Instances' metrics and ensure optimal performance and usage of your resources. +This tutorial guides you through the process of monitoring your [GPU Instances](/instances/concepts/#gpu-instance) using Cockpit and the [NVIDIA Data Center GPU Manager (DCGM) Exporter](https://docs.nvidia.com/datacenter/cloud-native/gpu-telemetry/latest/dcgm-exporter.html). Visualize your GPU Instances' metrics and ensure optimal performance and usage of your resources. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [GPU Instance](/compute/gpu/how-to/create-manage-gpu-instance/) -- [Connected to your Instance via SSH](/compute/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [GPU Instance](/gpu/how-to/create-manage-gpu-instance/) +- [Connected to your Instance via SSH](/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance) - Installed [Docker Engine](https://docs.docker.com/engine/install/) and [Docker Compose](https://docs.docker.com/compose/install/linux/#install-using-the-repository) on your GPU Instance. ## Create a Cockpit data source and credentials @@ -29,7 +29,7 @@ This tutorial guides you through the process of monitoring your [GPU Instances]( We are creating a Cockpit data source because your GPU Instance's metrics will be stored in it and the exporter agent needs data source configuration information to then export your Instance's metrics. -1. Create a metrics [custom data source in Cockpit](/observability/cockpit/how-to/create-external-data-sources/). For the sake of this tutorial, we will name it `gpu-instance-metrics`. +1. Create a metrics [custom data source in Cockpit](/cockpit/how-to/create-external-data-sources/). For the sake of this tutorial, we will name it `gpu-instance-metrics`. - To fill in the cost estimator, you can assume that **1 metric sent without [specific cardinality](https://grafana.com/docs/tempo/latest/metrics-generator/cardinality/)** (ie. without labels or value duplication for a same metric) **every minute will generate around 50 000 samples per month** (60 minutes x 730 hours per month = 43 800 samples). By default, DCGM and node exporter will send multiple metrics and add labels to these metrics leading to a higher number of samples. @@ -39,7 +39,7 @@ We are creating a Cockpit data source because your GPU Instance's metrics will b ### Create a token -1. Create a [Cockpit token](/observability/cockpit/how-to/create-token/) from the [Scaleway console](https://console.scaleway.com/cockpit/tokens). +1. Create a [Cockpit token](/cockpit/how-to/create-token/) from the [Scaleway console](https://console.scaleway.com/cockpit/tokens). 2. Select a region for the data source. 3. Tick the **Push Metrics** box and click **Create token** to confirm. @@ -51,7 +51,7 @@ We are creating a Cockpit data source because your GPU Instance's metrics will b ### Install the NVIDIA DCGM Exporter, node exporter and Grafana Alloy agent on your GPU Instance -1. [Connect to your GPU Instance through SSH](/compute/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance). +1. [Connect to your GPU Instance through SSH](/gpu/how-to/create-manage-gpu-instance/#how-to-connect-to-a-gpu-instance). 2. Copy and paste the following command to create a configuration file named `config.alloy` in your Instance: ```sh touch config.alloy diff --git a/tutorials/monitor-k8s-grafana/index.mdx b/tutorials/monitor-k8s-grafana/index.mdx index a3d016448f..a6dd22a016 100644 --- a/tutorials/monitor-k8s-grafana/index.mdx +++ b/tutorials/monitor-k8s-grafana/index.mdx @@ -30,9 +30,9 @@ This tutorial will explain how to monitor your [Kubernetes Kapsule](https://www. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) -- A working [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) on your machine +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Kapsule cluster](/kubernetes/how-to/create-cluster/) +- A working [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) on your machine - Installed `helm` (version 3.2+), the Kubernetes [package manager](https://helm.sh/), on your local machine ## Preparing the Kubernetes Kapsule cluster diff --git a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx index d0bb4901eb..f915d2b3dd 100644 --- a/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx +++ b/tutorials/mutli-node-rocket-chat-community-private-network/index.mdx @@ -20,23 +20,23 @@ In this tutorial, you will learn how the Private Network feature can help you to Private Networks are a LAN-like layer 2 Ethernet network. A new network interface with a unique MAC address is configured on each Instance in a Private Network. You can use this interface to communicate in a secure and isolated network, using private IP addresses of your choice. -To reach the goal of this tutorial, you will use four [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/) running **Ubuntu 24.04 Noble Numbat** or later: +To reach the goal of this tutorial, you will use four [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/) running **Ubuntu 24.04 Noble Numbat** or later: - 1 POP2-2C-8G Instance as NGINX Proxy frontend, that distributes the load on the Rocket.Chat applications - 1 POP2-8C-32G Instance as MongoDB® host - 2 POP2-4C-16G Instances running the Rocket.Chat application -- A [Private Network](/network/vpc/quickstart/) between these Instances +- A [Private Network](/vpc/quickstart/) between these Instances - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- Created 4 [Instances](/compute/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- Created 4 [Instances](/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04 LTS) ## Configuring the Private Network @@ -49,7 +49,7 @@ To reach the goal of this tutorial, you will use four [Production-Optimized Inst 5. Add all Instances for your Rocket.Chat setup to the Private Network. Once added, they are listed on the network overview page together with their corresponding virtual MAC address: -6. Log into each of your Instances using [SSH](/compute/instances/how-to/connect-to-instance/) to configure the Private Network interface. Use the `ip link show` command to identify the automatically assigned name of the interface: +6. Log into each of your Instances using [SSH](/instances/how-to/connect-to-instance/) to configure the Private Network interface. Use the `ip link show` command to identify the automatically assigned name of the interface: ``` root@virtual-instance:~# ip link show 1: lo: mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 @@ -422,4 +422,4 @@ Once everything is set up and working, you can remove the public flexible IP add ## Conclusion -You have now configured a Rocket.Chat application based on several Instances and communicating internally using the Private Networks feature. The connection between these Instances is isolated from the internet and the internal network and only the Instances added to the Private Network can communicate with each other. For more advanced configuration options of Rocket.Chat, refer to the [official documentation](https://docs.rocket.chat/). More information about the Private Networks feature is available in our [feature documentation](/network/vpc/concepts/#private-networks). Do you have any remaining questions or suggestions? We welcome your feedback on Slack: [Scaleway Community](https://scaleway-community.slack.com/join/shared_invite/zt-19uuwgo5h-bofWNwE~jijt70lQkziQxg#/shared-invite/email). Join us in the `#private-network` chan. \ No newline at end of file +You have now configured a Rocket.Chat application based on several Instances and communicating internally using the Private Networks feature. The connection between these Instances is isolated from the internet and the internal network and only the Instances added to the Private Network can communicate with each other. For more advanced configuration options of Rocket.Chat, refer to the [official documentation](https://docs.rocket.chat/). More information about the Private Networks feature is available in our [feature documentation](/vpc/concepts/#private-networks). Do you have any remaining questions or suggestions? We welcome your feedback on Slack: [Scaleway Community](https://scaleway-community.slack.com/join/shared_invite/zt-19uuwgo5h-bofWNwE~jijt70lQkziQxg#/shared-invite/email). Join us in the `#private-network` chan. \ No newline at end of file diff --git a/tutorials/nats-rdb-offload/index.mdx b/tutorials/nats-rdb-offload/index.mdx index 95c1f92b6a..c5759072fe 100644 --- a/tutorials/nats-rdb-offload/index.mdx +++ b/tutorials/nats-rdb-offload/index.mdx @@ -28,22 +28,22 @@ We show how to provision all the required Scaleway resources using code examples This project exemplifies a decoupled architecture, where producer and consumer perform specific tasks independently. This kind of design is modular and allows for flexibility and scalability. It also adheres to the principles of microservices and serverless architectures, where individual functions or scripts focus on specific tasks. -To properly follow this tutorial, we recommend you [create a dedicated Project](/identity-and-access-management/organizations-and-projects/how-to/create-a-project/) in your Scaleway account. You can name it `RDB and NATS Tutorial`. It will hold all your Scaleway resources created for this tutorial, so they will be easier to find. +To properly follow this tutorial, we recommend you [create a dedicated Project](/organizations-and-projects/how-to/create-a-project/) in your Scaleway account. You can name it `RDB and NATS Tutorial`. It will hold all your Scaleway resources created for this tutorial, so they will be easier to find. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Installed the NATS CLI](https://github.com/nats-io/natscli) on your local machine -- [Created a Scaleway NATS account](/serverless/messaging/how-to/get-started/#how-to-create-a-nats-account) -- [Generated NATS credentials](/serverless/messaging/how-to/create-credentials/#how-to-create-credentials-for-a-nats-account) -- [Created a mySQL Managed Database](/managed-databases/postgresql-and-mysql/quickstart/) +- [Created a Scaleway NATS account](/messaging/how-to/get-started/#how-to-create-a-nats-account) +- [Generated NATS credentials](/messaging/how-to/create-credentials/#how-to-create-credentials-for-a-nats-account) +- [Created a mySQL Managed Database](/managed-databases-for-postgresql-and-mysql/quickstart/) ## Create a NATS stream -Refer to the [dedicated documentation](/serverless/messaging/api-cli/nats-cli/) to create your NATS stream. We recommend keeping your stream specifications as simple as possible. There is no need for replication or specific parameters for this tutorial. +Refer to the [dedicated documentation](/messaging/api-cli/nats-cli/) to create your NATS stream. We recommend keeping your stream specifications as simple as possible. There is no need for replication or specific parameters for this tutorial. -When your NATS server is up and running, check you did not forget anything for the Scaleway [context](/serverless/messaging/api-cli/nats-cli/#define-a-context) by running the following code in a new window of your terminal: +When your NATS server is up and running, check you did not forget anything for the Scaleway [context](/messaging/api-cli/nats-cli/#define-a-context) by running the following code in a new window of your terminal: ```bash nats context info scaleway @@ -198,7 +198,7 @@ To see the flow running, you can follow these steps: ## How to remove all resources used in the tutorial -To be sure that you are not running resources without using them, you can delete your database by following [this documentation](/managed-databases/postgresql-and-mysql/how-to/delete-a-database/). +To be sure that you are not running resources without using them, you can delete your database by following [this documentation](/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database/). You can also delete your NATS server with the following command in your terminal: diff --git a/tutorials/nextcloud-instantapp/index.mdx b/tutorials/nextcloud-instantapp/index.mdx index 1c74c40e57..0c26ec2b52 100644 --- a/tutorials/nextcloud-instantapp/index.mdx +++ b/tutorials/nextcloud-instantapp/index.mdx @@ -15,13 +15,13 @@ dates: In this tutorial, we show you how to deploy your personal cloud storage with the NextCloud InstantApp in seconds. NextCloud allows you to create self-hosted cloud storage to host files, folders, contacts, photo galleries, calendars, and more on your Instance. -Scaleway's NextCloud image is based on Ubuntu 22.04 LTS (Jammy Jellyfish), the NextCloud application, MariaDB as the database engine, and it uses database tuning according to [NextCloud's official recommendations](https://docs.nextcloud.com/server/27/admin_manual/configuration_database/linux_database_configuration.html#configuring-a-mysql-or-mariadb-database). By default, this image supports [routed IPs](/compute/instances/api-cli/using-routed-ips/). +Scaleway's NextCloud image is based on Ubuntu 22.04 LTS (Jammy Jellyfish), the NextCloud application, MariaDB as the database engine, and it uses database tuning according to [NextCloud's official recommendations](https://docs.nextcloud.com/server/27/admin_manual/configuration_database/linux_database_configuration.html#configuring-a-mysql-or-mariadb-database). By default, this image supports [routed IPs](/instances/api-cli/using-routed-ips/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Creating a NextCloud Instance @@ -35,14 +35,14 @@ Scaleway's NextCloud image is based on Ubuntu 22.04 LTS (Jammy Jellyfish), the N 8. Click **Create Instance** to launch your NextCloud Instance. - For detailed information about Instance creation, refer to the [create an Instance](/compute/instances/how-to/create-an-instance/) documentation. + For detailed information about Instance creation, refer to the [create an Instance](/instances/how-to/create-an-instance/) documentation. ## Configuring NextCloud When the Instance is running, you can see the Instance's IP address in the server list on the control panel. -1. Copy the IP address and open an [SSH session](/compute/instances/how-to/create-an-instance/) to find the database credentials required for NextCloud. +1. Copy the IP address and open an [SSH session](/instances/how-to/create-an-instance/) to find the database credentials required for NextCloud. 2. The MySQL user, password, and database name are shown in the MOTD message that displays upon your first connection to the server: ``` ################### NEXTCLOUD ################### @@ -87,7 +87,7 @@ You are now connected to your personal cloud storage and can start using it. ## Opening the mail ports to send emails - To prevent spam, our infrastructure does not allow access to remote mail ports by default. However, NextCloud requires the ability to send emails, so you must enable access to these ports. Your account needs to undergo a validation process before you can enable the SMTP ports. [Learn more about identity verification](/console/account/how-to/verify-identity/). + To prevent spam, our infrastructure does not allow access to remote mail ports by default. However, NextCloud requires the ability to send emails, so you must enable access to these ports. Your account needs to undergo a validation process before you can enable the SMTP ports. [Learn more about identity verification](/account/how-to/verify-identity/). 1. Click the **Security groups** tab on the Instances overview page. diff --git a/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx b/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx index 9e7cdb48ca..8735f5c688 100644 --- a/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx +++ b/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx @@ -22,9 +22,9 @@ You can either deploy your application: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Installed and initialized the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Installed and initialized the [Scaleway CLI](/scaleway-cli/quickstart/) - Installed [Docker Engine](https://docs.docker.com/engine/install/) - Installed [Node 18 or newer](https://nodejs.org/en/download) @@ -140,11 +140,11 @@ You can either deploy your application: ### Pushing the image to Scaleway Container Registry -1. Run the following command to create a [Container Registry namespace](/containers/container-registry/concepts/#namespace) and export its endpoint as a variable: +1. Run the following command to create a [Container Registry namespace](/container-registry/concepts/#namespace) and export its endpoint as a variable: ```bash export REGISTRY_ENDPOINT=$(scw registry namespace create -o json | jq -r '.endpoint') ``` -2. Log in to your [Container Registry](/containers/container-registry/concepts/#container-registry) from your local terminal: +2. Log in to your [Container Registry](/container-registry/concepts/#container-registry) from your local terminal: ```bash docker login $REGISTRY_ENDPOINT -u nologin --password-stdin <<< "$SCW_SECRET_KEY" ``` @@ -161,7 +161,7 @@ You can either deploy your application: ### Deploying the container with Scaleway Serverless Containers -1. Run the following command to create a [Serverless Containers namespace](/serverless/containers/concepts/#namespace) and export its ID as a variable: +1. Run the following command to create a [Serverless Containers namespace](/serverless-containers/concepts/#namespace) and export its ID as a variable: ```bash export CONTAINER_NAMESPACE_ID=$(scw container namespace create name="my-nextjs-blog-ns" -o json | jq -r '.id') ``` @@ -189,7 +189,7 @@ Your application cannot store any data persistently yet. We will now add a serve ### Setting up the database -1. Run the following command to create a [Serverless SQL Database](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) and export its attributes as variables: +1. Run the following command to create a [Serverless SQL Database](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) and export its attributes as variables: ```bash export PGHOST=$(scw sdb-sql database create name=tutorial-nextjs-blog-db cpu-min=0 cpu-max=4 -o json | jq -r '.endpoint' | cut -d "/" -f3 | cut -d ":" -f1 ) @@ -494,24 +494,24 @@ Note that this repository differs slightly in configuration, as it will dynamica Congratulations! You can already deploy your application by building a new container version, pushing it to the **Container Registry**, and deploying it to **Serverless Containers**. -However, your application would then connect with your [user credentials](/identity-and-access-management/iam/concepts/#user), which is not a recommended security practice. -To secure your deployment, we will now add a dedicated [IAM application](/identity-and-access-management/iam/concepts/#application), give it the minimum required permissions, and provide its credentials to your application. +However, your application would then connect with your [user credentials](/iam/concepts/#user), which is not a recommended security practice. +To secure your deployment, we will now add a dedicated [IAM application](/iam/concepts/#application), give it the minimum required permissions, and provide its credentials to your application. ## Secure and redeploy your application -1. Run the following command to create an [IAM application](/identity-and-access-management/iam/concepts/#application) and export it as a variable: +1. Run the following command to create an [IAM application](/iam/concepts/#application) and export it as a variable: ```bash export SCW_APPLICATION_ID=$(scw iam application create name=tutorial-nextjs-app -o json | jq -r '.id') ``` The `SCW_APPLICATION_ID` environment variable will store the IAM application ID so you can use it in later commands. -2. Create an [IAM policy](/identity-and-access-management/iam/concepts/#policy) giving your application rights to access the database: +2. Create an [IAM policy](/iam/concepts/#policy) giving your application rights to access the database: ```bash scw iam policy create application-id=$SCW_APPLICATION_ID name=tutorial-nextjs-policy rules.0.organization-id=$(scw config get default-organization-id) rules.0.permission-set-names.0=ServerlessSQLDatabaseFullAccess ``` The permission `ServerlessSQLDatabaseFullAccess` lets your application read and write data or create new databases. You can restrict this later to fit your database use cases, using `ServerlessSQLDatabaseRead` or `ServerlessSQLDatabaseReadWrite` permissions sets. -3. Create an [IAM API Key](/identity-and-access-management/iam/concepts/#api-key) and export its secret key as an environment variable: +3. Create an [IAM API Key](/iam/concepts/#api-key) and export its secret key as an environment variable: ```bash export SCW_APPLICATION_SECRET=$(scw iam api-key create application-id=$SCW_APPLICATION_ID -o json | jq -r '.secret_key') ``` @@ -561,7 +561,7 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi - You can display your **Serverless SQL Database** in the [Serverless SQL Databases section](https://console.scaleway.com/serverless-db/databases). -- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless/containers/how-to/manage-a-container/). +- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless-containers/how-to/manage-a-container/). ## Deploy a Next.js application using Terraform templates @@ -632,12 +632,12 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi ### Pushing the image containing your Next.js app -1. Run the following command to create a [Container Registry namespace](/containers/container-registry/concepts/#namespace) and export its endpoint as a variable: +1. Run the following command to create a [Container Registry namespace](/container-registry/concepts/#namespace) and export its endpoint as a variable: ```bash export REGISTRY_ENDPOINT=$(scw registry namespace create -o json | jq -r '.endpoint') ``` -2. Log in to your [Container Registry](/containers/container-registry/concepts/#container-registry) from your local terminal: +2. Log in to your [Container Registry](/container-registry/concepts/#container-registry) from your local terminal: ```bash docker login $REGISTRY_ENDPOINT -u nologin --password-stdin <<< "$SCW_SECRET_KEY" ``` @@ -765,15 +765,15 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi The Terraform file creates several resources: -- A [Serverless Containers namespace](/serverless/containers/concepts/#namespace), that contains a [Serverless Container](/serverless/containers/quickstart/), which hosts your Next.js application +- A [Serverless Containers namespace](/serverless-containers/concepts/#namespace), that contains a [Serverless Container](/serverless-containers/quickstart/), which hosts your Next.js application -- A [Serverless SQL Database](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) which stores posts data +- A [Serverless SQL Database](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) which stores posts data -- An [IAM policy](/identity-and-access-management/iam/concepts/#policy) which grants your application the right permissions +- An [IAM policy](/iam/concepts/#policy) which grants your application the right permissions -- An [IAM application](/identity-and-access-management/iam/concepts/#application), used as a principal for your IAM policy +- An [IAM application](/iam/concepts/#application), used as a principal for your IAM policy -- An [IAM API key](/identity-and-access-management/iam/concepts/#api-key) used as credentials to authenticate your application to the database +- An [IAM API key](/iam/concepts/#api-key) used as credentials to authenticate your application to the database ### Deploying the app with Terraform @@ -925,7 +925,7 @@ The Terraform file creates several resources: - You can display your **Serverless SQL Database** in the [Serverless SQL Databases section](https://console.scaleway.com/serverless-db/databases) -- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless/containers/how-to/manage-a-container/). +- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless-containers/how-to/manage-a-container/). - **Change the security configuration** for your container. It is currently public and anyone with the link can access it, but you can make it [private to require authentication](https://www.scaleway.com/en/developers/api/serverless-containers/#authentication). @@ -933,7 +933,7 @@ The Terraform file creates several resources: If you happen to encounter any issues, first check that you meet all the requirements. -- You have installed and configured the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/). Running the `scw account project get` command should return the following output: +- You have installed and configured the [Scaleway CLI](/scaleway-cli/quickstart/). Running the `scw account project get` command should return the following output: ``` ID example-7afa-4a5d-9f6c-27db072f1527 Name default @@ -949,4 +949,4 @@ If you happen to encounter any issues, first check that you meet all the require ``` Docker version 24.0.6, build ed223bc820 ``` -- You have the right [IAM permissions](/identity-and-access-management/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** and **ServerlessSQLDatabaseFullAccess**. \ No newline at end of file +- You have the right [IAM permissions](/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** and **ServerlessSQLDatabaseFullAccess**. \ No newline at end of file diff --git a/tutorials/nginx-reverse-proxy/index.mdx b/tutorials/nginx-reverse-proxy/index.mdx index 5fcbbfc30c..0d668f4d31 100644 --- a/tutorials/nginx-reverse-proxy/index.mdx +++ b/tutorials/nginx-reverse-proxy/index.mdx @@ -26,9 +26,9 @@ There are significant benefits to setting up an Nginx HTTPS reverse proxy: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver - A web application running on a non-standard web port on the Instance You can, for example, install a lightweight web server like [Webfsd](http://manpages.ubuntu.com/manpages/trusty/man1/webfsd.1.html), which runs on port 8000 by default to be reachable on the standard HTTP(s) ports via the proxy. - [Installed and configured Apache](/tutorials/configure-apache-lets-encrypt/#installing-apache) on your Instance diff --git a/tutorials/nvidia-triton/index.mdx b/tutorials/nvidia-triton/index.mdx index 75967228b7..2f675ea094 100644 --- a/tutorials/nvidia-triton/index.mdx +++ b/tutorials/nvidia-triton/index.mdx @@ -22,9 +22,9 @@ We will cover how to set up Triton Inference Server, store your model in an Obje - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A [GPU Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu GPU 12 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A [GPU Instance](/instances/how-to/create-an-instance/) running on Ubuntu GPU 12 - `sudo` privileges or access to the root user - Basic understanding of machine learning models and Docker @@ -35,7 +35,7 @@ In this step, we will create an Object Storage bucket on Scaleway and upload you For this tutorial, we will use a pre-trained model available in the Triton Inference Server model repository. You can replace this with your own model if desired. 1. Click **Object Storage** on the left side menu of the console. The Object Storage dashboard displays. -2. [Create a new bucket](/storage/object/how-to/create-a-bucket/) to store your model artifacts. +2. [Create a new bucket](/object-storage/how-to/create-a-bucket/) to store your model artifacts. 3. Download the example model repository from NVIDIA's GitHub to your local computer: ```bash git clone https://github.com/triton-inference-server/server.git @@ -46,7 +46,7 @@ For this tutorial, we will use a pre-trained model available in the Triton Infer ./fetch_models.sh ``` 5. Navigate to the `server/docs/examples/model_repository` directory within the cloned repository. -6. Upload the example model folder to your bucket in Scaleway Object Storage. You can use the [Scaleway Object Storage API](/storage/object/api-cli/using-api-call-list/), any Amazon S3-compatible tool, or web interface to upload the model folder. +6. Upload the example model folder to your bucket in Scaleway Object Storage. You can use the [Scaleway Object Storage API](/object-storage/api-cli/using-api-call-list/), any Amazon S3-compatible tool, or web interface to upload the model folder. You can use the `s3cmd` [command-line tool](/tutorials/s3cmd/) or any other Amazon S3-compatible tool to upload your data. @@ -64,7 +64,7 @@ For this tutorial, we will use a pre-trained model available in the Triton Infer ``` Replace `` and `` with the appropriate values for your Scaleway Object Storage setup. - When using S3, the credentials and default region can be passed by using either the [created AWS-CLI configuration file](/storage/object/api-cli/object-storage-aws-cli/) or via the respective environment variables. If the environment variables are set they will take a higher priority and will be used by Triton instead of the credentials set using the AWS-CLI configuration file. + When using S3, the credentials and default region can be passed by using either the [created AWS-CLI configuration file](/object-storage/api-cli/object-storage-aws-cli/) or via the respective environment variables. If the environment variables are set they will take a higher priority and will be used by Triton instead of the credentials set using the AWS-CLI configuration file. 4. Save the configuration file. @@ -114,9 +114,9 @@ Configure Triton to export metrics in Prometheus format by adding the following } ] ``` - Replace `` and `` with your Cockpit [token credentials](/observability/cockpit/how-to/create-token/). + Replace `` and `` with your Cockpit [token credentials](/cockpit/how-to/create-token/). -Your metrics are now pushed to Cockpit and you can [access Grafana](/observability/cockpit/how-to/access-grafana-and-managed-dashboards/) to visualize them. +Your metrics are now pushed to Cockpit and you can [access Grafana](/cockpit/how-to/access-grafana-and-managed-dashboards/) to visualize them. ## Conclusion diff --git a/tutorials/object-storage-s3fs/index.mdx b/tutorials/object-storage-s3fs/index.mdx index 2825b61f89..f1b378286a 100644 --- a/tutorials/object-storage-s3fs/index.mdx +++ b/tutorials/object-storage-s3fs/index.mdx @@ -13,13 +13,13 @@ dates: posted: 2018-07-16 --- -In this tutorial you learn how to use [s3fs](https://github.com/s3fs-fuse/s3fs-fuse) as a client for [Scaleway Object Storage](/storage/object/concepts/#object-storage). `s3fs` is a FUSE-backed file interface for S3, allowing you to mount Object Storage buckets on your local Linux or macOS system. Files are preserved in their native object format, enabling compatibility with tools like AWS CLI. +In this tutorial you learn how to use [s3fs](https://github.com/s3fs-fuse/s3fs-fuse) as a client for [Scaleway Object Storage](/object-storage/concepts/#object-storage). `s3fs` is a FUSE-backed file interface for S3, allowing you to mount Object Storage buckets on your local Linux or macOS system. Files are preserved in their native object format, enabling compatibility with tools like AWS CLI. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Installing s3fs diff --git a/tutorials/odoo-easy-deploy/index.mdx b/tutorials/odoo-easy-deploy/index.mdx index 68da62e5ae..0cba310556 100644 --- a/tutorials/odoo-easy-deploy/index.mdx +++ b/tutorials/odoo-easy-deploy/index.mdx @@ -19,14 +19,14 @@ categories: Are you prepared to elevate your business operations using the capabilities of open-source technology? Look no further than Odoo! This collection of business applications, coded in Python, encompasses a wide range of functionalities, including website development, e-commerce, HR management, and accounting, all conveniently bundled into an accessible and cost-effective package. With a user base exceeding 2 million worldwide, enterprises of all scales are capitalizing on Odoo's harmonious integration and modular structure to streamline their processes and enhance their profitability. -But how can you initiate your Odoo journey? Our guide will walk you through the process of setting up Odoo on a [Scaleway Kubernetes Kapsule](/containers/kubernetes/quickstart/) using the [easy-deploy](/containers/kubernetes/how-to/enable-easy-deploy/) feature, easily accessible right from the [Scaleway console](https://console.scaleway.com). In minimal time, you will have Odoo up and operational, primed to advance your business endeavors. Just adhere to the steps outlined in the sidebar on the right to get started. +But how can you initiate your Odoo journey? Our guide will walk you through the process of setting up Odoo on a [Scaleway Kubernetes Kapsule](/kubernetes/quickstart/) using the [easy-deploy](/kubernetes/how-to/enable-easy-deploy/) feature, easily accessible right from the [Scaleway console](https://console.scaleway.com). In minimal time, you will have Odoo up and operational, primed to advance your business endeavors. Just adhere to the steps outlined in the sidebar on the right to get started. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [Docker](https://www.docker.com/) on your local computer ## Creating a Scaleway Container Registry namespace @@ -49,7 +49,7 @@ But how can you initiate your Odoo journey? Our guide will walk you through the 1. Open a terminal window on your local machine, and log in to your namespace with Docker. - Replace `odoo-tutorial-namespace` with the name of your namespace and $SCW_SECRET_KEY with the corresponding [secret key](/identity-and-access-management/iam/how-to/create-api-keys/). + Replace `odoo-tutorial-namespace` with the name of your namespace and $SCW_SECRET_KEY with the corresponding [secret key](/iam/how-to/create-api-keys/). ``` @@ -80,7 +80,7 @@ But how can you initiate your Odoo journey? Our guide will walk you through the 2. Click **Create a cluster**. 3. Enter the required information: - - **Cluster type**: select one between [Kapsule](/containers/kubernetes/concepts/#kubernetes-kapsule) or [Kosmos (Multi-AZ)](/containers/kubernetes/concepts/#kubernetes-kosmos) + - **Cluster type**: select one between [Kapsule](/kubernetes/concepts/#kubernetes-kapsule) or [Kosmos (Multi-AZ)](/kubernetes/concepts/#kubernetes-kosmos) - **Cluster name**: any identifying name of your choice (must contain only alphanumeric characters and dashes) - **Cluster description** a description for your cluster - **Region**: a geographical region for your cluster. diff --git a/tutorials/odoo/index.mdx b/tutorials/odoo/index.mdx index 03da2f043f..1fd638f5bb 100644 --- a/tutorials/odoo/index.mdx +++ b/tutorials/odoo/index.mdx @@ -25,12 +25,12 @@ This tutorial will show you how to deploy Odoo 16 on a Scaleway machine running - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - One of the following remote machines running Ubuntu Noble Numbat (24.04 LTS): - - An [Instance](/compute/instances/how-to/create-an-instance/) - - An [Elastic Metal server](/bare-metal/elastic-metal/how-to/create-server/) - - A [Dedibox dedicated server](/dedibox/dedicated-servers/how-to/order-a-server/) + - An [Instance](/instances/how-to/create-an-instance/) + - An [Elastic Metal server](/elastic-metal/how-to/create-server/) + - A [Dedibox dedicated server](/dedicated-servers/how-to/order-a-server/) - Configured an A-record pointing to your server's IP address - `sudo` privileges or access to the root user diff --git a/tutorials/openvpn-instant-app/index.mdx b/tutorials/openvpn-instant-app/index.mdx index 4707164e14..d85f7a65a4 100644 --- a/tutorials/openvpn-instant-app/index.mdx +++ b/tutorials/openvpn-instant-app/index.mdx @@ -25,18 +25,18 @@ OpenVPN InstantApp comes with: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - Installed a VPN client on your local machine 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. 2. Click **Create Instance**. The [Instance creation wizard](https://console.scaleway.com/instance/servers/create) displays. 3. Choose the **OpenVPN** image in the **InstantApps** tab: -4. Follow the remaining steps to [create your Instance](/compute/instances/how-to/create-an-instance/). +4. Follow the remaining steps to [create your Instance](/instances/how-to/create-an-instance/). ## Create a VPN user -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. You see the following message: +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. You see the following message: ``` ############################################################################### # SCALEWAY OPENVPN INSTANTAPP # diff --git a/tutorials/overleaf/index.mdx b/tutorials/overleaf/index.mdx index 256384eaa2..92f9369bb4 100644 --- a/tutorials/overleaf/index.mdx +++ b/tutorials/overleaf/index.mdx @@ -20,9 +20,9 @@ It is particularly favored by academics and professionals for producing scientif - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) with Docker installed and at least **30 GB of storage** +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) with Docker installed and at least **30 GB of storage** - Installed `git` on your Instance - Properly configured DNS A/AAAA records pointing to your Instance's public IP diff --git a/tutorials/pihole-vpn/index.mdx b/tutorials/pihole-vpn/index.mdx index 33fa235af7..322e75991d 100644 --- a/tutorials/pihole-vpn/index.mdx +++ b/tutorials/pihole-vpn/index.mdx @@ -21,13 +21,13 @@ To secure the connection, we use the PiVPN tool to install an OpenVPN virtual Pr - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Deploying the Instance 1. Log in to your Scaleway console and [create a new Instance](https://console.scaleway.com/instance/servers/create). For this tutorial, we use a [PLAY2-NANO](https://console.scaleway.com/instance/servers/create?imageKey=3f1b9623-71ba-4fe3-b994-27fcdaa850ba&offerName=PLAY2-NANO&zone=fr-par-1) Instance running on Ubuntu Focal Fossa (20.04 LTS). -2. Log into the newly created Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +2. Log into the newly created Instance using [SSH](/instances/how-to/connect-to-instance/). 3. Update the cache of the APT package manager and upgrade the software already installed on the server: ``` apt update && apt upgrade -y diff --git a/tutorials/plausible-analytics-ubuntu/index.mdx b/tutorials/plausible-analytics-ubuntu/index.mdx index 972a0dd755..9bf5bbcbab 100644 --- a/tutorials/plausible-analytics-ubuntu/index.mdx +++ b/tutorials/plausible-analytics-ubuntu/index.mdx @@ -18,15 +18,15 @@ Plausible Analytics is an open-source web analytics initiative driven by the goa This tool significantly contributes to the enhancement of site performance, with its analytics script weighing in at less than 1 KB. This is 45 times smaller than the size tag of a typical commercial analytics solution. Plausible Analytics is intentionally designed for self-hosting through Docker, providing you with control over your analytics setup. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) 1. Log into your Instance using SSH: ``` diff --git a/tutorials/postgis-managed-databases/index.mdx b/tutorials/postgis-managed-databases/index.mdx index cbc29afac4..1aac24af3a 100644 --- a/tutorials/postgis-managed-databases/index.mdx +++ b/tutorials/postgis-managed-databases/index.mdx @@ -26,7 +26,7 @@ The answers to these frequently asked questions used to be provided by specializ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [Database Instance](https://www.scaleway.com/en/database/) ## Creating a new database for PostGIS diff --git a/tutorials/postman-api/index.mdx b/tutorials/postman-api/index.mdx index c4af8d9fa1..ebdf23afb7 100644 --- a/tutorials/postman-api/index.mdx +++ b/tutorials/postman-api/index.mdx @@ -27,8 +27,8 @@ In this tutorial, you will learn how to import Scaleway APIs into Postman, confi - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - An account logged into [Postman](https://www.postman.com/postman-account/) ## Importing Scaleway APIs into Postman diff --git a/tutorials/powerdns-ubuntu-bionic/index.mdx b/tutorials/powerdns-ubuntu-bionic/index.mdx index d4618defb1..08d6a00343 100644 --- a/tutorials/powerdns-ubuntu-bionic/index.mdx +++ b/tutorials/powerdns-ubuntu-bionic/index.mdx @@ -19,9 +19,9 @@ PowerDNS runs on most Linux distributions, including Ubuntu. This tutorial demon - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- At least 2 [Instances](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- At least 2 [Instances](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) ## Installing PowerDNS diff --git a/tutorials/prestashop-dedibox/index.mdx b/tutorials/prestashop-dedibox/index.mdx index 34f6693271..59d7dbaaf1 100644 --- a/tutorials/prestashop-dedibox/index.mdx +++ b/tutorials/prestashop-dedibox/index.mdx @@ -23,8 +23,8 @@ In this tutorial, you will learn how to install and configure PrestaShop on Ubun - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - A [Dedibox](https://www.scaleway.com/en/dedibox/) server running Ubuntu Jammy Jellyfish (22.04 LTS) - PHP version 7.4 or 8.0 installed (PrestaShop 8.x is not compatible with PHP 8.1, which is the default for Ubuntu 22.04). - MariaDB or MySQL database installed and configured. diff --git a/tutorials/processing-images-structured-outputs-pixtral/index.mdx b/tutorials/processing-images-structured-outputs-pixtral/index.mdx index 263908a3ca..3d6442cc88 100644 --- a/tutorials/processing-images-structured-outputs-pixtral/index.mdx +++ b/tutorials/processing-images-structured-outputs-pixtral/index.mdx @@ -25,8 +25,8 @@ This tutorial will guide you through the process of using the Pixtral vision mod - A Scaleway account logged into the [console](https://console.scaleway.com) - A Python environment (version 3.7 or higher) -- An API key from Scaleway [Identity and Access Management](/identity-and-access-management/iam/) -- Access to a Scaleway [Managed Inference](/ai-data/managed-inference/reference-content/pixtral-12b-2409/) endpoint with Pixtral deployed or to Scaleway [Generative APIs](/ai-data/generative-apis/quickstart/) service +- An API key from Scaleway [Identity and Access Management](/iam/) +- Access to a Scaleway [Managed Inference](/managed-inference/reference-content/pixtral-12b-2409/) endpoint with Pixtral deployed or to Scaleway [Generative APIs](/generative-apis/quickstart/) service - The `openai` and `pydantic` Python libraries installed ## Setting up the environment diff --git a/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx b/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx index d7bf48e378..028f5ccdf6 100644 --- a/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx +++ b/tutorials/prometheus-monitoring-grafana-dashboard/index.mdx @@ -21,12 +21,12 @@ In this tutorial, you will learn how to use a Prometheus Monitoring Instance wit - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on [Ubuntu Focal Fossa (20.04 LTS)](https://www.ubuntu.com/) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on [Ubuntu Focal Fossa (20.04 LTS)](https://www.ubuntu.com/) or later - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). ## Preparing your environment diff --git a/tutorials/protect-server-fail2ban/index.mdx b/tutorials/protect-server-fail2ban/index.mdx index d7ca6c279a..aeace30966 100644 --- a/tutorials/protect-server-fail2ban/index.mdx +++ b/tutorials/protect-server-fail2ban/index.mdx @@ -20,9 +20,9 @@ In this tutorial, you will learn how to configure the service on an Ubuntu Bioni - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An Ubuntu Bionic [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An Ubuntu Bionic [Instance](/instances/how-to/create-an-instance/) - `sudo` privileges or access to the root user ## Installing Fail2Ban @@ -41,7 +41,7 @@ In this tutorial, you will learn how to configure the service on an Ubuntu Bioni Make sure to replace `me@mydomain.tld` with your actual email address. - To receive notifications by email, it is required that the [email ports are unlocked](/compute/instances/how-to/send-emails-from-your-instance/). + To receive notifications by email, it is required that the [email ports are unlocked](/instances/how-to/send-emails-from-your-instance/). ## Configuring Fail2Ban diff --git a/tutorials/protect-server-using-crowdsec/index.mdx b/tutorials/protect-server-using-crowdsec/index.mdx index f6975c610d..c8105985f3 100644 --- a/tutorials/protect-server-using-crowdsec/index.mdx +++ b/tutorials/protect-server-using-crowdsec/index.mdx @@ -26,9 +26,9 @@ In this tutorial, we will set up [CrowdSec](https://crowdsec.net/) on a Dedibox - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created](/dedibox/dedicated-servers/how-to/order-a-server/) a Dedibox server and [installed Debian](/dedibox/dedicated-servers/how-to/install-a-server/) on it -- [Connected](/dedibox/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh) to your Dedibox via SSH as `root` +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created](/dedicated-servers/how-to/order-a-server/) a Dedibox server and [installed Debian](/dedicated-servers/how-to/install-a-server/) on it +- [Connected](/dedicated-servers/how-to/connect-to-server/#connecting-via-ssh) to your Dedibox via SSH as `root` - Installed [Docker](https://www.docker.com/) on your Dedibox ## Installing CrowdSec diff --git a/tutorials/proxmox-softraid/index.mdx b/tutorials/proxmox-softraid/index.mdx index 44995045c0..c95a56ed20 100644 --- a/tutorials/proxmox-softraid/index.mdx +++ b/tutorials/proxmox-softraid/index.mdx @@ -23,12 +23,12 @@ The tool provides a REST-API as well as a graphical web interface to manage the - A Dedibox account logged into the [console](https://console.online.net) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Dedibox](https://www.scaleway.com/en/dedibox/) with [KVM-over-IP](/dedibox/kvm-over-ip/concepts/#kvm-over-ip) access +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Dedibox](https://www.scaleway.com/en/dedibox/) with [KVM-over-IP](/dedibox-kvm-over-ip/concepts/#kvm-over-ip) access ## Installing Proxmox -1. Create a [KVM-over-IP](/dedibox/kvm-over-ip/quickstart/) session from your [Dedibox console](https://console.online.net/). +1. Create a [KVM-over-IP](/dedibox-kvm-over-ip/quickstart/) session from your [Dedibox console](https://console.online.net/). 2. Mount the Proxmox ISO, available on the server [virtualmedia.online.net](http://virtualmedia.online.net). The mounting procedure may differ slightly depending on the KVM module of your Dedibox. The instructions for Proxmox VE 6 can be found [here](https://virtualmedia.online.net/proxmox/proxmox-ve_6.0-1.iso). 3. Boot the server from the ISO file by choosing the virtual CD-ROM drive in the boot options. 4. The Proxmox [EULA](https://www.gnu.org/licenses/agpl-3.0.html) displays. Agree to it by clicking **I agree**. A summary of the Proxmox installer displays. @@ -81,4 +81,4 @@ Once the server has rebooted, the Proxmox web interface is available. ## Going further - [Deploy and Manage virtual machines with Proxmox](/tutorials/configure-failover-proxmox/) -- [Failover IP configuration for VMs on Dedibox servers](/dedibox-network/ip-failover/quickstart/) \ No newline at end of file +- [Failover IP configuration for VMs on Dedibox servers](/dedibox-ip-failover/quickstart/) \ No newline at end of file diff --git a/tutorials/proxy-protocol-v2-load-balancer/index.mdx b/tutorials/proxy-protocol-v2-load-balancer/index.mdx index ac21733915..1af1f9c734 100644 --- a/tutorials/proxy-protocol-v2-load-balancer/index.mdx +++ b/tutorials/proxy-protocol-v2-load-balancer/index.mdx @@ -21,9 +21,9 @@ This tutorial shows you how and why to enable Proxy Protocol on your Scaleway Lo - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Created and configured a Load Balancer](/network/load-balancer/how-to/create-load-balancer/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Created and configured a Load Balancer](/load-balancer/how-to/create-load-balancer/) ## Do I need to enable Proxy Protocol on my Load Balancer? @@ -62,9 +62,9 @@ Note that Proxy Protocol is more commonly activated for Load Balancers using TCP ## Enabling Proxy Protocol on your Load Balancer -You can enable Proxy Protocol for your Load Balancer when you [create your Load Balancer's backend](/network/load-balancer/how-to/create-frontends-backends/), or after creation by [editing a backend](/network/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks). Proxy protocol is one of the basic backend settings you are prompted to configure. +You can enable Proxy Protocol for your Load Balancer when you [create your Load Balancer's backend](/load-balancer/how-to/create-frontends-backends/), or after creation by [editing a backend](/load-balancer/how-to/manage-frontends-and-backends/#how-to-edit-backends-and-health-checks). Proxy protocol is one of the basic backend settings you are prompted to configure. -See our advanced documentation on [configuring backends](/network/load-balancer/reference-content/configuring-backends/#proxy-protocol) for full information about the different Proxy Protocol versions available, and the configuration process. +See our advanced documentation on [configuring backends](/load-balancer/reference-content/configuring-backends/#proxy-protocol) for full information about the different Proxy Protocol versions available, and the configuration process. ## Configuring your backend web server for Proxy Protocol diff --git a/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx b/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx index eacf3bf6d6..d715e1c3e5 100644 --- a/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx +++ b/tutorials/pushing-metrics-logs-from-scw-instance/index.mdx @@ -14,22 +14,22 @@ dates: posted: 2023-06-28 --- -This page shows you how to push your metrics and logs from a [Scaleway Instance](/compute/instances/concepts/#instance). You can also use this tutorial to **push metrics and logs from external Instances (i.e. Instances outside of Scaleway)**. +This page shows you how to push your metrics and logs from a [Scaleway Instance](/instances/concepts/#instance). You can also use this tutorial to **push metrics and logs from external Instances (i.e. Instances outside of Scaleway)**. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - - Having the default configuration on your agents might lead to more of your resources’ metrics being sent, a high consumption, and a high bill at the end of the month. Find out [how to avoid additional costs when using Cockpit](/observability/cockpit/reference-content/understanding-cockpit-usage/). + - Having the default configuration on your agents might lead to more of your resources’ metrics being sent, a high consumption, and a high bill at the end of the month. Find out [how to avoid additional costs when using Cockpit](/cockpit/reference-content/understanding-cockpit-usage/). - Sending metrics and logs for Scaleway resources or personal data using an external path is a billable feature. In addition, any data that you push yourself is billed, even if you send data from Scaleway products. Refer to the [product pricing](https://www.scaleway.com/en/pricing/?tags=available,managedservices-observability-cockpit) for more information. ## Configure your environment -1. [Create an Instance](/compute/instances/how-to/create-an-instance/) from the **Compute** section of the Scaleway console. +1. [Create an Instance](/instances/how-to/create-an-instance/) from the **Compute** section of the Scaleway console. 2. Copy your Instance's public IP as you will need it in the next steps. 3. Open a terminal and type the following command to connect to your Instance: @@ -51,7 +51,7 @@ The `tuto-cockpit-instance` directory contains a `workshop` folder with several - `nginx.conf` specifies server settings - `run.sh` executes the Grafana agent with the specified configuration file (agent.yaml). -The only file we will be editing in this tutorial is the `agent.yaml` file to add your Cockpit [token](/observability/cockpit/concepts/#tokens). +The only file we will be editing in this tutorial is the `agent.yaml` file to add your Cockpit [token](/cockpit/concepts/#tokens). 1. Open another terminal and type the following command to clone our `tuto-cockpit-instance` directory on your local machine: @@ -97,7 +97,7 @@ The only file we will be editing in this tutorial is the `agent.yaml` file to ad ## Configure the Grafana agent file and push your data -1. [Generate a token](/observability/cockpit/how-to/create-token/) and select the push permissions for metrics and logs. Make sure you note down your token's secret key as you will need it in the following steps. +1. [Generate a token](/cockpit/how-to/create-token/) and select the push permissions for metrics and logs. Make sure you note down your token's secret key as you will need it in the following steps. 2. In the same terminal where you are connected to your Instance, run the following command to download the Grafana agent: ```bash bash ./download.sh diff --git a/tutorials/remote-desktop-with-xrdp/index.mdx b/tutorials/remote-desktop-with-xrdp/index.mdx index 9dafa28bb1..4153fc0b8e 100644 --- a/tutorials/remote-desktop-with-xrdp/index.mdx +++ b/tutorials/remote-desktop-with-xrdp/index.mdx @@ -26,9 +26,9 @@ In this tutorial, you will learn how to install the [xRDP](http://xrdp.org/) ser - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu - `sudo` privileges or access to the root user ## Installing the desktop environment diff --git a/tutorials/restic-s3-backup/index.mdx b/tutorials/restic-s3-backup/index.mdx index fc96bdb553..d99189c261 100644 --- a/tutorials/restic-s3-backup/index.mdx +++ b/tutorials/restic-s3-backup/index.mdx @@ -22,12 +22,12 @@ In this tutorial, you learn how to backup a Scaleway Instance running on Ubuntu - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) -- [Installed and configured the AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/) to use with Scaleway Object Storage -- [Created an Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) +- [Installed and configured the AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/) to use with Scaleway Object Storage +- [Created an Object Storage bucket](/object-storage/how-to/create-a-bucket/) ## Installing Restic @@ -52,7 +52,7 @@ In this tutorial, you learn how to backup a Scaleway Instance running on Ubuntu A repository is the storage space where your backups will be hosted. In this tutorial, we will use Scaleway Object Storage buckets to host our backups. -1. Set up your [environment variables](/developer-tools/scaleway-cli/reference-content/environment-variables/), if you have not done so yet. Replace `$SCW_ACCESS_KEY` and `$SCW_SECRET_KEY` with their corresponding values. +1. Set up your [environment variables](/scaleway-cli/reference-content/environment-variables/), if you have not done so yet. Replace `$SCW_ACCESS_KEY` and `$SCW_SECRET_KEY` with their corresponding values. ``` export AWS_ACCESS_KEY_ID=$SCW_ACCESS_KEY export AWS_SECRET_ACCESS_KEY=$SCW_SECRET_KEY @@ -90,7 +90,7 @@ created restic repository da8e38a165 at s3:https://s3.fr-par.scw.cloud/ - By default, the backups you create are stored using `STANDARD` [storage class](/storage/object/concepts/#storage-class). If you want to use a different storage class, you can add the `-o s3.storage-class=` option to your command, as shown below: + By default, the backups you create are stored using `STANDARD` [storage class](/object-storage/concepts/#storage-class). If you want to use a different storage class, you can add the `-o s3.storage-class=` option to your command, as shown below: ``` restic -r s3:https://s3.fr-par.scw.cloud/ backup -o s3.storage-class=ONEZONE_IA ~/ ``` diff --git a/tutorials/rtmp-self-hosted-streaming/index.mdx b/tutorials/rtmp-self-hosted-streaming/index.mdx index 8aa431d398..1f789a3170 100644 --- a/tutorials/rtmp-self-hosted-streaming/index.mdx +++ b/tutorials/rtmp-self-hosted-streaming/index.mdx @@ -22,19 +22,19 @@ For individuals craving absolute control over their content, open-source solutio Using the open-source [RTMP protocol](https://en.wikipedia.org/wiki/Real-Time_Messaging_Protocol) on self-hosted streaming servers, users gain autonomy to manage their content free from external constraints and interruptions. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) ## Setting up the server -1. Log into the Instance via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Log into the Instance via [SSH](/instances/how-to/connect-to-instance/). 2. Update the apt sources lists and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/ruby-on-rails/index.mdx b/tutorials/ruby-on-rails/index.mdx index e8810bf661..1b389418ae 100644 --- a/tutorials/ruby-on-rails/index.mdx +++ b/tutorials/ruby-on-rails/index.mdx @@ -33,9 +33,9 @@ In this tutorial, you will learn basic steps to configure a deployment-ready mac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) or [Elastic Metal server](/bare-metal/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) or [Elastic Metal server](/elastic-metal/quickstart/#how-to-create-an-elastic-metal-server) running on Ubuntu Jammy Jellyfish (22.04 LTS) - `sudo` privileges or access to the root user ## Installing rbenv and Node.js diff --git a/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx b/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx index 6ea70d3636..f20ec87544 100644 --- a/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx +++ b/tutorials/run-manage-linux-vm-on-apple-silicon-tart/index.mdx @@ -28,8 +28,8 @@ This service not only offers 2-3 times better performance but also does so at a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Created a Mac mini](/bare-metal/apple-silicon/how-to/create-mac-mini/) running macOS 13.0 (Ventura) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Created a Mac mini](/apple-silicon/how-to/create-mac-mini/) running macOS 13.0 (Ventura) or later - Installed a package manager In this tutorial, we will use [Homebrew](https://brew.sh/index), which is a popular package manager for macOS. diff --git a/tutorials/run-messaging-platform-with-rocketchat/index.mdx b/tutorials/run-messaging-platform-with-rocketchat/index.mdx index 1442e7e5a3..894c85c84e 100644 --- a/tutorials/run-messaging-platform-with-rocketchat/index.mdx +++ b/tutorials/run-messaging-platform-with-rocketchat/index.mdx @@ -20,9 +20,9 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) - A domain name pointed to your Instance - `sudo` privileges or access to the root user diff --git a/tutorials/run-nodejs-express-server-on-serverless-containers/index.mdx b/tutorials/run-nodejs-express-server-on-serverless-containers/index.mdx index 12b3d49723..d69efe6416 100644 --- a/tutorials/run-nodejs-express-server-on-serverless-containers/index.mdx +++ b/tutorials/run-nodejs-express-server-on-serverless-containers/index.mdx @@ -21,8 +21,8 @@ In this tutorial you will learn how to configure your [Express.js](http://expres - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Serverless Containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Serverless Containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) - Installed [Node.js](https://nodejs.org/en/), [NPM](https://www.npmjs.com/), and [Docker](https://www.docker.com/) on your computer ## Creating an Express.js application @@ -151,7 +151,7 @@ To Dockerize our simple web app, we will use the official Node.js image. ```sh docker build . -t ``` -2. [Push](/containers/container-registry/how-to/push-images/) the created image into the [Container Registry](/containers/container-registry/quickstart/) linked to your Containers namespace +2. [Push](/container-registry/how-to/push-images/) the created image into the [Container Registry](/container-registry/quickstart/) linked to your Containers namespace The registry name starts with `funcscw` + the namespace name. @@ -159,4 +159,4 @@ To Dockerize our simple web app, we will use the official Node.js image. ## Conclusion -You have built, pushed, and deployed your first web application using Node.js and Express Server on Scaleway Serverless Containers. For more information about the Containers product, refer to our [dedicated product documentation](/serverless/containers/quickstart/). +You have built, pushed, and deployed your first web application using Node.js and Express Server on Scaleway Serverless Containers. For more information about the Containers product, refer to our [dedicated product documentation](/serverless-containers/quickstart/). diff --git a/tutorials/run-python-flask-server-on-serverless-container/index.mdx b/tutorials/run-python-flask-server-on-serverless-container/index.mdx index f2d99a3d09..1dc20dd4a4 100644 --- a/tutorials/run-python-flask-server-on-serverless-container/index.mdx +++ b/tutorials/run-python-flask-server-on-serverless-container/index.mdx @@ -19,8 +19,8 @@ Flask is a Python framework that enables you to easily deploy simple web servers - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Serverless Containers namespace](/serverless/containers/how-to/create-manage-delete-containers-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Serverless Containers namespace](/serverless-containers/how-to/create-manage-delete-containers-namespace/) - Installed [Python 3](https://www.python.org/downloads/), [pip](https://pypi.org/project/pip/), and [Docker](https://www.docker.com/) on your computer ## Creating a Flask application @@ -134,8 +134,8 @@ To Dockerize our simple web app, we will use the official Python 3 Alpine image ```sh docker build . -t ``` -2. [Push](/containers/container-registry/how-to/push-images/) the created image into the [container registry](/containers/container-registry/quickstart/) linked to your Containers namespace +2. [Push](/container-registry/how-to/push-images/) the created image into the [container registry](/container-registry/quickstart/) linked to your Containers namespace The registry name starts with `funcscw` + the namespace name. -3. [Deploy the image using the Scaleway console](/serverless/containers/how-to/deploy-container/). \ No newline at end of file +3. [Deploy the image using the Scaleway console](/serverless-containers/how-to/deploy-container/). \ No newline at end of file diff --git a/tutorials/s3-customize-url-cname/index.mdx b/tutorials/s3-customize-url-cname/index.mdx index 3f22787a1c..169225b6ff 100644 --- a/tutorials/s3-customize-url-cname/index.mdx +++ b/tutorials/s3-customize-url-cname/index.mdx @@ -22,11 +22,11 @@ In this tutorial, we show you how to use CNAME to map a domain or subdomain to a - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Access to the [DNS zone](/network/domains-and-dns/concepts/#dns-zone) of your domain name +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Access to the [DNS zone](/domains-and-dns/concepts/#dns-zone) of your domain name -1. From the Scaleway console, [create a new bucket](/storage/object/how-to/create-a-bucket/). When entering a name for your bucket, the name must be the same as the domain/subdomain you intend to use with the bucket. For example, to create a bucket accessible at `download.example.com` the bucket name must be `download.example.com`. -2. Set the bucket ACL with [AWS-CLI](/storage/object/api-cli/object-storage-aws-cli/): +1. From the Scaleway console, [create a new bucket](/object-storage/how-to/create-a-bucket/). When entering a name for your bucket, the name must be the same as the domain/subdomain you intend to use with the bucket. For example, to create a bucket accessible at `download.example.com` the bucket name must be `download.example.com`. +2. Set the bucket ACL with [AWS-CLI](/object-storage/api-cli/object-storage-aws-cli/): ``` aws s3api put-bucket-acl --bucket download.example.com --acl public-read ``` diff --git a/tutorials/s3cmd/index.mdx b/tutorials/s3cmd/index.mdx index 5ff2be2b8b..e1c91171e2 100644 --- a/tutorials/s3cmd/index.mdx +++ b/tutorials/s3cmd/index.mdx @@ -13,13 +13,13 @@ dates: posted: 2018-06-04 --- -In this tutorial, you will learn how to use [s3cmd](https://github.com/s3tools/s3cmd) as a client for [Scaleway Object Storage](/storage/object/concepts/#object-storage). `s3cmd` is a tool that allows you to create, list and delete buckets from the command line, as well as to download, upload, and delete objects to/from your buckets. +In this tutorial, you will learn how to use [s3cmd](https://github.com/s3tools/s3cmd) as a client for [Scaleway Object Storage](/object-storage/concepts/#object-storage). `s3cmd` is a tool that allows you to create, list and delete buckets from the command line, as well as to download, upload, and delete objects to/from your buckets. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Installing s3cmd @@ -60,7 +60,7 @@ Carry out the following commands from your terminal. ```bash nano .s3cfg ``` -3. Copy and paste the following text into the file, then save and close. Make sure you use the `host-base`, `host-bucket`, and `bucket_location` details of your own bucket (visible in the **Bucket settings** tab of the console). You will also need to replace `` and `` with your [own API credentials](/identity-and-access-management/iam/how-to/create-api-keys/). +3. Copy and paste the following text into the file, then save and close. Make sure you use the `host-base`, `host-bucket`, and `bucket_location` details of your own bucket (visible in the **Bucket settings** tab of the console). You will also need to replace `` and `` with your [own API credentials](/iam/how-to/create-api-keys/). ```bash [default] # Object Storage Region NL-AMS @@ -91,7 +91,7 @@ Carry out the following steps from the terminal. cd $HOME touch .s3cfg-fr-par ``` -3. Copy and paste the following text into the file, then save and close. Make sure you replace `` and `` with your [own API credentials](/identity-and-access-management/iam/how-to/create-api-keys/). +3. Copy and paste the following text into the file, then save and close. Make sure you replace `` and `` with your [own API credentials](/iam/how-to/create-api-keys/). ```bash [default] signature = s3v4 @@ -251,7 +251,7 @@ s3cmd delcors s3://bucketname ``` - It is currently not possible to get the CORS configuration of a bucket with `s3cmd`. It is recommended to use [aws-cli](/storage/object/api-cli/bucket-operations/#getbucketcors) to get the CORS settings of a bucket. + It is currently not possible to get the CORS configuration of a bucket with `s3cmd`. It is recommended to use [aws-cli](/object-storage/api-cli/bucket-operations/#getbucketcors) to get the CORS settings of a bucket. ## Going further diff --git a/tutorials/self-hosted-repository-gitea/index.mdx b/tutorials/self-hosted-repository-gitea/index.mdx index d5f3084387..6e973e3b51 100644 --- a/tutorials/self-hosted-repository-gitea/index.mdx +++ b/tutorials/self-hosted-repository-gitea/index.mdx @@ -24,9 +24,9 @@ While Git was initially developed for software development purposes, it can trac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later ## Installing Gitea diff --git a/tutorials/sem-terraform/index.mdx b/tutorials/sem-terraform/index.mdx index dde0ea306d..01f49a0a30 100644 --- a/tutorials/sem-terraform/index.mdx +++ b/tutorials/sem-terraform/index.mdx @@ -15,14 +15,14 @@ dates: posted: 2024-06-03 --- -In this tutorial, you will use a Terraform configuration file that builds your entire infrastructure, such as a [Database Instance](/managed-databases/postgresql-and-mysql/concepts/#database-instance), a [secret](/identity-and-access-management/secret-manager/concepts/#secret), and a [version](/identity-and-access-management/secret-manager/concepts/#version) in which your database credentials are stored. You will then be able to access your database credentials securely from the Scaleway console. +In this tutorial, you will use a Terraform configuration file that builds your entire infrastructure, such as a [Database Instance](/managed-databases-for-postgresql-and-mysql/concepts/#database-instance), a [secret](/secret-manager/concepts/#secret), and a [version](/secret-manager/concepts/#version) in which your database credentials are stored. You will then be able to access your database credentials securely from the Scaleway console. - A Scaleway account logged into the [console](https://console.scaleway.com/) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- [Created an SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- [Created an SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Clone the GitHub repository and configure your environment variables @@ -60,7 +60,7 @@ examples/ ``` - The `key-value` folder contains two additional folders named `app` and `infra`. -- The `app` folder will interact with the database and ask [Secret Manager](/identity-and-access-management/secret-manager/concepts/#secret-manager) for the password to connect to the database. +- The `app` folder will interact with the database and ask [Secret Manager](/secret-manager/concepts/#secret-manager) for the password to connect to the database. - The `infra` folder contains the files that will configure your database and secret. ## Build and deploy your infrastructure diff --git a/tutorials/send-emails-tem-serverless-framework/index.mdx b/tutorials/send-emails-tem-serverless-framework/index.mdx index 2f61b6b8e1..444061a82e 100644 --- a/tutorials/send-emails-tem-serverless-framework/index.mdx +++ b/tutorials/send-emails-tem-serverless-framework/index.mdx @@ -16,13 +16,13 @@ dates: posted: 2024-02-01 --- -In this tutorial, you will learn how to send emails with [Transactional Email](/managed-services/transactional-email/quickstart/) and [Serverless Functions](/serverless/functions/quickstart/) using the [Serverless Framework tool](/serverless/functions/reference-content/deploy-function/#serverless-framework). +In this tutorial, you will learn how to send emails with [Transactional Email](/transactional-email/quickstart/) and [Serverless Functions](/serverless-functions/quickstart/) using the [Serverless Framework tool](/serverless-functions/reference-content/deploy-function/#serverless-framework). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain with Transactional Email and added SPF, DKIM, and MX records](/managed-services/transactional-email/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain with Transactional Email and added SPF, DKIM, and MX records](/transactional-email/quickstart/) - [Installed the Scaleway CLI](https://github.com/scaleway/scaleway-cli) on your machine ## Install and clone the necessary tools @@ -84,7 +84,7 @@ The `go-mail` directory you have cloned contains a `.env` file in which you will 4. Click the **Endpoints** tab and copy your function's domain. Make sure you save it as you will need it in the next steps. 5. Click the **Security** tab, then click **+ Generate token**. - Find out [how to restrict access](/serverless/functions/how-to/secure-a-function/#restrict-access-to-your-functions) to your functions. + Find out [how to restrict access](/serverless-functions/how-to/secure-a-function/#restrict-access-to-your-functions) to your functions. 6. Follow the instructions that display in the pop-up and click **Generate token**. 7. Copy your token and make sure that you save it before closing the pop-up. diff --git a/tutorials/send-emails-with-serverless-and-tem/index.mdx b/tutorials/send-emails-with-serverless-and-tem/index.mdx index d724a5eb33..93647e329b 100644 --- a/tutorials/send-emails-with-serverless-and-tem/index.mdx +++ b/tutorials/send-emails-with-serverless-and-tem/index.mdx @@ -16,13 +16,13 @@ dates: posted: 2023-04-27 --- -In this tutorial, you will learn how to send emails with [Transactional Email](/managed-services/transactional-email/quickstart/) and [Serverless Functions](/serverless/functions/quickstart/) using a Terraform configuration file that builds your entire infrastructure, such as a Serverless Function and a website with a registration page hosted on an Object Storage bucket. It also allows you to configure SPF, DKIM, and MX records on your sending domain. +In this tutorial, you will learn how to send emails with [Transactional Email](/transactional-email/quickstart/) and [Serverless Functions](/serverless-functions/quickstart/) using a Terraform configuration file that builds your entire infrastructure, such as a Serverless Function and a website with a registration page hosted on an Object Storage bucket. It also allows you to configure SPF, DKIM, and MX records on your sending domain. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [domain name](/network/domains-and-dns/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [domain name](/domains-and-dns/quickstart/) - [Installed Terraform](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) ## Clone the GitHub repository diff --git a/tutorials/send-sms-iot-device-twilio/index.mdx b/tutorials/send-sms-iot-device-twilio/index.mdx index 553d124523..8bbef4ddac 100644 --- a/tutorials/send-sms-iot-device-twilio/index.mdx +++ b/tutorials/send-sms-iot-device-twilio/index.mdx @@ -34,7 +34,7 @@ We are going to do things in reverse order: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Getting Twilio credentials @@ -121,4 +121,4 @@ Let's say we want the Hub to trigger our function when a message is published on 2. To simulate your sensor device write `my-home/alert` in the `Topic` box and click `Publish`. 3. Verify on your phone that the message was received. - For more information about Scaleway IoT Hub refer to our [product documentation](/managed-services/iot-hub/concepts/). \ No newline at end of file + For more information about Scaleway IoT Hub refer to our [product documentation](/iot-hub/concepts/). \ No newline at end of file diff --git a/tutorials/sentry-error-tracking/index.mdx b/tutorials/sentry-error-tracking/index.mdx index 175ecb52d1..e7769a22ac 100644 --- a/tutorials/sentry-error-tracking/index.mdx +++ b/tutorials/sentry-error-tracking/index.mdx @@ -23,7 +23,7 @@ Crafted using Python, Sentry employs a client/server architecture that facilitat With Sentry as your ally, you can streamline your development workflow, enhance your applications, and provide your users with the seamless experience they desire. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/production-optimized/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/production-optimized/). You can find all reports on a dashboard, which makes it easy to triage the problem, how often it occurs, its impact on the user experience, which part of your code causes the problem, and so on. @@ -33,9 +33,9 @@ This tutorial details how to set up a [Sentry](https://sentry.io/welcome/) self- - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04 LTS) Sentry requires at least 8 GB of RAM to run. We recommend, therefore, that you use a Scaleway Instance with at least 4 CPU cores, 8 GB of RAM, and 20 GB of available disk space to follow this tutorial. diff --git a/tutorials/set-up-spf-dkim-for-dns-providers/index.mdx b/tutorials/set-up-spf-dkim-for-dns-providers/index.mdx index 5d1b7e02a9..1bec57cae4 100644 --- a/tutorials/set-up-spf-dkim-for-dns-providers/index.mdx +++ b/tutorials/set-up-spf-dkim-for-dns-providers/index.mdx @@ -14,13 +14,13 @@ dates: posted: 2022-11-07 --- -In this tutorial, you will learn how to set up [SPF](/managed-services/transactional-email/concepts/#spf-record) and [DKIM](/managed-services/transactional-email/concepts/#dkim-record) records with Transactional Email for other DNS providers such as [GoDaddy](https://www.godaddy.com/), [Cloudflare](https://www.cloudflare.com/) and [Namecheap](https://www.namecheap.com/). +In this tutorial, you will learn how to set up [SPF](/transactional-email/concepts/#spf-record) and [DKIM](/transactional-email/concepts/#dkim-record) records with Transactional Email for other DNS providers such as [GoDaddy](https://www.godaddy.com/), [Cloudflare](https://www.cloudflare.com/) and [Namecheap](https://www.namecheap.com/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured your domain(s) with Transactional Email](/managed-services/transactional-email/how-to/configure-domain-with-transactional-email/). +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured your domain(s) with Transactional Email](/transactional-email/how-to/configure-domain-with-transactional-email/). - Domain names with GoDaddy, Cloudflare, and/or Namecheap ## Configure DNS settings for GoDaddy diff --git a/tutorials/set-up-yunohost-debian/index.mdx b/tutorials/set-up-yunohost-debian/index.mdx index b1a1de0679..0ea5ac3dee 100644 --- a/tutorials/set-up-yunohost-debian/index.mdx +++ b/tutorials/set-up-yunohost-debian/index.mdx @@ -18,14 +18,14 @@ Yunohost is an open-source solution designed for the administration of a persona - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Debian 11 (Bullseye) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Debian 11 (Bullseye) - A domain name pointed to your Instance ## Installing Yunohost -1. Connect to the Instance via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to the Instance via [SSH](/instances/how-to/connect-to-instance/). 2. Update the APT package cache and the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/setting-up-tunnel/index.mdx b/tutorials/setting-up-tunnel/index.mdx index 9e736532d4..4e66bd2f2b 100644 --- a/tutorials/setting-up-tunnel/index.mdx +++ b/tutorials/setting-up-tunnel/index.mdx @@ -23,10 +23,10 @@ The [Generic Routing Encapsulation (GRE)](https://en.wikipedia.org/wiki/Generic_ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) -- [Ordered](/dedibox/dedicated-servers/how-to/order-a-server/) and [installed](/dedibox/dedicated-servers/how-to/install-a-server/) a Dedibox Dedicated server +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) +- [Ordered](/dedicated-servers/how-to/order-a-server/) and [installed](/dedicated-servers/how-to/install-a-server/) a Dedibox Dedicated server - Configured your SSH key on both machines - `sudo` privileges or access to the root user diff --git a/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx b/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx index 57d7067a3b..41407498f8 100644 --- a/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx +++ b/tutorials/setup-ampere-ai-framework-arm-instances/index.mdx @@ -23,8 +23,8 @@ In this tutorial, we will walk through the process of setting up and using Amper - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) ## Setting up the COP-ARM Instance @@ -42,7 +42,7 @@ In this tutorial, we will walk through the process of setting up and using Amper 5. Adjust the size of your system volume to meet the needs of your models. 6. Leave the default IP settings, ensuring that a public IPv4 address is assigned to the Instance. 7. Enter a name for your Instance to easily identify it, or use the default suggested name. -8. Verify your SSH key fingerprint is shown. If not, click **Add SSH key** and paste the SSH key you have [pre-generated](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) for secure access to the Instance. +8. Verify your SSH key fingerprint is shown. If not, click **Add SSH key** and paste the SSH key you have [pre-generated](/organizations-and-projects/how-to/create-ssh-key/) for secure access to the Instance. 9. Review the cost estimation, and click **Create Instance** to proceed. The Instance may take a few minutes to start. Once it is up and running, copy its public IP address. ## Installing an Ampere-optimized AI framework diff --git a/tutorials/setup-cockroachdb-cluster/index.mdx b/tutorials/setup-cockroachdb-cluster/index.mdx index c05d4a9239..e79a235247 100644 --- a/tutorials/setup-cockroachdb-cluster/index.mdx +++ b/tutorials/setup-cockroachdb-cluster/index.mdx @@ -19,9 +19,9 @@ In this tutorial, you will gain knowledge on how to deploy a multi-node Cockroac - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 16.04 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 16.04 ## What is CockroachDB and why you should use it @@ -50,7 +50,7 @@ Below you find a schema of the architecture of CockroachDB: ## Installation of CockroachDB -1. [Spin up](/compute/instances/how-to/create-an-instance/) at least three Instances to guarantee redundancy and fault tolerance. We use [Ubuntu Xenial (16.04)](https://www.ubuntu.com/) in this example. +1. [Spin up](/instances/how-to/create-an-instance/) at least three Instances to guarantee redundancy and fault tolerance. We use [Ubuntu Xenial (16.04)](https://www.ubuntu.com/) in this example. 2. Once the servers have booted we install CockroachDB on them: ``` wget -qO- https://binaries.cockroachdb.com/cockroach-latest.linux-amd64.tgz | tar xvz diff --git a/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx b/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx index 40ab8e5df8..1a9b0b8392 100644 --- a/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx +++ b/tutorials/setup-elastic-metal-proxmox-cluster-with-private-networks/index.mdx @@ -19,9 +19,9 @@ Proxmox Virtual Environment (Proxmox VE) is a server virtualization platform, ba - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - At least 2 [Elastic Metal servers](https://www.scaleway.com/en/dedibox/) -- Created a [Private Network](/bare-metal/elastic-metal/how-to/use-private-networks/) and [attached](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-attach-and-detach-elastic-metal-servers-to-a-private-network) your Elastic Metal servers to it +- Created a [Private Network](/elastic-metal/how-to/use-private-networks/) and [attached](/elastic-metal/how-to/use-private-networks/#how-to-attach-and-detach-elastic-metal-servers-to-a-private-network) your Elastic Metal servers to it ## Installing Proxmox @@ -59,7 +59,7 @@ Once the server has rebooted, the Proxmox web interface is available. ## Configuring the Private Network -Instead of [configuring the Private Network interface directly from your server's command line](/bare-metal/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks), we must configure it using the Proxmox interface. +Instead of [configuring the Private Network interface directly from your server's command line](/elastic-metal/how-to/use-private-networks/#how-to-configure-the-network-interface-on-your-elastic-metal-server-for-private-networks), we must configure it using the Proxmox interface. 1. Click the Proxmox host in the data center menu on the left. The server's dashboard displays. 2. Click **Network** in the **System** section of the menu. The network dashboard displays. @@ -70,7 +70,7 @@ Instead of [configuring the Private Network interface directly from your server' * **Name**: The name of your primary network interface followed by a dot and the VLAN ID of your Private Network (e.g. `eno1.1918` for the primary network interface `eno1` and the VLAN ID `1918`) * **IPv4/CIDR**: The IP address of the machine in your Private Network followed by its CIDR netmask (e.g. `192.168.1.101/24`) - * **(Optional) Gateway (IPv4)**: The IP address of your [Public Gateway](/network/public-gateways/concepts/#public-gateway), if you want to use one. + * **(Optional) Gateway (IPv4)**: The IP address of your [Public Gateway](/public-gateways/concepts/#public-gateway), if you want to use one. * **Autostart**: Tick this box to automatically bring up the interface during system startup. 5. Click **Create** to create the Private Network interface. diff --git a/tutorials/setup-jupyter-notebook/index.mdx b/tutorials/setup-jupyter-notebook/index.mdx index 37d3ccb843..378d1776e2 100644 --- a/tutorials/setup-jupyter-notebook/index.mdx +++ b/tutorials/setup-jupyter-notebook/index.mdx @@ -26,14 +26,14 @@ This evolutionary journey has seen Jupyter expand its horizons to provide suppor - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user ## Setting up a remote Jupyter Notebook on a GPU Instance -1. Deploy a new [GPU Instance](/compute/instances/how-to/create-an-instance/) with the [Ubuntu ML](https://www.scaleway.com/en/imagehub/) image from the [Scaleway console](https://console.scaleway.com). -2. [Log in to](/compute/instances/how-to/connect-to-instance/) the Instance using SSH. +1. Deploy a new [GPU Instance](/instances/how-to/create-an-instance/) with the [Ubuntu ML](https://www.scaleway.com/en/imagehub/) image from the [Scaleway console](https://console.scaleway.com). +2. [Log in to](/instances/how-to/connect-to-instance/) the Instance using SSH. 3. Update the apt repositories list and upgrade the packages already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/setup-k8s-cluster-rancher/index.mdx b/tutorials/setup-k8s-cluster-rancher/index.mdx index 7973b88faa..7307cdf02d 100644 --- a/tutorials/setup-k8s-cluster-rancher/index.mdx +++ b/tutorials/setup-k8s-cluster-rancher/index.mdx @@ -22,9 +22,9 @@ The Rancher UI makes it easy to manage secrets, roles, and permissions. It allow - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- [Configured a domain name](/network/domains-and-dns/quickstart/) (i.e. `rancher.example.com`) pointing to the first Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- [Configured a domain name](/domains-and-dns/quickstart/) (i.e. `rancher.example.com`) pointing to the first Instance ### Spinning up the required Instances @@ -39,7 +39,7 @@ The Rancher UI makes it easy to manage secrets, roles, and permissions. It allow ### Installing Rancher -1. Log into the first Instance (`rancher1`) via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Log into the first Instance (`rancher1`) via [SSH](/instances/how-to/connect-to-instance/). 2. Launch the following command to fetch the docker image `rancher/rancher` to run in a container with automatic restarting enabled, in case the container fails. Edit the value `rancher.example.com` with the personalized domain name pointing to the Instance to generate a Let's Encrypt certificate automatically: ``` docker run -d --restart=unless-stopped -p 80:80 -p 443:443 -v /host/rancher:/var/lib/rancher rancher/rancher --acme-domain rancher.example.com diff --git a/tutorials/setup-lamp-stack-ubuntu2204/index.mdx b/tutorials/setup-lamp-stack-ubuntu2204/index.mdx index b41c6c1a57..ede0084497 100644 --- a/tutorials/setup-lamp-stack-ubuntu2204/index.mdx +++ b/tutorials/setup-lamp-stack-ubuntu2204/index.mdx @@ -20,15 +20,15 @@ The concept describes a server environment that consists of a Linux operating sy - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Jammy Jellyfish (22.04) - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address - `sudo` privileges or access to the root user ## Installing the LAMP stack on an Ubuntu 22.04 Instance -1. [Connect to your Instance via SSH](/compute/instances/how-to/connect-to-instance/). +1. [Connect to your Instance via SSH](/instances/how-to/connect-to-instance/). 2. Use the `apt` package manager of Ubuntu to install the required packages. Make sure that the system is up-to-date and has the latest bug fixes and updates installed by running the following command: ```bash apt update && apt -y upgrade diff --git a/tutorials/setup-minecraft/index.mdx b/tutorials/setup-minecraft/index.mdx index 08e586563e..7cf1404042 100644 --- a/tutorials/setup-minecraft/index.mdx +++ b/tutorials/setup-minecraft/index.mdx @@ -46,19 +46,19 @@ The Minecraft server is a Java application and runs perfectly on [Scaleway Insta - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later - `sudo` privileges or access to the root user - A copy of the [Minecraft game client](https://www.minecraft.net/en-us/) for your local computer -Deploying your own Minecraft server can be done in a few easy steps on a [Scaleway Development Instance](https://www.scaleway.com/en/cost-optimized-instances/). In case you do not have an Instance yet, start by [deploying your first Instance](/compute/instances/how-to/create-an-instance/). +Deploying your own Minecraft server can be done in a few easy steps on a [Scaleway Development Instance](https://www.scaleway.com/en/cost-optimized-instances/). In case you do not have an Instance yet, start by [deploying your first Instance](/instances/how-to/create-an-instance/). - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the `apt` package cache and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/setup-mongodb-on-ubuntu/index.mdx b/tutorials/setup-mongodb-on-ubuntu/index.mdx index b8bc97da02..4814e48c6f 100644 --- a/tutorials/setup-mongodb-on-ubuntu/index.mdx +++ b/tutorials/setup-mongodb-on-ubuntu/index.mdx @@ -17,18 +17,18 @@ dates: Diverging from traditional relational databases, MongoDB® users no longer need an intricate predefined schema before adding data. This flexibility stems from its ability to modify schemas at any point in time. Embracing the NoSQL philosophy, it employs JSON-like documents for data storage, allowing the insertion of diverse and arbitrary data. -Powerful [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/) comes with the compute and storage capabilities you need to run your MongoDB® Instance smoothly. +Powerful [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/) comes with the compute and storage capabilities you need to run your MongoDB® Instance smoothly. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Noble Numbat (24.04) or later - `sudo` privileges or access to the root user ## Setting up MongoDB @@ -39,7 +39,7 @@ Powerful [Production-Optimized Instance](/compute/instances/reference-content/ch Always use the official MongoDB `mongodb-org` packages, to make sure you have the latest, up-to-date major and minor MongoDB releases. -1. [Connect to your Instance](/compute/instances/how-to/connect-to-instance/) via SSH. +1. [Connect to your Instance](/instances/how-to/connect-to-instance/) via SSH. ``` ssh root@your.instance.ip.address ``` diff --git a/tutorials/setup-moodle/index.mdx b/tutorials/setup-moodle/index.mdx index bffb713d06..c76b30e672 100644 --- a/tutorials/setup-moodle/index.mdx +++ b/tutorials/setup-moodle/index.mdx @@ -21,10 +21,10 @@ This tutorial shows you how to create your own learning platform by installing M - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) or later -- A [domain or subdomain](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04 LTS) or later +- A [domain or subdomain](/domains-and-dns/quickstart/) pointed to your Instance ## Installing and configuring the LEMP stack diff --git a/tutorials/setup-mysql/index.mdx b/tutorials/setup-mysql/index.mdx index e6c2486f31..04c4dbeadf 100644 --- a/tutorials/setup-mysql/index.mdx +++ b/tutorials/setup-mysql/index.mdx @@ -24,9 +24,9 @@ Ready-to-use binary packages of MySQL are available for various operating system - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Focal Fossa (20.04) or later - `sudo` privileges or access to the root user ## Installing MySQL diff --git a/tutorials/setup-nginx-reverse-proxy-s3/index.mdx b/tutorials/setup-nginx-reverse-proxy-s3/index.mdx index 091f7480fc..a8743e67f4 100644 --- a/tutorials/setup-nginx-reverse-proxy-s3/index.mdx +++ b/tutorials/setup-nginx-reverse-proxy-s3/index.mdx @@ -31,10 +31,10 @@ In this setup, requested objects are temporarily stored in Nginx's cache. Conseq - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu or Debian Linux -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) with [public, readable](/storage/object/how-to/manage-object-visibility/) objects +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu or Debian Linux +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) with [public, readable](/object-storage/how-to/manage-object-visibility/) objects ## Installing Nginx on a Scaleway Instance diff --git a/tutorials/setup-nomad-cluster/index.mdx b/tutorials/setup-nomad-cluster/index.mdx index fddb8bc633..a517149e30 100644 --- a/tutorials/setup-nomad-cluster/index.mdx +++ b/tutorials/setup-nomad-cluster/index.mdx @@ -18,8 +18,8 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - Installed [Packer 1.7.7 or a later version](https://developer.hashicorp.com/packer/tutorials/docker-get-started/get-started-install-cli) - Installed [Terraform 1.2.0 or a later version](https://developer.hashicorp.com/terraform/tutorials/aws-get-started/install-cli) - Installed [Nomad 1.3.3 or a later version](https://developer.hashicorp.com/nomad/tutorials/get-started/gs-install) diff --git a/tutorials/setup-postfix-ubuntu-bionic/index.mdx b/tutorials/setup-postfix-ubuntu-bionic/index.mdx index 21b954ef42..2e71bc90cf 100644 --- a/tutorials/setup-postfix-ubuntu-bionic/index.mdx +++ b/tutorials/setup-postfix-ubuntu-bionic/index.mdx @@ -17,24 +17,24 @@ In this tutorial you will learn how to configure a mail server that uses Postfi You learn also how to install a Roundcube webmail interface to be able to read your emails directly from your browser. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu Bionic Beaver or later -- A [domain or subdomain](/network/domains-and-dns/quickstart/) configured to point to the IP address of your Instance -- Enabled the [SMTP ports](/compute/instances/how-to/send-emails-from-your-instance/) to send emails from your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu Bionic Beaver or later +- A [domain or subdomain](/domains-and-dns/quickstart/) configured to point to the IP address of your Instance +- Enabled the [SMTP ports](/instances/how-to/send-emails-from-your-instance/) to send emails from your Instance ## Pre-work and system preparation Before you continue with this tutorial, some configuration is required to make sure your mail server will be working. - - To ensure that other servers will accept emails sent from your Instance a [valid reverse DNS](/compute/instances/how-to/configure-reverse-dns/) within your own domain name (for example `mail.domain.com`) must be configured. - - The [SMTP ports](/compute/instances/how-to/send-emails-from-your-instance/) have been unlocked in the security group of the server. + - To ensure that other servers will accept emails sent from your Instance a [valid reverse DNS](/instances/how-to/configure-reverse-dns/) within your own domain name (for example `mail.domain.com`) must be configured. + - The [SMTP ports](/instances/how-to/send-emails-from-your-instance/) have been unlocked in the security group of the server. 1. Update the system: @@ -248,7 +248,7 @@ You learn also how to install a Roundcube webmail interface to be able to read y ``` Add the output as a `TXT` record to your domain's DNS zone to publish your DKIM public key in DNS. - Refer to [How to manage DNS records](/network/domains-and-dns/how-to/manage-dns-records/) for furher information. + Refer to [How to manage DNS records](/domains-and-dns/how-to/manage-dns-records/) for furher information. ## Install Roundcube Webmail diff --git a/tutorials/sinatra/index.mdx b/tutorials/sinatra/index.mdx index f7e760375b..f76d2fe4d2 100644 --- a/tutorials/sinatra/index.mdx +++ b/tutorials/sinatra/index.mdx @@ -23,9 +23,9 @@ To use Sinatra, we need to install three pieces of software: Ruby, RubyGems, and - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Linux +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Linux ## Installing Ruby and RubyGems diff --git a/tutorials/snapshot-instances-jobs/index.mdx b/tutorials/snapshot-instances-jobs/index.mdx index 3f8079cf24..b93a0b7030 100644 --- a/tutorials/snapshot-instances-jobs/index.mdx +++ b/tutorials/snapshot-instances-jobs/index.mdx @@ -14,16 +14,16 @@ dates: posted: 2024-06-19 --- -[Scaleway Serverless Jobs](/serverless/jobs/quickstart/) allows you to create and automate recurring tasks. This tutorial will guide you through the process of creating snapshots of a [Scaleway Instance](/compute/instances/quickstart/) on a recurring schedule using a Serverless Job. +[Scaleway Serverless Jobs](/serverless-jobs/quickstart/) allows you to create and automate recurring tasks. This tutorial will guide you through the process of creating snapshots of a [Scaleway Instance](/instances/quickstart/) on a recurring schedule using a Serverless Job. -Serverless Jobs are perfectly adapted for these autonomous tasks, as we do not need autoscaling or exposure via a web server. Refer to the [differences between jobs, containers and functions](/serverless/jobs/reference-content/difference-jobs-functions-containers/) for more information. +Serverless Jobs are perfectly adapted for these autonomous tasks, as we do not need autoscaling or exposure via a web server. Refer to the [differences between jobs, containers and functions](/serverless-jobs/reference-content/difference-jobs-functions-containers/) for more information. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- Created a [Container Registry namespace](/containers/container-registry/how-to/create-namespace/). -- Created an [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- Created a [Container Registry namespace](/container-registry/how-to/create-namespace/). +- Created an [Instance](/instances/how-to/create-an-instance/) - Installed and started the [Docker daemon](https://docs.docker.com/engine/install/) to build the image. ## Creating the snapshot generator files @@ -56,7 +56,7 @@ You can also download the work files by cloning our [Scaleway Serverless example // Get your credentials at https://console.scaleway.com/iam/api-keys scw.WithAuth(os.Getenv("SCW_ACCESS_KEY"), os.Getenv("SCW_SECRET_KEY")), - // Get more about our availability zones at https://www.scaleway.com/en/docs/console/my-account/reference-content/products-availability/ + // Get more about our availability zones at https://www.scaleway.com/en/docs/my-account/reference-content/products-availability/ scw.WithDefaultRegion(scw.RegionFrPar), ) if err != nil { @@ -165,7 +165,7 @@ You can also download the work files by cloning our [Scaleway Serverless example ## Building and pushing the image to Container Registry -Serverless Jobs rely on containers to run in the cloud, and therefore require a [container image](/serverless/jobs/concepts/#container-image) hosted in the cloud using [Scaleway Container Registry](/containers/container-registry/). +Serverless Jobs rely on containers to run in the cloud, and therefore require a [container image](/serverless-jobs/concepts/#container-image) hosted in the cloud using [Scaleway Container Registry](/container-registry/). 1. Create a `Dockerfile`, and add the following code to it: @@ -222,11 +222,11 @@ Your image and its tag now appear in the [Container Registry in the Scaleway con 6. Keep the default **resources** values, as this job requires little compute capabilities. -7. Set the **cron schedule** to `0 2 * * *` and select the relevant time zone to run the job every day at 2:00 a.m. Refer to the [cron schedules documentation](/serverless/jobs/reference-content/cron-schedules/) for more information. +7. Set the **cron schedule** to `0 2 * * *` and select the relevant time zone to run the job every day at 2:00 a.m. Refer to the [cron schedules documentation](/serverless-jobs/reference-content/cron-schedules/) for more information. 8. Define the following environment variables: - `INSTANCE_ID`: the ID of the instance you want to snapshot - - `INSTANCE_ZONE`: the [Availabilitiy Zone](/compute/instances/concepts/#availability-zone) of your Instance (e.g. `fr-par-2`) + - `INSTANCE_ZONE`: the [Availabilitiy Zone](/instances/concepts/#availability-zone) of your Instance (e.g. `fr-par-2`) - `SCW_ACCESS_KEY`: your API access key - `SCW_SECRET_KEY`: your API secret key - `SCW_DEFAULT_ORGANIZATION_ID`: your Oganization ID @@ -248,7 +248,7 @@ This tutorial is a lightweight example of how to create recurring snapshots of a ## Additional resources -- [Serverless Jobs Documentation](/serverless/jobs/how-to/create-job/) -- [Other methods to deploy Jobs](/serverless/jobs/reference-content/deploy-job/) -- [API keys documentation](/identity-and-access-management/iam/how-to/create-api-keys/) -- [CRON schedule reference](/serverless/jobs/reference-content/cron-schedules/) \ No newline at end of file +- [Serverless Jobs Documentation](/serverless-jobs/how-to/create-job/) +- [Other methods to deploy Jobs](/serverless-jobs/reference-content/deploy-job/) +- [API keys documentation](/iam/how-to/create-api-keys/) +- [CRON schedule reference](/serverless-jobs/reference-content/cron-schedules/) \ No newline at end of file diff --git a/tutorials/sns-instances-notification-system/index.mdx b/tutorials/sns-instances-notification-system/index.mdx index 1dfdbd383f..134bd54403 100644 --- a/tutorials/sns-instances-notification-system/index.mdx +++ b/tutorials/sns-instances-notification-system/index.mdx @@ -32,8 +32,8 @@ You can find the code for the publisher and the subscriber servers on [GitHub](h - A Scaleway account logged into the [console](https://console.scaleway.com) - [Set up authentication for the Terraform provider](https://registry.terraform.io/providers/scaleway/scaleway/latest/docs#authentication) - - An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - [Set up the Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) + - An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) + - [Set up the Scaleway CLI](/scaleway-cli/quickstart/) ## Create the base Terraform repository and files @@ -141,7 +141,7 @@ Continue to add code to your `main.tf` file as shown below to create the SNS top We continue to add to our `main.tf` file to create the subscriber and publisher Instances, and create a subscription to the topic: -1. Create the [security group](/compute/instances/concepts/#security-group) that will serve both Instances: +1. Create the [security group](/instances/concepts/#security-group) that will serve both Instances: ``` resource "scaleway_instance_security_group" "sns_www" { project_id = scaleway_account_project.sns_tutorial.id @@ -222,7 +222,7 @@ We continue to add to our `main.tf` file to create the subscriber and publisher } } ``` - This will allow the subscriber Instance to immediately receive the [confirmation link](/serverless/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) to subscribe to the topic, and not wait for the retry policy to confirm the subscription. + This will allow the subscriber Instance to immediately receive the [confirmation link](/messaging/how-to/create-manage-subscriptions/#how-to-confirm-an-http-or-https-subscription) to subscribe to the topic, and not wait for the retry policy to confirm the subscription. The confirmation step is done manually for the purposes of this tutorial, but it could also be performed with an HTTP request. 5. Create the SNS topic subscription with the subscriber Instance's endpoint: diff --git a/tutorials/socket-io/index.mdx b/tutorials/socket-io/index.mdx index 3bf317a151..fca5669de2 100644 --- a/tutorials/socket-io/index.mdx +++ b/tutorials/socket-io/index.mdx @@ -20,9 +20,9 @@ Learn how to install and use Socket.io with Express using the `npm` package mana - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running Ubuntu 20.04 LTS or later +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running Ubuntu 20.04 LTS or later - Root access to the Instances you want to manage - Installed [Node.js](https://nodejs.org/en/) (version 18.x or later) and [NPM](https://www.npmjs.com/) on your Instance diff --git a/tutorials/stop-outgoing-spam/index.mdx b/tutorials/stop-outgoing-spam/index.mdx index 685a94bb13..9d0c70f7c0 100644 --- a/tutorials/stop-outgoing-spam/index.mdx +++ b/tutorials/stop-outgoing-spam/index.mdx @@ -22,9 +22,9 @@ When you receive an abuse alert for spam on one of your machines, an intruder li Your immediate action is required in this case to stop the spam outgoing from the machine. It is recommended to boot the machine in **rescue mode**, to interrupt the outgoing connections as a first step, before proceeding with more in-depth investigations into what is going on: -- [Rescue Mode on Instances](/compute/instances/how-to/use-boot-modes/) -- [Rescue Mode on Elastic Metal servers](/bare-metal/elastic-metal/how-to/reboot-server/) -- [Rescue Mode on Dedibox dedicated servers](/dedibox/dedicated-servers/how-to/use-rescue-mode/) +- [Rescue Mode on Instances](/instances/how-to/use-boot-modes/) +- [Rescue Mode on Elastic Metal servers](/elastic-metal/how-to/reboot-server/) +- [Rescue Mode on Dedibox dedicated servers](/dedicated-servers/how-to/use-rescue-mode/) The rescue mode is a small Linux distribution, based on Ubuntu Linux, that runs directly in your server's RAM. It allows you to check your machine in a secure environment without being in a potentially infected environment. Once the server has booted into rescue mode, connect to it using SSH (depending on your product, the username, and password required for the connection are displayed in the console.) diff --git a/tutorials/store-s3-cyberduck/index.mdx b/tutorials/store-s3-cyberduck/index.mdx index 334b82bb05..913bcd3c9b 100644 --- a/tutorials/store-s3-cyberduck/index.mdx +++ b/tutorials/store-s3-cyberduck/index.mdx @@ -23,12 +23,12 @@ Among these tools, Cyberduck stands out as a reliable and efficient option for s - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Retrieving your credentials -To access Object Storage using s3md, you require your [API key](/identity-and-access-management/iam/how-to/create-api-keys/). +To access Object Storage using s3md, you require your [API key](/iam/how-to/create-api-keys/). ## Downloading Cyberduck diff --git a/tutorials/store-s3-transmit/index.mdx b/tutorials/store-s3-transmit/index.mdx index a9bd000ddf..5f39642713 100644 --- a/tutorials/store-s3-transmit/index.mdx +++ b/tutorials/store-s3-transmit/index.mdx @@ -22,12 +22,12 @@ Additionally, you can manage your storage using the intuitive control panel or u - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Retrieving your credentials -To access Object Storage using s3md, you need to [configure your API key](/identity-and-access-management/iam/how-to/create-api-keys/). +To access Object Storage using s3md, you need to [configure your API key](/iam/how-to/create-api-keys/). ## Downloading Transmit 5 diff --git a/tutorials/store-wp-mediacloud-s3/index.mdx b/tutorials/store-wp-mediacloud-s3/index.mdx index 4ef01400f2..3cdae6c7a2 100644 --- a/tutorials/store-wp-mediacloud-s3/index.mdx +++ b/tutorials/store-wp-mediacloud-s3/index.mdx @@ -19,9 +19,9 @@ Media Cloud is a WordPress plugin that allows you to automatically import the me - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A [WordPress blog](/tutorials/wordpress-instantapp/) running on an [Instance](https://www.scaleway.com/en/virtual-instances/) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) Media Cloud requires the PHP extensions `xml` and `mbstring`. If they are not installed on your system you can install them from the command line using the `apt` package manager on Debian and Ubuntu-based systems: `apt install php7.2-xml php7.2-mbstring` (For PHP version 7.2 - if you are using another PHP version modify the command accordingly). @@ -50,9 +50,9 @@ Media Cloud can be installed directly from the admin interface of your WordPress 5. Enter the connection credentials of your Object Storage bucket: - - **Access key**: Your Scaleway [access key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - **Secret key**: Your Scaleway [secret key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) - - **Bucket**: The name of your [Object Storage Bucket](/storage/object/how-to/create-a-bucket/) + - **Access key**: Your Scaleway [access key](/organizations-and-projects/how-to/create-ssh-key/) + - **Secret key**: Your Scaleway [secret key](/organizations-and-projects/how-to/create-ssh-key/) + - **Bucket**: The name of your [Object Storage Bucket](/object-storage/how-to/create-a-bucket/) - **Region**: Automatic - **Custom Endpoint**: The endpoint of your bucket, can either be: - `https://s3.fr-par.scw.cloud` for Paris (France) diff --git a/tutorials/strapi-app-serverless-containers-sqldb/index.mdx b/tutorials/strapi-app-serverless-containers-sqldb/index.mdx index c17b7ad5dc..f20641306a 100644 --- a/tutorials/strapi-app-serverless-containers-sqldb/index.mdx +++ b/tutorials/strapi-app-serverless-containers-sqldb/index.mdx @@ -23,9 +23,9 @@ You can either deploy your application: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- Installed and initialized the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- Installed and initialized the [Scaleway CLI](/scaleway-cli/quickstart/) - Installed [Docker Engine](https://docs.docker.com/engine/install/) - Installed [Node 18 or newer](https://nodejs.org/en/download) @@ -56,7 +56,7 @@ You can either deploy your application: ### Setting up the database -1. Run the following command to create a [Serverless SQL Database](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) and export its attributes as variables: +1. Run the following command to create a [Serverless SQL Database](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) and export its attributes as variables: ```bash export DATABASE_HOST=$(scw sdb-sql database create name=tutorial-strapi-blog-db cpu-min=0 cpu-max=4 -o json | jq -r '.endpoint' | cut -d "/" -f3 | cut -d ":" -f1 ) @@ -215,18 +215,18 @@ You can either deploy your application: ``` - The first run of this container will raise a database constraints error such as `error: YupValidationError: This attribute must be unique`, which will not alter any data. This occurs because we use the same [Serverless SQL Database](/serverless/sql-databases/) for development and production environments. Hence, initial sample data loading happens twice, once in `NODE_ENV=development` when running `npm run develop` initially and once in `NODE_ENV=production` when running `docker build -t my-strapi-blog .` The second loading triggers errors as data already exists, but will not happen again afterwards for these environments. + The first run of this container will raise a database constraints error such as `error: YupValidationError: This attribute must be unique`, which will not alter any data. This occurs because we use the same [Serverless SQL Database](/serverless-sql-databases/) for development and production environments. Hence, initial sample data loading happens twice, once in `NODE_ENV=development` when running `npm run develop` initially and once in `NODE_ENV=production` when running `docker build -t my-strapi-blog .` The second loading triggers errors as data already exists, but will not happen again afterwards for these environments. 8. Access [http://localhost:1337/admin](http://localhost:1337/admin) in a browser. The Strapi Administration Panel displays. ### Pushing the image to Scaleway Container Registry -1. Run the following command to create a [Container Registry namespace](/containers/container-registry/concepts/#namespace) and export its endpoint as a variable: +1. Run the following command to create a [Container Registry namespace](/container-registry/concepts/#namespace) and export its endpoint as a variable: ```bash export REGISTRY_ENDPOINT=$(scw registry namespace create -o json | jq -r '.endpoint') ``` -2. Run the following command to log in to your [Container Registry](/containers/container-registry/concepts/#container-registry): +2. Run the following command to log in to your [Container Registry](/container-registry/concepts/#container-registry): ```bash docker login $REGISTRY_ENDPOINT -u nologin --password-stdin <<< "$SCW_SECRET_KEY" ``` @@ -243,7 +243,7 @@ You can either deploy your application: ### Deploying the container with Scaleway Serverless Containers -1. Run the following command to create a [Serverless Containers namespace](/serverless/containers/concepts/#namespace) and export its ID as a variable: +1. Run the following command to create a [Serverless Containers namespace](/serverless-containers/concepts/#namespace) and export its ID as a variable: ```bash export CONTAINER_NAMESPACE_ID=$(scw container namespace create name="my-strapi-blog-ns" -o json | jq -r '.id') ``` @@ -312,25 +312,25 @@ Your Strapi headless CMS for a blog is now online. You can already edit stored c Moreover, your textual content data is already stored in serverless storage, so that your full application only runs when you connect to the administration panel or perform requests to the Strapi API. -However, your Strapi container currently connects to your database with your [user credentials](/identity-and-access-management/iam/concepts/#user), which is not a recommended security practice. +However, your Strapi container currently connects to your database with your [user credentials](/iam/concepts/#user), which is not a recommended security practice. ## Secure and redeploy your application -To secure your deployment, we will now add a dedicated [IAM application](/identity-and-access-management/iam/concepts/#application), give it the minimum required permissions, and provide its credentials to your Strapi container. +To secure your deployment, we will now add a dedicated [IAM application](/iam/concepts/#application), give it the minimum required permissions, and provide its credentials to your Strapi container. -1. Run the following command to create an [IAM application](/identity-and-access-management/iam/concepts/#application) and export it as a variable: +1. Run the following command to create an [IAM application](/iam/concepts/#application) and export it as a variable: ```bash export SCW_APPLICATION_ID=$(scw iam application create name=tutorial-strapi-blog -o json | jq -r '.id') ``` The `SCW_APPLICATION_ID` environment variable will store the IAM application ID so you can use it in the next commands. -2. Create an [IAM policy](/identity-and-access-management/iam/concepts/#policy) giving your application rights to access the database: +2. Create an [IAM policy](/iam/concepts/#policy) giving your application rights to access the database: ```bash scw iam policy create application-id=$SCW_APPLICATION_ID name=tutorial-strapi-policy rules.0.organization-id=$(scw config get default-organization-id) rules.0.permission-set-names.0=ServerlessSQLDatabaseFullAccess ``` The `ServerlessSQLDatabaseFullAccess` permission lets your application read and write data or create new databases. You can restrict this later to fit your database use cases, using the `ServerlessSQLDatabaseRead` or `ServerlessSQLDatabaseReadWrite` permissions sets. -3. Create an [IAM API Key](/identity-and-access-management/iam/concepts/#api-key) and export its secret key as an environment variable: +3. Create an [IAM API Key](/iam/concepts/#api-key) and export its secret key as an environment variable: ```bash export SCW_APPLICATION_SECRET=$(scw iam api-key create application-id=$SCW_APPLICATION_ID -o json | jq -r '.secret_key') ``` @@ -377,7 +377,7 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi - You can display your **Serverless SQL Database** in the [Serverless SQL Databases section](https://console.scaleway.com/serverless-db/databases). -- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless/containers/how-to/manage-a-container/). +- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless-containers/how-to/manage-a-container/). - Create a secondary development environment by duplicating your built container, building it in `NODE_ENV=development` environment, running `npm run develop`, and plugging it onto another **Serverless SQL Database**. This will let you, for instance, edit content types, which is not possible in production. @@ -524,12 +524,12 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi ### Pushing the image to Scaleway Container Registry -1. Run the following command to create a [Container Registry namespace](/containers/container-registry/concepts/#namespace) and export its endpoint as a variable: +1. Run the following command to create a [Container Registry namespace](/container-registry/concepts/#namespace) and export its endpoint as a variable: ```bash export REGISTRY_ENDPOINT=$(scw registry namespace create -o json | jq -r '.endpoint') ``` -2. Log in to your [Container Registry](/containers/container-registry/concepts/#container-registry) from your local terminal: +2. Log in to your [Container Registry](/container-registry/concepts/#container-registry) from your local terminal: ```bash docker login $REGISTRY_ENDPOINT -u nologin --password-stdin <<< "$SCW_SECRET_KEY" ``` @@ -691,15 +691,15 @@ To secure your deployment, we will now add a dedicated [IAM application](/identi The Terraform file creates several resources: -- A [Serverless Containers namespace](/serverless/containers/concepts/#namespace), that contains a [Serverless Container](/serverless/containers/quickstart/), which hosts your Strapi application +- A [Serverless Containers namespace](/serverless-containers/concepts/#namespace), that contains a [Serverless Container](/serverless-containers/quickstart/), which hosts your Strapi application -- A [Serverless SQL Database](/serverless/sql-databases/reference-content/serverless-sql-databases-overview/) which stores posts data +- A [Serverless SQL Database](/serverless-sql-databases/reference-content/serverless-sql-databases-overview/) which stores posts data -- An [IAM policy](/identity-and-access-management/iam/concepts/#policy) which grants your application the right permissions +- An [IAM policy](/iam/concepts/#policy) which grants your application the right permissions -- An [IAM application](/identity-and-access-management/iam/concepts/#application), used as a principal for your IAM policy +- An [IAM application](/iam/concepts/#application), used as a principal for your IAM policy -- An [API key](/identity-and-access-management/iam/concepts/#api-key) used as credentials to authenticate your application to the database +- An [API key](/iam/concepts/#api-key) used as credentials to authenticate your application to the database ### Deploying the app with Terraform @@ -809,7 +809,7 @@ Once you are done, run the following command to stop all your resources: - You can display your **Serverless SQL Database** in the [Serverless SQL Databases section](https://console.scaleway.com/serverless-db/databases) -- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless/containers/how-to/manage-a-container/) +- **Fine-tune deployment options** such as autoscaling, targeted regions, and more. You can find more information by typing `scw container deploy --help` in your terminal, or by referring to the [dedicated documentation](/serverless-containers/how-to/manage-a-container/) - Create a secondary production environment by duplicating your built container, building it in `NODE_ENV=production` environment, running `npm run start`, and plugging it onto another **Serverless SQL Database**. For instance, this will allow you to edit content-types which is not possible in production. @@ -817,7 +817,7 @@ Once you are done, run the following command to stop all your resources: If you happen to encounter any issues, first check that you meet all the requirements. -- You have installed and configured the [Scaleway CLI](/developer-tools/scaleway-cli/quickstart/). Running the `scw account project get` command should return the following output: +- You have installed and configured the [Scaleway CLI](/scaleway-cli/quickstart/). Running the `scw account project get` command should return the following output: ``` ID example-7afa-4a5d-9f6c-27db072f1527 Name default @@ -833,4 +833,4 @@ If you happen to encounter any issues, first check that you meet all the require ``` Docker version 24.0.6, build ed223bc820 ``` -- You have the right [IAM permissions](/identity-and-access-management/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** and **ServerlessSQLDatabaseFullAccess**. \ No newline at end of file +- You have the right [IAM permissions](/iam/reference-content/policy/), specifically **ContainersRegistryFullAccess**, **ContainersFullAccess** and **ServerlessSQLDatabaseFullAccess**. \ No newline at end of file diff --git a/tutorials/strapi/index.mdx b/tutorials/strapi/index.mdx index b2f770f7e8..a175577130 100644 --- a/tutorials/strapi/index.mdx +++ b/tutorials/strapi/index.mdx @@ -16,18 +16,18 @@ dates: Strapi is an open-source, Node.js-based, headless CMS to manage content and make it available through a fully customizable API. Unlike traditional CMSs such as WordPress, with Strapi the content is decoupled from the front end. Strapi simultaneously provides for **content creators**, who get an easy-to-use, database-driven interface to create, organize, and manage content, and **developers**, who get the convenience of an API that they can use to query, deliver, and integrate that content to diverse applications and front ends. -In this tutorial, you will learn how to deploy Strapi on a [Scaleway Instance](/compute/instances/how-to/create-an-instance/). +In this tutorial, you will learn how to deploy Strapi on a [Scaleway Instance](/instances/how-to/create-an-instance/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) ## Installing dependencies -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Update the APT package cache and upgrade the software already installed on the Instance: ``` apt update && apt upgrade -y diff --git a/tutorials/systemd-essentials/index.mdx b/tutorials/systemd-essentials/index.mdx index b0e6b216c9..4eeecace2e 100644 --- a/tutorials/systemd-essentials/index.mdx +++ b/tutorials/systemd-essentials/index.mdx @@ -21,8 +21,8 @@ In this tutorial, you will learn a quick overview of the most important commands - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user ## Analyzing the system state diff --git a/tutorials/terraform-quickstart/index.mdx b/tutorials/terraform-quickstart/index.mdx index e3c89f6add..66f2782166 100644 --- a/tutorials/terraform-quickstart/index.mdx +++ b/tutorials/terraform-quickstart/index.mdx @@ -21,9 +21,9 @@ HashiCorp [Terraform](http://terraform.io) is an open-source software tool to de - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- A valid [API key](/iam/how-to/create-api-keys/) ## Installing Terraform @@ -105,7 +105,7 @@ To create a first Instance using Terraform, a declarative configuration file is ``` nano scaleway.tf ``` -3. Add the following content to the file to deploy a Development DEV1-L Instance running the Ubuntu Focal Fossa (20.04 LTS) base image in the `fr-par-1` zone. Replace `` and `` with your own [API key information](/identity-and-access-management/iam/how-to/create-api-keys/) and `` with your own Project ID: +3. Add the following content to the file to deploy a Development DEV1-L Instance running the Ubuntu Focal Fossa (20.04 LTS) base image in the `fr-par-1` zone. Replace `` and `` with your own [API key information](/iam/how-to/create-api-keys/) and `` with your own Project ID: ```json terraform { required_providers { @@ -344,7 +344,7 @@ To create a first Instance using Terraform, a declarative configuration file is ## Modifying an Instance using Terraform -We now have a first Instance up and running. Next, we will modify it by restricting access using [security groups](/compute/instances/how-to/use-security-groups/). We are going to `DROP` all traffic to the Instance by default: only traffic to ports 80 (HTTP), 443 (HTTPS) and 22 (SSH) will be allowed. To do this, we have to add some more lines to our existing configuration file `scaleway.tf`. +We now have a first Instance up and running. Next, we will modify it by restricting access using [security groups](/instances/how-to/use-security-groups/). We are going to `DROP` all traffic to the Instance by default: only traffic to ports 80 (HTTP), 443 (HTTPS) and 22 (SSH) will be allowed. To do this, we have to add some more lines to our existing configuration file `scaleway.tf`. All changes made to the local configuration file are not effective in production before the new configuration is applied using the `terraform apply` command. diff --git a/tutorials/traefik-v2-cert-manager/index.mdx b/tutorials/traefik-v2-cert-manager/index.mdx index 4b450c8360..5e6e328e4a 100644 --- a/tutorials/traefik-v2-cert-manager/index.mdx +++ b/tutorials/traefik-v2-cert-manager/index.mdx @@ -27,9 +27,9 @@ Our goal in this tutorial is to: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Kubernetes Kapsule cluster](/containers/kubernetes/how-to/create-cluster/) with an ingress controller (Traefik 2) -- Downloaded the corresponding [kubeconfig](/containers/kubernetes/how-to/edit-cluster/) file and ensured the [kubectl](/containers/kubernetes/how-to/connect-cluster-kubectl/) is configured and working +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Kubernetes Kapsule cluster](/kubernetes/how-to/create-cluster/) with an ingress controller (Traefik 2) +- Downloaded the corresponding [kubeconfig](/kubernetes/how-to/edit-cluster/) file and ensured the [kubectl](/kubernetes/how-to/connect-cluster-kubectl/) is configured and working ### Deploying Traefik 2 using the Easy Deploy feature diff --git a/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx b/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx index 4043d088ca..8d1f8e3009 100644 --- a/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx +++ b/tutorials/transform-bucket-images-triggers-functions-deploy/index.mdx @@ -21,11 +21,11 @@ In the [previous tutorial](/tutorials/transform-bucket-images-triggers-functions -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A Scaleway [Project](/identity-and-access-management/organizations-and-projects/concepts/#project) dedicated to this tutorial -- A source [bucket](/storage/object/how-to/create-a-bucket/) containing images +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A Scaleway [Project](/organizations-and-projects/concepts/#project) dedicated to this tutorial +- A source [bucket](/object-storage/how-to/create-a-bucket/) containing images - An empty destination bucket -- A [Scaleway queue](/serverless/messaging/how-to/create-manage-queues) with credentials +- A [Scaleway queue](/messaging/how-to/create-manage-queues) with credentials You will now learn how to deploy Serverless Functions and connect them using triggers. diff --git a/tutorials/trigger-ifttt-actions/index.mdx b/tutorials/trigger-ifttt-actions/index.mdx index b31c49155a..3f5295d092 100644 --- a/tutorials/trigger-ifttt-actions/index.mdx +++ b/tutorials/trigger-ifttt-actions/index.mdx @@ -22,7 +22,7 @@ In this tutorial, we will show you how to quickly build a simple reporting appli -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization ## Create an IFTTT account and set up an applet @@ -40,7 +40,7 @@ Now the applet is set up, we need to find our webhook key. Head to your [webhook Now that we have our IFTTT applet ready, we need to create an IoT Hub. This will be where our simulated IoT Device will publish messages to trigger our IFTTT applet. -1. Follow [this procedure](/managed-services/iot-hub/how-to/create-hub/) to create an IoT Hub. Select your name and plan of choice, and click the `Create Hub` button. +1. Follow [this procedure](/iot-hub/how-to/create-hub/) to create an IoT Hub. Select your name and plan of choice, and click the `Create Hub` button. 2. Head to the Routes tab of your IoT Hub. 3. Create a new route with the following settings: - Name: anything you'd like (ex: `IFTTT Route`) @@ -76,4 +76,4 @@ We hope you had fun collecting data from your IoT Hub to a Google sheet. This is --- -Learn more about [Scaleway IoT Hub](/managed-services/iot-hub/concepts/), discover how to add [Devices to the hub](/managed-services/iot-hub/how-to/add-device/) or check out the [IoT Hub metrics](/managed-services/iot-hub/how-to/view-metrics/). \ No newline at end of file +Learn more about [Scaleway IoT Hub](/iot-hub/concepts/), discover how to add [Devices to the hub](/iot-hub/how-to/add-device/) or check out the [IoT Hub metrics](/iot-hub/how-to/view-metrics/). \ No newline at end of file diff --git a/tutorials/upgrade-managed-postgresql-database/index.mdx b/tutorials/upgrade-managed-postgresql-database/index.mdx index 5f25bc83f5..e1df0e2c86 100644 --- a/tutorials/upgrade-managed-postgresql-database/index.mdx +++ b/tutorials/upgrade-managed-postgresql-database/index.mdx @@ -31,8 +31,8 @@ There are three steps to completing a manual migration: creating a new PostgreSQ - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) - A PostgreSQL database running on version 9.6 - Installed `curl` on your local computer @@ -44,7 +44,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ 1. Open the [Scaleway console](https://console.scaleway.com) in a web browser and click **Managed Databases** in the **Storage** section of the side menu. The list of your databases displays. 2. Click **+ Create a Database Instance**. The [Database Instance creation wizard](https://console.scaleway.com/rdb/instances/create) displays. -3. Select **PostgreSQL-13** from the drop-down list and fill in the [required information](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) for your new database Instance. Then click **Create an Instance**. Your database is created, and you are redirected to the database dashboard. +3. Select **PostgreSQL-13** from the drop-down list and fill in the [required information](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) for your new database Instance. Then click **Create an Instance**. Your database is created, and you are redirected to the database dashboard. Ensure your new Database Instance is located in the same geographical region as your old one. @@ -54,7 +54,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ -- Generated your [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- Generated your [API key](/iam/how-to/create-api-keys/) - Installed `curl` on your local computer 1. Retrieve the database ID of your **old** Database Instance. You can find it on the **Database Instance Information** page of your Instance: @@ -70,7 +70,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ }' ``` 3. Replace the following information in the command above: - * `$SECRET_KEY`: Your Scaleway API [secret key](/identity-and-access-management/iam/concepts/#api-key) + * `$SECRET_KEY`: Your Scaleway API [secret key](/iam/concepts/#api-key) * ``: The region of your Database Instance. It can either be `fr-par`, `nl-ams`, or `pl-waw`. * ``: The ID of your **old** Database Instance, for example: `ad085d32-16e0-4ce6-862c-8e70c56b9ee7`. * ``: The name of your PostgreSQL database, for example, `customer_data`. @@ -117,7 +117,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ ``` Replace the following information in the command above: - * `$SECRET_KEY`: Your Scaleway API [secret key](/identity-and-access-management/iam/concepts/#api-key) + * `$SECRET_KEY`: Your Scaleway API [secret key](/iam/concepts/#api-key) * ``: The region of your Database Instance. It can either be `fr-par`, `nl-ams`, or `pl-waw`. * ``: The ID of your database backup, for example: `7feaab67-0f22-4170-96cc-6fbb11c57256`. * ``: The name of your PostgreSQL database, for example: `customer_data`. @@ -154,7 +154,7 @@ There are three steps to completing a manual migration: creating a new PostgreSQ Optionally, you can verify the status of your database with a tool like [pgAdmin 4](/tutorials/manage-database-instance-pgadmin4/). 4. Update your applications with the endpoint (IP address and port) of the new Database Instance. -5. Once the migration is complete, [delete](/managed-databases/postgresql-and-mysql/how-to/delete-a-database/) the old Database Instance from your account. +5. Once the migration is complete, [delete](/managed-databases-for-postgresql-and-mysql/how-to/delete-a-database/) the old Database Instance from your account. ## Automatic migration via a bash script using the Scaleway CLI v2 diff --git a/tutorials/use-cockpit-with-terraform/index.mdx b/tutorials/use-cockpit-with-terraform/index.mdx index f17922221b..375f278ce4 100644 --- a/tutorials/use-cockpit-with-terraform/index.mdx +++ b/tutorials/use-cockpit-with-terraform/index.mdx @@ -15,16 +15,16 @@ dates: In this tutorial, you will learn how to get started with Cockpit using a Terraform configuration file containing all the code you need to create: -- A [Grafana user](/observability/cockpit/concepts/#grafana-users) +- A [Grafana user](/cockpit/concepts/#grafana-users) - A folder in the Grafana user interface -- A Cockpit [token](/observability/cockpit/concepts/#tokens) with permission to query and push metrics -- A metric [data source](/observability/cockpit/concepts/#data-sources) +- A Cockpit [token](/cockpit/concepts/#tokens) with permission to query and push metrics +- A metric [data source](/cockpit/concepts/#data-sources) - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- [Configured an SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ed25519-ssh-key-pair-on-macos-and-linux) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Configured an SSH key](/organizations-and-projects/how-to/create-ssh-key/#how-to-generate-an-ed25519-ssh-key-pair-on-macos-and-linux) - [Installed Terraform](https://www.terraform.io/downloads.html) on your local machine @@ -42,10 +42,10 @@ Open a terminal on your local machine and clone the `cockpit-terraform` reposito 1. Access the `main.tf` file inside the `cockpit-terraform` directory. We recommend that you do it manually, as you need to add your values. 2. Replace `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx` line 5, with your Scaleway Project ID. -3. Replace `your-grafana-user` line 28, with a name for the [Grafana user](/observability/cockpit/concepts/#grafana-users) you will be creating. +3. Replace `your-grafana-user` line 28, with a name for the [Grafana user](/cockpit/concepts/#grafana-users) you will be creating. 4. Replace `Test Folder` line 39, with a name of your choice. 5. Replace `your-push-token` line 45, with a name for your Cockpit token. -6. Replace `your-data-source` line 57, with a name for your [metric](/observability/cockpit/concepts/#metric) data source. +6. Replace `your-data-source` line 57, with a name for your [metric](/cockpit/concepts/#metric) data source. 7. Save your changes and close the file. ## Build and deploy your infrastructure diff --git a/tutorials/use-container-registry-github-actions/index.mdx b/tutorials/use-container-registry-github-actions/index.mdx index 05b7ba1bfd..37e9bb75d9 100644 --- a/tutorials/use-container-registry-github-actions/index.mdx +++ b/tutorials/use-container-registry-github-actions/index.mdx @@ -20,9 +20,9 @@ GitHub Actions is a platform for automating software development workflows in th - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) -- A private [Container Registry namespace](/containers/container-registry/how-to/create-namespace/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) +- A private [Container Registry namespace](/container-registry/how-to/create-namespace/) - A [member role in a GitHub organization](https://docs.github.com/en/organizations/managing-peoples-access-to-your-organization-with-roles/roles-in-an-organization) - Created [a GitHub repository](https://docs.github.com/en/get-started/quickstart/create-a-repo) in that organization - A [working Dockerfile in the root of the repository](https://docs.docker.com/engine/reference/builder/) in that organization diff --git a/tutorials/use-managed-redis-with-mysql/index.mdx b/tutorials/use-managed-redis-with-mysql/index.mdx index 550dbb285e..26194e34ef 100644 --- a/tutorials/use-managed-redis-with-mysql/index.mdx +++ b/tutorials/use-managed-redis-with-mysql/index.mdx @@ -22,9 +22,9 @@ This tutorial demonstrates the integration of a [Scaleway Redis™](https://www. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A [Redis™ Database Instance](/managed-databases/redis/how-to/create-a-database-for-redis/) -- A [MySQL Database Instance](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A [Redis™ Database Instance](/managed-databases-for-redis/how-to/create-a-database-for-redis/) +- A [MySQL Database Instance](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) - Installed the [.NET 7 SDK](https://dotnet.microsoft.com/en-us/download/dotnet/7.0) ## Scaffold a project with Entity Framework diff --git a/tutorials/using-bucket-website-with-mkdocs/index.mdx b/tutorials/using-bucket-website-with-mkdocs/index.mdx index 0e0773d9b3..497cadf31a 100644 --- a/tutorials/using-bucket-website-with-mkdocs/index.mdx +++ b/tutorials/using-bucket-website-with-mkdocs/index.mdx @@ -13,7 +13,7 @@ dates: posted: 2024-10-07 --- -This tutorial shows you how to create a documentation website using the Scaleway [Object Storage bucket website](/storage/object/concepts/#bucket-website) feature with MkDocs. +This tutorial shows you how to create a documentation website using the Scaleway [Object Storage bucket website](/object-storage/concepts/#bucket-website) feature with MkDocs. [MkDocs](https://www.mkdocs.org/) is a static site generator that allows users to generate a static website from a set of Markdown files. It is written in Python and uses Markdown for content creation. We will use MkDocs to generate our website, and Material for MkDocs which is a documentation framework that extends MkDocs with additional features and customization options, to create visually appealing and user-friendly documentation websites. @@ -23,7 +23,7 @@ Find out how to Set up MkDocs and configure your website in the first tab, then - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - [Installed Python](https://www.python.org/downloads/) - [Installed pip](https://pip.pypa.io/en/stable/installation/) - [Installed Visual Studio Code](https://code.visualstudio.com/download) @@ -434,8 +434,8 @@ Find out how to Set up MkDocs and configure your website in the first tab, then ### Deploy your website - 1. [Create an Object Storage bucket](/storage/object/how-to/create-a-bucket/) from the [Scaleway console](https://console.scaleway.com/). - 2. [Enable](/storage/object/how-to/use-bucket-website/) the bucket website feature on your bucket. + 1. [Create an Object Storage bucket](/object-storage/how-to/create-a-bucket/) from the [Scaleway console](https://console.scaleway.com/). + 2. [Enable](/object-storage/how-to/use-bucket-website/) the bucket website feature on your bucket. 3. Click your bucket, then the **Bucket settings** tab. 4. Scroll down to the **Bucket website** section and enter the names of your **index** and **error** documents and save your changes. By default, your index file is named `index.html`, and your error file is named `404.html`. 5. Scroll back up and click the **Files** tab. diff --git a/tutorials/using-own-grafana/index.mdx b/tutorials/using-own-grafana/index.mdx index 47b7120376..92bb944ec9 100644 --- a/tutorials/using-own-grafana/index.mdx +++ b/tutorials/using-own-grafana/index.mdx @@ -13,12 +13,12 @@ dates: posted: 2023-05-10 --- -In this tutorial, you will learn how to use your own Grafana with [Scaleway's Cockpit](/observability/cockpit/quickstart/) service. In this tutorial, we are using Grafana version 9.5.1. +In this tutorial, you will learn how to use your own Grafana with [Scaleway's Cockpit](/cockpit/quickstart/) service. In this tutorial, we are using Grafana version 9.5.1. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - Installed [Docker](https://docs.docker.com/engine/install/) - Downloaded the [latest version of Grafana](https://grafana.com/grafana/download) @@ -29,7 +29,7 @@ In this tutorial, you will learn how to use your own Grafana with [Scaleway's Co ```bash docker run -d -p 3000:3000 grafana/grafana-oss:9.5.1 ``` -2. [Create a token](/observability/cockpit/how-to/create-token/) with the following permissions: +2. [Create a token](/cockpit/how-to/create-token/) with the following permissions: - Query metrics - Query logs - Query traces diff --git a/tutorials/using-secret-manager-with-github-action/index.mdx b/tutorials/using-secret-manager-with-github-action/index.mdx index 666a5e028f..3a8d66f3af 100644 --- a/tutorials/using-secret-manager-with-github-action/index.mdx +++ b/tutorials/using-secret-manager-with-github-action/index.mdx @@ -15,16 +15,16 @@ dates: GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want. -In this tutorial, you will learn how to use the [Scaleway Secret Manager GitHub Action](https://github.com/scaleway/action-scw-secret) in your GitHub Actions workflow to retrieve your secrets stored in [Secret Manager](/identity-and-access-management/secret-manager/quickstart/) and expose them as environment variables. +In this tutorial, you will learn how to use the [Scaleway Secret Manager GitHub Action](https://github.com/scaleway/action-scw-secret) in your GitHub Actions workflow to retrieve your secrets stored in [Secret Manager](/secret-manager/quickstart/) and expose them as environment variables. Oftentimes, when doing Continuous Integration/Continuous Deployment, you need to access secrets to log in to a Docker registry, push code changes, call APIs, etc. -A good practice is to use a [Secret Manager](/identity-and-access-management/secret-manager/quickstart/) to store your secrets, securely in one place. When doing that, you have to copy and paste your secrets and put them in your CI which duplicates the secrets and leads to desynchronization with your source of truth. This is where GitHub action is useful. +A good practice is to use a [Secret Manager](/secret-manager/quickstart/) to store your secrets, securely in one place. When doing that, you have to copy and paste your secrets and put them in your CI which duplicates the secrets and leads to desynchronization with your source of truth. This is where GitHub action is useful. -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- A valid [API key](/identity-and-access-management/iam/how-to/create-api-keys/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- A valid [API key](/iam/how-to/create-api-keys/) ## Preparing your GitHub repository diff --git a/tutorials/veeam-backup-replication-s3/index.mdx b/tutorials/veeam-backup-replication-s3/index.mdx index 11bd7cba28..aa1b8595b3 100644 --- a/tutorials/veeam-backup-replication-s3/index.mdx +++ b/tutorials/veeam-backup-replication-s3/index.mdx @@ -27,13 +27,13 @@ The following schema represents the functionality of Veeam Backup and Restore wh - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization - A machine running [VMware vSphere](https://www.vmware.com/products/vsphere.html) - An intermediate Instance running [Veeam Backup & Replication](https://www.veeam.com/vm-backup-recovery-replication-software.html) -- An [Object Storage bucket](/storage/object/how-to/create-a-bucket/) +- An [Object Storage bucket](/object-storage/how-to/create-a-bucket/) - - **[Glacier storage class](/storage/object/concepts/#storage-class) is currently not supported by Veeam.** + - **[Glacier storage class](/object-storage/concepts/#storage-class) is currently not supported by Veeam.** If you use lifecycle rules to transition your objects from Standard to Glacier, you will lose the link between Veeam and your data. In this case, your data will still exist, but it will no longer be usable. @@ -68,9 +68,9 @@ The following schema represents the functionality of Veeam Backup and Restore wh 8. The setup wizard for the repository appears, provide a name and additional information for it, then click **Next**: -9. Click **Add** (1) to enter the [API key](/identity-and-access-management/iam/how-to/create-api-keys/) (2) related to the bucket. Optionally a description can be provided: +9. Click **Add** (1) to enter the [API key](/iam/how-to/create-api-keys/) (2) related to the bucket. Optionally a description can be provided: -10. Provide the **Service Point** ([regional endpoint](/storage/objects/concepts/#endpoint)), and the **Region** of your bucket, then click **Next**: +10. Provide the **Service Point** ([regional endpoint](/objects/concepts/#endpoint)), and the **Region** of your bucket, then click **Next**: @@ -180,9 +180,9 @@ The application cannot access the Object Storage resource. If you encounter one or several of the error messages above: -- make sure that you have the `ObjectStorageFullAccess` [IAM permission](/identity-and-access-management/iam/concepts/#permission). +- make sure that you have the `ObjectStorageFullAccess` [IAM permission](/iam/concepts/#permission). -- make sure that there is no [bucket policy](/storage/object/api-cli/bucket-policy/) preventing the application to access your bucket. +- make sure that there is no [bucket policy](/object-storage/api-cli/bucket-policy/) preventing the application to access your bucket. ### Too many requests error @@ -225,7 +225,7 @@ You may experience reduced throughput due to the limitation. ### Going further -If you did not manage to identify the error and solve it by yourself, [open a support ticket](/console/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: +If you did not manage to identify the error and solve it by yourself, [open a support ticket](/account/how-to/open-a-support-ticket/), and provide as many details as possible, along with the necessary information below: - Object Storage Endpoint (e.g. `s3.fr-par.scw.cloud`) - Bucket name diff --git a/tutorials/visualize-timeseries-data-timescaledb-grafana/index.mdx b/tutorials/visualize-timeseries-data-timescaledb-grafana/index.mdx index a683dd3f53..ef285e48d3 100644 --- a/tutorials/visualize-timeseries-data-timescaledb-grafana/index.mdx +++ b/tutorials/visualize-timeseries-data-timescaledb-grafana/index.mdx @@ -27,9 +27,9 @@ In this tutorial, we use a [Database for PostgreSQL](https://www.scaleway.com/en - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later to host the Grafana interface -- A [Database for PostgreSQL](/managed-databases/postgresql-and-mysql/how-to/create-a-database/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) or later to host the Grafana interface +- A [Database for PostgreSQL](/managed-databases-for-postgresql-and-mysql/how-to/create-a-database/) - `sudo` privileges or access to the root user ## Creating a new database @@ -219,7 +219,7 @@ For more information on how to read data from your database, refer to TimescaleD You can visualize the time-series data by creating a dashboard using [Grafana](https://grafana.com/), an open-source analytics & monitoring solution. 1. Create a new [Instance](https://www.scaleway.com/en/virtual-instances/) running on Ubuntu Bionic (18.04) from your [Scaleway console](https://console.scaleway.com/dashboard) -2. Log into the Instance [using SSH](/compute/instances/how-to/connect-to-instance/). +2. Log into the Instance [using SSH](/instances/how-to/connect-to-instance/). 3. Add the Grafana repository to the `apt` package cache. ``` add-apt-repository "deb https://packages.grafana.com/oss/deb stable main" diff --git a/tutorials/vpc-public-gateway-autoconfiguration/index.mdx b/tutorials/vpc-public-gateway-autoconfiguration/index.mdx index 92213d9d9c..803212a3d0 100644 --- a/tutorials/vpc-public-gateway-autoconfiguration/index.mdx +++ b/tutorials/vpc-public-gateway-autoconfiguration/index.mdx @@ -20,13 +20,13 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) ## Creating a Private Network for the Instance -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). ``` ssh root@ ``` @@ -87,7 +87,7 @@ The Instance is now added to the Private Network, and the Private Network's inbu 6. Configure the attachment: - Select the Private Network you previously created from the drop-down list. - Either choose a specific IPv4 address to use for the attachment, or leave the default auto-allocation option in place. - - Activate the toggle to [advertise the default route](/network/public-gateways/concepts/#default-route) + - Activate the toggle to [advertise the default route](/public-gateways/concepts/#default-route) 7. Click **Attach to Private Network**. The Public Gateway is attached to the Private Network, and you are returned to the list of Private Networks for this gateway. @@ -111,6 +111,6 @@ SSH bastion allows you to make secure SSH connections to resources attached to a Congratulations, you have completed your first configuration of Instances in a Private Network, attached to a Public Gateway. To move forward, check out our product documentation: -* [VPC Quickstart](/network/public-gateways/quickstart/) -* [How to use Private Networks](/compute/instances/how-to/use-private-networks/) -* [How to configure a Public Gateway](/network/public-gateways/how-to/configure-a-public-gateway/) \ No newline at end of file +* [VPC Quickstart](/public-gateways/quickstart/) +* [How to use Private Networks](/instances/how-to/use-private-networks/) +* [How to configure a Public Gateway](/public-gateways/how-to/configure-a-public-gateway/) \ No newline at end of file diff --git a/tutorials/vuls-security-scanner/index.mdx b/tutorials/vuls-security-scanner/index.mdx index b45355128a..977e0e8de5 100644 --- a/tutorials/vuls-security-scanner/index.mdx +++ b/tutorials/vuls-security-scanner/index.mdx @@ -18,13 +18,13 @@ dates: - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu Bionic Beaver (18.04) ## Installing the dependencies and pre-work -1. Connect to the server as `root` via [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to the server as `root` via [SSH](/instances/how-to/connect-to-instance/). 2. Update the APT package cache and the software already installed on the Instance: ``` apt update && apt upgrade -y @@ -257,7 +257,7 @@ Vuls is capable of performing security checks on multiple machines. To configure - root access on the machine - the ability to create an additional user account on the remote machine -1. Connect to the remote server as `root` via [SSH](/compute/instances/how-to/create-an-instance/#-Logging-into-the-Instance). +1. Connect to the remote server as `root` via [SSH](/instances/how-to/create-an-instance/#-Logging-into-the-Instance). 2. Update the APT package cache, the already installed software on the Instance, and install `sudo` and `debian-goodies`, which is required for Vuls: ``` apt update && apt upgrade -y && apt installl sudo debian-goodies -y @@ -280,7 +280,7 @@ Vuls is capable of performing security checks on multiple machines. To configure ``` adduser vuls sudo ``` -7. Create a [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) for on the Vuls master instance: +7. Create a [SSH key](/organizations-and-projects/how-to/create-ssh-key/) for on the Vuls master instance: ``` ssh-keygen -o ``` diff --git a/tutorials/wireguard-mesh-vpn/index.mdx b/tutorials/wireguard-mesh-vpn/index.mdx index e65a49f9a0..95d74e0e52 100644 --- a/tutorials/wireguard-mesh-vpn/index.mdx +++ b/tutorials/wireguard-mesh-vpn/index.mdx @@ -24,15 +24,15 @@ We use two Ubuntu Instances, one located in the `PAR-1` region, and the other lo - If you are looking to configure WireGuard as a VPN to provide secure internet access, [check out our other WireGuard tutorial](/tutorials/install-wireguard/). -- We recommend you follow this tutorial using a [Learning Instance](/compute/instances/reference-content/choosing-instance-type/). +- We recommend you follow this tutorial using a [Learning Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- 2 [Instances](/compute/instances/how-to/create-an-instance/) running a Linux kernel ≥ 3.10 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- 2 [Instances](/instances/how-to/create-an-instance/) running a Linux kernel ≥ 3.10 ## Downloading and installing WireGuard diff --git a/tutorials/wordpress-instantapp/index.mdx b/tutorials/wordpress-instantapp/index.mdx index 414ca77091..b212e99783 100644 --- a/tutorials/wordpress-instantapp/index.mdx +++ b/tutorials/wordpress-instantapp/index.mdx @@ -15,18 +15,18 @@ dates: WordPress is a popular, free, and open-source blogging tool and content management system (CMS) based on PHP and MariaDB. -Using the WordPress application can significantly save you time and effort, as it comes pre-installed and configured. By default, the WordPress image used in this tutorial [supports routed IPs](/compute/instances/api-cli/using-routed-ips/). +Using the WordPress application can significantly save you time and effort, as it comes pre-installed and configured. By default, the WordPress image used in this tutorial [supports routed IPs](/instances/api-cli/using-routed-ips/). This guide demonstrates how to quickly deploy a WordPress application in seconds using Scaleway's InstantApp. - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended organizations -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended organizations +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/cost-optimized/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/cost-optimized/). diff --git a/tutorials/wordpress-lemp-stack-focal/index.mdx b/tutorials/wordpress-lemp-stack-focal/index.mdx index 35baf5bebd..aee27eba36 100644 --- a/tutorials/wordpress-lemp-stack-focal/index.mdx +++ b/tutorials/wordpress-lemp-stack-focal/index.mdx @@ -20,8 +20,8 @@ In this tutorial, we will learn how to install WordPress on a freshly created Ub - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user - Installed [LEMP](/tutorials/installation-lemp-ubuntu-bionic/) - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address diff --git a/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx b/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx index 6e207d8a35..0c000a2a01 100644 --- a/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx +++ b/tutorials/wordpress-lemp-stack-ubuntu-jammy-jellyfish-22-04/index.mdx @@ -18,14 +18,14 @@ dates: If you are seeking to install WordPress on a newly established Ubuntu 22.04 LTS Instance, this tutorial is tailor-made for your needs. We will meticulously walk you through the installation steps, employing the LEMP stack (Linux + Nginx - pronounced "engine x" + MySQL + PHP). For the sake of this tutorial, we are choosing Nginx, a robust HTTP server that is efficient in resource usage, resulting in faster page delivery, especially for static content. By opting for a Cost-Optimized Instance configured with LEMP, you will gain access to a robust web server that elevates website performance, thus ensuring a seamless WordPress installation experience. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user - Installed [LEMP](/tutorials/installation-lemp-ubuntu-bionic/) - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address diff --git a/tutorials/wordpress-lemp-stack/index.mdx b/tutorials/wordpress-lemp-stack/index.mdx index 1e9ef80739..ea61cabc2b 100644 --- a/tutorials/wordpress-lemp-stack/index.mdx +++ b/tutorials/wordpress-lemp-stack/index.mdx @@ -21,8 +21,8 @@ In this tutorial, you will learn how to install WordPress on a freshly created U - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) - `sudo` privileges or access to the root user - Installed [LEMP](/tutorials/installation-lemp-ubuntu-bionic/) - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address diff --git a/tutorials/zabbix-monitoring/index.mdx b/tutorials/zabbix-monitoring/index.mdx index a0d4d6c69e..67e270a8ee 100644 --- a/tutorials/zabbix-monitoring/index.mdx +++ b/tutorials/zabbix-monitoring/index.mdx @@ -17,18 +17,18 @@ Zabbix is a powerful open-source software that offers real-time monitoring for s This monitoring tool enables users to determine the health status of their IT infrastructure and analyze data over time. The insights provided by Zabbix can be used to plan upgrades to the infrastructure when requirements grow. -In this tutorial, we will use two Scaleway [Production-Optimized](/compute/instances/reference-content/choosing-instance-type/) Ubuntu Jammy Jellyfish (22.04 LTS) Instances. One Instance will be a server hosting the Zabbix application, while the other will be a client being monitored. Following this tutorial will teach you how to set up Zabbix and take control of your IT infrastructure. +In this tutorial, we will use two Scaleway [Production-Optimized](/instances/reference-content/choosing-instance-type/) Ubuntu Jammy Jellyfish (22.04 LTS) Instances. One Instance will be a server hosting the Zabbix application, while the other will be a client being monitored. Following this tutorial will teach you how to set up Zabbix and take control of your IT infrastructure. - We recommend you follow this tutorial using a [Production-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Production-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- 2 [Instances](/compute/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.O4 LTS) +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- 2 [Instances](/instances/how-to/create-an-instance/) running Ubuntu Jammy Jellyfish (22.O4 LTS) - Installed a [LEMPStack](/tutorials/installation-lemp-ubuntu-bionic/) on the Instance acting as the server ## Installing the Zabbix server @@ -379,7 +379,7 @@ Zabbix proposes a wide range of [notification plugins](https://www.zabbix.com/in 2. Click **Email** to edit the settings. Enter the SMTP credentials of your email provider and update the configuration by clicking on **Update**. - To send email from the Instance, make sure to [unblock](/compute/instances/how-to/send-emails-from-your-instance/) the SMTP ports in the Instances security group. + To send email from the Instance, make sure to [unblock](/instances/how-to/send-emails-from-your-instance/) the SMTP ports in the Instances security group. 3. Click **Administration** in the navigation bar on the top of the page, then on **Users** 4. Click the **Alias** of the user to modify. diff --git a/tutorials/zammad-ticketing/index.mdx b/tutorials/zammad-ticketing/index.mdx index 1bae7226cd..206281252c 100644 --- a/tutorials/zammad-ticketing/index.mdx +++ b/tutorials/zammad-ticketing/index.mdx @@ -19,22 +19,22 @@ Zammad is an open-source helpdesk system that allows you to oversee customer int This tutorial will guide you through the process of installing Zammad on a Scaleway Instance operating on **Ubuntu 20.04 LTS (Focal Fossa)**. Furthermore, you will receive a brief orientation of the application. - We recommend you follow this tutorial using a [Cost-Optimized Instance](/compute/instances/reference-content/choosing-instance-type/). + We recommend you follow this tutorial using a [Cost-Optimized Instance](/instances/reference-content/choosing-instance-type/). - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/), running on Ubuntu Focal Fossa (20.04 LTS), with at least 4 GB of RAM -- A [domain name](/network/domains-and-dns/quickstart/) pointed to your Instance +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/), running on Ubuntu Focal Fossa (20.04 LTS), with at least 4 GB of RAM +- A [domain name](/domains-and-dns/quickstart/) pointed to your Instance ## Installing Elasticsearch Zammad requires an [Elasticsearch](https://www.elastic.co/elasticsearch/) database to increase search performance and to support advanced features like reports or searching by email attachment contents. Start by installing the Elasticsearch engine on your Instance. -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/). +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/). 2. Install the Elastic GPG Key to validate the packages. ``` wget -qO - https://artifacts.elastic.co/GPG-KEY-elasticsearch | gpg --dearmor -o /usr/share/keyrings/elasticsearch-keyring.gpg diff --git a/tutorials/zulip/index.mdx b/tutorials/zulip/index.mdx index d7f41a3afd..8d3ff23b24 100644 --- a/tutorials/zulip/index.mdx +++ b/tutorials/zulip/index.mdx @@ -23,15 +23,15 @@ More than 90 integrations are available for Zulip, including GitHub, Jira, Zende - A Scaleway account logged into the [console](https://console.scaleway.com) -- [Owner](/identity-and-access-management/iam/concepts/#owner) status or [IAM permissions](/identity-and-access-management/iam/concepts/#permission) allowing you to perform actions in the intended Organization -- An [SSH key](/identity-and-access-management/organizations-and-projects/how-to/create-ssh-key/) -- An [Instance](/compute/instances/how-to/create-an-instance/) running on Ubuntu 20.04 +- [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization +- An [SSH key](/organizations-and-projects/how-to/create-ssh-key/) +- An [Instance](/instances/how-to/create-an-instance/) running on Ubuntu 20.04 - An FQDN (Fully Qualified Domain Name) pointing to your Instance's IP address -- Enabled the [email ports](/bare-metal/elastic-metal/how-to/enable-smtp/) +- Enabled the [email ports](/elastic-metal/how-to/enable-smtp/) ## Installing Zulip -1. Connect to your Instance using [SSH](/compute/instances/how-to/connect-to-instance/): +1. Connect to your Instance using [SSH](/instances/how-to/connect-to-instance/): ``` ssh root@ ```