Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Command line interface
  • Getting started
    • All guides
    • Installation
    • Updates
    • Deletion
    • Working with command versions
    • Running commands
    • Endpoints
    • Configuration
    • Synchronous and asynchronous command execution modes
  • Releases
  • Troubleshooting

In this article:

  • Access through a firewall or proxy server
  • Checking connections
  1. Concepts
  2. Endpoints

Connecting the CLI to Yandex Cloud endpoints

Written by
Yandex Cloud
Updated at August 19, 2026
View in Markdown
  • Access through a firewall or proxy server
  • Checking connections

An endpoint is the address the CLI uses to communicate with the API of a specific Yandex Cloud service. The endpoints you use depend on the command you run.

As soon as you run yc init, the CLI connects to the regional https://api.cloud.yandex.net endpoint to fetch the current list of endpoints used by the services. Then, the CLI contacts endpoints used for authentication and profile configuration. After the initialization, the CLI selects an endpoint based on which service the command belongs to.

To retrieve the complete list of available Yandex Cloud endpoints and ports, run the following request:

curl https://api.cloud.yandex.net/endpoints

The response contains the IDs of services and their endpoint addresses:

{
  "endpoints": [
    {
      "id": "<service_ID>",
      "address": "<endpoint_address>:<port>"
    }
  ]
}

Tip

Do not use a static copy of this list because its data may change as new services and endpoints get added. For details on the response format, see Yandex Cloud service API endpoints.

Access through a firewall or proxy serverAccess through a firewall or proxy server

If outgoing connections are restricted by a firewall, allow access to api.cloud.yandex.net and the endpoints of the services you are expecting to use. Use the ports specified in the response to https://api.cloud.yandex.net/endpoints.

Authentication via a browser will also require the user to have access to https://auth.yandex.cloud and identity provider domains.

If Yandex Cloud is accessed through a proxy server, configure the HTTPS_PROXY environment variable.

Checking connectionsChecking connections

To look up the endpoints yc init connects to, enable detailed gRPC logging:

yc init --debug-grpc

Connection addresses are logged in the lines labeled original dial target and Dialing. A successful connection is logged as successfully connected.

The --debug-grpc parameter outputs detailed information about gRPC connections. To view the general command execution log, use the --debug parameter. For more on these parameters, see Yandex Cloud CLI configuration.

Warning

The debug log may contain data pertaining to requests. Do not share them with other users until you remove tokens and other sensitive information.

Useful linksUseful links

Yandex Cloud service API endpoints

Was the article helpful?

Previous
Running commands
Next
Configuration
© 2026 Direct Cursus Technology L.L.C.