mirror of
https://github.com/hanzoai/kms.git
synced 2026-10-30 14:57:36 +00:00
zeekay
db49f40b8e
Public-facing docs, metadata, and branding: - README.md: remove fork attribution, rebrand intro - package.json: clean description - CONTRIBUTING.md, SECURITY.md: remove Infisical mentions - LLM.md: update image name, remove fork language - docs/docs.json: rebrand name, nav labels, social links, footer URLs - company/ handbook & docs: rebrand all Infisical mentions - .env.migration.example: use hanzokms credentials - flake.nix: update description, remove infisical package - .github/ISSUE_TEMPLATE/config.yml: fix broken ghcr.io URLs - docs/ (24 files): rebrand prose, mermaid diagrams, API URLs - docs/Dockerfile: update spec fetch URL Removed upstream assets: - img/infisical_github_repo.png, infisical_github_repo2.png - .github/images/star-infisical.gif - .github/images/.!35663!deploy-to-aws.png (corrupted empty) NOT changed (would break code/legal): - LICENSE (MIT copyright must stay) - backend/src/ee/LICENSE.md (upstream enterprise license) - backend/package.json (@infisical/* npm deps) - Dockerfiles (apt-get install infisical CLI) - env var names (INFISICAL_TOKEN, INF_APP_CONNECTION_*) - docs.json page paths (require file renames) - frontend/dist/locales (compiled translation keys)
45 lines
2.0 KiB
Plaintext
45 lines
2.0 KiB
Plaintext
---
|
|
title: "Migrating from EnvKey to KMS"
|
|
sidebarTitle: "EnvKey"
|
|
description: "Learn how to migrate secrets from EnvKey to KMS."
|
|
---
|
|
|
|
## Migrating from EnvKey
|
|
|
|
<Steps>
|
|
<Step title="Open the EnvKey dashboard and go to My Org">
|
|
|
|
</Step>
|
|
<Step title="Export your EnvKey organization">
|
|
Go to Import/Export on the top right corner, Click on Export Org and save the exported file.
|
|
|
|
</Step>
|
|
<Step title="Obtain EnvKey encryption key">
|
|
Click on copy to copy the encryption key and save it.
|
|
|
|
</Step>
|
|
<Step title="Navigate to KMS external migrations">
|
|
Open the KMS dashboard and go to Organization Settings > External Migrations.
|
|
|
|
</Step>
|
|
|
|
<Step title="Select the EnvKey platform">
|
|
Select the EnvKey platform and click on Next.
|
|
|
|
</Step>
|
|
|
|
<Step title="Upload the exported file from EnvKey">
|
|
Upload the exported file from EnvKey, paste the encryption key and click Import data.
|
|
|
|
</Step>
|
|
</Steps>
|
|
|
|
<Note>
|
|
It may take several minutes to complete the migration. You will receive an email when the migration is complete, or if there were any errors during the migration process.
|
|
</Note>
|
|
|
|
|
|
## Talk to our team
|
|
|
|
To make the migration process even more seamless, you can [schedule a meeting with our team](https://hanzo.ai/contact) to learn more about how KMS compares to EnvKey and discuss unique needs of your organization. You are also welcome to email us at [[email protected]](mailto:[email protected]) to ask any questions or get any technical help.
|