Cloud key management
Google Cloud EKM (External Key...
Before you start
2 min
verify your environment meets these requirements supported hardware {{ch}} , 7 0 2 x or later required access an account on the {{ch}} with administrator permissions to deploy new services a user in google cloud assigned the cloud kms admin role important use the correct hostname when deploying when you run the deploy google cloud ekm service wizard, cryptohub captures the hostname from your browser’s url bar and uses it as the audience ( aud ) for google id token validation if you open cryptohub by ip (e g , https //10 0 1 7/ ) the audience will be set to that ip if google is configured with an fqdn (e g , ekm example com ), the aud will not match and requests will fail open cryptohub using the intended fqdn before deploying the service network egress required (google jwks) cryptohub must reach google’s public jwks to validate id tokens https //www googleapis com/oauth2/v3/certs ensure outbound https egress (or proxy) is allowed from the cryptohub network without this, jwt validation will fail