user-managed service account

Related topics

• Compute Engine works with user-managed service account From the official documentation: “A user-managed service account can be attached to a Compute Engine instance to provide credentials to applications running on the instance.”
• Organization Policy Service configures user-managed service account From the official documentation: “To limit who can create service accounts, use the [Organization Policy Service](/resource-manager/docs/organization-policy/overview).”
• service agent is an alternative to user-managed service account From the official documentation: “Grant the permissions listed in [Service agent permissions](/storage-transfer/docs/iam-cloud#manually_assigning_roles) to the user-managed service account, instead of to the service agent.”
• managed constraints is part of Organization Policy Service From the official documentation: “Organization Policy provides built-in [managed constraints](/organization-policy/reference/org-policy-constraints) for various Google Cloud services.”
• custom constraints is an alternative to managed constraints From the official documentation: “However, if you want more granular, customizable control over the specific fields that are restricted in your organization policies, you can also create *custom constraints* and use those custom constraints in an organization policy.”
• custom constraints is part of Organization Policy Service From the official documentation: “You can use Google Cloud Organization Policy custom constraints to restrict specific operations on data lineage resources.”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• Compute Engine works with service account From the official documentation: “A common method is to attach a service account to a resource like a Compute Engine instance.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• Organization Policy Service configures service account From the official documentation: “To limit who can create service accounts, use the [Organization Policy Service](/resource-manager/docs/organization-policy/overview).”
• OS Login is part of Compute Engine From the official documentation: “Require OS Login on Compute Engine Instances”
• customer-managed encryption keys secures Compute Engine From the official documentation: “In IL5, CMEK is enabled by default for Compute Engine, Google Kubernetes Engine (GKE), Cloud Storage, and Cloud SQL.”
• customer-managed encryption keys secures GKE From the official documentation: “CMEKs encrypt data at rest in Cloud SQL, Cloud Storage, and within GKE clusters.”
• Compute Engine works with custom constraints From the official documentation: “For Compute Engine, you can set custom constraints on the following resources and fields.”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• Compute Engine depends on service account From the official documentation: “The Service Account is used by Compute Engine to access other Google APIs.”
• customer-managed encryption keys depends on service account From the official documentation: “To use a CMEK on a project, you must have a service account and you must grant the key access to the service account.”
• customer-managed encryption keys depends on service agent From the official documentation: “You need to create a [service agent](/iam/docs/service-agents) identity for each project that requires customer-managed encryption keys.”
• GKE works with Organization Policy Service From the official documentation: “The following limitations apply to using the Organization Policy Service with GKE:”
• managed constraints secures Compute Engine From the official documentation: “Managed constraints are predefined organization policies, built on a modern platform, that provide centralized, programmatic control over your Compute Engine resources.”
• Organization Policy Service configures Compute Engine From the official documentation: “You can use organization policies to enforce constraints on how Compute Engine resources, such as virtual machine (VM) instances, disks, and networks, are configured.”
• Organization Policy Service configures OS Login From the official documentation: “For managing OS Login across multiple projects in an organization, consider enforcing OS Login by using an Organization Policy Service constraint (`compute.requireOsLogin`).”
• OS Login secures Compute Engine From the official documentation: “If you let developers access Compute Engine resources using SSH, configure OS Login with 2-step verification.”
• service agent is part of service account From the official documentation: “Service accounts can be divided into *user-managed service accounts* and Google-managed service accounts, which are called *service agents*:”