Automatic Secrets Migration Into Akeyless
Deeper DiveFor more in-depth information, check out our detailed documentation on the following topics:
Automatic Secrets Migration
Need any help?If something in this tutorial isn't working as expected, feel free to contact our support team via Slack.
Below is a text-only guide for users based on the above video
Why Migrate Your Secrets Into Akeyless?
There are several key reasons to migrate secrets directly into Akeyless.
Firstly, migrating secrets from fragmented platforms into Akeyless provides a single pane of glass for enterprise-wide visibility and governance of your secrets, streamlining compliance and eliminating the complexity of managing siloed access policies across multiple clouds and tools.
Moreover, with Akeyless’s patented Distributed Fragments Cryptography with Zero-Knowledge encryption security is significantly upgraded.
Also, centralizing secrets gives developers and automated workloads a standardized workflow to retrieve credentials regardless of where their underlying applications are hosted.
Finally, transitioning to a unified SaaS model drastically cuts the licensing fees and operational overhead associated with maintaining legacy self-hosted vault infrastructure.
TipBefore getting started, ensure that the platform where the secrets are stored is accessible over the network from the Akeyless Gateway server. Depending on the deployment, it might require adding an Akeyless Gateway IP address to a security group or a firewall.
Migrating AWS Secrets into Akeyless
Notes
- Akeyless currently only has static secret migration capabilities.
- If there are existing secrets under the Target location, their values will be replaced in case of conflict. This can happen if you leave the "Target location" field blank and a new secret has the same name as the existing one.
Prerequisites
To import secrets from AWS Secrets Manager, you need to provide access credentials of a user with sufficient permissions to get all secrets. The required configuration includes:
- AWS Access Key ID
- AWS Secret Access Key
- AWS region
Migration
In the console, click on Discovery & Migration -> Choose your Gateway -> New.
Choose AWS Secrets Manager and click "Next".
Give it a name and location where you want the secrets to be stored inside your Akeyless account.
Add your Region and AWS Credentials and click "Next".
Once it's created, go to the three dots on the top-right and click Sync Now.
Within a short amount of time all of your static secrets from AWS Secrets Manager will show up in the folder you chose.
Migrating Kubernetes Secrets into Akeyless
In the Discovery & Migration section, click the "New" button.
Give it a name and location where you want the secrets to be stored inside your Akeyless account.
Next, add your Kubernetes credentials. You can use any of these options: Token, username & password, or Cluster CA Certificate. Once done, click "Finish".
Once it's created, go to the three dots on the top-right and click Sync Now.
Within a short amount of time all of your static secrets from your Kubernetes cluster will show up in the folder you chose.
Updated 5 days ago