Resource locations constraint

Related topics

• Resource locations constraint configures AlloyDB for PostgreSQL From the official documentation: “For data residency, you can use the [resource locations constraint](/resource-manager/docs/organization-policy/defining-locations) to limit the physical location of new [supported AlloyDB…”
• Resource locations constraint is part of Organization Policy Service From the official documentation: “If you have an [organization policy](/resource-manager/docs/organization-policy/overview) that includes the resource locations [constraint](/resource-manager/docs/organization-policy/understanding-constraints), any snapshot storage location that you specify must be in the set…”
• Compute Engine is an alternative to GKE From the official documentation: “To use TPU7x, you can use Google Kubernetes Engine (GKE) or Compute Engine.”
• GKE depends on Compute Engine From the official documentation: “For example, GKE deploys clusters on Compute Engine VMs.”
• AlloyDB for PostgreSQL works with Compute Engine From the official documentation: “In this tutorial, you integrate an AlloyDB instance and a [Compute Engine](https://cloud.google.com/compute) VM instance on a [Virtual Private Cloud (VPC)](https://cloud.google.com/vpc) network.”
• AlloyDB for PostgreSQL works with GKE From the official documentation: “Route AlloyDB for PostgreSQL events to GKE”
• Compute Engine works with GKE From the official documentation: “For example, Google Kubernetes Engine (GKE) can cause usage in Compute Engine.”
• GKE works with Organization Policy Service From the official documentation: “The following limitations apply to using the Organization Policy Service with GKE:”
• 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.”