/yandex-cloud

name: yandex-cloud
description: "[RU: Яндекс.Облако — yc CLI, Compute Cloud, Managed PostgreSQL/MySQL/Redis/ClickHouse/MongoDB/Kafka, Object Storage S3, VPC, Managed Kubernetes, IAM, Lockbox, Cloud Functions] Yandex Cloud production operations — yc CLI (canonical control), Compute Cloud (VMs + disks + snapshots + placement groups), Managed Service for PostgreSQL 17 / MySQL 8 / Redis 7 / ClickHouse / MongoDB / Kafka / Greenplum / OpenSearch, Object Storage (S3-compatible), VPC (folders, networks, security groups, NAT GW), Managed Service for Kubernetes 1.31, Application Load Balancer (L7) + Network Load Balancer (L4), Container Registry, Cloud Functions / Serverless Containers, IAM (service accounts, OAuth, federations), Lockbox (secrets), Cloud DNS, Cloud Logging, Monitoring, Backup. Canonical docs: https://github.com/yandex-cloud/docs (mirrored to https://yandex.cloud/ru/docs). Use when: yc CLI, yandex cloud, яндекс облако, yc compute, yc-mdb-pg, mdb-pg, managed postgresql яндекс, managed redis яндекс, ydb, ymq, object storage yc, s3.yandexcloud.net, vpc яндекс, security groups яндекс, yandex k8s, managed kubernetes, container registry, lockbox, service account, IAM token, oauth-token yandex, yc init, yc config profile, terraform yandex provider, миграция на яндекс облако, yc compute instance create, yandex serverless. SKIP: AWS/GCP/Azure (→aws/gcp/azure equivalents); self-managed PostgreSQL on bare metal (→postgresql + linux-sysadmin); Yandex.Cloud-Functions code logic itself (→nodejs/python); Yandex 360 / Yandex Music / consumer products."
stacks:
  - cloud
  - devops
  - sysadmin
tags:
  - yandex-cloud
  - yc
  - cloud
  - iaas
  - paas
category: devops
color: red
displayName: Yandex Cloud
risk: high-stakes

<!-- versions:start -->

🎯 Version Requirements (May 2026)

**Canonical sources:**

• **Docs repo**: https://github.com/yandex-cloud/docs (markdown source for yandex.cloud/ru/docs)
• **Public mirror**: https://yandex.cloud/ru/docs · https://yandex.cloud/en/docs
• **yc CLI**: latest stable from https://storage.yandexcloud.net/yandexcloud-yc/install.sh (rolling release)
• **Terraform provider**: `yandex-cloud/yandex` v0.115.x+
• **S3 endpoint**: `https://storage.yandexcloud.net` (S3 v4 sig)
• **Cloud API gRPC endpoint**: `*.api.cloud.yandex.net:443`

**Managed service versions (May 2026):**

• Managed PostgreSQL: 14/15/16/**17** (default new clusters)
• Managed MySQL: 5.7/8.0/**8.4**
• Managed Redis: 6.2/7.0/**7.2**
• Managed ClickHouse: latest LTS
• Managed Kubernetes: 1.27 → **1.31** (default)
• Managed Kafka: 3.x

**Always confirm version pins via** `yc managed-postgresql cluster list-hosts` etc. — never assume.

<!-- versions:end -->

Usage

Loaded automatically when its description matches the active task. Read only the reference section you need — full documentation lives in the canonical repo above (this skill is a navigator, not a copy).

Use this skill when

• Provisioning, migrating to, or operating workloads on **Yandex Cloud**
• Working with the `yc` CLI: profiles, federations, service accounts, IAM tokens
• Setting up Managed Service for PostgreSQL / MySQL / Redis / ClickHouse / MongoDB / Kafka / Greenplum
• Using Object Storage (S3-compatible) — bucket policy, lifecycle, presigned URLs, CORS
• Designing VPC: folders/clouds, networks, subnets, security groups, NAT gateways, peering
• Managed Service for Kubernetes — node groups, autoscaling, network policies, ALB Ingress
• IAM design — service accounts, roles, federations (SAML/OIDC), OAuth tokens
• Storing credentials in Lockbox; serving secrets to VMs/k8s/serverless via metadata
• Cloud Functions / Serverless Containers / API Gateway / Triggers
• Cost optimisation, billing alerts, committed-use discounts
• Migrating from self-hosted (Ubuntu + PostgreSQL + Redis on a single box) to managed YC services

Do not use this skill when

• Target cloud is AWS / GCP / Azure / DigitalOcean / Hetzner — use the appropriate skill
• Task is application code that just happens to run on YC — use the framework skill (`nodejs`, `fastapi`, etc.)
• Task is purely about S3 SDK usage with `aws-sdk` against YC Object Storage — use the SDK skill, treat YC as a vanilla S3 endpoint
• Task is self-managed PostgreSQL/Redis on a YC Compute Cloud VM that you administer yourself — use `postgresql` / `redis` / `linux-sysadmin` (this skill covers managed services, not BYOPostgres)

Purpose

This skill is the **operational map** for Yandex Cloud: which surface to reach for, the canonical control commands (`yc ...`), and the cross-references to the upstream docs at https://github.com/yandex-cloud/docs. It deliberately does NOT duplicate the docs — it routes the agent to the right reference and the right `yc` invocation.

This skill does NOT cover: application logic, language SDKs (defer to the language skill), other clouds. For raw S3 protocol semantics, defer to S3 docs; this skill knows the YC-specific deviations.

Operating Contract

1. **Always confirm folder + cloud** before any destructive `yc` command — `yc config list` and `yc config get folder-id` 2. **Use `--dry-run` / `--format yaml` first** for any `yc * create` / `update` / `delete` — preview before mutate 3. **Service accounts > OAuth tokens** for automation — never bake `--token <OAuth>` into scripts; use SA + `iam create-token` 4. **Production deletes need confirmation** — `yc compute instance delete`, `yc managed-* cluster delete`, `yc storage bucket remove` are irreversible; ask before running 5. **Backups before schema/version upgrade** — `yc managed-postgresql backup list` + create on-demand before any `cluster update --postgresql-version` 6. **Network changes outside maintenance** trigger downtime — security-group edits + subnet moves; do during a window 7. **Read the docs repo, not stale memory** — paths in https://github.com/yandex-cloud/docs/tree/master/ru change; verify before quoting

Service Map (canonical surface)

| Layer | Service | yc namespace