Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/sql/docs/postgres/org-policy/custom-org-policy below:

Add custom organization policies | Cloud SQL for PostgreSQL

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.

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.

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.

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.

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.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

3. Make sure 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. Ensure that you know your organization ID.

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.

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.

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

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 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.region. The maximum length of this field is 70 characters.

• RESOURCE_NAME: the fully qualified name of the Google Cloud resource containing the object and field 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 has a maximum length of 1000 characters. See Supported resources for more information about the resources available to write conditions against. For example, "resource.region == "us-central1"".

• ACTION: the action to take if the condition is met. Possible values are ALLOW and DENY.

• DISPLAY_NAME: a human-friendly name for the constraint. 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. This field has a maximum length of 2000 characters.

For more information about how to create a custom constraint, see Defining custom constraints.

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

command:

gcloud org-policies set-custom-constraint CONSTRAINT_PATH

Replace

with the full path to your custom constraint file. For example,

. Once completed, your custom constraints are available as organization policies in your list of Google Cloud organization policies. To verify that the custom constraint exists, use the

command:

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

Replace

with the ID of your organization resource. For more information, see

.

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

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

   Go to Organization policies

2. From the project picker, select the project for which you want to set the organization policy.
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 enforcement of this organization policy is on or off.
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. Policy simulation isn't available for legacy managed constraints. For more information, see Test organization policy changes with Policy Simulator.
10. To finish and apply the organization policy, click Set policy. The policy requires up to 15 minutes to take effect.

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

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

Replace the following:

• PROJECT_ID: the project on which you want to enforce your constraint.
• CONSTRAINT_NAME: the name you defined for your custom constraint. For example, custom.region.

To enforce the organization policy containing the constraint, run the following command:

    gcloud org-policies set-policy POLICY_PATH
    

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

The following table provides the syntax of some custom constraints for common use cases:

    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.
    

    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.
    

    name: organizations/ORGANIZATION_ID/customConstraints/custom.enforcePassword
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.passwordValidationPolicy.enablePasswordPolicy == true"
    actionType: ALLOW
    displayName: The password policy must be enabled for Cloud SQL instances.
    description: Cloud SQL instances must have a password policy.
    

    name: organizations/ORGANIZATION_ID/customConstraints/custom.passwordMinLength
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.passwordValidationPolicy.minLength >= 6"
    actionType: ALLOW
    displayName: The password policy must have a minimum length of six characters.
    description: Cloud SQL instances must have a password policy that has a minimum length of six characters.
    

    name: organizations/ORGANIZATION_ID/customConstraints/custom.passwordComplexity
    resourceTypes:
    - sqladmin.googleapis.com/Instance
    methodTypes:
    - CREATE
    - UPDATE
    condition: "resource.settings.passwordValidationPolicy.complexity == 'COMPLEXITY_DEFAULT'"
    actionType: ALLOW
    displayName: The password policy complexity must be enabled.
    description: Cloud SQL instances must have a password policy with complex passwords.
    

    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.
    

    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.
    

    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.
    

    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.
    

    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.
    

    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.
    

    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.
    

    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.
    

    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.
    

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

• Learn more about Organization Policy Service.
• Learn more about how to create and manage organization policies.
• See the full list of managed organization policy constraints.

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4