Release 13.03.2024

* Billing, Cloud Functions, Tutorials: added tutorial on how to create triggers that invokes a Cloud Functions functions to stop VM instances and send notifications to Telegram.
* Cloud DNS: added Monitoring metrics reference.
* Cloud Logging: updated list of services that can write logs to Cloud Logging.
* Managed Service for Apache Kafka: added instructions on migrating cluster topics to a new availability zone.
* Translations updated.
* Fixes and improvements.

en/_includes/audit-trails/data-plane-on-console.md

@@ -3,4 +3,3 @@
 * **{{ ui-key.yacloud.audit-trails.label_collecting-logs }}**: Select `{{ ui-key.yacloud.common.enabled }}`.
 * Select the [services](../../audit-trails/concepts/index.md#data-plane-logs) to collect audit logs for.
 * For each service you select, specify the audit log collection [scope](../../audit-trails/concepts/trail.md#collecting-area) and objects.
-

en/_includes/audit-trails/events/storage-events.md

@@ -11,12 +11,4 @@
 | `BucketPolicyUpdate` | Updating the access policies for a bucket |
 | `BucketTagsUpdate` | Updating bucket tags |
 | `BucketUpdate` | Updating a bucket |
-| `BucketWebsiteUpdate` | Updating a website configuration |
-| `ObjectAclUpdate` | Updating an object's ACL in a bucket ^*^ |
-| `ObjectCreate` | Creating an object in a bucket ^*^ |
-| `ObjectDelete` | Deleting an object from a bucket ^*^ |
-| `ObjectUpdate` | Updating an object in a bucket ^*^ |
-| `ObjectTagsDelete` | Deleting object tags |
-| `ObjectTagsUpdate` | Updating object tags |
-
-\* The audit log does not include the above events by default. To find out whether these events can be added to the audit log, contact [support]({{ link-console-support }}).
+| `BucketWebsiteUpdate` | Updating a website configuration |

en/_includes/backup-image-snapshot-comparison.md

@@ -0,0 +1,6 @@
+| | Disk snapshots in {{ compute-name }} | {{ backup-name }} |
+| --- | --- | --- |
+| **Granularity** | Disk | VMs with all disks.<br>We may also add support for VM application backups. |
+| **Disk types** | Network SSD and HDD | Any:<br>Network SSD and HDD,<br>non-replicated disks,<br>and local disks on [dedicated hosts](../compute/concepts/dedicated-host.md) |
+| **Application awareness** | No | To be implemented |
+| **Pricing** | Per disk | Per VM |

en/_includes/compute/boot-disk-recover.md

@@ -1 +1 @@
-You cannot recover a boot disk of an existing VM from a snapshot or image. However, you can create a new VM to recover a boot disk from a snapshot. To recover a boot disk on an existing VM, use [{{ backup-name }}](../../backup/index.yaml).
+You cannot recover a boot disk of an existing VM from a snapshot or image. However, you can create a new VM to recover a boot disk from a snapshot. To recover a boot disk on an existing VM, use [{{ backup-full-name }}](../../backup/index.yaml).

en/_includes/compute/public-image-support.md

@@ -0,0 +1 @@
+The terms and conditions of technical support for public images may differ. For more information, see the product page in [{{ marketplace-full-name }}](/marketplace).

en/_includes/compute/serial-console-warning.md

@@ -3,7 +3,7 @@
 When assessing the risk of enabling access via the serial console, consider the following:
 
 * The VM can still be managed from the internet even if there is no external IP address.
-   To access the VM serial console from the {{ yandex-cloud }} management console, a user must be authenticated in the {{ yandex-cloud }} management console and have the proper rights to the VM. One can access the VM serial console from an SSH client application (such as PuTTY) or the YC CLI via SSH key authentication. To reduce the risk of web session hijacking, you should closely monitor your SSH key and make sure you terminate the web session.
+   To access the VM serial console from the {{ yandex-cloud }} management console, a user must be authenticated in the {{ yandex-cloud }} management console and have the proper permissions to the VM. One can access the VM serial console from an [SSH](../../compute/operations/vm-connect/ssh.md) client application, such as PuTTY, or the [YC CLI](../../cli/) via SSH key authentication. To reduce the risk of web session hijacking, you should closely monitor your SSH key and make sure you terminate the web session.
 
 * The session will be simultaneously shared by all users who have access to the serial console.
    Users will be able to see each other's actions if concurrently watching the serial console's output.
@@ -14,6 +14,4 @@ We recommend using the serial console only when absolutely necessary, grant acce
 
 Make sure you [disable access](../../compute/operations/serial-console/disable.md) after you finish using the serial console.
 
-[Federated users](../../organization/concepts/add-federation.md) can only connect to the serial console using the [CLI](../../cli/) or [SSH](../../compute/operations/vm-connect/ssh.md). These users cannot access the serial console from the {{ yandex-cloud }} management console.
-
 {% endnote %}

en/_includes/data-transfer/connectivity-marix.md

@@ -11,7 +11,7 @@ Possible source and target combinations:
 | ![clickhouse](../../_assets/data-transfer/icons/clickhouse-icon.svg =10x)<br>[{{ CH }}](../../data-transfer/operations/endpoint/source/clickhouse.md) | - | - | - | [C](../../data-transfer/tutorials/managed-clickhouse) | - | - | - | - | - | - | - | ![clickhouse](../../_assets/data-transfer/icons/clickhouse-icon.svg =10x)<br>[{{ CH }}](../../data-transfer/operations/endpoint/source/clickhouse.md) |
 | ![greenplum](../../_assets/data-transfer/icons/greenplum-icon.svg =10x)<br>[{{ GP }}](../../data-transfer/operations/endpoint/source/greenplum.md) | [C^1^](../../data-transfer/tutorials/greenplum-to-postgresql.md) | - | - | [C](../../data-transfer/tutorials/greenplum-to-clickhouse.md) | [C^1^](../../data-transfer/tutorials/managed-greenplum.md) | - | - | - | - | - | - | ![greenplum](../../_assets/data-transfer/icons/greenplum-icon.png =10x)<br>[{{ GP }}](../../data-transfer/operations/endpoint/source/greenplum.md) |
 | ![ydb](../../_assets/data-transfer/icons/ydb-icon.svg =10x)<br>[{{ ydb-short-name }}](../../data-transfer/operations/endpoint/source/ydb.md) | - | - | - | CR^1^ | - | - | C^1^ | [CR^1^](../../data-transfer/tutorials/cdc-ydb.md) | [CR^1^](../../data-transfer/tutorials/ydb-to-yds.md) | - | - | ![ydb](../../_assets/data-transfer/icons/ydb-icon.svg =10x)<br>[{{ ydb-short-name }}](../../data-transfer/operations/endpoint/source/ydb.md) |
-| ![object storage](../../_assets/data-transfer/icons/object-storage-icon.svg =10x)<br>[Object Storage](../../data-transfer/operations/endpoint/source/object-storage.md) | [CR^2^](../../data-transfer/tutorials/object-storage-to-postgresql.md) | CR^2^ | - | [CR^2^](../../data-transfer/tutorials/object-storage-to-clickhouse.md) | CR^2^ | CR^2^ | - | - | - | - | - | ![object storage](../../_assets/data-transfer/icons/object-storage-icon.svg =10x)<br>[Object Storage](../../data-transfer/operations/endpoint/source/object-storage.md) |
+| ![object storage](../../_assets/data-transfer/icons/object-storage-icon.svg =10x)<br>[Object Storage](../../data-transfer/operations/endpoint/source/object-storage.md) | [CR^2^](../../data-transfer/tutorials/object-storage-to-postgresql.md) | CR^2^ | - | [CR^2^](../../data-transfer/tutorials/object-storage-to-clickhouse.md) | CR^2^ | [CR^2^](../../data-transfer/tutorials/object-storage-to-ydb.md) | - | - | - | - | - | ![object storage](../../_assets/data-transfer/icons/object-storage-icon.svg =10x)<br>[Object Storage](../../data-transfer/operations/endpoint/source/object-storage.md) |
 | ![metrica](../../_assets/data-transfer/icons/metrica.png =32x)<br>[{{ metrika-endpoint }}](../../data-transfer/operations/endpoint/source/metrika.md) | - | - | - | [R^1^](../../data-transfer/tutorials/metrika-to-clickhouse.md) | - | - | - | - | - | - | - | ![metrica](../../_assets/data-transfer/icons/metrica.png =32x)<br>[{{ metrika-endpoint }}](../../data-transfer/operations/endpoint/source/metrika.md) |
 | ![yds](../../_assets/data-transfer/icons/yds-icon.svg =10x)<br>[{{ yds-short-name }}](../../data-transfer/operations/endpoint/source/data-streams.md) | R^1^ | R^1^ | R^1^ | [R^1^](../../data-transfer/tutorials/yds-to-clickhouse.md) | R^1^ | R^1^ | [R^1^](../../data-transfer/tutorials/yds-to-objstorage.md) | R^1^ | R^1^ | R^1^ | [R^1^](../../data-transfer/tutorials/trails-to-os.md) | ![yds](../../_assets/data-transfer/icons/yds-icon.svg =10x)<br>[{{ yds-full-name }}](../../data-transfer/operations/endpoint/source/data-streams.md) |
 | ![kafka](../../_assets/data-transfer/icons/kafka-icon.svg =10x)<br>[{{ KF }}](../../data-transfer/operations/endpoint/source/kafka.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mpg.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mmy.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mmg.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mch) | [R^1^](../../data-transfer/tutorials/managed-kafka-to-greenplum.md) | [R^1^](../../data-transfer/tutorials/mkf-to-ydb.md) | R^1^ | [R^1^](../../data-transfer/tutorials/mkf-to-mkf.md) | [R^1^](../../data-transfer/tutorials/mkf-to-yds.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mes.md) | [R^1^](../../data-transfer/tutorials/mkf-to-mos.md) | ![kafka](../../_assets/data-transfer/icons/kafka-icon.svg =10x)<br>[{{ KF }}](../../data-transfer/operations/endpoint/source/kafka.md) |

en/_includes/data-transfer/endpoints/targets/pg-prepare.md

@@ -4,20 +4,6 @@
 
    1. Make sure that the {{ PG }} major version on the target is not lower than that on the source.
 
-   1. Disable the following settings on the target:
-
-      * Integrity checks for foreign keys
-      * Triggers
-      * Other constraints
-
-      {% note warning %}
-
-      Do not reactivate these settings before the transfer is complete. This will ensure data integrity with respect to foreign keys.
-
-      If you use the _{{ dt-type-copy-repl }}_ transfer type, you can enable the settings again after the [copy stage](../../../../data-transfer/concepts/transfer-lifecycle.md#copy-and-replication) is completed.
-
-      {% endnote %}
-
    1. In the target database, [enable the same extensions](../../../../managed-postgresql/operations/extensions/cluster-extensions.md) that are enabled in the source database.
 
    1. Make sure the target has the `DROP transfer tables` cleanup policy selected.
@@ -49,20 +35,6 @@
 
    1. Make sure that the {{ PG }} major version on the target is not lower than that on the source.
 
-   1. Disable the following settings on the target:
-
-      * Integrity checks for foreign keys
-      * Triggers
-      * Other constraints
-
-      {% note warning %}
-
-      Do not reactivate these settings before the transfer is complete. This will ensure data integrity with respect to foreign keys.
-
-      If you use the _{{ dt-type-copy-repl }}_ transfer type, you can enable the settings again after the [copy stage](../../../../data-transfer/concepts/transfer-lifecycle.md#copy-and-replication) is completed.
-
-      {% endnote %}
-
    1. In the target database, enable the same extensions that are enabled in the source database.
 
    1. Make sure the target has the `DROP transfer tables` cleanup policy selected.

en/_includes/edit-cells.md

@@ -1,5 +1,5 @@
-* In the selected cell, click ![](../_assets/wiki/svg/edit.svg) and enter the value. The height of the row depends on the contents of the cell in which the largest value is recorded.
-* To format the text, use [Markdown markup](../wiki/basic-markup.md). 
-* To switch to a new row inside a cell, press the **Shift** + **Enter**.
-* To open the input field in a separate window, click ![](../_assets/wiki/svg/write.svg). 
-* To save the changes, exit the cell editing window. Changes are saved automatically.
+* Click ![](../_assets/wiki/svg/edit.svg) in the selected cell and enter a value. The row height depends on the content of the cell where the largest value is written.
+* Use the [Markdown markup](../wiki/wysiwyg/text-format.md) to format text.
+* To switch to a new row in a cell, press the **Shift** + **Enter** hotkey.
+* To open an input field in a separate window, click ![](../_assets/wiki/svg/write.svg).
+* To save the changes, exit the cell editing window. This saves the changes automatically.

en/_includes/instance-groups/instance-group-list.md

@@ -1,5 +1,10 @@
 ```bash
 {{ yc-compute-ig }} list
+```
+
+Result:
+
+```text
 +----------------------+-----------------------+------+
 |          ID          |         NAME          | SIZE |
 +----------------------+-----------------------+------+

en/_includes/managed-kubernetes/note-another-catalog-network.md

@@ -3,6 +3,7 @@
 If you select a [cloud network](../../vpc/concepts/network.md#network) from another [folder](../../resource-manager/concepts/resources-hierarchy.md#folder), [assign](../../iam/operations/sa/assign-role-for-sa.md) the resource [service account](../../iam/concepts/users/service-accounts.md) the following [roles](../../iam/concepts/access-control/roles.md) in this folder:
 * [{{ roles-vpc-private-admin }}](../../vpc/security/index.md#vpc-private-admin)
 * [{{ roles-vpc-user }}](../../vpc/security/index.md#vpc-user)
+* [vpc.bridgeAdmin](../../vpc/security/index.md#vpc-bridge-admin)
 
 To use a [public IP address](../../vpc/concepts/address.md#public-addresses), also [assign](../../iam/operations/sa/assign-role-for-sa.md) the [{{ roles-vpc-public-admin }}](../../vpc/security/index.md#vpc-public-admin) role.
 

en/_includes/mdb/mkf/truststore.md

@@ -0,0 +1,33 @@
+TrustStore is a trusted certificate store used in JKS files. It serves for authenticating a client when connecting to the server. The server validates the client using certificates stored in TrustStore. However, the client stores the private key and the certificate on their side in KeyStore.
+
+In the example below, TrustStore is used to connect to a {{ mkf-name }} cluster. With no TrustStore created, the {{ KF }} web interface will lack information about the cluster.
+
+To use TrustStore:
+
+1. Create an SSL certificate:
+
+   ```bash
+   sudo mkdir -p {{ crt-local-dir }} && \
+   sudo wget "{{ crt-web-path }}" \
+        --output-document {{ crt-local-dir }}YandexCA.crt && \
+   sudo chmod 0655 {{ crt-local-dir }}YandexCA.crt
+   ```
+
+1. Create a directory named `/truststore`:
+
+   ```bash
+   mkdir /truststore
+   ```
+
+   It will store the `truststore.jks` file. You need a separate directory so that the file path is correctly recognized in commands and configuration files.
+
+1. Upload the `YandexCA.crt` certificate to the `truststore.jks` file:
+
+   ```bash
+   sudo keytool -import \
+                -file {{ crt-local-dir }}YandexCA.crt \
+                -alias "kafka-ui-cert" \
+                -keystore /truststore/truststore.jks
+   ```
+
+   You will be prompted to create a password. Memorize it: you will need it to deploy the {{ KF }} web interface.