Add Cloud SQL organization policies

This page describes how to add organization policies on Cloud SQL instances, to put restrictions on Cloud SQL at the project, folder, or organization level. For an overview, see Cloud SQL organization policies.

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.

    Go to project selector

  3. Make sure that billing is enabled for your Google Cloud project.

  4. Install the Google Cloud CLI.
  5. To initialize the gcloud CLI, run the following command:

    gcloud init
  6. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

    Go to project selector

  7. Make sure that billing is enabled for your Google Cloud project.

  8. Install the Google Cloud CLI.
  9. To initialize the gcloud CLI, run the following command:

    gcloud init
  10. Add the Organization Policy Administrator role (roles/orgpolicy.policyAdmin) to your user or service account from the IAM & Admin page.

    Go to the IAM accounts page

  11. See Restrictions before performing this procedure.

Add the connection organization policy

For an overview see Connection organization policies.

To add a connection organization policy:

  1. Go to the Organization policies page.

    Go to the Organization policies page

  2. Click projects dropdown menu in the top tab, and then select the project, folder, or organization that requires the organization policy. The Organization policies page displays a list of organization policy constraints that are available.

  3. Filter for the constraint name or display_name.

    • To disable access to or from the Internet:

      name: "constraints/sql.restrictPublicIp"
      display_name: "Restrict Public IP access on Cloud SQL instances"
      
    • To disable access from the internet when IAM authentication is missing (this does not affect access using Private IP):

      name: "constraints/sql.restrictAuthorizedNetworks"
      display_name: "Restrict Authorized Networks on Cloud SQL instances"
      
  4. Select the policy Name from the list.

  5. Click Edit.

  6. Click Customize.

  7. Click Add rule.

  8. Under Enforcement, click On.

  9. Click Save.

Add the CMEK organization policy

For an overview see Customer-managed encryption keys organization policies.

To add a CMEK organization policy:

  1. Go to the Organization policies page.

    Go to the Organization policies page

  2. Click projects dropdown menu in the top tab, and then select the project, folder, or organization that requires the organization policy. The Organization policies page displays a list of organization policy constraints that are available.

  3. Filter for the constraint name or display_name.

    • To put service names in a DENY list to ensure that CMEK is used in the resources for that service:

      name: "constraints/gcp.restrictNonCmekServices"
      display_name: "Restrict which services may create resources without CMEK"
      

      You must add sqladmin.googleapis.com to the list of restricted services with Deny.

    • To put project IDs in an ALLOW list to ensure that only keys from an instance of Cloud KMS within that project are used for CMEK.

      name: "constraints/gcp.restrictCmekCryptoKeyProjects"
      display_name: "Restrict which projects may supply KMS CryptoKeys for CMEK"
      
  4. Select the policy Name from the list.

  5. Click Edit.

  6. Click Customize.

  7. Click Add rule.

  8. Under Policy values, click Custom.

  9. For constraints/gcp.restrictNonCmekServices: a. Under Policy types, select Deny. b. Under Custom values, enter sqladmin.googleapis.com.

    For constraints/gcp.restrictCmekCryptoKeyProjects: a. Under Policy types, select Allow. b. Under Custom values, enter the resource using the following format: under:organizations/ORGANIZATION_ID, under:folders/FOLDER_ID, or projects/PROJECT_ID.

  10. Click Done.

  11. Click Save.

What's next