Release 27.04.2024

* Translations updated. * Fixes and improvements.
yandex-cloud · Apr 27, 2024 · 531d7bc · 531d7bc
1 parent c7a2910
commit 531d7bc
Show file tree

Hide file tree

Showing 246 changed files with 663 additions and 478 deletions.
diff --git a/README.md b/README.md
@@ -1,14 +1,14 @@
 # Документация Yandex Cloud
 
-Приветствуем в репозитории yandex-cloud/docs. Здесь вы можете предложить дополнения и правки для [документации](https://cloud.yandex.ru/docs) Yandex Cloud или сделать их самостоятельно и получить грант в рамках контент-программы.
+Приветствуем в репозитории yandex-cloud/docs. Здесь вы можете предложить дополнения и правки для [документации](https://yandex.cloud/ru/docs) Yandex Cloud или сделать их самостоятельно и получить грант в рамках контент-программы.
 
 ## Предложить правки
 
 Откройте Issue и напишите свои замечания и предложения там. Мы вернемся с ответом. Если вам требуется помощь в работе с облаком, обратитесь в техническую поддержку.
 
 ## Поучаствуйте в контент-программе
 
-[Контент-программа Yandex Cloud](https://cloud.yandex.ru/content-program) позволяет вам самим написать документацию и получить за нее грант на ваш платежный аккаунт. Поучаствовать в контент-программе можно двумя способами:
+[Контент-программа Yandex Cloud](https://yandex.cloud/ru/content-program) позволяет вам самим написать документацию и получить за нее грант на ваш платежный аккаунт. Поучаствовать в контент-программе можно двумя способами:
 
 1. Если вы заметили опечатку или у вас есть небольшая правка, сделайте PR. Такие правки мы рассматриваем быстро и обычно они не требуют обсуждения.
 1. Если вы хотите написать большой текст, пошаговое руководство или внести крупные смысловые правки, откройте Issue и расскажите, о чем вы хотите написать. Не нужно сразу приносить большой PR: давайте сначала обсудим ваши идеи и вместе решим, как действовать дальше.

diff --git a/en/_includes/data-proc/cli-job-intro.md b/en/_includes/data-proc/cli-job-intro.md
@@ -1,3 +1,3 @@
-Jobs are run using the {{ yandex-cloud }} CLI through the {{ dataproc-name }} agent installed on the cluster master host. Job parameters are communicated to the agent through the [Data Proc API](../../data-proc/api-ref/Job/index.md).
+Jobs are run using the {{ yandex-cloud }} CLI through the {{ dataproc-name }} agent installed on the cluster master host. Job parameters are communicated to the agent through the [{{ dataproc-name }} API](../../data-proc/api-ref/Job/index.md).
 
 The executable file and its dependencies must be located in a storage accessible to the {{ dataproc-name }} cluster service account. The executed application itself must have access to the storages in which the source data set and execution results are saved.
diff --git a/en/_includes/datalens/internal/datalens-yt-connection.md b/en/_includes/datalens/internal/datalens-yt-connection.md
@@ -4,7 +4,7 @@ To create a {{ ytsaurus-name }} CHYT connection:
 {% include [datalens-workbooks-collections-note](../../../_includes/datalens/operations/datalens-workbooks-collections-note.md) %}
 
 
-1. Go to the [connections page](https://datalens.yandex.ru/connections).
+1. Go to the [connections page]({{ link-datalens-main }}/connections).
 1. Click **Create connection**.
 1. Select **{{ ytsaurus-name }} CHYT** as the connection type.
 

diff --git a/en/_includes/datalens/operations/datalens-public-chart.md b/en/_includes/datalens/operations/datalens-public-chart.md
@@ -2,7 +2,7 @@
 {% include [datalens-workbooks-collections-select-note](./datalens-workbooks-collections-select-note.md) %}
 
 
-1. On the [navigation page](https://datalens.yandex.ru/navigation), find the chart you need and open it.
+1. On the [navigation page]({{ link-datalens-main }}/navigation), find the chart you need and open it.
 1. At the top of the wizard interface, click ![image](../../../_assets/console-icons/ellipsis.svg) and select ![image](../../../_assets/console-icons/nodes-right.svg) **Public access**.
 1. In the window that opens, set up public access as follows:
 

diff --git a/en/_includes/datalens/operations/datalens-public-dashboard.md b/en/_includes/datalens/operations/datalens-public-dashboard.md
@@ -2,7 +2,7 @@
 {% include [datalens-workbooks-collections-select-note](./datalens-workbooks-collections-select-note.md) %}
 
 
-1. On the [navigation page](https://datalens.yandex.ru/navigation), find the dashboard you need and open it.
+1. On the [navigation page]({{ link-datalens-main }}/navigation), find the dashboard you need and open it.
 1. At the top of the dashboard interface, click ![image](../../../_assets/console-icons/ellipsis.svg) and select ![image](../../../_assets/console-icons/nodes-right.svg) **Public access**.
 1. In the window that opens, set up public access as follows:
 

diff --git a/en/_includes/datasphere/pay-for-resources.md b/en/_includes/datasphere/pay-for-resources.md
@@ -3,4 +3,4 @@ How you pay for shared {{ ml-platform-name }} resources depends on the resource
 * Storing a [dataset](../../datasphere/concepts/dataset.md) is paid from the billing account of the <q>parent</q> community whose project the dataset belongs to.
 * You can use secrets, Docker images, and aliases free-of-charge.
 * S3 connectors are free of charge, but, storing objects in {{ objstorage-full-name }} [buckets](../../storage/concepts/bucket.md) is paid from the billing account linked to the cloud the bucket belongs to.
-* You can use [Data Proc](../../datasphere/concepts/data-proc.md) templates free-of-charge. However, running a cluster automatically created from a template is paid from the billing account of the cloud that the cluster belongs to.
+* You can use [{{ dataproc-name }}](../../datasphere/concepts/data-proc.md) templates free-of-charge. However, running a cluster automatically created from a template is paid from the billing account of the cloud that the cluster belongs to.
diff --git a/en/_includes/iam/federated-user-auth.md b/en/_includes/iam/federated-user-auth.md
@@ -1,3 +1,3 @@
 To log in to the management console, federated users must follow the link with the federation ID:
 
-`https://{{ console-host }}/federations/<federation_ID>`
+`{{ link-console-main }}/federations/<federation_ID>`
diff --git a/en/_includes/organization/get-acs-url.md b/en/_includes/organization/get-acs-url.md
@@ -0,0 +1,5 @@
+1. Go to [{{ org-full-name }}]({{ link-org-main }}).
+
+1. In the left-hand panel, select [{{ ui-key.yacloud_org.pages.federations }}]({{ link-org-federations }}) ![icon-federation](../../_assets/console-icons/vector-square.svg).
+
+1. From the list, pick the federation you are configuring access to, and copy its ACS URL.
diff --git a/en/_includes/security/security-bulletins/cve-2023-44487.md b/en/_includes/security/security-bulletins/cve-2023-44487.md
@@ -59,7 +59,7 @@ Update or patch version:
 
    <https://www.nginx.com/blog/http-2-rapid-reset-attack-impacting-f5-nginx-products/>
 
-* Use [{{ sws-full-name }}](https://cloud.yandex.ru/services/smartwebsecurity)
+* Use [{{ sws-full-name }}](https://yandex.cloud/en/services/smartwebsecurity)
 
 ### Safe version of vulnerable product or patch {#safe-version}
 

diff --git a/en/_includes/security/security-bulletins/cve-2023-5043.md b/en/_includes/security/security-bulletins/cve-2023-5043.md
@@ -38,7 +38,7 @@ Here is what we recommend in order to avoid exploiting these vulnerabilities:
 
 1. Add the `strict-validate-path-type` option to `Configmap`.
 
-1. Use a policy engine, such as [Kyverno](https://cloud.yandex.com/en/marketplace/products/yc/kyverno), to validate the paths used in the Ingress rules. You can find [this ready-to-use policy](https://kyverno.io/policies/nginx-ingress/restrict-ingress-paths/restrict-ingress-paths/) on the Kyverno website.
+1. Use a policy engine, such as [Kyverno](https://yandex.cloud/en/marketplace/products/yc/kyverno), to validate the paths used in the Ingress rules. You can find [this ready-to-use policy](https://kyverno.io/policies/nginx-ingress/restrict-ingress-paths/restrict-ingress-paths/) on the Kyverno website.
 
 ### Safe version of vulnerable product or patch {#safe-version}
 

diff --git a/en/_includes/speechkit/try-speechkit.md b/en/_includes/speechkit/try-speechkit.md
@@ -1 +1 @@
-To try out the Text-to-Speech and Speech-to-Text product demos, visit the [{{ speechkit-name }} page](https://cloud.yandex.ru/services/speechkit#demo) on our website.
+To try out the Text-to-Speech and Speech-to-Text product demos, visit the [{{ speechkit-name }} page](https://yandex.cloud/en/services/speechkit#demo) on our website.
diff --git a/en/_includes/support/notify.md b/en/_includes/support/notify.md
@@ -12,7 +12,7 @@ By default, notifications about upcoming maintenance and notifications from serv
 
 {% note info %}
 
-You can add users with a [Yandex account](../../iam/concepts/index.md#passport) as well as [federated users](../../iam/concepts/index.md#saml-federation). Federated users should specify their email address in their account settings.
+You can add users with a [Yandex account](../../iam/concepts/users/accounts.md#passport) as well as [federated users](../../iam/concepts/users/accounts.md#saml-federation). Federated users should specify their email address in their account settings.
 
 {% endnote %}
 

diff --git a/en/_includes/vpc/public-ip-list.md b/en/_includes/vpc/public-ip-list.md
@@ -4,7 +4,7 @@ For {{ yandex-cloud }} network resources, one can use two types of IP addresses:
 
 * IP addresses used by {{ yandex-cloud }} to run services, e.g., to write [audit logs](../../audit-trails/concepts/format.md) in {{ at-name }}.
 
-## Service IP addresses for users
+## Service IP addresses for users {#user-ips}
 
 The following IP address ranges are assigned to resources that are available to users:
 
@@ -38,7 +38,7 @@ For example, the resources assigned such IP address ranges are:
 * NAT instances
 * {{ network-load-balancer-name }} and {{ alb-name }} load balancers
 
-## IP addresses used by {{ yandex-cloud }}
+## IP addresses used by {{ yandex-cloud }} {#yandex-cloud-ips}
 
 The following IP address ranges are assigned to the resources that support {{ yandex-cloud }} operation:
 

diff --git a/en/_qa/compute/disks.md b/en/_qa/compute/disks.md
@@ -159,7 +159,7 @@ A snapshot is created asynchronously. You can resume writing data to your disk i
 
 This is not supported yet. However, you can copy data from a VM using application software, such as rsync, dd, or GNU Wget.
 
-If you would like us to implement downloading or manually exporting VM images and disk snapshots to external resources or a local device, [suggest](https://cloud.yandex.ru/features) this idea or vote for a similar one. We regularly review all the suggestions and add them to our development roadmap. We will notify you as soon as the idea you suggested or voted for has been implemented.
+If you would like us to implement downloading or manually exporting VM images and disk snapshots to external resources or a local device, [suggest](https://yandex.cloud/ru/features) this idea or vote for a similar one. We regularly review all the suggestions and add them to our development roadmap. We will notify you as soon as the idea you suggested or voted for has been implemented.
 
 #### How do I detect processes that put a heavy load on a disk? {#disk-heavy-load}
 

diff --git a/en/_qa/data-proc/general.md b/en/_qa/data-proc/general.md
@@ -38,7 +38,7 @@ This error occurs because the [lightweight clusters](../../data-proc/concepts/in
 
 We also recommend using [{{ objstorage-full-name }} buckets](../../storage/concepts/bucket.md) to work with jobs. You can [upload scripts to them](../../storage/operations/objects/upload.md) to run jobs. These scripts are stored as objects one can [get links](../../storage/operations/objects/link-for-download.md) to. As a result, you can use links from {{ objstorage-name }} instead of `file:/` format links in your jobs.
 
-#### Why does the `Create Data Proc cluster Error: 0 Address space exhausted` error occur and how do I fix it? {#addresses-exhausted}
+#### Why does the `Create {{ dataproc-name }} cluster Error: 0 Address space exhausted` error occur and how do I fix it? {#addresses-exhausted}
 
 The error means that your {{ dataproc-name }} cluster's subnet has run out of IPs that can be allocated to cluster hosts. To check how many IPs are available, [view the list of addresses used](../../vpc/operations/subnet-used-addresses.md) in the subnet and its mask.
 

diff --git a/en/_qa/data-proc/minitoc/general.md b/en/_qa/data-proc/minitoc/general.md
@@ -14,7 +14,7 @@
 
 * [Why does the `Using fileUris is forbidden on lightweight cluster` error occur and how do I fix it?](#file-uri)
 
-* [Why does the `Create Data Proc cluster Error: 0 Address space exhausted` error occur and how do I fix it?](#addresses-exhausted)
+* [Why does the `Create {{ dataproc-name }} cluster Error: 0 Address space exhausted` error occur and how do I fix it?](#addresses-exhausted)
 
 * [Why is my cluster's status `Unknown`?](#unknown)
 

diff --git a/en/_qa/datalens/pricing.md b/en/_qa/datalens/pricing.md
@@ -0,0 +1,37 @@
+# Billing and payment
+
+### Will the new features only be available in the Business service plan? {#new-features-on-business}
+
+No, new basic features will be available across all [service plans](../../datalens/pricing.md). However, certain updates will be exclusive to the paid plan.
+
+### Can I continue using the old {{ datalens-short-name }} with no service plan applied? {#use-datalens-without-pricing}
+
+On April 23, 2024, all {{ datalens-short-name }} instances will be migrated to the free Community plan. You can continue using this plan if your users authenticate with [Yandex ID](https://yandex.com/support/id/index.html) / [Yandex 360](https://yandex.com/support/business/index.html). No restrictions will apply.
+
+If you had set up authentication with an [identity federation](../../organization/concepts/add-federation.md) (corporate SSO, e.g., via LDAP), the free Community plan will remain effective for your {{ datalens-short-name }} instance until December 31, 2024. To continue using {{ datalens-short-name }}, you should plan an upgrade to the Business plan or switch to Yandex ID authentication.
+
+### What is the timeline for introducing the billing system? {#timeline}
+
+The billing system for {{ datalens-short-name }} will be introduced in stages:
+
+* March 20, 2024: We announce the service plans and notify all our users.
+* April 23, 2024: You can change your service plan to Business free of charge.
+* June 1, 2024: We start charging for the Business service plan.
+* December 31, 2024: We discontinue SSO for the existing free Community plan users.
+
+### Can I go back to the free Community service plan? {#free-rollback}
+
+Yes, you can. The move can only be effected from the beginning of the next month. However, you will lose access to the paid service plan features.
+
+### Is a partial upgrade to Business possible? For example, can I have 10 users on Business and the rest of them on the Community plan? {#part-business}
+
+No, the upgrade takes effect for the whole [organization](../../datalens/concepts/organizations.md) for which {{ datalens-short-name }} is enabled.
+
+### What if I have both federated and regular users? {#sso-and-users-pricing}
+
+If you need to retain federated users, schedule an upgrade to the Business service plan. Note that, under this plan, you will be charged for all your users — both SSO and Yandex ID.
+
+### How will you count the users of public charts and dashboards? {#public-pricing}
+
+[Public URLs](../../datalens/concepts/datalens-public.md) to dashboards and charts work without authentication and do not contribute to the active user count. Public charts and dashboards will be free of charge across all service plans.
+
diff --git a/en/_roles/dataproc/admin.md b/en/_roles/dataproc/admin.md
@@ -1 +1 @@
-The `dataproc.admin` role enables you to create, edit, and delete clusters and jobs, view information about them, provides access to the Data Proc component web interfaces, and manages access to clusters. It includes the `dataproc.editor` role.
+The `dataproc.admin` role enables you to create, edit, and delete clusters and jobs, view information about them, provides access to the {{ dataproc-name }} component web interfaces, and manages access to clusters. It includes the `dataproc.editor` role.
diff --git a/en/_roles/dataproc/agent.md b/en/_roles/dataproc/agent.md
@@ -1,4 +1,4 @@
-The `dataproc.agent` role allows the service account assigned to the Data Proc cluster to notify the service of the status of each host in the cluster.
+The `dataproc.agent` role allows the service account assigned to the {{ dataproc-name }} cluster to notify the service of the status of each host in the cluster.
 
 This role must be assigned to the service account specified when creating the cluster.
 

diff --git a/en/_roles/dataproc/editor.md b/en/_roles/dataproc/editor.md
@@ -1 +1 @@
-The `dataproc.editor` role enables you to create, edit, and delete clusters and jobs, view information about them, and provides access to the Data Proc component web interfaces. It includes the `dataproc.viewer` role.
+The `dataproc.editor` role enables you to create, edit, and delete clusters and jobs, view information about them, and provides access to the {{ dataproc-name }} component web interfaces. It includes the `dataproc.viewer` role.
diff --git a/en/_roles/dataproc/provisioner.md b/en/_roles/dataproc/provisioner.md
@@ -1 +1 @@
-The `dataproc.provisioner` role grants access to the API to create, update, and delete Data Proc cluster objects.
+The `dataproc.provisioner` role grants access to the API to create, update, and delete {{ dataproc-name }} cluster objects.
diff --git a/en/_roles/dataproc/user.md b/en/_roles/dataproc/user.md
@@ -1 +1 @@
-The `dataproc.user` role provides access to the Data Proc component web interfaces and enables you to create jobs. It includes the `dataproc.viewer` role.
+The `dataproc.user` role provides access to the {{ dataproc-name }} component web interfaces and enables you to create jobs. It includes the `dataproc.viewer` role.
diff --git a/en/_tutorials/archive/ha-regional-glusterfs-high-performance.md b/en/_tutorials/archive/ha-regional-glusterfs-high-performance.md
@@ -183,13 +183,13 @@ The infrastructure support costs include:
       {% note info %}
 
       In this use case, we will deploy 30 VMs. You can change this number depending on the requirements for the final storage size or total bandwidth.
-      The maximum aggregate bandwidth of the entire system is calculated as the product of each segment's bandwidth (450 MB/s for [network SSDs](https://cloud.yandex.ru/docs/compute/concepts/disk#disks-types)) and the number of segments (30), which is about 13.5 GB/s.
+      The maximum aggregate bandwidth of the entire system is calculated as the product of each segment's bandwidth (450 MB/s for [network SSDs](../../compute/concepts/disk.md#disks-types)) and the number of segments (30), which is about 13.5 GB/s.
       The system capacity is calculated as the product of the number of segments (30) and the size of each storage (1 TB), which amounts to 30 TB.
 
       {% endnote %}
 
    1. If you chose a non-default name when creating the SSH key pair, under `local_pubkey_path`, change `default` to `<path_to_the_public_SSH_key>`.
-   1. If you need enhanced performance without guaranteed data durability, you can use [non-replicated SSDs](https://cloud.yandex.ru/docs/compute/concepts/disk#nr-disks). To do this, under `disk_type`, change `default` to `network-ssd-nonreplicated`. In addition, make sure the `default` value under `disk_size` is a multiple of 93.
+   1. If you need enhanced performance without guaranteed data durability, you can use [non-replicated SSDs](../../compute/concepts/disk.md#nr-disks). To do this, under `disk_type`, change `default` to `network-ssd-nonreplicated`. In addition, make sure the `default` value under `disk_size` is a multiple of 93.
 
 ## Deploy your resources {#deploy-resources}
 

diff --git a/en/_tutorials/datalens/data-from-csv-geo-visualization.md b/en/_tutorials/datalens/data-from-csv-geo-visualization.md
@@ -423,7 +423,7 @@ You can switch the **Number of accidents by region** chart to **Death rate by re
 
 Sometimes, heat maps are not very informative. Upload the polygon reference and add a chart with a color fill for Russian regions.
 
-1. Download the [**Regions.csv**](https://{{ s3-storage-host }}/doc-files/Regions.csv) file.
+1. Download the [**Regions.csv**](https://storage.yandexcloud.net/doc-files/Regions.csv) file.
 1. Open the `dtp_data` connection.
 1. Click **Upload files** and select the downloaded file.
 1. Take a look at a preview of the file data. For the **Column header** parameter, set the **Yes** value.