Configure the Konnect Config Store vault

Uses: Kong Gateway decK

Deployment Platform:

Prerequisites

Kong Konnect

This is a Konnect tutorial and requires a Konnect personal access token.

Create a new personal access token by opening the Konnect PAT page and selecting Generate Token.
Export your token to an environment variable:
```
 export KONNECT_TOKEN='YOUR_KONNECT_PAT'
```
Copied to clipboard!
Run the quickstart script to automatically provision a Control Plane and Data Plane, and configure your environment:
```
 curl -Ls https://get.konghq.com/quickstart | bash -s -- -k $KONNECT_TOKEN --deck-output
```
Copied to clipboard!
This sets up a Konnect Control Plane named quickstart, provisions a local Data Plane, and prints out the following environment variable exports:
```
 export DECK_KONNECT_TOKEN=$KONNECT_TOKEN
 export DECK_KONNECT_CONTROL_PLANE_NAME=quickstart
 export KONNECT_CONTROL_PLANE_URL=https://us.api.konghq.com
 export KONNECT_PROXY_URL='http://localhost:8000'
```
Copied to clipboard!
Copy and paste these into your terminal to configure your session.

Kong Gateway running

This tutorial requires Kong Gateway Enterprise. If you don’t have Kong Gateway set up yet, you can use the quickstart script with an enterprise license to get an instance of Kong Gateway running almost instantly.

Export your license to an environment variable:
```
 export KONG_LICENSE_DATA='LICENSE-CONTENTS-GO-HERE'
```
Copied to clipboard!
Run the quickstart script:
```
curl -Ls https://get.konghq.com/quickstart | bash -s -- -e KONG_LICENSE_DATA 
```
Copied to clipboard!
Once Kong Gateway is ready, you will see the following message:
```
 Kong Gateway Ready
```

decK

Konnect API

To use the copy, paste, and run the instructions in this how-to, you must export the additional environmental variable CONTROL_PLANE_ID:

export CONTROL_PLANE_ID='YOUR CONTROL PLANE ID'

Copied to clipboard!

You can find your control plane UUID by navigating to the control plane in the Konnect UI or by sending a GET request to the /control-planes endpoint.

Configure a Konnect Config Store

Before you can configure a Konnect Vault, you must first create a Config Store using the Control Planes Configuration API by sending a POST request to the /config-stores endpoint:

 curl -X POST "$KONNECT_CONTROL_PLANE_URL/v2/control-planes/$CONTROL_PLANE_ID/config-stores" \
     -H "Accept: application/json"\
     -H "Content-Type: application/json"\
     -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
     --json '{
       "name": "my-config-store"
     }'

      
        
      
    
Copied to clipboard!

Export the Config Store ID in the response body as an environment variable so you can use it later:

export DECK_CONFIG_STORE_ID='CONFIG STORE ID'

Copied to clipboard!

Configure Konnect as your Vault

Enable Konnect as your vault with the Vault entity:

echo '
_format_version: "3.0"
vaults:
  - name: konnect
    prefix: mysecretvault
    description: Storing secrets in Konnect
    config:
      config_store_id: "${{ env "DECK_CONFIG_STORE_ID" }}"
' | deck gateway apply -

      
        
      
    
Copied to clipboard!

Store a secret in your Konnect Vault

By storing a secret in a Konnect Vault, you can reference it within kong.conf or as a referenceable plugin fields without having to store any values in plain-text.

Store your secret by sending a POST request to the /secrets endpoint:

 curl -X POST "$KONNECT_CONTROL_PLANE_URL/v2/control-planes/$CONTROL_PLANE_ID/config-stores/$DECK_CONFIG_STORE_ID/secrets/" \
     -H "Accept: application/json"\
     -H "Content-Type: application/json"\
     -H "Authorization: Bearer $DECK_KONNECT_TOKEN" \
     --json '{
       "key": "secret-key",
       "value": "my-secret-value"
     }'

      
        
      
    
Copied to clipboard!

Validate

You can validate that your secret was stored correctly by sending a GET request to the /secrets endpoint:

 curl -X GET "$KONNECT_CONTROL_PLANE_URL/v2/control-planes/$CONTROL_PLANE_ID/config-stores/$DECK_CONFIG_STORE_ID/secrets/" \
     -H "Accept: application/json"\
     -H "Content-Type: application/json"\
     -H "Authorization: Bearer $DECK_KONNECT_TOKEN"

Copied to clipboard!

If your secret was successfully stored in Konnect, the endpoint should return a 201 status code and your secret-key key in the output.

You can now reference your Konnect secret in configurations as {vault://mysecretvault/secret-key}.

Cleanup

Clean up Konnect environment

If you created a new control plane and want to conserve your free trial credits or avoid unnecessary charges, delete the new control plane used in this tutorial.

FAQs

Can I reference Konnect Config Store Vault secrets in kong.conf?

Next Steps

Review the Vaults entity