Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/kms/docs/kms-autokey below:

Cloud KMS with Autokey | Google Cloud

Stay organized with collections Save and categorize content based on your preferences.

Cloud KMS Autokey simplifies creating and using customer-managed encryption keys (CMEKs) by automating provisioning and assignment. With Autokey, key rings and keys are generated on-demand. Service accounts that use the keys to encrypt and decrypt resources are created and granted Identity and Access Management (IAM) roles when needed. Cloud KMS administrators retain full control and visibility to keys created by Autokey, without needing to pre-plan and create each resource.

Using keys generated by Autokey can help you consistently align with industry standards and recommended practices for data security, including the HSM protection level, separation of duties, key rotation, location, and key specificity. Autokey creates keys that follow both general guidelines and guidelines specific to the resource type for Google Cloud services that integrate with Cloud KMS Autokey. After they are created, keys requested using Autokey function identically to other Cloud HSM keys with the same settings.

Autokey can also simplify usage of Terraform for key management, removing the need to run infrastructure-as-code with elevated key-creation privileges.

To use Autokey, you must have an organization resource that contains a folder resource. For more information about organization and folder resources, see Resource hierarchy.

Cloud KMS Autokey is available in all Google Cloud locations where Cloud HSM is available. For more information about Cloud KMS locations, see Cloud KMS locations. There is no additional cost to use Cloud KMS Autokey. Keys created using Autokey are priced the same as any other Cloud HSM keys. For more information about pricing, see Cloud Key Management Service pricing.

For more information about Autokey, see Autokey overview.

Cloud KMS with Autokey is like an autopilot for customer-managed encryption keys: it does the work on your behalf, on demand. You don't need to plan keys ahead of time or create keys that might never be needed. Keys and key usage are consistent. You can define the folders where you want Autokey to be used and control who can use it. You retain full control of the keys created by Autokey. You can use manually-created Cloud KMS keys alongside keys created using Autokey. You can disable Autokey and continue to use the keys it created the same way you'd use any other Cloud KMS key.

Cloud KMS Autokey is a good choice if you want consistent key usage across projects, with a low operational overhead, and want to follow Google's recommendations for keys.

If you need to use a protection level other than HSM or a custom rotation period, you can use CMEK without Autokey.

The following table lists services that are compatible with Cloud KMS Autokey:

• artifactregistry.googleapis.com/Repository

Autokey creates keys during Repository creation, used for all stored artifacts.

• bigquery.googleapis.com/Dataset

Autokey creates default keys for datasets. Tables, models, queries, and temporary tables within a dataset use the dataset default key.

Autokey doesn't create keys for BigQuery resources other than datasets. To protect resources that are not part of a dataset, you must create your own default keys at the project or organization level.

• bigtable.googleapis.com/Cluster

Autokey creates keys for clusters.

Autokey doesn't create keys for Bigtable resources other than clusters.

Bigtable is only compatible with Cloud KMS Autokey when creating resources using Terraform or the Google Cloud SDK.

• alloydb.googleapis.com/Cluster
• alloydb.googleapis.com/Backup

AlloyDB for PostgreSQL is only compatible with Cloud KMS Autokey when creating resources using Terraform or the REST API.

• run.googleapis.com/Service
• run.googleapis.com/Job

• sqladmin.googleapis.com/Instance

Autokey doesn't create keys for Cloud SQL BackupRun resources. When you create a backup of a Cloud SQL instance, the backup is encrypted with the primary instance's customer-managed key.

Cloud SQL is only compatible with Cloud KMS Autokey when creating resources using Terraform or the REST API.

• storage.googleapis.com/Bucket

Objects within a storage bucket use the bucket default key. Autokey doesn't create keys for storage.object resources.

• compute.googleapis.com/Disk
• compute.googleapis.com/Image
• compute.googleapis.com/Instance
• compute.googleapis.com/MachineImage

Snapshots use the key for the disk that you are creating a snapshot of. Autokey doesn't create keys for compute.snapshot resources.

• secretmanager.googleapis.com/Secret

Secret Manager is only compatible with Cloud KMS Autokey when creating resources using Terraform or the REST API.

• spanner.googleapis.com/Database

Spanner is only compatible with Cloud KMS Autokey when creating resources using Terraform or the REST API.

• dataflow.googleapis.com/Job

• To learn more about how Cloud KMS Autokey works, see Autokey overview.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-02 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-02 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4