Add custom organization policies

This page describes how to create, set up, and manage custom constraints in Cloud SQL instances. For an overview of custom organization policies, see custom organization policies.

Cloud SQL supported resources

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

  • sqladmin.googleapis.com/Instance
  • sqladmin.googleapis.com/BackupRun

To learn more about Organization Policy, see 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, 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. You can enforce organization policies at the organization, folder, or project level.

Organization Policy provides built-in managed constraints 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.

Before you begin

  1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

  2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Roles required to select or create a project

    • Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
    • Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains the resourcemanager.projects.create permission. Learn how to grant roles.

    Go to project selector

  3. Verify that billing is enabled for your Google Cloud project.

  4. Install the gcloud CLI.

  5. If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

  6. To initialize the gcloud CLI, run the following command: 

    gcloud init

  7. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Roles required to select or create a project

    • Select a project: Selecting a project doesn't require a specific IAM role—you can select any project that you've been granted a role on.
    • Create a project: To create a project, you need the Project Creator role (roles/resourcemanager.projectCreator), which contains the resourcemanager.projects.create permission. Learn how to grant roles.

    Go to project selector

  8. Verify that billing is enabled for your Google Cloud project.

  9. Install the gcloud CLI.

  10. If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.

  11. To initialize the gcloud CLI, run the following command: 

    gcloud init
  12. Ensure that you know your organization ID.

Required roles

To get the permissions that you need to manage custom organization policies, ask your administrator to grant you the Organization Policy Administrator (roles/orgpolicy.policyAdmin) IAM role on the organization resource. For more information about granting roles, see Manage access to projects, folders, and organizations.

You might also be able to get the required permissions through custom roles or other predefined roles.

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). For more information about how to build conditions in custom constraints using CEL, see the CEL section of Creating and managing custom constraints.

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

  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 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 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.disableGkeAutoUpgrade. 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/NodePool. 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 on 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. Not all Google Cloud services support both methods. To see supported methods for each service, find the service in Supported services.

  9. 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.management.autoUpgrade == false. This field can contain up to 1000 characters. For details about CEL usage, see Common Expression Language. For more information about the service resources you can use in your custom constraints, see Custom constraint supported services.
    2. Click Save.
  10. Under Action, select whether to allow or deny the evaluated method if the condition is met.

    11. The deny action means that the operation to create or update the resource is blocked if the condition evaluates to true.

    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 ones explicitly listed in the condition is blocked.

  11. Click Create constraint.

    12. 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: 
    2.       name: organizations/ORGANIZATION_ID/customConstraints/CONSTRAINT_NAME
      resourceTypes:
      - RESOURCE_NAME
      methodTypes:
      - CREATE
    - UPDATE     
      condition: "CONDITION"
      actionType: ACTION
      displayName: DISPLAY_NAME
      description: DESCRIPTION

    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.region. This field can contain up to 70 characters.
    • RESOURCE_NAME: the fully qualified name of the Google Cloud resource containing the object and field that you want to restrict. For example, sqladmin.googleapis.com/Instance.
    • CONDITION: a CEL condition that is written against a representation of a supported service resource. This field can contain up to 1000 characters. For example, "resource.region == "us-central1"".

      • For more information about the resources available to write conditions against, see 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-friendly name for the constraint. 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.
  2. 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 command: 
    3.         gcloud org-policies set-custom-constraint CONSTRAINT_PATH

    Replace CONSTRAINT_PATH with the full path to your custom constraint file. For example, /home/user/customconstraint.yaml.

    After this operation is complete, your custom constraints are available as organization policies in your list of Google Cloud organization policies.

  3. To verify that the custom constraint exists, use the gcloud org-policies list-custom-constraints command: 
    4.       gcloud org-policies list-custom-constraints --organization=ORGANIZATION_ID

    Replace ORGANIZATION_ID with the ID of your organization resource.

    For more information, see 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

  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 Setting an organization policy with tags.
  9. Click Test changes to simulate the effect of the organization policy. For more information, see Test organization policy changes with Policy Simulator.
  10. To enforce the organization policy in dry-run mode, click Set dry run policy. For more information, see Create an organization policy in dry-run mode.
  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: 
    2.         name: projects/PROJECT_ID/policies/CONSTRAINT_NAME
        spec:
          rules:
          - enforce: true
        
        dryRunSpec:
          rules:
          - enforce: true

    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.region.
  2. To enforce the organization policy in dry-run mode, run the following command with the dryRunSpec flag: 
    3.         gcloud org-policies set-policy POLICY_PATH \
          --update-mask=dryRunSpec

    Replace POLICY_PATH with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.

  3. 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: 
    4.         gcloud org-policies set-policy POLICY_PATH \
          --update-mask=spec

    Replace POLICY_PATH with the full path to your organization policy YAML file. The policy requires up to 15 minutes to take effect.

