Ask or search…


Learn how to use secrets in your custom pipeline configuration
When creating custom pipelines you may have settings that you do not wish to store in plain text or share with other users of the pipeline. A good way to prevent this is by using secrets within Calyptia Core.
Secrets within Calyptia Core are stored per pipeline and referenced in configuration paths by using brackets. For example a secret that looks like the following:
Can be referenced in a configuration as {{ secrets.key }}.

Creating a secret

Within the Pipeline Overview page you can navigate to the Advanced Settings page to modify and add secrets.
In the following example we create the secret file from above in the user interface:

Updating a secret with a new value

You can update a secret by select update within the Advanced Settings page.
Secrets can be edited only with a new value, and previous values are neither displayed nor stored.

Secret storage

Calyptia Core stores all the secrets encrypted using RSA Public key cryptography.
Each deployment of Calyptia Core has its unique key pair (private, public) generated when the new instance registers. Calyptia Cloud does not store this private key on any form.
When a new instance of Calyptia Core gets registered, a new unique key pair is generated and the private key is stored in your operating environment. When a pipeline is deployed or updated and it requires a secret, that secret is fetched encrypted from Calyptia Core and decrypted by the keys within your environment using the in-memory private RSA key.
The following diagrams illustrate the secret generation and usage:

Calyptia CLI

To reference secrets in the Calyptia CLI you need to create a new file in your local environment and then add them within your configuration. For example, in the pipeline-es.conf file, we do not want to specify HTTP_Passwd in plain text. Instead we will use a secret with a variable es_http_passwd. This variable is defined in the following secrets.env file:
Name forward
Port 24284
Name es
Match *
Host hostname.us-east-2.es.amazonaws.com
HTTP_User es
HTTP_Passwd {{secrets.es_http_passwd}}
Port 443
TLS on
Now you need to define them in another file:

Creating a pipeline with a secret

When creating a pipeline we will need to ensure that we specify --secrets-file so that the pipeline configuration will be able to use them. The command for that is:
calyptia create pipeline --aggregator <AGGREGATOR ID> --config-file pipeline-es.conf --secrets-file secrets.env

Update a Secret's Value

If you need to update a secret, you can update the secret by first listing all secrets, and then updating the secret with new values.
List all the secrets from a pipeline:
$> calyptia get pipeline_secrets --pipeline <PIPELINE ID> --show-ids
73a941d6-e658-4f12-a175-97d9063c466f es_http_passwd 5 minutes
You can take the secret ID and use it to update its value:
calyptia update pipeline_secret <SECRET ID> <NEW VALUE>