Yandex Cloud
Search
Contact UsGet started
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • AI for business
    • Business tools
  • 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
  • Pricing
  • Customer Stories
  • Documentation
  • Blog
© 2025 Direct Cursus Technology L.L.C.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • kms_asymmetric_encryption_key
          • kms_asymmetric_signature_key
          • kms_symmetric_key

In this article:

  • Example Usage
  • Schema
  • Optional
  • Read-Only
  • Nested Schema for timeouts
  1. Terraform reference
  2. Resources
  3. Key Management Service (KMS)
  4. Data Sources
  5. kms_asymmetric_encryption_key

yandex_kms_asymmetric_encryption_key (Data Source)

Written by
Yandex Cloud
Updated at October 2, 2025
  • Example Usage
  • Schema
    • Optional
    • Read-Only
    • Nested Schema for timeouts

An asymmetric KMS key that may contain several versions of the cryptographic material.

Example UsageExample Usage

//
// TBD
//

SchemaSchema

OptionalOptional

  • asymmetric_encryption_key_id (String) ID of the asymmetric KMS key to return.
    To get the ID of an asymmetric KMS key use a [AsymmetricEncryptionKeyService.List] request.
  • deletion_protection (Boolean) Flag that inhibits deletion of the key
  • encryption_algorithm (String) Asymmetric Encryption Algorithm ID.
  • folder_id (String) ID of the folder that the key belongs to.
  • id (String) ID of the asymmetric KMS key to return.
    To get the ID of an asymmetric KMS key use a [AsymmetricEncryptionKeyService.List] request.
  • timeouts (Block, Optional) (see below for nested schema)

Read-OnlyRead-Only

  • created_at (String) Time when the key was created.
  • description (String) Description of the key.
  • labels (Map of String) Custom labels for the key as key:value pairs. Maximum 64 per key.
  • name (String) Name of the key.
  • status (String) Current status of the key.

Nested Schema for Nested Schema for timeouts

Optional:

  • create (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
  • delete (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
  • read (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
  • update (String) A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

Was the article helpful?

Previous
iot_core_registry
Next
kms_asymmetric_signature_key
© 2025 Direct Cursus Technology L.L.C.