Example custom organization policies for common use cases

This table provides syntax examples for some common custom constraints.

Description Constraint syntax
Ensure that instances are Enterprise Plus 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.edition
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.edition == 'ENTERPRISE_PLUS'"
    actionType: ALLOW
    displayName: Instances must be Enterprise Plus.
    description: Cloud SQL instances must be Enterprise Plus.
Ensure instances are highly available 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.availability
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.availabilityType == 'REGIONAL'"
    actionType: ALLOW
    displayName: Instances must be regional.
    description: Cloud SQL instances must be highly available. To do this, make them regional.
Require the SSL Mode to be enabled with encrypted connections only. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.sslMode
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.ipConfiguration.sslMode == 'ENCRYPTED_ONLY'"
    actionType: ALLOW
    displayName: Only allow connections that are encrypted with SSL/TLS.
    description: Cloud SQL instances must only allow connections that are encrypted with SSL/TLS.
Block database access from anywhere in the public internet. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.authorizedNetworks
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.ipConfiguration.authorizedNetworks.exists(network, network.value == '0.0.0.0/0')"
    actionType: DENY
    displayName: The list of authorized networks can't contain 0.0.0.0/0
    description: Authorized networks for Cloud SQL instances can't contain 0.0.0.0/0. This allows users to access the database from any IP address.
Ensure that instances aren't created with an external IP address. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.ipv4Enabled
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.ipConfiguration.ipv4Enabled == false"
    actionType: ALLOW
    displayName: ipv4Enabled must be set to false.
    description: Cloud SQL instances can't have an external IP address.
Ensure that instances are encrypted with a KMS key. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.encrypted
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.diskEncryptionConfiguration.kmsKeyName.size() > 0"
    actionType: ALLOW
    displayName: Instances must be encrypted with a KMS key.
    description: Cloud SQL instances must be disk-encrypted with a KMS key.
Ensure Instances are in the us-central1 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.region
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.region == 'us-central1'"
    actionType: ALLOW
    displayName: Instances must be in the us-central1 region.
    description: Cloud SQL instances must be in the us-central1 region.
Ensure that instances have data cache enabled. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.dataCache
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.dataCacheConfig.dataCacheEnabled == true"
    actionType: ALLOW
    displayName: Instances must have data cache enabled.
    description: Cloud SQL instances must have data cache enabled.
Enforce automated backups. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.enableBackups
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.backupConfiguration.enabled == true"
    actionType: ALLOW
    displayName: Automated backups must be enabled.
    description: Cloud SQL instances must have automated backups enabled.
Restrict the location of automated backups. 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.automatedBackupLocation
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.backupConfiguration.location == 'us-central1'"
    actionType: ALLOW
    displayName: The location of automated backups must be in the us-central1 region.
    description: The location of automated backups for Cloud SQL instances must be in the us-central1 region.
Restrict the location of on-demand backups to us-central1 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.onDemandBackupLocation
    resourceTypes:
    - sqladmin.googleapis.com/BackupRun
    methodTypes:
    - CREATE
    - UPDATE
    condition: "condition: resource.location == 'us-central1'"
    actionType: ALLOW
    displayName: The location of on-demand backups must be in the us-central1 region.
    description: On-demand backups are restricted to the us-central1.
Enforce a final backup at instance deletion 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.retainBackupsOnDelete
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "condition: resource.settings.finalBackupConfig.enabled == true"
    actionType: ALLOW
    displayName: Final backup is enabled and must be taken at instance deletion.
    description: Final backups are enabled for instance.
