Cloud key management
Google Cloud EKM (External Key...

Set up Google Cloud External Key Manager (EKM) initially

3min

To set up EKM the first time, perform the steps in this section in the Google dashboard to create a new key ring and find the service account address.

Go to the Google Cloud Key Management Dashboard

1

From the main Google Cloud dashboard, enter Key Management in the search bar at the top of the page.

2

Select Key Management - Security service.

Create a new key ring

1

From the Key Management dashboard, select [ Create Key Ring ] at the top of the page.

2

In the Create key ring wizard, enter a name for the key ring.

Key ring names can only contain letters, numbers, underscores (_), and hyphens (-). You can't rename or delete them.

3

Select Region as the Location type (EKM does not support Multi-region). In the drop-down menu, select the Google region where you want to create the key ring.

4

Select [ Create ].

Note the following regarding the key ring location:

  • Cloud EKM needs to be able to reach your keys quickly to avoid an error. When creating a Cloud EKM key, choose a Google Cloud location that is geographically near the location of the KMES Series 3.
  • You can use Cloud EKM in any Google Cloud location supported for Cloud KMS, except for global.

Find the Service Account email address

After you create the Key Ring, the browser redirects to the key creation wizard. Perform the following steps to find the Service Account email address:

1

Enter a name for the key in the Key Creation wizard.

2

Select the External as the protection level for the key.

3

Select either via internet or via VPC as the External key manager (EKM) connection type.

4

Select [ Continue ].

5

Note the service account email address in the Key material section. The service account email address is copied later to the email field of the identity that Google uses to interact with the KMES Series 3.

You return to this dialog in the Google Cloud dashboard after creating a Google Crypto Space on the KMES in an upcoming section.