Skip to main content
Already keeping secrets somewhere else? Move them into Enkryptify in two steps. Pull your environment into a local dotenv file, then upload it with the CLI. 
ek import                  # imports ./.env by default
ek import .env.production  # or pass any dotenv file
The file path is optional. With no argument ek import reads .env in the current directory, or you can pass any path such as .env.production. It then parses the file and uploads the secrets into the workspace, project and environment you choose. See the command reference for all options.

​
Choose your source

.env file

Upload an existing local .env file from the CLI or the dashboard.

Vercel

Pull project environment variables with the Vercel CLI.

1Password

Resolve secret references into a .env with the 1Password CLI.

AWS Secrets Manager

Export a secret into a .env with the AWS CLI.

​
Before you start

  • Install the Enkryptify CLI and run ek login.
  • Keep the generated .env file local and do not commit it to git.
  • After a successful import the CLI offers to delete the source file, so no plaintext copy is left behind.
Whatever the source, the goal is a plain .env file with KEY=value lines. Once you have that, ek import handles the rest.