Enforce a final backup at instance deletion retention period 
    name: organizations/ORGANIZATION_ID/customConstraints/custom.retainBackupsOnDelete
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "condition: resource.settings.finalBackupConfig.enabled == true && resource.settings.finalBackupConfig.retentionDays == 20"
    actionType: ALLOW
    displayName: Final backup is enabled and must be retained for 20 days after
    instance deletion.
    description: Final backups is retained for 20 days after instance deletion.

Cloud SQL for SQL Server supported resources

The following table lists the Cloud SQL for SQL Server resources that you can reference in custom constraints.

Resource Field
sqladmin.googleapis.com/BackupRun resource.description
resource.location
sqladmin.googleapis.com/Instance resource.databaseVersion
resource.diskEncryptionConfiguration.kmsKeyName
resource.diskEncryptionStatus.kmsKeyVersionName
resource.failoverReplica.name
resource.masterInstanceName
resource.name
resource.nodeCount
resource.project
resource.region
resource.replicaConfiguration.cascadableReplica
resource.replicaConfiguration.failoverTarget
resource.settings.activationPolicy
resource.settings.activeDirectoryConfig.domain
resource.settings.advancedMachineFeatures.threadsPerCore
resource.settings.availabilityType
resource.settings.backupConfiguration.backupRetentionSettings.retainedBackups
resource.settings.backupConfiguration.backupRetentionSettings.retentionUnit
resource.settings.backupConfiguration.binaryLogEnabled
resource.settings.backupConfiguration.enabled
resource.settings.backupConfiguration.location
resource.settings.backupConfiguration.pointInTimeRecoveryEnabled
resource.settings.backupConfiguration.startTime
resource.settings.backupConfiguration.transactionLogRetentionDays
resource.settings.collation
resource.settings.connectionPoolConfig.connectionPoolingEnabled
resource.settings.connectionPoolConfig.flags.name
resource.settings.connectionPoolConfig.flags.value
resource.settings.connectorEnforcement
resource.settings.databaseFlags.name
resource.settings.databaseFlags.value
resource.settings.dataCacheConfig.dataCacheEnabled
resource.settings.dataDiskProvisionedIops
resource.settings.dataDiskProvisionedThroughput
resource.settings.dataDiskSizeGb
resource.settings.dataDiskType
resource.settings.deletionProtectionEnabled
resource.settings.denyMaintenancePeriods.endDate
resource.settings.denyMaintenancePeriods.startDate
resource.settings.denyMaintenancePeriods.time
resource.settings.edition
resource.settings.enableDataplexIntegration
resource.settings.enableGoogleMlIntegration
resource.settings.insightsConfig.queryInsightsEnabled
resource.settings.insightsConfig.queryPlansPerMinute
resource.settings.insightsConfig.queryStringLength
resource.settings.insightsConfig.recordApplicationTags
resource.settings.insightsConfig.recordClientAddress
resource.settings.ipConfiguration.authorizedNetworks.name
resource.settings.ipConfiguration.authorizedNetworks.value
resource.settings.ipConfiguration.customSubjectAlternativeNames
resource.settings.ipConfiguration.enablePrivatePathForGoogleCloudServices
resource.settings.ipConfiguration.ipv4Enabled
resource.settings.ipConfiguration.privateNetwork
resource.settings.ipConfiguration.pscConfig.allowedConsumerProjects
resource.settings.ipConfiguration.pscConfig.pscAutoConnections.consumerNetwork
resource.settings.ipConfiguration.pscConfig.pscAutoConnections.consumerProject
resource.settings.ipConfiguration.pscConfig.pscEnabled
resource.settings.ipConfiguration.serverCaMode
resource.settings.ipConfiguration.serverCaPool
resource.settings.ipConfiguration.sslMode
resource.settings.locationPreference.secondaryZone
resource.settings.locationPreference.zone
resource.settings.maintenanceWindow.day
resource.settings.maintenanceWindow.hour
resource.settings.maintenanceWindow.updateTrack
resource.settings.replicationLagMaxSeconds
resource.settings.retainBackupsOnDelete
resource.settings.sqlServerAuditConfig.bucket
resource.settings.sqlServerAuditConfig.retentionInterval
resource.settings.sqlServerAuditConfig.uploadInterval
resource.settings.storageAutoResize
resource.settings.tier
resource.settings.timeZone

What's next