Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
  • Blog
  • Pricing
  • Documentation
Yandex project
© 2025 Yandex.Cloud LLC
Security in Yandex Cloud
  • Key security principles
  • Division of responsibility
  • Compliance
  • Security measures on the Yandex Cloud side
  • Security tools available to cloud service users
    • All tutorials
      • Which encryption method should I choose?
      • Encrypting data using the Yandex Cloud CLI and API
      • Encrypting data using the Yandex Cloud SDK
      • Encrypting data using the AWS Encryption SDK
      • Encrypting data using Google Tink
      • Managing Key Management Service keys with Terraform
      • Encrypting secrets in Terraform
      • Auto Unseal in Hashicorp Vault
      • Secure password transmission to an initialization script
      • Secure storage of GitLab CI passwords as Yandex Lockbox secrets
        • Overview
        • Using a Yandex Lockbox secret to store a static access key via the CLI
        • Using a Yandex Lockbox secret to store a static access key using Terraform
      • Getting Yandex Lockbox secret value on the GitHub side
      • Getting Yandex Lockbox secret value on the GitLab side
  • User support policy during vulnerability scanning
  • Security bulletins
  • Public IP address ranges
  1. Tutorials
  2. Data encryption and key management
  3. Using a Yandex Lockbox secret to store a static access key
  4. Overview

Using a Yandex Lockbox secret to store a static access key

Written by
Yandex Cloud
Updated at May 7, 2025

If you frequently use services with an AWS-compatible API, such as Yandex Object Storage, Yandex Data Streams, or Yandex Message Queue, it is up to you to ensure safe storage of your static access keys.

This tutorial covers a scenario where a Yandex Lockbox secret serves as the static access key storage. In this configuration, the access key value is neither stored locally on the user's computer nor displayed on the screen.

When accessing a resource of an AWS-compatible service (Object Storage), the static access key and its ID will be extracted from the Yandex Lockbox secret into special environment variables, which will be used for request authentication.

This approach will ensure safe storage and use of your key when accessing the services.

You can use the following tools to create an infrastructure:

  • CLI: Use this method to create an infrastructure step-by-step via the CLI.
  • Terraform: Streamline creating and managing your resources with the infrastructure as code (IaC) approach. Download a Terraform configuration example from GitHub and deploy your infrastructure with the Yandex Cloud Terraform provider.

Was the article helpful?

Previous
Secure storage of GitLab CI passwords as Yandex Lockbox secrets
Next
Using a Yandex Lockbox secret to store a static access key via the CLI
Yandex project
© 2025 Yandex.Cloud LLC