This page shows you how to use Organization Policy Service custom constraints to restrict
specific operations on the following Google Cloud resources:

- `storage.googleapis.com/Bucket`

To learn more about Organization Policy, see
[Custom organization policies](https://docs.cloud.google.com/organization-policy/overview.md.txt#custom-organization-policies).

## About organization policies and constraints

The Google Cloud Organization Policy Service gives you centralized, programmatic
control over your organization's resources. As the
[organization policy administrator](https://docs.cloud.google.com/iam/docs/roles-permissions/orgpolicy.md.txt#orgpolicy.policyAdmin), you can define an organization
policy, which is a set of restrictions called *constraints* that apply to
Google Cloud resources and descendants of those resources in the
[Google Cloud resource hierarchy](https://docs.cloud.google.com/resource-manager/docs/cloud-platform-resource-hierarchy.md.txt). You can enforce organization
policies at the organization, folder, or project level.

Organization Policy provides built-in [managed constraints](https://docs.cloud.google.com/organization-policy/reference/org-policy-constraints.md.txt)
for various Google Cloud services. 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.

### 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/organization-policy/hierarchy-evaluation.md.txt#disallow_inheritance).

## Limitations


- [Bucket labels](https://docs.cloud.google.com/storage/docs/tags-and-labels.md.txt#bucket-labels) aren't recommended for use in custom constraint
  conditions. Instead, use [tags](https://docs.cloud.google.com/storage/docs/tags-and-labels.md.txt#tags), which can only be set by individuals with
  required Identity and Access Management (IAM) roles and are more tightly controlled than
  labels.

- Newly enforced custom constraints don't apply to existing resources. Existing
  resources must be updated for the constraint to apply.

  To find existing resources that will need to be updated, you can enforce a
  [dry-run organization policy](https://docs.cloud.google.com/resource-manager/docs/organization-policy/dry-run-policy).
- Custom constraints can't be used to constrain ACLs or IAM
  policies on objects or buckets.

## Before you begin

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
- Test the example organization policy on this page by creating a bucket: [Storage Admin](https://docs.cloud.google.com/iam/docs/roles-permissions/storage.md.txt#storage.admin) (`roles/storage.admin`) on the project


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.*` on the organization
- Test the example organization policy on this page by creating a bucket: `storage.buckets.create` on the project


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).

## Cloud Storage supported resources


The following table lists the Cloud Storage resources that you can
reference in custom constraints.

<br />

| Resource | Field |
|---|---|
| storage.googleapis.com/Bucket | `resource.billing.requesterPays` |
| storage.googleapis.com/Bucket | `resource.cors.maxAgeSeconds` |
| storage.googleapis.com/Bucket | `resource.cors.method` |
| storage.googleapis.com/Bucket | `resource.cors.origin` |
| storage.googleapis.com/Bucket | `resource.cors.responseHeader` |
| storage.googleapis.com/Bucket | `resource.customPlacementConfig.dataLocations` |
| storage.googleapis.com/Bucket | `resource.defaultEventBasedHold` |
| storage.googleapis.com/Bucket | `resource.encryption.defaultKmsKeyName` |
| storage.googleapis.com/Bucket | `resource.iamConfiguration.publicAccessPrevention` |
| storage.googleapis.com/Bucket | `resource.iamConfiguration.uniformBucketLevelAccess.enabled` |
| storage.googleapis.com/Bucket | `resource.ipFilter.mode` |
| storage.googleapis.com/Bucket | `resource.ipFilter.publicNetworkSource.allowedIpCidrRanges` |
| storage.googleapis.com/Bucket | `resource.ipFilter.vpcNetworkSources.allowedIpCidrRanges` |
| storage.googleapis.com/Bucket | `resource.ipFilter.vpcNetworkSources.network` |
| storage.googleapis.com/Bucket | `resource.labels` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.action.storageClass` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.action.type` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.age` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.createdBefore` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.customTimeBefore` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.daysSinceCustomTime` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.daysSinceNoncurrentTime` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.isLive` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.matchesPrefix` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.matchesStorageClass` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.matchesSuffix` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.noncurrentTimeBefore` |
| storage.googleapis.com/Bucket | `resource.lifecycle.rule.condition.numNewerVersions` |
| storage.googleapis.com/Bucket | `resource.location` |
| storage.googleapis.com/Bucket | `resource.locationType` |
| storage.googleapis.com/Bucket | `resource.logging.logBucket` |
| storage.googleapis.com/Bucket | `resource.logging.logObjectPrefix` |
| storage.googleapis.com/Bucket | `resource.name` |
| storage.googleapis.com/Bucket | `resource.objectRetention.mode` |
| storage.googleapis.com/Bucket | `resource.retentionPolicy.isLocked` |
| storage.googleapis.com/Bucket | `resource.retentionPolicy.retentionPeriod` |
| storage.googleapis.com/Bucket | `resource.rpo` |
| storage.googleapis.com/Bucket | `resource.softDeletePolicy.retentionDurationSeconds` |
| storage.googleapis.com/Bucket | `resource.storageClass` |
| storage.googleapis.com/Bucket | `resource.versioning.enabled` |
| storage.googleapis.com/Bucket | `resource.website.mainPageSuffix` |
| storage.googleapis.com/Bucket | `resource.website.notFoundPage` |

Note the following:

- You must use uppercase to specify the values for the following fields:
  - `resource.lifecycle.rule.action.storageClass`
  - `resource.location`
  - `resource.storageClass`
- You must use lowercase to specify the values for the following fields:
  - `resource.customPlacementConfig.dataLocations`
- The `resource.retentionPolicy.isLocked` field can only be used to prohibit the use of Bucket Lock, not to enforce Bucket Lock.

<br />

## Set up a custom constraint

A custom constraint is defined in a YAML file by the resources, methods,
conditions, and actions that are supported by the service on which you are
enforcing the organization policy. Conditions for your custom constraints are
defined using
[Common Expression Language (CEL)](https://github.com/google/cel-spec/blob/master/doc/intro.md). For more information about how to build
conditions in custom constraints using CEL, see the CEL section of
[Creating and managing custom constraints](https://docs.cloud.google.com/organization-policy/create-custom-constraints.md.txt#common_expression_language).

### 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.bucketNamingRequirement`. 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. Under **Enforcement method** , select whether to enforce the constraint on a REST `CREATE` method or both `CREATE` and `UPDATE` methods. If you enforce the constraint with the `UPDATE` method on a resource that violates the constraint, changes to that resource are blocked by the organization policy unless the change resolves the violation.
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
  - UPDATE 
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.bucketNamingRequirement`. 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, `storage.googleapis.com/Bucket`. 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 be `CREATE` or both `CREATE` and `UPDATE`. If you enforce the constraint with the `UPDATE` method on a resource that violates the constraint, changes to that resource are blocked by the organization policy unless the change resolves the violation.
   - 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.name.matches('^[a-zA-Z]+$')"`.
   - For more information about the resources available to write conditions against, see [Supported resources](https://docs.cloud.google.com/storage/docs/custom-constraints.md.txt#supported_resources).
   - `ACTION`: the action to take if the `condition` is met. Possible values are `ALLOW` and `DENY`.
   - 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.
   - The deny action means that if the condition evaluates to true, the operation to create or update the resource 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 organization policy

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.bucketNamingRequirement`.
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 organization policy


The following example creates a custom constraint and policy that require all
newly created buckets to have a name that contains only letters. You can test
the policy by trying to take an action that the policy should prevent.

### Create the constraint

1. Save the following file as `constraint-bucket-names.yaml`:

   ```bash
   name: organizations/ORGANIZATION_ID/customConstraints/custom.bucketNamingRequirement
   resource_types: storage.googleapis.com/Bucket
   method_types:
   - CREATE
   condition: "resource.name.matches('^[a-zA-Z]+$')"
   action_type: ALLOW
   display_name: Bucket names must match the specified regular expression
   description: Newly created buckets must have a name that matches the specified regular expression. Only letters are allowed in the bucket name.
   ```

   Replace `ORGANIZATION_ID` with your organization ID.
2. Apply the constraint:

   ```bash
   gcloud org-policies set-custom-constraint ~/constraint-bucket-names.yaml
   ```
3. Verify that the constraint exists:

   ```bash
   gcloud org-policies list-custom-constraints --organization=ORGANIZATION_ID
   ```

   The output is similar to the following:

       CUSTOM_CONSTRAINT                 ACTION_TYPE    METHOD_TYPES    RESOURCE_TYPES                  DISPLAY_NAME
       custom.bucketNamingRequirement    ALLOW          CREATE          storage.googleapis.com/Bucket   Bucket names must match the specified regular expression
       ...

### Create the policy

1. Save the following file as `policy-bucket-names.yaml`:

   ```yaml
   name: projects/PROJECT_ID/policies/custom.bucketNamingRequirement
   spec:
     rules:
     - enforce: true
   ```

   Replace `PROJECT_ID` with your project ID.

   In this example, you enforce this constraint at the project level, but you
   might also set this at the organization or folder level.
2. Apply the policy:

   ```bash
   gcloud org-policies set-policy ~/policy-bucket-names.yaml
   ```
3. Verify that the policy exists:

   ```bash
   gcloud org-policies list --project=PROJECT_ID
   ```

   The output is similar to the following:

       CONSTRAINT                        LIST_POLICY    BOOLEAN_POLICY    ETAG
       custom.bucketNamingRequirement    -              SET               CIqktscGELiZn6cC-

After you apply the policy, wait for about two minutes for Google Cloud
to start enforcing the policy.

### Test the policy

- Try to create a bucket with a name that contains a character that isn't a
  letter:

  ```bash
  gcloud storage buckets create gs://example-bucket --location=BUCKET_LOCATION
  ```

  Replace `BUCKET_LOCATION` with the location of the
  bucket. For example, `US`.

  The request fails with an error similar to the following:

  ```bash
  ERROR: (gcloud.storage.buckets.create) HTTPError 412: orgpolicy:projects/_/buckets/example-bucket violates customConstraints/custom.bucketNamingRequirement. Details: Newly created buckets must have a name that matches the specified regular expression. Only letters are allowed in the bucket name.
  ```

## Example custom organization policies for common use cases


The following table provides syntax examples for some common custom constraints.
For a list of predefined constraints that you can use with
Cloud Storage, see
[Organization policy constraints for Cloud Storage](https://docs.cloud.google.com/storage/docs/org-policy-constraints.md.txt).

<br />

<br />

<br />

| Description | Constraint syntax |
|---|---|
| Buckets must have Object Versioning enabled | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.enforceBucketVersioning method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "resource.versioning.enabled == true" action_type: ALLOW display_name: Buckets must have Object Versioning enabled description: Newly created buckets and newly updated buckets must have Object Versioning enabled. ``` |
| Buckets must be named using a specific regular expression | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.bucketNamingRequirement method_types: - CREATE resource_types: storage.googleapis.com/Bucket condition: "resource.name.matches('^[a-zA-Z]+$')" action_type: ALLOW display_name: Bucket names must match the specified regular expression description: Newly created buckets must have a name that matches the specified regular expression. Only letters are allowed in the bucket name. ``` |
| Buckets cannot have Bucket Lock enabled | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.prohibitBucketLock method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "resource.retentionPolicy.isLocked == true" action_type: DENY display_name: Prohibit the use of Bucket Lock description: Newly created buckets and newly updated buckets cannot have Bucket Lock enabled. ``` |
| Buckets cannot have Object Retention Lock enabled | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.prohibitObjectRetentionLock method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "resource.objectRetention.mode == 'Enabled'" action_type: DENY display_name: Objects cannot have retention configurations description: Newly created buckets and newly updated buckets cannot have Object Retention Lock enabled. ``` |
| Buckets located in the `US` or `EU` multi-regions must have a retention period of 86,400 seconds | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.locationRetentionPolicy method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "(resource.location.startsWith('US') || resource.location.startsWith('EU')) && resource.retentionPolicy.retentionPeriod != 86400" action_type: DENY display_name: All buckets in US and EU must have a retention policy of 86,400 seconds description: Newly created buckets and newly updated buckets located in US and EU regions must have a retention policy of 86,400 seconds. ``` |
| Buckets must have labels^1^ | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.labels method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "'my_annotations.data.source' in resource.labels && resource.labels['my_annotations.data.source'] in ['SOURCE_IMAGES','SOURCE_TEXT','SOURCE_VIDEOS']" action_type: ALLOW display_name: Buckets must have a label classifying the contents of the bucket description: Newly created buckets and newly updated buckets must have the label my_annotations.data.source with the SOURCE_IMAGES, SOURCE_TEXT, or SOURCE_VIDEOS key. ``` |
| Buckets must be located in a dual-region | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.dualRegionUS method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "'us-east1' in resource.customPlacementConfig.dataLocations && 'us-east4' in resource.customPlacementConfig.dataLocations" action_type: ALLOW display_name: Buckets must be located in a dual-region description: Newly created buckets and newly updated buckets must be located in a dual-region composed of the us-east1 and us-east4 regions. ``` |
| Buckets cannot use legacy storage classes | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.disableLegacyStorageClass method_types: - CREATE - UPDATE resource_types: storage.googleapis.com/Bucket condition: "resource.storageClass in ['STANDARD', 'NEARLINE', 'COLDLINE', 'ARCHIVE']" action_type: ALLOW display_name: Buckets cannot use legacy storage classes description: Newly created buckets and newly updated buckets must use Standard storage, Nearline storage, Coldline storage, or Archive storage. ``` |
| Bucket IP filtering must restrict requests from all the public internet | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.IpFilter method_types: - CREATE resource_types: storage.googleapis.com/Bucket condition: "!has(resource.ipFilter) || (resource.ipFilter.mode == 'Disabled' || resource.ipFilter.publicNetworkSource.allowedIpCidrRanges.size() > 0)" action_type: DENY display_name: Bucket IP filter rules must restrict all the public network description: Newly created buckets must have IP filtering and IP filtering rules must restrict all public network resources. ``` |
| Objects in a bucket must use customer-managed encryption keys (CMEK) | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.EnforceCmekOnBucket resource_types: storage.googleapis.com/Bucket method_types: - CREATE - UPDATE condition: "resource.encryption.googleManagedEncryptionEnforcementConfig.restrictionMode != 'FullyRestricted' || resource.encryption.customerManagedEncryptionEnforcementConfig.restrictionMode != 'NotRestricted' || resource.encryption.customerSuppliedEncryptionEnforcementConfig.restrictionMode != 'FullyRestricted'" action_type: DENY display_name: Buckets must enforce CMEK encryption for new objects description: Newly created buckets and newly updated buckets must allow only customer-managed encryption keys (CMEK) to encrypt new objects. Encryption using standard encryption (Google default encryption) or customer-supplied encryption keys must be prohibited for new objects. ``` |
| Objects in a bucket cannot use customer-supplied encryption keys (CSEK) | ```yaml name: organizations/ORGANIZATION_ID/customConstraints/custom.restrictCsekOnBucket resource_types: storage.googleapis.com/Bucket method_types: - CREATE - UPDATE condition: "resource.encryption.customerSuppliedEncryptionEnforcementConfig.restrictionMode != 'FullyRestricted'" action_type: DENY display_name: Buckets must prohibit CSEK encryption for new objects description: Newly created buckets and newly updated buckets must prohibit the use of customer-supplied encryption keys (CSEK) to encrypt new objects. ``` |
| ^1^ Specifying a bucket label key that does not exist returns a `BAD_CONDITION` error. This error blocks the `CREATE` and `UPDATE` methods from being run on the bucket. To avoid this error, always check that the label key exists first by using `"my_annotations.data.source" in resource.labels`. ||

### Conditional organization policies


You can make a custom organization policy conditional by using tags. For more
information, see
[Setting an organization policy with tags](https://docs.cloud.google.com/resource-manager/docs/organization-policy/tags-organization-policy#setting_an_organization_policy_with_tags).


## What's next

- Learn more about [Organization Policy Service](https://docs.cloud.google.com/organization-policy/overview.md.txt).
- Learn more about how to [create and manage organization policies](https://docs.cloud.google.com/organization-policy/create-organization-policies.md.txt).
- See the full list of managed [organization policy constraints](https://docs.cloud.google.com/organization-policy/reference/org-policy-constraints.md.txt).