rotation schedule

Related topics

• Google Cloud console configures rotation schedule From the official documentation: “You can configure a rotation schedule using the Google Cloud console, the Google Cloud CLI, or the Secret Manager API.”
• rotation schedule configures Secret From the official documentation: “Set up a [rotation schedule](/secret-manager/docs/secret-rotation) for your secret.”
• rotation schedule is part of Secret Manager From the official documentation: “Secret Manager lets you schedule periodic rotations of your secrets.”
• Compute Engine works with Secret Manager From the official documentation: “To use Secret Manager with workloads running on Compute Engine or GKE, the underlying instance or node must have the `cloud-platform` OAuth scope.”
• Apigee works with Compute Engine From the official documentation: “| [Compute Engine](https://console.cloud.google.com/apis/library/compute.googleapis.com) | `compute.googleapis.com` | Used for managing your Apigee runtime. |”
• Identity and Access Management secures Compute Engine From the official documentation: “Compute Engine uses Identity and Access Management (IAM) for authorization.”
• Identity and Access Management secures Secret Manager From the official documentation: “Secret Manager uses Identity and Access Management (IAM) for authorization.”
• secret version is part of Secret From the official documentation: “Lists all versions of a secret.”
• Apigee works with Google Cloud console From the official documentation: “Now that Apigee has been integrated with Google Cloud, support will be provided through the [Google Cloud console](http://console.cloud.google.com/support/cases) using [Cloud Customer Care offers](https://cloud.google.com/support#support-plans).”
• Apigee works with Secret Manager From the official documentation: “Apigee supports using [Google OAuth tokens](https://developers.google.com/identity/protocols/oauth2) or [OpenID Connect tokens](https://developers.google.com/identity/protocols/oauth2/openid-connect) to authenticate with Google services such as [Cloud…”
• Cloud Key Management Service works with Google Cloud console From the official documentation: “There is also a web-based interface for [Cloud KMS on the Google Cloud console](https://console.cloud.google.com/security/kms), which allows for key management operations.”
• Cloud Key Management Service depends on Identity and Access Management From the official documentation: “Whatever the mechanism, Cloud KMS resolves the provided credential to identify the principal (the entity which is authenticated and is authorizing the request), and calls IAM to see whether the principal is authorized to make the request and whether an audit log is written.”
• Cloud Key Management Service works with Identity and Access Management From the official documentation: “The Cloud KMS platform is integrated with [IAM](/iam/docs/overview) and [Cloud Audit Logs](/logging/docs/audit) so that you can manage permissions on individual keys and audit how they are used.”
• Cloud Key Management Service works with Secret Manager From the official documentation: “If you want to control your encryption keys, then you can use customer-managed encryption keys (CMEKs) in [Cloud KMS](/kms/docs) with CMEK-integrated services including Secret Manager.”
• Cloud Key Management Service is an alternative to Secret Manager From the official documentation: “Secret Manager is the recommended technique for managing sensitive data with Cloud Build. For existing projects, you can continue using Cloud KMS, but for new projects, use Secret Manager.”
• Google Cloud console configures Compute Engine From the official documentation: “You can use the standard Google Cloud methods to deploy your VMs on Compute Engine: the Google Cloud console, the Google Cloud CLI, Terraform, and the [REST API](/compute/docs/reference/latest).”
• IAM secures Google Cloud console From the official documentation: “For information about the various user roles and getting access control to Google Cloud console see [Access control with IAM](https://cloud.google.com/support/docs/access-control).”
• IAM configures Secret Manager From the official documentation: “Configuring proper IAM permissions when using secret backends like Secret Manager so that the environment's service account has access to it.”
• IAM secures Secret Manager From the official documentation: “Access to the Secret Manager API is protected by IAM.”
• Identity and Access Management secures Cloud Key Management Service From the official documentation: “If you need to prevent a user from using a Cloud KMS resource during the time needed for propagation of an eventually consistent operation, remove the Identity and Access Management (IAM) permission for the resource.”
• Identity and Access Management secures Secret From the official documentation: “However, the ability to view these Secrets is governed by Identity and Access Management (IAM) access permissions for the GKE details page.”
• Secret is part of Secret Manager From the official documentation: “A secret in Secret Manager can have multiple secret versions.”
• Secret Manager configures Secret From the official documentation: “After you create the user, create a secret in Secret Manager to store the username and password, which prevents the loss of your sensitive information.”
• secret version is part of Secret Manager From the official documentation: “A secret in Secret Manager contains a collection of secret versions.”