Skip to main content

​
Introduction

ZEDEDA Store is a feature of Edge Infrastructure Services that provides an interface to third-party secret and artifact storage solutions, such as HashiCorp Vault. It gives edge applications automated, secure access to licenses, tokens, certificates, passwords, and other sensitive data stored in your own storage provider. ZEDEDA Store does not store your data directly. It stores only metadata about your resources. Your underlying storage provider (for example, HashiCorp Vault) is responsible for the actual storage, encryption, and decryption of the data. In ZEDEDA Store, data items are called resources. Each resource is classified as either a secret or an artifact, determined by the type of store that contains it:
  • Secrets are stored in a secret store and cannot be read in plain text after creation.
  • Artifacts are stored in an artifact store and can be read in plain text.
You manage ZEDEDA Store resources exclusively through ZCLI. You reference resources in edge applications through the custom configuration feature in Edge Infrastructure Services.

​
Prerequisites

  • You have the SysManager or SysAdmin role in your enterprise. See Manage Roles.
  • ZCLI installed and authenticated. See the ZCLI documentation for setup instructions.
  • A ZEDEDA Store datastore created in your enterprise. See the zcli datastore create command for instructions.

​
How Resources Are Used

To make a resource available to an edge application, reference it in the application’s custom configuration using one of the following variable formats:
  • Reference a specific resource by name: $datastore.STORE_NAME.RESOURCE_NAME
  • Reference the next available resource (for resource pools): $datastore.STORE_NAME.#
Each resource can only be used by one application instance at a time. When an application instance is deployed, it claims one resource. If all resources in a store are claimed, new application instances that depend on that store fail to start. Resources can be configured with an expiry date. An expired resource does not affect a running application instance, but new instances cannot claim an expired resource and will fail to start. Expiry dates do not reset after a resource is released.

​
Create a Resource

The resource type (secret or artifact) is determined by the store type specified when the store was created.

​
View a Resource

To view a specific resource in a store:
To view all resources in a store by type:

​
Update a Resource

​
Delete a Resource

Use -f to skip the confirmation prompt.

​
Examples

​
Secret management

This example creates a secret store, adds a secret to it, and references the secret in an edge application’s custom configuration.
  1. Create a secret store:
  2. Create a secret in the store. The resource automatically becomes a secret because the store is a secret store:
  3. Reference the secret in an edge application’s custom configuration. In the Configuration Template field, enter:

​
License pool management

This example creates an artifact store, uploads multiple license files to it, and configures an edge application to claim one license on deployment.
  1. Create an artifact store:
  2. Add license artifacts to the store. The value is the Base64-encoded content of the license file:
  3. Reference the next available license in the edge application’s custom configuration. The # character references the next unclaimed resource:
    When each application instance is deployed, it claims one of the available licenses. If all licenses are claimed, new instances fail to start.

​
Next Steps

Create a Datastore

Set up a new datastore for your enterprise.

Manage a Datastore

View, update, or delete an existing datastore.