Document updated on Feb 2, 2020
KrakenD Enterprise is delivered in several formats, including Docker, Linux packages (deb, rpm) and generic installation options.
If you are already familiar with Docker, the easiest way to get started is by pulling our KrakenD image from Azure or AWS. As the repositories are private, you need to provide the credentials we sent.
To pull our Docker image from AWS, you need to:
The AWS credentials that you received need to be stored under ~/.aws/credentials
. The file might looks like this (fake credentials below):
[default]
aws_access_key_id = AKIAQYWA47SCCDSQLWAN
aws_secret_access_key = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If you already have credentials, add another named profile.
Now you are ready to login into ECR and download the content. Depending on which version of the AWS CLI you have installed you might need one of these two commands:
AWS CLI v2:
$aws ecr get-login-password --region us-east-1 | \
docker login --username AWS --password-stdin \
052351007912.dkr.ecr.us-east-1.amazonaws.com
AWS CLI v1:
$$(aws ecr get-login --region us-east-1 --no-include-email)
$docker pull krakend/krakend-ee:1.3.0
If you have a corporate Docker registry you might want to push the image locally:
$docker tag krakend/krakend-ee:1.3.0 youregistry.com/krakend-ee:1.3.0
docker push youregistry.com/krakend-ee:1.3.0
To pull pur Docker image from Azure, you need to:
az login
az acr login --name krakend
docker pull krakend.azurecr.io/krakend-ee:1.3.0
After these commands you will have in your local computer the krakend enterprise container. You can push it to your own ACR or use it locally.
The installation process requires going through these steps:
The first step to all Linux flavours is to download the certicate chain from our repository:
$aws s3 cp s3://download.enterprise.krakend.io/krakend-ca-chain.pem /etc/krakend/krakend-ca-chain.pem
AWS-CLI needed. The credentials to access this bucket are provided in the welcoming email.
Create a config file in /etc/apt/apt.conf.d/99krakend
with this content:
Acquire::https::repo.enterprise.krakend.io {
CaInfo "/etc/krakend/krakend-ca-chain.pem";
SslCert "/etc/krakend/LICENSE";
SslKey "/etc/krakend/LICENSE.key";
};
Make sure the three files referenced above are placed in /etc/krakend
.
Run the following commands:
$apt-key adv --keyserver keyserver.ubuntu.com --recv 5DE6FD698AD6FDD2
echo "deb https://repo.enterprise.krakend.io/apt stable main" | tee /etc/apt/sources.list.d/krakend-ee.list
apt-get update
apt-get install -y krakend-ee
Now the krakend
command is available in the system.
KrakenD should run on old systems too, at least from Debian 8 and Ubuntu 16.x
The RPM file can be downloaded from here:
aws s3 cp s3://download.enterprise.krakend.io/krakend-ee-repo-1.0-2.x86_64.rpm .
Make sure the LICENSE files LICENSE
, and LICENSE.key
are placed in /etc/krakend
.
Then install and start the latest version of KrakenD with:
$rpm -Uvh krakend-ee-repo-1.0-2.x86_64.rpm
yum install krakend-ee
systemctl start krakend-ee
tar.gz
)You can also download a tar.gz
and decompress it anywhere. Instructions to check the SHA and PGP signature here
$aws s3 cp s3://download.enterprise.krakend.io/bin/krakend-ee_1.2.1_amd64.tar.gz .
aws s3 cp s3://download.enterprise.krakend.io/bin/krakend-ee_1.2.1_amd64.tar.gz.sha256 .
aws s3 cp s3://download.enterprise.krakend.io/bin/krakend-ee_1.2.1_amd64.tar.gz.asc .
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.
We use cookies to understand how you use our site and to improve your overall experience. By continuing to use our site, you accept our Privacy Policy. More information