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 d702ecbe3f..6bbd620c68 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 @@ -1,5 +1,5 @@ --- -title: New bucket policy version allowing to set up granular access to ressources is now in GA! +title: New bucket policy version allowing to set up granular access to resources is now in GA! status: added author: fullname: 'Join the #object-storage channel on Slack.' diff --git a/pages/account/assets/closed-account.webp b/pages/account/assets/closed-account.webp deleted file mode 100644 index 673fe150c8..0000000000 Binary files a/pages/account/assets/closed-account.webp and /dev/null differ diff --git a/pages/account/assets/scaleway-account-closed.webp b/pages/account/assets/scaleway-account-closed.webp new file mode 100644 index 0000000000..1350839346 Binary files /dev/null and b/pages/account/assets/scaleway-account-closed.webp differ diff --git a/pages/account/how-to/assets/scaleway-2FA-disable.webp b/pages/account/how-to/assets/scaleway-2FA-disable.webp deleted file mode 100644 index 36dcc90b40..0000000000 Binary files a/pages/account/how-to/assets/scaleway-2FA-disable.webp and /dev/null differ diff --git a/pages/account/how-to/assets/scaleway-2FA-login.webp b/pages/account/how-to/assets/scaleway-2FA-login.webp deleted file mode 100644 index 25f2d24956..0000000000 Binary files a/pages/account/how-to/assets/scaleway-2FA-login.webp and /dev/null differ diff --git a/pages/account/how-to/assets/scaleway-2FA-popup-1.webp b/pages/account/how-to/assets/scaleway-2FA-popup-1.webp deleted file mode 100644 index 39c224dc0b..0000000000 Binary files a/pages/account/how-to/assets/scaleway-2FA-popup-1.webp and /dev/null differ diff --git a/pages/account/how-to/assets/scaleway-2FA-popup-2.webp b/pages/account/how-to/assets/scaleway-2FA-popup-2.webp deleted file mode 100644 index 0e942bdb43..0000000000 Binary files a/pages/account/how-to/assets/scaleway-2FA-popup-2.webp and /dev/null differ diff --git a/pages/account/how-to/change-console-appearance.mdx b/pages/account/how-to/change-console-appearance.mdx index 75f1d5822e..c4354fb960 100644 --- a/pages/account/how-to/change-console-appearance.mdx +++ b/pages/account/how-to/change-console-appearance.mdx @@ -7,7 +7,7 @@ content: paragraph: Customize the appearance of the Scaleway console. tags: color-scheme change color theme dark-mode change-color dates: - validation: 2024-11-04 + validation: 2025-02-28 posted: 2022-10-12 categories: - console @@ -20,18 +20,14 @@ You can choose the color scheme of the [Scaleway console](/account/concepts/#con - A Scaleway account logged into the [console](https://console.scaleway.com) - [Owner](/iam/concepts/#owner) status or [IAM permissions](/iam/concepts/#permission) allowing you to perform actions in the intended Organization -1. Click on your name in the top right corner of the Scaleway console. A pop-up menu opens. - -2. Click **Profile** to view your Scaleway user profile. - -3. Scroll to the **Appearance** section and select the color scheme for your Scaleway console. You can choose from four options: - * A light color scheme - * A dark color scheme - * A darker color scheme - * A color scheme based on your system preferences - - - - Your selection is saved automatically once you have chosen a color scheme. - - +1. Access the [My profile](https://console.scaleway.com/account/profile) tab of your **User Account** page. + Alternatively, click your Organization name on the top-right corner of the console navigation menu, then click **Profile**. +2. Scroll to the **Appearance** section and select the color scheme for your Scaleway console. You can choose from four color scheme options: + * Light + * Dark + * Darker + * System + + + Your selection is saved automatically once you have chosen a color scheme. + \ No newline at end of file diff --git a/pages/account/how-to/change-language.mdx b/pages/account/how-to/change-language.mdx index 97aede5446..773695e808 100644 --- a/pages/account/how-to/change-language.mdx +++ b/pages/account/how-to/change-language.mdx @@ -7,7 +7,7 @@ content: paragraph: Switch languages in the Scaleway account interface. tags: account language change dates: - validation: 2025-02-11 + validation: 2025-02-28 posted: 2021-06-22 categories: - console @@ -20,11 +20,9 @@ You can choose which language you would like to view the [Scaleway console](/acc - A [Scaleway account](https://console.scaleway.com) 1. Log into the [Scaleway console](https://console.scaleway.com). +2. Access the [My profile](https://console.scaleway.com/account/profile) tab of your **User Account** page. + Alternatively, click your Organization name on the top-right corner of the console navigation menu, then click **Profile**. +3. Click the **Edit profile** button, in the **User information** section. A pop-up displays. +4. Select your preferred language from the drop-down list, then click **Confirm changes**. -2. Click your Organization name in the top right corner of the console to open the Organization drop-down menu, then click the **Profile** button. The **User Account** screen displays. - -3. In the User information section, click the **Edit profile** button. The **Edit your account profile** screen displays. - -4. Choose your preferred language from the drop-down list, then click **Confirm changes**. - -Your console will now be displayed in your preferred language, which will also be used for all marketing and product communications you receive. You can change your preferred language at any time by repeating this procedure. +Your console will now be displayed in your chosen language, which will also be used for all marketing and product communications you receive. You can change your preferred language at any time by repeating this procedure. \ No newline at end of file diff --git a/pages/account/how-to/close-account.mdx b/pages/account/how-to/close-account.mdx index 0d81e2492b..5a8c2696cd 100644 --- a/pages/account/how-to/close-account.mdx +++ b/pages/account/how-to/close-account.mdx @@ -7,7 +7,7 @@ content: paragraph: Close your Scaleway account securely. tags: account close cancel delete deactivate close-account dates: - validation: 2024-09-02 + validation: 2025-02-28 posted: 2021-06-22 categories: - console @@ -32,16 +32,16 @@ Closing your account will permanently delete your Organization’s servers, reso - -1. Access the [Settings](https://console.scaleway.com/organization/settings) tab of your Organization dashboard (alternatively, you can go to the [User account](https://console.scaleway.com/account/profile) page). -2. Scroll down to the **Close** account section. -3. Click the **Close account** button once you have read and agreed with the warning message. -4. Type **CLOSE**, then click **Continue closing** to confirm your decision. +1. Access the [Settings](https://console.scaleway.com/organization/settings) tab of your Organization dashboard. + Alternatively, go to the [User account](https://console.scaleway.com/account/profile) page. +2. Scroll down to the **Close account** section. +3. Click the **Close account** button. +4. Type **Close**, then click **Continue closing** to confirm your decision, once you have read and agreed with the deletion terms. 5. Select the reasons why you are closing your account. 6. Click **Close account**. A message appears to confirm that closing has been scheduled. ## How to reopen your account -When your account is closed, you can still access the Scaleway console. A red banner in the top navigation bar will display to inform you that your account has been closed. If you want to reopen it, you can create a support ticket by clicking the link in the banner. +When your account is closed, you can still access the Scaleway console. A red banner at the top navigation bar will display to inform you that your account has been closed. If you want to reopen it, you can [open a support ticket](https://console.scaleway.com/support/tickets/create). - + \ No newline at end of file diff --git a/pages/account/how-to/enforce-mfa.mdx b/pages/account/how-to/enforce-mfa.mdx index 0bc3b7e3b1..43ef077a71 100644 --- a/pages/account/how-to/enforce-mfa.mdx +++ b/pages/account/how-to/enforce-mfa.mdx @@ -1,11 +1,11 @@ --- meta: title: How to enforce Multifactor Authentication for an Organization - description: Enable and enforce Multi-Factor Authentication (MFA). + description: Enable and enforce Multifactor Authentication (MFA). content: h1: How to enforce Multifactor Authentication for an Organization - paragraph: Enable and enforce Multi-Factor Authentication (MFA). -tags: authentication 2FA two-factor two multi factor security google authenticator authenticator mfa + paragraph: Enable and enforce Multifactor Authentication (MFA). +tags: authentication 2FA two-factor two multifactor security google authenticator authenticator mfa dates: validation: 2025-01-15 posted: 2023-06-12 @@ -62,4 +62,4 @@ categories: 5. Type **STOP**. 6. Click **Stop enforcing MFA** to confirm. - The Owner of your Organization will receive an informative email saying MFA is no longer enforced. + The Owner of your Organization will receive an informative email saying MFA is no longer enforced. \ No newline at end of file diff --git a/pages/account/how-to/use-2fa.mdx b/pages/account/how-to/use-2fa.mdx index 85696dddf4..9b824dc446 100644 --- a/pages/account/how-to/use-2fa.mdx +++ b/pages/account/how-to/use-2fa.mdx @@ -5,9 +5,9 @@ meta: content: h1: How to use Multifactor Authentication (MFA) paragraph: Enable and use Two-Factor Authentication (2FA) in Scaleway. -tags: authentication 2FA two-factor two multi factor security google authenticator authenticator +tags: authentication 2FA two-factor two multifactor security google authenticator authenticator dates: - validation: 2025-01-15 + validation: 2025-02-28 posted: 2022-01-14 categories: - console @@ -15,7 +15,7 @@ categories: You can enable multifactor authentication on your Scaleway account for heightened security. Once enabled, an additional security code generated by your phone is required to access your account. -Multifactor authentication provides extra layers of security. In addition to your password (the first factor), other factors (such as an MFA app) are required to gain access to your account. Even in the event of a leaked password, your account is protected. +Multifactor authentication provides extra layers of security. In addition to your password (the first factor), other factors (such as an MFA app) are required to access your account. Even in the event of a leaked password, your account is protected. @@ -32,17 +32,17 @@ Download the app of your choice and install it onto your smartphone. ## How to enable MFA -1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**. - -2. Scroll to the bottom of your profile page, and click **Enable MFA**. A pop-up displays. - +1. Access the [My security](https://console.scaleway.com/account/security) tab of your User Account page. + Alternatively, click your Organization name on the top-right corner of the console navigation menu, click **Profile**, then **My security**. +2. Click **Enable MFA**, in the **Multifactor authentication** section. A pop-up displays. 3. Enter the code shown on the pop-up into your MFA app, or scan the QR code into your app. Your app sets up MFA for your Scaleway account and displays a 6-digit code. -4. Enter the 6-digit code given by your app into the pop-up box, and click **Submit**. A pop-up displays: - -5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way you can regain access to your account without your MFA app. +4. Enter the 6-digit authentication code given by your app into the pop-up box, then click **Submit**. A pop-up displays. +5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way to regain access to your account without your MFA app. -MFA is now enabled. Next time you log in to your Scaleway account, you will be prompted for an MFA code. Use your MFA app to get the code and enter it in the Scaleway console. +MFA is now enabled on your account. + +Next time you log in to your Scaleway account, you will be prompted for an MFA code. Use your MFA app to get the code and enter it in the Scaleway console. ## How to update MFA @@ -58,12 +58,13 @@ If you no longer have access to the device in which you set up your MFA, you can If you have lost access to your account and are not able to log in, follow the [Cannot log into my account](/account/troubleshooting/cannot-log-into-my-account/) troubleshooting procedure. -1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**. -2. Scroll to the bottom of your profile page, and click **Update MFA**. A pop-up displays. +1. Access the [My security](https://console.scaleway.com/account/security) tab of your User Account page. + Alternatively, click your Organization name on the top-right corner of the console navigation menu, click **Profile**, then **My security**. +2. Click **Update MFA**, in the **Multifactor authentication** section. A pop-up displays. 3. Enter the code shown on the pop-up into your MFA app, or scan the QR code into your app. Your app sets up MFA for your Scaleway account and displays a 6-digit code. 4. Enter the 6-digit code given by your app into the pop-up box, and click **Submit**. A pop-up displays. -5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way you can regain access to your account without your MFA app. +5. Download or copy the backup codes shown, and save them in a safe place. These codes will be the only way to regain access to your account without your MFA app. ## How to disable MFA @@ -71,33 +72,35 @@ If you no longer have access to the device in which you set up your MFA, you can You cannot disable MFA if you are a member of one or more Organizations where MFA is enforced. If you wish to disable MFA, you must first leave these Organizations. If you do not know which of your Organizations enforce MFA, follow the procedure below until step 2. The Organizations will be listed in the **Disable MFA** pop-up. -1. Click to open the Organization drop-down menu in the top-right corner of the console, and select **My Profile**. -2. Scroll to the bottom of the page, and click **Disable MFA**. A pop-up displays. - -3. Type **DISABLE** in the box to confirm, and click **Disable**. +1. Access the [My security](https://console.scaleway.com/account/security) tab of your User Account page. + Alternatively, click your Organization name on the top-right corner of the console navigation menu, click **Profile**, then **My security**. +2. Click **Disable MFA**, in the **Multifactor authentication** section. A pop-up displays. +3. Type **DISABLE** in the box to confirm, then click **Disable**. + +MFA is now disabled on your account. ## How to regain access to your account ### If you lose your MFA device -If you lose your MFA device, you can use the backup codes that were generated when you activated MFA to regain access. +If you lose your authentication device, you can regain access to your account using the backup codes that were generated when you enabled MFA. -When you log into your account, you are prompted for an MFA code: +When you log into your account, you are prompted for an MFA code. - - -Enter one of your backup codes (instead of a code generated by your MFA device in real-time) and click **Send token**. You are logged into your account, and can disable MFA if you wish by [following the instructions above](#how-to-disable-mfa). +Enter one of your **backup codes** instead of a code generated by your MFA device in real-time, then click **Log in**. You are logged into your account and can [disable MFA](#how-to-disable-mfa) if you wish. ### If you lose your MFA device and backup codes -If you lose both your MFA device and backup codes, it is more difficult to regain access to your account. You will need to go through a manual identity verification process. +If you lose both your MFA device and backup codes, you must go through a manual identity verification process to regain access to your account. + +Contact our support team with the following information: + * Email address, + * Postal address, + * Two different documents proving your identity (passport or local ID card for individual accounts + certificate of incorporation for companies), + * A contact phone number, + * A copy of your last Scaleway invoice, or details about the amount charged if you do not have a copy, + * A card or bank statement showing your Scaleway invoice debit. -The only way to regain access to your account is to contact our support team with the following information: - * Email address - * Postal address - * Two different documents proving your identity (passport or local ID card for individual accounts + certificate of incorporation for companies) - * A contact phone number - * A copy of your last Scaleway invoice, or details about the amount charged if you do not have a copy - * A card or bank statement showing your Scaleway invoice debit +Once you have collected all this information, send it to [document@scaleway.com](mailto:document@scaleway.com). -Once you have collected all this information, send it to [document@scaleway.com](mailto:document@scaleway.com). \ No newline at end of file +Our team will then proceed with an identity verification to determine if you can regain access to your account. \ No newline at end of file diff --git a/pages/account/reference-content/protecting-yourself-fraud-phishing.mdx b/pages/account/reference-content/protecting-yourself-fraud-phishing.mdx index a051786819..d5aa9c643b 100644 --- a/pages/account/reference-content/protecting-yourself-fraud-phishing.mdx +++ b/pages/account/reference-content/protecting-yourself-fraud-phishing.mdx @@ -5,7 +5,7 @@ meta: content: h1: Protecting yourself against phishing and fraud paragraph: Protect yourself from fraud and phishing in Scaleway. -tags: login unrecognized-ip phising fraud +tags: login unrecognized-ip phishing fraud dates: validation: 2024-12-05 posted: 2024-05-22 @@ -35,9 +35,9 @@ Phishing is a method where attackers trick you into providing personal informati ## Securing your account -### Multi-factor authentication (MFA) +### Multifactor authentication (MFA) -Enable [Multi-factor authentication (MFA) on your Scaleway account](/account/how-to/use-2fa/#how-to-update-mfa) to add an extra layer of security. MFA requires a second form of verification beyond just a password. +Enable [Multifactor 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/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx b/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx index 7f31691f95..b83d4e61e4 100644 --- a/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx +++ b/pages/dedibox-account/how-to/enable-two-factor-authentication.mdx @@ -18,7 +18,7 @@ Multifactor authentication helps make your account safer. When enabled, after en - A Dedibox account logged into the [console](https://console.online.net) -- Downloaded a multi-factor authenticator application to your phone +- Downloaded a multifactor authenticator application to your phone 1. Click your username, next to _logged in as_, in the top right corner of the Dedibox console. Then click **Security** in the pop-up menu. @@ -35,4 +35,4 @@ Your account is now protected by multifactor authentication, and a security toke Make sure to keep your authentication device secure, as you cannot log in without the authentication token. - + \ No newline at end of file diff --git a/pages/iam/troubleshooting/cannot-use-resources.mdx b/pages/iam/troubleshooting/cannot-use-resources.mdx index 73f64c93c0..5d11fbd169 100644 --- a/pages/iam/troubleshooting/cannot-use-resources.mdx +++ b/pages/iam/troubleshooting/cannot-use-resources.mdx @@ -36,9 +36,9 @@ You (or the IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#appl 2. Make sure that the bearer of the API key (IAM [user](/iam/concepts/#user) or [application](/iam/concepts/#application)) has the appropriate [IAM permissions](/iam/how-to/view-permission-sets/) to perform the desired actions. -3. If you **do not** have [Owner](/iam/concepts/#owner) status for the organization in which you are trying to perform actions, contact the IAM manager or owner of this organization. +3. If you **do not** have [Owner](/iam/concepts/#owner) status for the Organization in which you are trying to perform actions, contact the IAM manager or owner of this Organization. -4. If your are using a command-line tool to interact with Scaleway resources, make sure that there is no environment variable overriding your API key. Refer to the [documentation on environment variables priority](/scaleway-cli/reference-content/environment-variables/#environment-variables-priority) for more information. +4. If you are using a command-line tool to interact with Scaleway resources, make sure that there is no environment variable overriding your API key. Refer to the [documentation on environment variables priority](/scaleway-cli/reference-content/environment-variables/#environment-variables-priority) for more information. If you encounter issues while using Object Storage, refer to the [dedicated troubleshooting page](/object-storage/troubleshooting/api-key-does-not-work/). diff --git a/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx b/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx index b6961d6051..11b0019efe 100644 --- a/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx +++ b/pages/instances/api-cli/managing-instance-snapshot-via-cli.mdx @@ -87,6 +87,4 @@ scw instance snapshot create zone=fr-par-1 name=my-imported-snapshot volume-type When importing existing QCOW / QCOW2 files from Object Storage as Instance snapshots, make sure that the file has the suffix `.qcow` or `.qcow2`. - - - + \ No newline at end of file diff --git a/pages/object-storage/api-cli/create-bucket-policy.mdx b/pages/object-storage/api-cli/create-bucket-policy.mdx index 94b1024f00..22dbf55f25 100644 --- a/pages/object-storage/api-cli/create-bucket-policy.mdx +++ b/pages/object-storage/api-cli/create-bucket-policy.mdx @@ -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](/object-storage/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/pages/serverless-containers/concepts.mdx b/pages/serverless-containers/concepts.mdx index d663d24b12..d837afa273 100644 --- a/pages/serverless-containers/concepts.mdx +++ b/pages/serverless-containers/concepts.mdx @@ -20,7 +20,7 @@ Scaling mechanisms ensure that resources are provisioned dynamically to handle i Autoscaling parameters are [min-scale](/serverless-containers/concepts/#min-scale) and [max-scale](/serverless-containers/concepts/#max-scale). Available scaling policies are: * **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. -* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. +* **RAM usage** to scale based on RAM percentage, suitable for memory-intensive workloads. Refer to the [dedicated documentation](/serverless-containers/reference-content/containers-autoscaling/) for more information on autoscaling. @@ -28,7 +28,7 @@ Refer to the [dedicated documentation](/serverless-containers/reference-content/ Cold start is the time a Container takes to handle a request when it is called for the first time. -Startup process steps are: +The startup process steps are: * Downloading the container image to our infrastructure * Starting the container. Optimize your container startup speed to minimize this step (e.g., avoid waiting for slow connections or downloading large objects at startup) * Waiting for the container to listen on the configured port. @@ -61,7 +61,7 @@ It works similarly to a traditional Linux [cron job](https://en.wikipedia.org/wi ## 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 allow 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 @@ -94,7 +94,7 @@ gRPC is supported on Serverless Containers, as long as you have enabled http2 (` To determine the status of a container, the default health check automatically checks if basic requirements are met, to define the status as `ready`. You can customize the following elements to better fit your use case: - The **probe type** defines the type of check to perform to define if your container is ready: - The **TCP** probe will check if the TCP connection of your Serverless Container is opened on the specified port - - The **HTTP** probe allows you to define a custom path to your Serverless Container to get the readiness status. It can be useful to check if all requirements are met, such as the connection to the database, etc. + - The **HTTP** probe allows you to define a custom path to your Serverless Container to get the readiness status. It can be useful to check if all requirements are met, such as the connection to the database, etc. - The **failure threshold** corresponds to the maximum number of checks that can fail before declaring the Serverless Container in error. Defaults to 30. - The **interval** corresponds to the duration in seconds between every check. Defaults to 10 seconds. - The **path** (HTTP probe type only) corresponds to the endpoint to call you Serverless Container (example: `/health`). @@ -137,7 +137,7 @@ A [vCPU](#vcpu) (Virtual Central Processing Unit) is equivalent to 1000 mvCPU. 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. +Containers in the same namespace can share environment variables, secrets, and access tokens, defined at the namespace level. ## NATS trigger @@ -177,7 +177,7 @@ The registry endpoint parameter is the resource linked to the container image us ## Request timeout -Request timeout is the maximum amount of time a request to a Serverless Container is allowed to run before the request is terminated. Purpose of this parameter is to ensure long-running requests do not hang indefinitely, which could impact ressource usage and scalability. +Request timeout is the maximum amount of time a request to a Serverless Container is allowed to run before the request is terminated. The purpose of this parameter is to ensure long-running requests do not hang indefinitely, which could impact resource usage and scalability. Use cases: * **Shorter timeouts:** Ideal for use cases with quick, predictable response times, such as HTTP APIs or real-time applications. @@ -197,8 +197,8 @@ This process ensures a seamless update experience, minimizing user disruption du ## Sandbox A sandbox is an isolation area for your container. Serverless Containers offer two sandboxing environments: -- **v2** - Recommended for faster cold starts. Can introduce some overhead on specific worklows with consequent amount of *syscalls*. -- **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux system call interface. Prefer this option when processing large amount of *syscalls*. +- **v2** - Recommended for faster cold starts. Can introduce some overhead on specific workflows with consequent amount of *syscalls*. +- **v1** - Legacy sandboxing with slower cold starts, but fully supports Linux system call interface. Prefer this option when processing large amounts of *syscalls*. ## Scale to zero @@ -262,4 +262,4 @@ Unit used to measure the resource consumption of a container. It reflects the am ## Protocol -Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise HTTP/1 is recommended. +Serverless Containers supports **http1** (default) and **http2** (`h2c`). Use HTTP/2 if your container application is configured to listen for HTTP/2 requests, such as a **gRPC** service or a web server that uses HTTP/2 features like multiplexing, otherwise, HTTP/1 is recommended. \ No newline at end of file diff --git a/pages/serverless-functions/concepts.mdx b/pages/serverless-functions/concepts.mdx index 0d1da7203e..644ba84e07 100644 --- a/pages/serverless-functions/concepts.mdx +++ b/pages/serverless-functions/concepts.mdx @@ -20,7 +20,7 @@ Scaling mechanisms ensure that resources are provisioned dynamically to handle i Autoscaling parameters are [min-scale](/serverless-functions/concepts/#min-scale) and [max-scale](/serverless-functions/concepts/#max-scale). Available scaling policies are: * **Concurrent requests:** requests incoming to the resource at the same time. Default value suitable for most use cases. * **CPU usage:** to scale based on CPU percentage, suitable for intensive CPU workloads. -* **RAM usage** to scale based on RAM percentage, suitable for memory intensive workloads. +* **RAM usage** to scale based on RAM percentage, suitable for memory-intensive workloads. ## Build step @@ -32,7 +32,7 @@ Once the Function is built into an image, it will be pushed to [Container Regist Cold Start is the time a function takes to handle a request when it is called for the first time. -Startup process steps are: +The startup process steps are: * Downloading the container image (which contains the built Function) to our infrastructure * Starting the container and the runtime * Waiting for the container to be ready. @@ -41,7 +41,7 @@ Startup process steps are: ## Container Registry -Container Registry is the place where your images of your Serverless Functions are stored before being deployed. +Container Registry is the place where the images of your Serverless Functions are stored before being deployed. ## CRON trigger @@ -49,7 +49,7 @@ A CRON trigger is a mechanism used to automatically invoke a Serverless Function ## 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 allow 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 @@ -125,7 +125,7 @@ The function can then process the message and perform any required actions, such ## Request timeout -Request timeout is the maximum amount of time a request to a Serverless Function is allowed to run before the request is terminated. Purpose of this parameter is to ensure long-running requests do not hang indefinitely, which could impact ressource usage and scalability. +Request timeout is the maximum amount of time a request to a Serverless Function is allowed to run before the request is terminated. The purpose of this parameter is to ensure long-running requests do not hang indefinitely, which could impact resource usage and scalability. Use cases: * **Shorter timeouts:** Ideal for use cases with quick, predictable response times, such as HTTP APIs or real-time applications. @@ -150,7 +150,7 @@ The runtime is the execution environment of your function. Regarding Serverless A sandbox is an isolation area for your function. Serverless Functions offer two sandboxing environments: - **v2** - Recommended for faster cold starts. -- **v1** - Legacy sandboxing with slower cold start, but fully supports Linux system call interface. +- **v1** - Legacy sandboxing with a slower cold start, but fully supports Linux system call interface. ## Scale to zero @@ -209,4 +209,4 @@ Triggers can take many forms, such as HTTP requests, messages from a queue or a ## vCPU-s -Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time. +Unit used to measure the resource consumption of a container. It reflects the amount of vCPU used over time. \ No newline at end of file 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 8cc5821e55..f5530d08d7 100644 --- a/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx +++ b/tutorials/cilicon-self-hosted-ci-on-apple-silicon/index.mdx @@ -56,7 +56,7 @@ Cilicon uses YAML configuration files for settings, expected to be in a `cilicon ### GitHub Actions provisioner -To use the GitHub Actions provisioner, create and install a new GitHub App with `Self-hosted runners` `Read & Write` permissions on the organization level. Download the private key file and reference it in the configuration file. +To use the GitHub Actions provisioner, create and install a new GitHub App with `Self-hosted runners` `Read & Write` permissions on the Organization level. Download the private key file and reference it in the configuration file. ```yaml source: oci://ghcr.io/cirruslabs/macos-ventura-xcode:14.3.1 diff --git a/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx b/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx index 4cb5ec6818..04c8a4bb4a 100644 --- a/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx +++ b/tutorials/nextjs-app-serverless-functions-sqldb/index.mdx @@ -943,7 +943,7 @@ If you happen to encounter any issues, first check that you meet all the require Description - ``` - You can also find and compare your Project and organization ID in the [Scaleway console settings](https://console.scaleway.com/project/settings). + You can also find and compare your Project and Organization ID in the [Scaleway console settings](https://console.scaleway.com/project/settings). - You have **Docker Engine** installed. Running the `docker -v` command in a terminal should display your currently installed docker version: ```