Secret Manager type trigger

Prev Next

Available in VPC

You can add Secret Manager type triggers on the NAVER Cloud Platform console's Cloud Functions > Action > Action details.

Secret Manager is a service designed to securely store and manage critical confidential information (referred to as Secret(s)), such as passwords, private keys for certificates, and authentication tokens, that are required for the operation of applications. With Secret Manager, there is no need to hard-code secrets into the application code or manually implement complex encryption methods.

Note
  • An additional fee is charged for a subscription to Secret Manager. For more information about Secret Manager and its pricing plan, see Services > Security > Secret Manager on the NAVER Cloud Platform portal.
  • Secret Manager type triggers are supported only in the Korea Region, Japan Region, and VPC platform.

Add trigger

To add a Secret Manager type trigger, click and select Secret Manager in the trigger type, then configure the trigger's basic information and Secret Manager connection information.

Connection information setup

You can configure the connection settings of Secret Manager-type trigger in Secret connection information within the console.

cloudfunctions-secretmanager_v2_01_ko

  • Select the Secret you want to connect in the Secret list.
  • Secrets that are disabled (DISABLE) or scheduled for revocation (REVOKE) cannot be connected. It is not included in the Secret list.
  • Secrets can be connected to up to 1 trigger. Secrets connected to other triggers are not included in the list.
  • Click [Create Secret] to go to the Secret Manager console and create a new Secret.
  • You must read and check the caution statements to create a trigger
Caution

When multiple Secrets are connected to the trigger, the rotation event of each Secret occurs independently. Even if multiple secret rotation events occur at the same time, each secret rotation action's success is not guaranteed. To execute secret rotation correctly, complete the secret rotation action configuration depending on the guide.

Events forwarded to trigger

When the Secret rotation event occurs in Secret Manager, the event information is forwarded to the Secret Manager type trigger. The event information can then be used as parameters within the action code connected to the Secret Manager type trigger for various applications. The examples of the events forwarded to Secret Manager type trigger are as follows:

{
    "__ncloud_eventSourceId":"nrn:PUB:SecretManager:KR:1234:Secret/<SECRET_ID>", // Secret NRN
    "secretId":"<SECRET_ID>",                                                    // Secret ID
    "jobToken":"ceda74cc-3fc7-4b23-991b-6471b40f74b9"                            // Secret rotation token
}