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
    • ML Services
    • 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
          • iam_oauth_client
          • iam_service_account
          • iam_service_account_api_key
          • iam_service_account_iam_binding
          • iam_service_account_iam_member
          • iam_service_account_iam_policy
          • iam_service_account_key
          • iam_service_account_static_access_key
          • iam_workload_identity_federated_credential
          • iam_workload_identity_oidc_federation
          • iam_workload_identity_oidc_federation_iam_binding

In this article:

  • Example usage
  • Schema
  • Required
  • Optional
  • Read-Only
  • Nested Schema for output_to_lockbox
  • Import
  1. Terraform reference
  2. Resources
  3. Identity and Access Management (IAM)
  4. Resources
  5. iam_service_account_static_access_key

yandex_iam_service_account_static_access_key (Resource)

Written by
Yandex Cloud
Updated at September 11, 2025
  • Example usage
  • Schema
    • Required
    • Optional
    • Read-Only
    • Nested Schema for output_to_lockbox
  • Import

Allows management of Yandex Cloud IAM service account static access keys. Generated pair of keys is used to access Yandex Object Storage on behalf of service account.

Before using keys do not forget to assign a proper role to the service account.

Example usageExample usage

//
// Create a new IAM Service Account Static Access SKey.
//
resource "yandex_iam_service_account_static_access_key" "sa-static-key" {
  service_account_id = "aje5a**********qspd3"
  description        = "static access key for object storage"
  pgp_key            = "keybase:keybaseusername"
}

SchemaSchema

RequiredRequired

  • service_account_id (String) ID of the service account which is used to get a static key.

OptionalOptional

  • description (String) The resource description.
  • output_to_lockbox (Block List, Max: 1) option to create a Lockbox secret version from sensitive outputs (see below for nested schema)
  • pgp_key (String) An optional PGP key to encrypt the resulting secret key material. May either be a base64-encoded public key or a keybase username in the form keybase:keybaseusername.

Read-OnlyRead-Only

  • access_key (String) ID of the static access key. This is only populated when output_to_lockbox is not provided.
  • created_at (String) The creation timestamp of the resource.
  • encrypted_secret_key (String) The encrypted secret, base64 encoded. This is only populated when pgp_key is supplied.
  • id (String) The ID of this resource.
  • key_fingerprint (String) The fingerprint of the PGP key used to encrypt the secret key. This is only populated when pgp_key is supplied.
  • output_to_lockbox_version_id (String) ID of the Lockbox secret version that contains the value of secret_key. This is only populated when output_to_lockbox is supplied. This version will be destroyed when the IAM key is destroyed, or when output_to_lockbox is removed.
  • secret_key (String, Sensitive) Private part of generated static access key. This is only populated when neither pgp_key nor output_to_lockbox are provided.

Nested Schema for Nested Schema for output_to_lockbox

Required:

  • entry_for_access_key (String) entry that will store the value of access_key
  • entry_for_secret_key (String) entry that will store the value of secret_key
  • secret_id (String) ID of the Lockbox secret where to store the sensible values.

ImportImport

Warning

Import for this resource is not implemented yet.

Was the article helpful?

Previous
iam_service_account_key
Next
iam_workload_identity_federated_credential
© 2025 Direct Cursus Technology L.L.C.