IssueTracker

Problem you have encountered:

I would expect the behaviour of encrypting a disk, gcs bucket to behave the same way.

• From the public docs there should be a 1:1 alignment between regions, with some exceptions for global (GCE public documentation)
• Ir

What you expected to happen:

• 1:1 alignment between regions and kms keys or for both gcs and gce pd to support encrypting regional resources with a key such as EUROPE

Steps to reproduce:

GCE Behavior

Currently, if I create a Key EUROPE and use this to encrypt a disk in europe-west4-b the operation succeeds.

This applies to any region in EUROPE

• using a US key fails as expected with error

  Invalid resource usage: 'Cloud KMS Key, projects/project_id/locations/us/keyRings/us-key-ring/cryptoKeys/us-key, cannot be used because it is 
  located in a different region. The key must reside in the same region or be global.'.
  

GCS Behavior

From documentation:

You must create the Cloud KMS key in the same location as the data you intend to encrypt. For example, if your bucket is located in US-EAST1, any Cloud KMS key encrypting objects in that bucket must also be created in US-EAST1. For available Cloud KMS locations, see Cloud KMS locations.

Testing this out myself I can see that GCS bucket does not work with a EUROPE key and returns in error.