Available in VPC
Review supported environments, service limits, and pricing information before using Secret Manager.
Cloud specifications
Secret Manager supports the following cloud environment specifications:
| Item | Specification |
|---|---|
| Region (zone) | Korea (KR-1, KR-2), Japan (JP-4, JP-5) |
| Platform | VPC |
| Language | Korean, Japanese |
Cautions in managing access keys and secret keys
The features of Secret Manager can be used with the Rest APIs. Secret Manager identifies users and verifies permissions using access keys and secret keys. You can check the access key and secret key of the sub account on the sub account details interface of Sub Account.
If the information used for API call (access key and secret key) is exposed, the secret owner can access it with the same permission retained by the owner. Therefore, users must make the appropriate efforts to comply with the cloud shared responsibility model when using API.
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:
- API credentials (access key and secret key of the sub account) should not be included directly in the code.
- Different credentials must be used for each service or application.
- API credential information must be renewed periodically.
- You must check the secret usage history of Secret Manager periodically to check for unauthorized API calls.
- Any unused API credentials must be discarded immediately.
Pricing information
Secret Manager is serviced on a pay-as-you-go pricing plan. For detailed pricing information about Secret Manager, refer to Portal > Service > Security > Secret Manager.