cmek-google-cloud-kms changedmanage-claude/cmek-google-cloud-kms
Nearest release: v2.1.310, published 2 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−2removed
From line
39
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits16to this page, all time
The whole hunk
from line 39, old and new numbered
/
from line 39
3939
4040Use only this address, never one sent by email or chat.
4141
42For the lowest latency, use `us-east5` or `us-central1`. Anthropic strongly recommends HSM protection.
42You can use any Cloud KMS location. For the lowest latency, use `us-east5` or `us-central1`. Anthropic strongly recommends HSM protection.
4343
4444To use a key you already have, [add the organization label](https://platform.claude.com/docs/en/manage-claude/cmek-google-cloud-kms#organization-label) first.
4545
from line 47
4747 <Tab title="Google Cloud Console">
4848 <Steps>
4949 <Step title="Create or choose a key ring">
50 In the Google Cloud console, go to the [Key management](https://console.cloud.google.com/security/kms) page. Open a key ring in a single-region US location, such as `us-east5`, or create one.
50 In the Google Cloud console, go to the [Key management](https://console.cloud.google.com/security/kms) page. Open a key ring, or create one in a location such as `us-east5`.
5151 </Step>
5252
5353 <Step title="Configure the key">
No line in this hunk matches that.