Last update: May 13, 2022
To run the Enterprise software with all its capabilities you must provide a valid license. When you get a license from sales, its placement and format must comply with what the binary expects.
When the license file is incorrect, KrakenD warns you about it but the server will start anyway.
The message you will see when the server starts with an invalid or missing license file is:
To start KrakenD Enterprise without seeing the message above, make sure that:
LICENSEfile is a plain text file with no extension
-----END CERTIFICATE-----, and you have not deleted any dash or character accidentally, neither you have deleted the line breaks.
You can store your LICENSE in any secret manager of your choice if you want to. However, ensure that the line breaks are respected when retrieving from the secret manager.
One of the particularities of AWS Secrets Manager is that it might have problems when storing multiline contents. Therefore, when working with AWS in plain text, we recommend keeping the
LICENSE content in
You can create an AWS secret with your license with this command:
Notice that we have added the license’s expiration date to the secret name. A practice like this will help you quickly realize for how long the license/secret is valid.
You can later retrieve the license file in your pipeline file with:
Note: Depending on your computer’s operative system, the decoding of base64 might be
base64 -D instead of
Any running processes will shut down when the KrakenD Enterprise license expires.
But you can start the Enterprise binary again with the license expired or missing, and it will run in the open-source mode without any of the Enterprise functionalities.
When your license renewal comes, you need to replace the
/etc/krakend/LICENSE with the new content in each of your servers running KrakenD and restart KrakenD. That’s all!
The documentation is only a piece of the help you can get! Whether you are looking for Open Source or Enterprise support, see more support channels that can help you.