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 90247422e2..2d3bdb30c7 100644 --- a/ai-data/generative-apis/api-cli/using-chat-api.mdx +++ b/ai-data/generative-apis/api-cli/using-chat-api.mdx @@ -56,8 +56,8 @@ Find required headers in [this page](/ai-data/generative-apis/api-cli/using-gene | Param | Type | Description | | ------------- |-------------|-------------| -| **messages*** | array of objects | A list of messages comprising the conversation so far. | -| **model*** | string | The name of the model to query. | +| **messages** | array of objects | A list of messages comprising the conversation so far. | +| **model** | string | The name of the model to query. | Our chat API is OpenAI compatible. Use OpenAI’s [API reference](https://platform.openai.com/docs/api-reference/chat/create) for more detailed information on the usage. @@ -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. +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 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 cf73250a13..0c36e50244 100644 --- a/ai-data/generative-apis/api-cli/using-embeddings-api.mdx +++ b/ai-data/generative-apis/api-cli/using-embeddings-api.mdx @@ -40,8 +40,8 @@ Find required headers in [this page](/ai-data/generative-apis/api-cli/using-gene | Param | Type | Description | | ------------- |-------------|-------------| -| **input*** | string or array | Input text to embed, encoded as a string or array of strings. It cannot be an empty string. | -| **model*** | string | The name of the model to query. | +| **input** | string or array | Input text to embed, encoded as a string or array of strings. It cannot be an empty string. | +| **model** | string | The name of the model to query. | Our embeddings API is OpenAI compatible. Use OpenAI’s [API reference](https://platform.openai.com/docs/api-reference/embeddings) for more detailed information on the usage. diff --git a/compute/gpu/how-to/create-manage-gpu-instance.mdx b/compute/gpu/how-to/create-manage-gpu-instance.mdx index 0cc76a226c..2fd2b1dfba 100644 --- a/compute/gpu/how-to/create-manage-gpu-instance.mdx +++ b/compute/gpu/how-to/create-manage-gpu-instance.mdx @@ -30,7 +30,7 @@ When you have completed your calculations using the GPU Instance, [deletion can ## How to create a GPU Instance 1. Navigate to **Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers). -2. Click ***+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers). +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. diff --git a/compute/gpu/quickstart.mdx b/compute/gpu/quickstart.mdx index 08c41e1088..e1dc002332 100644 --- a/compute/gpu/quickstart.mdx +++ b/compute/gpu/quickstart.mdx @@ -15,28 +15,28 @@ categories: -Scaleway GPU Instances are virtual compute instances equipped with dedicated high-end Nvidia graphical processing unit (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](/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. 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. ## How to create a GPU Instance 1. Navigate to **Instances** under the **Compute** section in the side menu of the [Scaleway console](https://console.scaleway.com/). This action will direct you to the [Instance dashboard](https://console.scaleway.com/instance/servers). -2. Click ***+ Create Instance** to proceed to the [Instance creation page](https://console.scaleway.com/instance/servers). +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. - - **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. + - **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/) - - **Network Configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. - - **Instance Name and Tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. - - **Advanced Options**: Configure `cloud-init` settings if required, or leave them at default values. - - **SSH Keys**: Verify the SSH keys that will grant you access to your Instance. - - **Estimated Cost**: Review the estimated cost of your GPU Instance based on the selected specifications. + - **Network configuration**: Choose between a routed public IP or a NAT public IP for your Instance. We recommend using a routed public IP. You can allocate IPv4 and IPv6 addresses as needed, with a maximum of 5 IPs per Instance. + - **Instance name and tags**: Assign a name to your Instance for easy identification. You can also add tags to organize your Instances efficiently. + - **Advanced options**: Configure `cloud-init` settings if required, or leave them at default values. + - **SSH keys**: Verify the SSH keys that will grant you access to your Instance. + - **Estimated cost**: Review the estimated cost of your GPU Instance based on the selected specifications. 4. Once you have completed the configuration, click on **Create Instance** to initiate the creation process. You will receive a notification once the GPU Instance is ready for use. ## How to connect to your GPU Instance @@ -59,7 +59,7 @@ To access a preinstalled working environment with all your favorite Python packa ## How to use the preinstalled environment -When you run your Docker container as shown above, the container launches, and you are taken to its `ai` directory, where the Pipenv virtual environment is already activated. +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/). @@ -67,10 +67,10 @@ When you run your Docker container as shown above, the container launches, and y ### Launching an application in your local browser -Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](https://www.tensorflow.org/tensorboard) and [Code Server](https://code-server.dev/), require a browser to run. You can launch these from the `ai` virtual environment of your Docker container, and view them in the browser of your local machine. This is thanks to the possibility to add port mapping arguments when launching a container with the `docker run` command. In our example, we added the port mapping arguments `-p 8888:8888 -p 6006:6006` when we launched our container, mapping `8888:8888` for Jupyter Lab and `6006:6006` for Tensorboard. +Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](https://www.tensorflow.org/tensorboard) and [Code Server](https://code-server.dev/), require a browser to run. You can launch these from the `ai` virtual environment of your Docker container, and view them in the browser of your local machine. This is possible thanks to the addition of port mapping arguments when launching a container with the `docker run` command. In our example, we added the port mapping arguments `-p 8888:8888 -p 6006:6006` when we launched our container, mapping `8888:8888` for Jupyter Lab and `6006:6006` for Tensorboard. - Code Server runs in Jupyter Lab via Jupyter Hub, so does not need port mapping in this case. You can add other port mapping arguments for other applications as you wish. + Code Server runs in Jupyter Lab via Jupyter Hub and does not need port mapping in this case. You can add other port mapping arguments for other applications as you wish. 1. Launch an application. Here, we launch Jupyter Lab: @@ -88,7 +88,7 @@ Some applications, such as [Jupyter Lab](https://jupyter.org/), [Tensorboard](ht ``` - Jupyter Lab is launched automatically when you run any Scaleway container image. You will see a message upon start up telling how to access the notebook in your browser. To override Jupyter Lab being launched automatically in this way, add `/bin/bash` to the end of your `docker run` command, e.g. `docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/pytorch:latest /bin/bash`. This preempts the launch of Jupyter Lab at container startup, and replaces it with the specified command, in this case a bash shell. + Jupyter Lab is launched automatically when you run any Scaleway container image. You will see a message upon start up telling how to access the notebook in your browser. To override Jupyter Lab being launched automatically in this way, add `/bin/bash` to the end of your `docker run` command, e.g. `docker run --runtime=nvidia -it --rm -p 8888:8888 -p 6006:6006 rg.fr-par.scw.cloud/scw-ai/pytorch:latest /bin/bash`. This preempts the launch of Jupyter Lab at container startup and replaces it with the specified command. In this case, a bash shell. 2. On your local computer, open a browser window and enter the following URL. Replace `` with the IP address of your Scaleway GPU Instance, and `` with the token shown displayed in the last lines of terminal output after the `jupyter-lab` command ``` diff --git a/compute/instances/how-to/create-a-block-volume.mdx b/compute/instances/how-to/create-a-block-volume.mdx index caf14ff6cc..055b88582b 100644 --- a/compute/instances/how-to/create-a-block-volume.mdx +++ b/compute/instances/how-to/create-a-block-volume.mdx @@ -28,18 +28,16 @@ categories: The volume must be in the same Availability Zone as the Instance you want to connect it to. 5. Enter the volume name and select a size. -6. Configure the volume type. You can either create a **Block Storage** or ***Local Storage** volume. +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](/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. - Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. + Alternatively, use the [Instances API](https://www.scaleway.com/en/developers/api/instance/#path-instance-types-list-instance-types) to check the `block_bandwidth` field at `/instance/v1/zones/{zone}/products/servers`. This field provides detailed information about block bandwidth for each Instance type, helping you ensure compatibility with high-performance storage. 7. Click **Create volume** to confirm. You can also [create](/storage/block/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/quickstart.mdx b/compute/instances/quickstart.mdx index 6d0a0bf52a..0517ec82a4 100644 --- a/compute/instances/quickstart.mdx +++ b/compute/instances/quickstart.mdx @@ -29,7 +29,7 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units - **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/). - - ***Choose an image** to run on your Instance.
+ - **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. - **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. @@ -49,7 +49,7 @@ Scaleway [Instances](/compute/instances/concepts/#instance) are computing units - **Verify the [SSH keys](/identity-and-access-management/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 + Once the Instance is created, you can connect to it using the SSH keys you have configured, and begin setting up your applications. ## How to connect to an Instance @@ -74,7 +74,7 @@ You are now connected to your Instance. To connect to your Instance from Windows, you will need to use a small application called **PuTTY**, an SSH client. -1. Download and install PuTTY [here](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html) +1. [Download and install PuTTY](https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html). 2. Launch PuTTY on your computer. 3. Enter your Instance's IP address in the **Hostname** field. 4. In the side menu, under **Connection**, navigate to the **Auth** sub-category. (**Connection** > **SSH** > **Auth**). @@ -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 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](/compute/instances/how-to/connect-to-instance/). ## How to delete an Instance @@ -96,5 +96,5 @@ To connect to your Instance from Windows, you will need to use a small applicati 1. Click **Instances** in the **Compute** section of the side menu. The [Instances page](https://console.scaleway.com/instance/servers) displays. -2. Click the icon next to the Instance you want to delete, and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action. +2. Click the icon next to the Instance you want to delete and select **Delete** from the drop-down menu. A pop-up asks you to confirm the action. 3. Type **DELETE** and then click **Delete Instance**. \ No newline at end of file diff --git a/compute/instances/reference-content/identify-devices.mdx b/compute/instances/reference-content/identify-devices.mdx index 7dcfea108b..57c589ba7d 100644 --- a/compute/instances/reference-content/identify-devices.mdx +++ b/compute/instances/reference-content/identify-devices.mdx @@ -17,9 +17,9 @@ An Instance is composed of a multitude of devices. Some of them can be configure On a Linux host, devices are named by the kernel in the order they are discovered. The order in which devices are discovered is dependent on things such as the topology of the PCI hierarchy which are *not* guaranteed to be stable across power off/power on/reboot actions. -This guide aims to provide tips to help you identify devices in a stable manner on a Linux host. +This guide aims to provide tips to help you stably identify devices on a Linux host. -# Identifying Instance Block Storage volumes (b_ssd) +## Identifying Instance Block Storage volumes (b_ssd) Instance Block Storage (`b_ssd`) volumes are connected to the Instance as SCSI disks. They will therefore appear as devices handled by the sd driver in the dev file system, i.e. as `/dev/sd{a,b,c...}` devices. @@ -96,7 +96,7 @@ Note that this rule relies on `ID_VENDOR` and `ID_SERIAL_SHORT` being in the env For more details on writing `udev` rules, please see `man 7 udev`. -# Identifying Block Storage volumes (SBS) +## Identifying Block Storage volumes (SBS) Block Storage devices are similar to Instance Block Storage devices. They are also connected to the Instance as SCSI devices and thus all explanations from the above section are also valid. @@ -117,7 +117,7 @@ sdb 0:0:1:0 disk SCW b_ssd v42 volume-03e206f6-2a3b-4223-bb56-3d7f1495 Here, the first volume has been created through the Block Storage API with class `sbs`. The second volume is an Instance Block Storage (`b_ssd`) volume which has been migrated to Block Storage, and is now a Block Storage volume with class `bssd`. -# Identifying VPC Private Network interfaces +## Identifying VPC Private Network interfaces VPC Private Networks to which the Instance is connected will appear as virtio PCI network devices, handled by the `virtio-net` driver. @@ -151,7 +151,7 @@ root@test-instance:~# ip link show altname enp0s6 ``` -Here, four interfaces are listed, one of which (`lo`) is the virtual loopback interface and can be disregarded. The three other correspond to the aforementioned public network interface, and VPC Private Network interfaces. +Here, four interfaces are listed, one of which (`lo`) is the virtual loopback interface and can be disregarded. The three others correspond to the aforementioned public network interface and VPC Private Network interfaces. A simple and effective way to distinguish the public network interface from the VPC Private Network interfaces is the MAC address prefix. VPC Private Network interfaces always have a MAC address starting with `02:00:00`. @@ -195,7 +195,7 @@ For example, querying `/instances/v1//servers//private_nics`, where } ``` -Two entries are listed, which correspond to the interfaces given by the output of `ip link show` above. The output contains the ID of the VPC Private Network, which helps distinguishing between the two. +Two entries are listed, which correspond to the interfaces given by the output of `ip link show` above. The output contains the ID of the VPC Private Network, which helps distinguish between the two. Through the use of `udev` rules, it is possible to rename the interfaces if desired. For example, the following rule would assign the static name `priv0` to the interface with MAC address `02:00:00:b7:c8:a5`: @@ -209,5 +209,5 @@ If a more complex scheme is desired, such as including part of the name of the c SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="02:00:00:*", ENV{SYSTEMD_WANTS}="my-vpc-script@$env{ID_NET_NAME}.service" ``` -This rule would start the systemd service `my-vpc-service@` when a new interface with name `` is added and has a MAC address matching the VPC Private Network prefix. -The systemd service can then execute complex operations (retrieving the server's `private_nics` informations, the VPC Private Network information through the VPC API, applying custom logic, etc.). \ No newline at end of file +This rule would start the systemd service `my-vpc-service@` when a new interface with the name `` is added and has a MAC address matching the VPC Private Network prefix. +The systemd service can then execute complex operations (retrieving the server's `private_nics` information, the VPC Private Network information through the VPC API, applying custom logic, etc.). \ No newline at end of file diff --git a/console/account/how-to/download-scaleway-contracts.mdx b/console/account/how-to/download-scaleway-contracts.mdx new file mode 100644 index 0000000000..0e47195c05 --- /dev/null +++ b/console/account/how-to/download-scaleway-contracts.mdx @@ -0,0 +1,40 @@ +--- +meta: + title: How to download Scaleway contracts + description: Download General Terms of Services, Data Processing Agreement, and more. +content: + h1: How to download Scaleway contracts + paragraph: Download General Terms of Services, Data Processing Agreement, and more. +tags: account contracts gdpr +dates: + validation: 2024-12-12 + posted: 2024-12-12 +categories: + - console +--- + +Scaleway contracts define the terms, conditions, and commitments that govern the use of our services. They ensure transparency and compliance with legal and regulatory requirements while outlining the rights and responsibilities of both Scaleway and its customers. + +## Contracts available for download + +You can access and download the following types of contracts: + +| **Contract type** | **Description** | +|---------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| General Terms of Services | Defines the respective rights and obligations of Scaleway and the client in connection with the client's use of the services provided by Scaleway. | +| Data Processing Agreement | Defines the conditions under which Scaleway undertakes to carry out, on behalf of the client and for the sole purpose of the strict execution of the contract, personal data processing operations. | +| Specific Conditions | The contractual document issued by Scaleway, specific to a service, that defines the conditions of provision and use applicable to said service. | +| Technical and Organizational Measures | Describes the measures taken by Scaleway to ensure the security of client's data. | +| Intrusion Testing Agreement | Defines the conditions applicable in the context of carrying out intrusion tests by the client or any third party acting on its behalf. | + +## How to download Scaleway contracts + +You can download Scaleway contracts either via the [console](https://console.scaleway.com/organization) or Scaleway's website: + +### From the Scaleway console +You can access and download the contracts applicable to your Organization: +1. Click the [Contracts](https://console.scaleway.com/organization/contracts) tab in your [Organization dashboard](https://console.scaleway.com/organization). +2. Click the download icon next to the contract you want to download. + +### From Scaleway's website +All available contracts can be viewed and downloaded directly from the [Contracts page](https://www.scaleway.com/en/contracts/). \ No newline at end of file diff --git a/console/account/reference-content/products-availability.mdx b/console/account/reference-content/products-availability.mdx index 0fcffb55e1..ac419551db 100644 --- a/console/account/reference-content/products-availability.mdx +++ b/console/account/reference-content/products-availability.mdx @@ -40,7 +40,7 @@ Scaleway products are available in multiple regions and locations worldwide. Thi | **Managed Databases** | PostgreSQL - MySQL | Across Paris region | Across Amsterdam region | Across Warsaw region | | | Redis™ | PAR1, PAR2 | AMS1, AMS2 | WAW1 | | **Network** | Private Networks | Across Paris region | Across Amsterdam region | Across Warsaw region | -| | Public Gateway | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | +| | Public Gateway | PAR1, PAR2 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | | | Load Balancer | PAR1, PAR2, PAR3 | AMS1, AMS2, AMS3 | WAW1, WAW2, WAW3 | | | Edge Services | Global | Global | Global | | | Domains and DNS | Automatically assigned | Automatically assigned | Automatically assigned | diff --git a/dedibox/dedicated-servers/how-to/terminate-dedibox-server.mdx b/dedibox/dedicated-servers/how-to/terminate-dedibox-server.mdx new file mode 100644 index 0000000000..e7d671387f --- /dev/null +++ b/dedibox/dedicated-servers/how-to/terminate-dedibox-server.mdx @@ -0,0 +1,32 @@ +--- +meta: + title: How to terminate a Dedibox server under Online console + description: Learn how to terminate a Dedibox server in the Online console. +content: + h2: How to terminate a Dedibox server + paragraph: This guide explains how to terminate a Online Dedibox server in the Online console. +tags: dedibox terminate server online console delete cancel +dates: + posted: 2024-12-12 + validation: 2024-12-12 +categories: + - dedibox-console +--- + + +- A Dedibox account logged into the [console](https://console.online.net) +- An active Dedibox server + +## How to terminate your Dedibox server +1. Click your username, next to _logged in as_, in the top right corner of the [Online console](https://console.online.net/). From the drop-down menu, select **Services**. The service page displays. +2. Click the **Detail** next to the Dedibox server you want to terminate. The **Server information** page displays. +3. Click **Terminate**. A pop-up displays. +4. Click **Confirm Termination**. The Server and all associated options display +5. Type a comment in the **Reason for termination** field, and enter a summary. +6. Click **TERMINATE THIS SERVICE AND OPTION ASSOCIATED** to confirm the termination + + +Your Dedibox server will be terminated in accordance with the timing of your termination request: +To terminate a server at the end of the current month, you must submit your termination request between the 1st and 20th of that month. +If you submit your termination request after the 20th, the termination will be effective at the end of the following month. + diff --git a/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx b/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx index 12c99168dd..3b4e40b8b5 100644 --- a/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx +++ b/identity-and-access-management/iam/reference-content/users-groups-and-applications.mdx @@ -9,7 +9,7 @@ dates: validation: 2024-10-16 --- -IAM users, groups, and applications are principals in Scaleway Organizations. A principal is an entity that can be attached to policy. +IAM users, groups, and applications are principals in Scaleway Organizations. A principal is an entity that can be attached to a policy. Users and applications are capable of bearing API keys. They can have one or more API keys attributed to them. @@ -20,7 +20,7 @@ An IAM user is a human user in an Organization. They can be of two types: - **Owner** - you are the Owner of the Organization that was created with your account. -- **Guest** - you are Guest when invited to another Organization of which you are not the Owner. Similarly, you can invite other users to be Guests in your Organization. +- **Guest** - you are a Guest when invited to an Organization of which you are not the Owner. Similarly, you can invite other users to be Guests in your Organization. @@ -46,7 +46,7 @@ An IAM group is a grouping of users and/or applications. You can create groups to attach policies to multiple users and/or applications at the same time. -For example, instead of creating two different policies that give **user A** and **application C** full access to the Instances in Project B, you can assemble user "A" and application "C" into **group 1** attach it to a singular policy: +For example, instead of creating two different policies that give **user A** and **application C** full access to the Instances in Project B, you can assemble user "A" and application "C" into **group 1** and attach it to a singular policy: PRINCIPAL : Group 1 (consisting of user A and application C) @@ -58,7 +58,5 @@ Permission set : InstancesFullAccess - It is possible to create empty groups, with no users or applications. - - - + It is possible to create empty groups with no users or applications. + \ No newline at end of file diff --git a/menu/navigation.json b/menu/navigation.json index 747ef44dd3..362f083976 100644 --- a/menu/navigation.json +++ b/menu/navigation.json @@ -72,6 +72,10 @@ "label": "Manage my personal information (GDPR)", "slug": "manage-my-personal-data-gdpr" }, + { + "label": "Download Scaleway contracts", + "slug": "download-scaleway-contracts" + }, { "label": "Use the search bar", "slug": "use-the-search-bar"