This page describes how to configure Database Center with
VPC Service Controls, a Google Cloud feature to secure data and resources.

VPC Service Controls helps mitigate the risk of data exfiltration from
Database Center instances. You can use VPC Service Controls
to create service perimeters that protect the resources and data of
services that you explicitly specify.

For a general overview of VPC Service Controls, its security benefits, and its
capabilities across supported products, see
[Overview of VPC Service Controls](https://docs.cloud.google.com/vpc-service-controls/docs/overview).

## Before you begin

Before you begin, review [Overview of VPC Service Controls](https://docs.cloud.google.com/vpc-service-controls/docs/overview)
and
[Database Center limitations when using VPC Service Controls](https://docs.cloud.google.com/vpc-service-controls/docs/supported-products#table_database_center_api).
Then, do the following steps to make sure you have the correct permissions to
use VPC Service Controls.

1. In the Google Cloud console, go to the **Project Selector** page.

   [Go to project selector](https://console.cloud.google.com/projectselector2/home/dashboard)
2. Select or [create a Google Cloud project](https://docs.cloud.google.com/resource-manager/docs/creating-managing-projects).

   > [!NOTE]
   > **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.

3. Make sure that billing is enabled for your Google Cloud project. Learn how to [check if billing is enabled on a project](https://docs.cloud.google.com/billing/docs/how-to/verify-billing-enabled).
4. Enable the Compute Engine API. [Enable the Compute Engine API](https://console.cloud.google.com/apis/enableflow?apiid=compute.googleapis.com)

5. Enable the Service Networking API. [Enable the Service Networking API](https://console.cloud.google.com/apis/enableflow?apiid=servicenetworking.googleapis.com)

6. Add the [Identity and Access Management (IAM) roles](https://docs.cloud.google.com/vpc-service-controls/docs/access-control#required_roles) to the user or service account you are using to set up and administer VPC Service Controls. For more information, see [IAM Roles for Administering VPC Service Controls](https://docs.cloud.google.com/vpc-service-controls/docs/access-control).
7. Review [limitations](https://docs.cloud.google.com/vpc-service-controls/docs/supported-products#table_database_center_api) when using VPC Service Controls with Database Center.

## How to secure Database Center service using VPC Service Controls

Configuring VPC Service Controls for Database Center project includes
the following steps:

1. [Create and manage a service perimeter](https://docs.cloud.google.com/database-center/docs/configure-vpc-service-controls#create-manage-perimeters).

   First, you select the Database Center project that you want
   the service perimeter to protect, and then you create and manage the service
   perimeter.
2. [Create and manage access levels](https://docs.cloud.google.com/database-center/docs/configure-vpc-service-controls#create-manage-access-levels).

   Optionally, to permit external access to protected resources inside a
   perimeter, you can use access levels. Access levels apply only to requests
   for protected resources coming from outside the service perimeter. You can't
   use access levels to give protected resources or VMs permission to access
   data and services outside the perimeter.

## Create and manage a service perimeter

To create and manage a service perimeter, complete the following steps:

1. Select the Database Center project that you want the service
   perimeter to protect.

2. Create a service perimeter by following the instructions in
   [Creating a service perimeter](https://docs.cloud.google.com/vpc-service-controls/docs/create-service-perimeters).

3. Add more instances to the service perimeter. To add existing
   Database Center instances to the perimeter, follow the
   instructions in
   [Updating a service perimeter](https://docs.cloud.google.com/vpc-service-controls/docs/manage-service-perimeters#update).

4. Add APIs to the service perimeter. To mitigate the risk of your data being
   exfiltrated from Database Center, you must restrict
   Database Center API, Compute Engine API, Cloud Storage
   API, Container Registry API, Certificate Authority Service API, and Cloud KMS
   API. For more information, see
   [`access-context-manager perimeters update`](https://docs.cloud.google.com/sdk/gcloud/reference/access-context-manager/perimeters/update).

   To add APIs as restricted services, complete following steps:

   ### Console

   1. In the Google Cloud console, go to the **VPC Service Controls** page.

      [Go to VPC Service Controls](https://console.cloud.google.com/projectselector2/security/service-perimeter)
   2. In the **VPC Service Controls** page, in the table, click the name of the service perimeter that you want to modify.
   3. Click **Edit**.
   4. In the **Edit VPC Service Perimeter** page, click **Add Services**.
   5. Select **Database Center** (`databasecenter.googleapis.com`).
   6. Click **Save**.

   ### gcloud

   ```
   gcloud access-context-manager perimeters update PERIMETER_ID \
   --policy=POLICY_ID \
   --add-restricted-services=databasecenter.googleapis.com
   ```
   - <var translate="no">PERIMETER_ID</var>: The ID of the perimeter or the fully qualified identifier for the perimeter.
   - <var translate="no">POLICY_ID</var>: The ID of the access policy.

## Create and manage access levels

To create and manage access levels, follow the instructions in
[Allowing access to protected resources from outside a perimeter](https://docs.cloud.google.com/vpc-service-controls/docs/use-access-levels).