<br />

# Manage resources using custom constraints

Custom constraints let you enforce granular governance rules on Managed Service for Apache Spark cluster configurations across your [Google Cloud resource hierarchy](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy.md.txt). By defining these rules, you can restrict specific cluster properties and maintain compliance across your environments.

While Organization Policy Service provides [predefined constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints) for common settings, custom constraints let you target specific resource fields when clusters are created or updated. As an [organization policy administrator](https://docs.cloud.google.com/resource-manager/docs/organization-policy/using-constraints#add-org-policy-admin), you can define *custom constraints* and enforce them at the organization, folder, or project level.

## Benefits

You can use a custom organization policy to allow or deny specific
operations on Managed Service for Apache Spark clusters. For example, if
a request to create or update a cluster fails to satisfy
custom constraint validation as set by your organization policy,
the request will fail, and an error will be returned to the caller.

## Policy inheritance

By default, organization policies are inherited by the descendants of the
resources on which you enforce the policy. For example, if you enforce a policy
on a folder, Google Cloud enforces the policy on all projects in the
folder. To learn more about this behavior and how to change it, refer to
[Hierarchy evaluation rules](https://docs.cloud.google.com/resource-manager/docs/organization-policy/understanding-hierarchy#disallow_inheritance).

## Pricing

The Organization Policy, including predefined and custom organization policies, is
offered at no charge.

## Before you begin

1. **Set up your project**
   1. Ensure that you know your [organization ID](https://docs.cloud.google.com/resource-manager/docs/creating-managing-organization.md.txt#retrieving_your_organization_id).

### Required roles


To get the permissions that
you need to manage organization policies,

ask your administrator to grant you the
following IAM roles:

- [Organization policy administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/orgpolicy.md.txt#orgpolicy.policyAdmin) (`roles/orgpolicy.policyAdmin`) on the organization resource
- To create or update a Managed Service for Apache Spark cluster: [Managed Service for Apache Spark Admin or Managed Service for Apache Spark Editor](https://docs.cloud.google.com/managed-spark/docs/concepts/iam/iam.md.txt#roles) (`roles/dataproc.admin` or `roles/dataproc.editor`) on the project resource


For more information about granting roles, see [Manage access to projects, folders, and organizations](https://docs.cloud.google.com/iam/docs/granting-changing-revoking-access.md.txt).


These predefined roles contain

the permissions required to manage organization policies. To see the exact permissions that are
required, expand the **Required permissions** section:


#### Required permissions

The following permissions are required to manage organization policies:

- `orgpolicy.constraints.list`
- `orgpolicy.policies.create`
- `orgpolicy.policies.delete`
- `orgpolicy.policies.list`
- `orgpolicy.policies.update`
- `orgpolicy.policy.get`
- `orgpolicy.policy.set`


You might also be able to get
these permissions
with [custom roles](https://docs.cloud.google.com/iam/docs/creating-custom-roles.md.txt) or
other [predefined roles](https://docs.cloud.google.com/iam/docs/roles-overview.md.txt#predefined).

## Create a custom constraint

A custom constraint is defined in a YAML file by the resources, methods,
conditions, and actions it is applied to. Managed Service for Apache Spark supports
custom constraints that are applied to the `CREATE` and `UPDATE` methods of the
`CLUSTER` resource (see
[Managed Service for Apache Spark constraints on resources and operations](https://docs.cloud.google.com/managed-spark/docs/concepts/custom-constraints.md.txt#supported_resources)).

To create a YAML file for a Managed Service for Apache Spark custom constraint:

```yaml
name: organizations/ORGANIZATION_ID/customConstraints/CONSTRAINT_NAME
resourceTypes:
- dataproc.googleapis.com/Cluster
methodTypes: 
- METHOD
condition: "CONDITION"
actionType: ACTION
displayName: DISPLAY_NAME
description: DESCRIPTION
```

Replace the following:

- `ORGANIZATION_ID`: your organization ID, such as
  `123456789`.

- `CONSTRAINT_NAME`: the name you want for your new
  custom constraint. A custom constraint must start with `custom.`, and can
  only include uppercase letters, lowercase letters, or numbers, for
  example, custom.dataprocEnableComponentGateway. The maximum length of this field is 70
  characters, not counting the prefix, for example,
  `organizations/123456789/customConstraints/custom`.

- `METHOD`: When creating a cluster creation constraint,
  specify `CREATE`. When creating a cluster `UPDATE` constraint, specify both as
  follows:

  ```
  methodTypes:
  - CREATE
  - UPDATE
  ```

  <br />

- `CONDITION`: a [CEL condition](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language) that is written against
  a representation of a supported service resource. This field has a maximum
  length of 1,500 characters. See [Supported resources](https://docs.cloud.google.com/managed-spark/docs/concepts/custom-constraints.md.txt#supported_resources) for
  more information about the resources available to write conditions against.
  For example, `"resource.config.endpointConfig.enableHttpPortAccess==true"`.

- `ACTION`: the action to take if the `condition` is
  met. This can be either `ALLOW` or `DENY`.

- `DISPLAY_NAME`: a human-friendly name for the
  constraint, for example, "Enforce enabling Managed Service for Apache Spark Component Gateway".
  This field has a maximum length of 200 characters.

- `DESCRIPTION`: a human-friendly description of the
  constraint to display as an error message when the policy is violated, for
  example, "Only allow Managed Service for Apache Spark cluster creation if the Component Gateway is
  enabled". This field has a maximum length of 2000 characters.

For more information about how to create a custom constraint, see
[Defining custom constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#defining_custom_constraints).

## Set up a custom constraint

### Console


To create a custom constraint, do the following:

1. In the Google Cloud console, go to the **Organization policies** page.

   [Go to Organization policies](https://console.cloud.google.com/iam-admin/orgpolicies)
2. From the project picker, select the project that you want to set the organization policy for.
3. Click **Custom constraint**.
4. In the **Display name** box, enter a human-readable name for the constraint. This name is used in error messages and can be used for identification and debugging. Don't use personally identifiable information (PII) or sensitive data in display names because this name could be exposed in error messages. This field can contain up to 200 characters.
5. In the **Constraint ID** box, enter the ID that you want for your new custom constraint. A custom constraint can only contain letters (including upper and lowercase) or numbers, for example `custom.dataprocEnableComponentGateway`. This field can contain up to 70 characters, not counting the prefix (`custom.`), for example, `organizations/123456789/customConstraints/custom`. Don't include PII or sensitive data in your constraint ID, because it could be exposed in error messages.
6. In the **Description** box, enter a human-readable description of the constraint. This description is used as an error message when the policy is violated. Include details about why the policy violation occurred and how to resolve the policy violation. Don't include PII or sensitive data in your description, because it could be exposed in error messages. This field can contain up to 2000 characters.
7. In the **Resource type** box, select the name of the Google Cloud REST resource containing the object and field that you want to restrict---for example, `container.googleapis.com/Cluster`. Most resource types support up to 20 custom constraints. If you attempt to create more custom constraints, the operation fails.
8. This constraint can only be enforced on the REST `CREATE` method.
9. To see supported methods for each service, find the service in [Services that support custom constraints](https://docs.cloud.google.com/organization-policy/reference/custom-constraint-supported-services.md.txt).
10. To define a condition, click **Edit condition**.
    1. In the **Add condition** panel, create a CEL condition that refers to a supported service resource, for example, `resource.autopilot.enabled == false`. This field can contain up to 1,500 characters. For details about CEL usage, see [Common Expression Language](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language). For more information about the service resources you can use in your custom constraints, see [Custom constraint supported services](https://docs.cloud.google.com/resource-manager/docs/organization-policy/custom-constraint-supported-services).
    2. Click **Save**.
11. Under **Action**, select whether to allow or deny the evaluated method if the condition is met.
12. The deny action means that the operation to create or update the resource is blocked if the condition evaluates to true.
13. The allow action means that the operation to create or update the resource is permitted only if the condition evaluates to true. Every other case except those explicitly listed in the condition is blocked.
14. Click **Create constraint**.
15. When you have entered a value into each field, the equivalent YAML configuration for this custom constraint appears on the right.

### gcloud

1. To create a custom constraint, create a YAML file using the following format:

```yaml
name: organizations/ORGANIZATION_ID/customConstraints/CONSTRAINT_NAME
resourceTypes: RESOURCE_NAME
methodTypes:
  - CREATE
condition: "CONDITION"
actionType: ACTION
displayName: DISPLAY_NAME
description: DESCRIPTION
```
2. Replace the following:
   - `ORGANIZATION_ID`: your organization ID, such as `123456789`.
   - `CONSTRAINT_NAME`: the name that you want for your new custom constraint. A custom constraint can only contain letters (including upper and lowercase) or numbers, for example, `custom.dataprocEnableComponentGateway`. This field can contain up to 70 characters, not counting the prefix (`custom.`)--- for example, `organizations/123456789/customConstraints/custom`. Don't include PII or sensitive data in your constraint ID, because it could be exposed in error messages.
   - `RESOURCE_NAME`: the fully qualified name of the Google Cloud resource containing the object and field that you want to restrict. For example, `dataproc.googleapis.com/Cluster`. Most resource types support up to 20 custom constraints. If you attempt to create more custom constraints, the operation fails.
   - `methodTypes`: the REST methods that the constraint is enforced on. Can only be `CREATE`.
   - To see the supported methods for each service, find the service in [Services that support custom constraints](https://docs.cloud.google.com/organization-policy/reference/custom-constraint-supported-services.md.txt).
   - `CONDITION`: a [CEL condition](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-custom-constraints#common_expression_language) that is written against a representation of a supported service resource. This field can contain up to 1,500 characters. For example, `` `"resource.config.endpointConfig.enableHttpPortAccess==true"` ``.
   - For more information about the resources available to write conditions against, see [Supported resources](https://docs.cloud.google.com/managed-spark/docs/concepts/custom-constraints.md.txt#supported_resources).
   - `ACTION`: the action to take if the `condition` is met. Can only be `ALLOW`.
   - The allow action means that if the condition evaluates to true, the operation to create or update the resource is permitted. This also means that every other case except the one explicitly listed in the condition is blocked.
   - `DISPLAY_NAME`: a human-readable name for the constraint. This name is used in error messages and can be used for identification and debugging. Don't use PII or sensitive data in display names because this name could be exposed in error messages. This field can contain up to 200 characters.
   - `DESCRIPTION`: a human-friendly description of the constraint to display as an error message when the policy is violated. This field can contain up to 2000 characters.
3. After you have created the YAML file for a new custom constraint, you must set it up to make it available for organization policies in your organization. To set up a custom constraint, use the [`gcloud org-policies set-custom-constraint`](https://docs.cloud.google.com/sdk/gcloud/reference/org-policies/set-custom-constraint) command:

```bash
gcloud org-policies set-custom-constraint CONSTRAINT_PATH
```
4. Replace `CONSTRAINT_PATH` with the full path to your custom constraint file. For example, `/home/user/customconstraint.yaml`.
5. After this operation is complete, your custom constraints are available as organization policies in your list of Google Cloud organization policies.
6. To verify that the custom constraint exists, use the [`gcloud org-policies list-custom-constraints`](https://docs.cloud.google.com/sdk/gcloud/reference/org-policies/list-custom-constraints) command:

```bash
gcloud org-policies list-custom-constraints --organization=ORGANIZATION_ID
```
7. Replace `ORGANIZATION_ID` with the ID of your organization resource.
8. For more information, see [Viewing organization policies](https://docs.cloud.google.com/resource-manager/docs/organization-policy/creating-managing-policies#viewing_organization_policies).

## Enforce a custom constraint

You can enforce a constraint by creating an organization policy that references it, and then applying that organization policy to a Google Cloud resource.

### Console

1. In the Google Cloud console, go to the **Organization policies** page.

   [Go to Organization policies](https://console.cloud.google.com/iam-admin/orgpolicies)
2. From the project picker, select the project that you want to set the organization policy for.
3. From the list on the **Organization policies** page, select your constraint to view the **Policy details** page for that constraint.
4. To configure the organization policy for this resource, click **Manage policy**.
5. On the **Edit policy** page, select **Override parent's policy**.
6. Click **Add a rule**.
7. In the **Enforcement** section, select whether this organization policy is enforced or not.
8. Optional: To make the organization policy conditional on a tag, click **Add condition** . Note that if you add a conditional rule to an organization policy, you must add at least one unconditional rule or the policy cannot be saved. For more information, see [Scope organization policies with tags](https://docs.cloud.google.com/organization-policy/scope-policies.md.txt).
9. Click **Test changes** to simulate the effect of the organization policy. For more information, see [Test organization policy changes with Policy Simulator](https://docs.cloud.google.com/policy-intelligence/docs/test-organization-policies.md.txt).
10. To enforce the organization policy in dry-run mode, click **Set dry run policy** . For more information, see [Test organization policies](https://docs.cloud.google.com/organization-policy/test-policies.md.txt).
11. After you verify that the organization policy in dry-run mode works as intended, set the live policy by clicking **Set policy**.

### gcloud

1. To create an organization policy with boolean rules, create a policy YAML file that references the constraint:

```yaml
name: projects/PROJECT_ID/policies/CONSTRAINT_NAME
spec:
  rules:
  - enforce: true

dryRunSpec:
  rules:
  - enforce: true
```
2. Replace the following:
   - `PROJECT_ID`: the project that you want to enforce your constraint on.
   - `CONSTRAINT_NAME`: the name you defined for your custom constraint. For example, `custom.dataprocEnableComponentGateway`.
3. To enforce the organization policy in [dry-run mode](https://docs.cloud.google.com/organization-policy/test-policies.md.txt), run the following command with the `dryRunSpec` flag:

```bash
gcloud org-policies set-policy POLICY_PATH --update-mask=dryRunSpec
```
4. Replace `POLICY_PATH` with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.
5. After you verify that the organization policy in dry-run mode works as intended, set the live policy with the `org-policies set-policy` command and the `spec` flag:

```bash
gcloud org-policies set-policy POLICY_PATH --update-mask=spec
```
6. Replace `POLICY_PATH` with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.

## Test the custom constraint

The following cluster creation example assumes a custom organization policy has
been created and enforced on cluster creation to require enabling the
[Component Gateway](https://docs.cloud.google.com/managed-spark/docs/concepts/accessing/dataproc-gateways#creating_a_cluster_with_component_gateway)
(`resource.config.endpointConfig.enableHttpPortAccess==true`).

```bash
gcloud dataproc clusters create example-cluster \
    --project=PROJECT_ID \
    --zone=COMPUTE_ZONE
```

Sample output (by default, the Component Gateway is not enabled when a
Managed Service for Apache Spark cluster is created):

    Operation denied by custom org policies: ["customConstraints/custom.dataprocEnableComponentGateway": "Only allow Dataproc cluster creation if the Component Gateway is enabled"]

## Managed Service for Apache Spark constraints on resources and operations

The following Managed Service for Apache Spark custom constraint fields are
available to use when you **create or update a Managed Service for Apache Spark cluster** .
Note that when updating a cluster, only the constraints related to editable cluster
parameters are supported (see
[Updating a cluster](https://docs.cloud.google.com/managed-spark/docs/guides/manage-cluster.md.txt#updating_a_cluster)).

- [Compute Engine network configuration](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#GceClusterConfig) (networkUri, internalIpOnly, serviceAccount, and metadata)
  - `resource.config.gceClusterConfig.networkUri`
  - `resource.config.gceClusterConfig.internalIpOnly`
  - `resource.config.gceClusterConfig.serviceAccount`
  - `resource.config.gceClusterConfig.metadata`
- [Compute Engine instance group configuration](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#instancegroupconfig) (imageUri and machineTypeUri)
  - `resource.config.masterConfig.imageUri`
  - `resource.config.masterConfig.machineTypeUri`
  - `resource.config.workerConfig.imageUri`
  - `resource.config.workerConfig.machineTypeUri`
  - `resource.config.secondaryWorkerConfig.imageUri`
  - `resource.config.secondaryWorkerConfig.machineTypeUri`
- [Compute Engine instance group disk configuration](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/InstanceGroupConfig.md.txt#DiskConfig) (bootDiskType, bootDiskSizeGb, numLocalSsds, and localSsdInterface)
  - `resource.config.masterConfig.diskConfig.bootDiskType`
  - `resource.config.workerConfig.diskConfig.bootDiskType`
  - `resource.config.secondaryWorkerConfig.diskConfig.bootDiskType`
  - `resource.config.masterConfig.diskConfig.bootDiskSizeGb`
  - `resource.config.workerConfig.diskConfig.bootDiskSizeGb`
  - `resource.config.secondaryWorkerConfig.diskConfig.bootDiskSizeGb`
  - `resource.config.masterConfig.diskConfig.numLocalSsds`
  - `resource.config.workerConfig.diskConfig.numLocalSsds`
  - `resource.config.secondaryWorkerConfig.diskConfig.numLocalSsds`
  - `resource.config.masterConfig.diskConfig.localSsdInterface`
  - `resource.config.workerConfig.diskConfig.localSsdInterface`
  - `resource.config.secondaryWorkerConfig.diskConfig.localSsdInterface`
- [Initialization actions](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#nodeinitializationaction) (executableFile)
  - `resource.config.initializationActions.executableFile`
- [Software config](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#softwareconfig) (imageVersion, properties, and optionalComponents)
  - `resource.config.softwareConfig.imageVersion`
  - `resource.config.softwareConfig.properties`
  - `resource.config.softwareConfig.optionalComponents`
- [Kerberos config](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#kerberosconfig) (enableKerberos and crossRealmTrustKdc)
  - `resource.config.securityConfig.kerberosConfig.enableKerberos`
  - `resource.config.securityConfig.kerberosConfig.crossRealmTrustKdc`
- [Component gateway](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#endpointconfig) (enableHttpPortAccess)
  - `resource.config.endpointConfig.enableHttpPortAccess`
- [Metastore config](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#metastoreconfig) (dataprocMetastoreService)
  - `resource.config.metastoreConfig.dataprocMetastoreService`
- [Persistent Disk CMEK](https://docs.cloud.google.com/managed-spark/docs/concepts/configuring-clusters/customer-managed-encryption.md.txt) (gcePdKmsKeyName)
  - `resource.config.encryptionConfig.gcePdKmsKeyName`
- [Cluster labels](https://docs.cloud.google.com/managed-spark/docs/guides/creating-managing-labels.md.txt)
  - `resource.labels`
- [Cluster size](https://docs.cloud.google.com/managed-spark/docs/concepts/configuring-clusters/scaling-clusters.md.txt)
  - `resource.config.masterConfig.numInstances`
  - `resource.config.workerConfig.numInstances`
  - `resource.config.secondaryWorkerConfig.numInstances`
- [Autoscaling](https://docs.cloud.google.com/managed-spark/docs/concepts/configuring-clusters/autoscaling.md.txt)
  - `resource.config.autoscalingConfig.policyUri`
- [Shielded instance config](https://docs.cloud.google.com/managed-spark/docs/reference/rest/v1/ClusterConfig.md.txt#shieldedinstanceconfig) (enableSecureBoot, enableVtpm and enableIntegrityMonitoring)
  - `resource.config.gceClusterConfig.shieldedInstanceConfig.enableSecureBoot`
  - `resource.config.gceClusterConfig.shieldedInstanceConfig.enableVtpm`
  - `resource.config.gceClusterConfig.shieldedInstanceConfig.enableIntegrityMonitoring`

## Example custom constraints for common use cases

The following table provides examples of custom constraints:

| Description | Constraint syntax |
|---|---|
| Restrict the number of Managed Service for Apache Spark worker instances to 10 or fewer when a cluster is created or updated. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocNoMoreThan10Workers resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE - UPDATE condition: "resource.config.workerConfig.numInstances + resource.config.secondaryWorkerConfig.numInstances > 10" actionType: DENY displayName: Total number of worker instances cannot be larger than 10 description: Cluster cannot have more than 10 workers, including primary and secondary workers. ``` |
| Prevent application master from running on Managed Service for Apache Spark cluster preemptible workers. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocAmPrimaryOnlyEnforced resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition:  "('dataproc:am.primary_only' in resource.config.softwareConfig.properties) && (resource.config.softwareConfig.properties['dataproc:am.primary_only']==true)" actionType: ALLOW displayName: Application master cannot run on preemptible workers description: Property "dataproc:am.primary_only" must be "true". ``` |
| Disallow custom Hive properties on Managed Service for Apache Spark clusters. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocNoCustomHiveProperties resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition: "resource.config.softwareConfig.properties.all(p, !p.startsWith('hive:'))" actionType: ALLOW displayName: Cluster cannot have custom Hive properties description: Only allow Dataproc cluster creation if no property starts with Hive prefix "hive:". ``` |
| Disallow the use of the `n1-standard-2` machine type for Managed Service for Apache Spark master instances. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocMasterMachineType resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition: "resource.config.masterConfig.machineTypeUri.contains('n1-standard-2')" actionType: DENY displayName: Master cannot use the n1-standard-2 machine type description:  Prevent Dataproc cluster creation if the master machine type is n1-standard-2. ``` |
| Enforce the use of a specified initialization action script. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocInitActionScript resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition: "resource.config.initializationActions.exists(action, action.executableFile=='gs://some/init-action.sh')" actionType: ALLOW displayName: Initialization action script "gs://some/init-action.sh" must be used description:  Only allow Dataproc cluster creation if the "gs://some/init-action.sh" initialization action script is used. ``` |
| Enforce the use of a specified persistent disk encryption key. | ```yaml name: organizations/ORGANIZATION_ID/custom.dataprocPdCmek resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition: "resource.config.encryptionConfig.gcePdKmsKeyName == 'projects/project-id/locations/global/keyRings/key-ring-name/cryptoKeys/key-name'" actionType: ALLOW displayName: Cluster PD must be encrypted with "key-name" from "key-ring-name" key-ring description: Only allow Dataproc cluster creation if the PD is encrypted with "key-name" from "key-ring-name" key-ring. ``` |
| Enforce cluster label restrictions. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocEnvLabel resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE - UPDATE condition:  "('env' in resource.labels) && (resource.labels.env=='test')" actionType: DENY displayName: Cluster cannot have the "env=test" label description:  Deny Dataproc cluster creation or update if the cluster will be labeled "env=test". ``` |
| Enforce the use of a non-default network. | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dataprocNoDefaultNetwork resourceTypes: - dataproc.googleapis.com/Cluster methodTypes: - CREATE condition:  "resource.config.gceClusterConfig.networkUri.contains('networks/default')" actionType: DENY displayName: Cluster cannot be created in the default network description:  Deny Dataproc cluster creation if the cluster will be created in the default network. ``` |

## What's next

- See [Introduction to the Organization Policy](https://docs.cloud.google.com/resource-manager/docs/organization-policy/overview) to learn more about organization policies.
- Learn more about how to [create and manage organization policies](https://docs.cloud.google.com/resource-manager/docs/organization-policy/using-constraints).
- See the full list of predefined [Organization policy constraints](https://docs.cloud.google.com/resource-manager/docs/organization-policy/org-policy-constraints).