Available in Classic and VPC
Check supported environments, pricing plans, and service limits, etc., for best usage of Key Management Service.
Cloud specifications
The cloud specifications supported by Key Management Service are as follows:
| Item | Specifications |
|---|---|
| Region (zone) | Korea (KR-1, KR-2), U.S., Singapore, Japan, and Germany |
| Platform | VPC, Classic |
| Languages | Korean, English, and Japanese |
Precautions on API credential management
Key Management Service's encryption/decryption features can be used via REST APIs. When accessing programmatically, APIs credentials are used to authenticate users or requests. API credentials can use sub account information or tokens, and API Gateway's API key may be used as needed.
- Sub-account information: Sub account's access key, secret key, and API key (optional)
- Token: refresh token and access token
For API credentials, the sub account's access key, secret key, and the API key of the API are used. The access key and secret key of the sub account can be checked on the sub account details screen of Sub Account, and the API key can be created or checked in the API Keys of the API Gateway. Key Management Service authentication tokens can be managed and used through the console's key management menu or REST APIs.
Anyone with information used in APIs credentials can access them with the same permissions as the owner of the corresponding key in Key Management Service. Therefore, users with Key Management Service permissions must make efforts to comply with the cloud responsibility sharing model when using.
For more information on NAVER Cloud Platform and the user's cloud shared responsibility model, see Security center of the NAVER Cloud Platform portal.
Precautions when using API credentials are as follows:
- APIs credential information (sub account's access key, secret key, and tokens) should not be directly included in code.
- Different credentials must be used for each service name or application.
- API credential information must be renewed periodically.
- You must periodically check the key usage history of Key Management Service to check for unauthorized API calls.
- Unused APIs credential information should be discarded immediately.
- If credentials are leaked, damage should be minimized by immediately changing the sub account's credential values or performing procedures to revoke the token generator.
Download Java SDKs
Key Management Service's Rest API provides Java SDKs (Maven project). Use the SDKs to easily call the Key Management Service API through the API Gateway. To download the Key Management Service Java Client SDKs file, check the information and click Download.
| Date of publication | Name | Extension | Size | Version | Composition | System requirements | File |
|---|---|---|---|---|---|---|---|
| 2022-07-21 | KMS-client-sdk-1.2 | zip | 29 KB | - | - | - | Download |
| 2024-01-11 | KMS-client-sdk-1.3 | zip | 163 KB | - | - | - | Download |
Pricing information
Key Management Service is provided on a pay-as-you-go pricing plan. For detailed pricing information about Key Management Service, see Portal > Service > Security > Key Management Service.