- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Google Cloud Key Management Service stores cryptographic keys in a hierarchical structure designed for useful and elegant access control management.
The format for the rotation schedule depends on the client library that is used. For the gcloud CLI, the flag --next-rotation-time
must be in ISO or RFC3339 format; the flag --rotation-period
must be in the format INTEGER[UNIT]
, where units can be one of: seconds (s), minutes (m), hours (h), or days (d). For example, 30d
for a rotation period of 30 days.
Set a key rotation period and starting time. A key can be created with a specified rotation period, which is the time between when new key versions are generated automatically. A key can also be created with a specified next rotation time.
A key is a named object that represents a cryptographic key and is used for a specific purpose. The key material (the actual bits used for encryption) can change over time as new key versions are created.
A key is used to protect a corpus of data. A collection of files could be encrypted with the same key, and people with decrypt
permissions on that key would be able to decrypt those files. Therefore, it’s necessary to make sure the rotation period is set to a specific time.
After a successful key rotation, the older key version is required to decrypt the data encrypted by the previous key version.
ROTATION_PERIOD
and NEXT_ROTATION_TIME
for each key:
For example, you can use the iam.json file shown below as follows: gcloud kms keys update new --keyring=KEY_RING --location=LOCATION --next- rotation-time=NEXT_ROTATION_TIME --rotation-period=ROTATION_PERIOD
By default, KMS encryption keys are rotated every 90 days.
A user-managed key cannot be created on GCP-Managed Service Accounts.