Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
Yandex DataSphere
  • Getting started
  • Tutorials
    • Integrating with Yandex Data Proc
  • Step-by-step instructions
    • All instructions
    • Community management
      • Create a community
      • Add a user to a community
      • Add a communication channel
      • Link a billing account
      • Viewing service usage details
      • Delete a community
    • Project management
      • Create a project
      • Add a user to a project
      • Select a Python version
      • Resize project storage
      • Change project settings
      • Set project limits
      • Delete a notebook or project
    • Working in a notebook
      • Select computing resources
      • Install packages
      • Reset the interpreter state
      • Notebook code snippets
      • Working with Git
      • Run a Docker container in a separate cell
    • Working with resources
      • Using secrets
      • Working with checkpoints
      • Working with Data Proc templates
      • Working with Docker images
      • Working with datasets
    • Connecting to data sources
      • Connecting to S3 storage
      • Connecting to a ClickHouse database
      • Connecting to a PostgreSQL database
      • Connecting to Yandex Disk
      • Connecting to Google Drive
    • Deploying models
      • Creating a node with Python code
      • Updating a node
      • Deleting a node
      • Configuring the node environment
      • Sending requests to nodes
      • Creating an alias
      • Updating an alias
      • Deleting an alias
    • Shared access
      • Publishing a notebook
      • Exporting a project
    • Launching distributed training
    • How to migrate to the new interface
  • Concepts
    • About Yandex DataSphere
    • Relationships between resources in DataSphere
    • Communities
    • Cost management
    • Project and its environment
      • Project
      • Computing resource configurations
      • Interpreter state
      • List of pre-installed software
      • Early access mode
    • Computing and model training
      • Available commands
      • #pragma service commands
      • Background operations
      • EA: Special background cells
      • Distributed training
      • Computing on Apache Spark™ clusters
    • Resources
      • Overview
      • Secrets
      • Docker images
      • Checkpoints
      • Datasets
      • Data Proc templates
    • Using models
    • Quotas and limits
  • Access management
  • Pricing policy
  • Public materials
  • Releases
  • Questions and answers
  1. Concepts
  2. Resources
  3. Secrets

Private data storage

Written by
Yandex Cloud
  • Information about secrets as a resource
  • Scope of secrets

To safely store keys, passwords, and other private information, DataSphere provides a special type of resource called secrets.

A secret is a key-value pair with the value stored in an encrypted format. After you create the secret, you will see *** instead of the value.

Secrets are created in a project and associated with it. You can use created secrets in a cell code as environment variables to securely connect to data sources and version control systems, and store keys there, which are needed to create other resources , such as S3 connectors.

You can't modify a secret created in a different project, but you can modify its copy.

A copied secret is separate from the original: you can edit and delete the copy without affecting the original.

Tip

The advantage of secrets is that their values are stored and transferred in encrypted form only and can't be used when publishing the code and in project logs. Do not output the value of a secret to the screen or assign it to a regular variable.

Information about secrets as a resource

The following information is stored about each secret:

  • Unique resource ID.
  • Resource creator.
  • Date when the resource was created and last modified, in UTC format, such as July 18, 2022, 14:23.

The secret page also contains sample bash and Python code for running the resource in a project cell.

Scope of secrets

Once created, a secret is available for a project. A community admin can share the secret with other community projects by granting access to it in the Access tab on the secret viewing page. Secrets available to the community appear on the community page under Resources.

What's next?

  • How to create, edit, copy, and delete a secret.

Was the article helpful?

Language / Region
Yandex project
© 2023 Yandex.Cloud LLC
In this article:
  • Information about secrets as a resource
  • Scope of secrets