Self-provisioning provisioners

furyctl provisioner documentation

2 minute read

furyctl can deploy infrastructure by itself. This is what we name self-provisioning feature.

It enables to deploy two different kinds of infrastructures: bootstrap and cluster.


Bootstrap provisioner deploys infrastructure components required by any Fury Kubernetes Cluster. All SIGHUP and Fury clusters are deployed on private infrastructure, meaning you need to solve the connectivity problem before deploying a Fury cluster. In some environments, this is already solved using IPSEC, SSH tunnel, or VPN solutions. In case you need to address this connectivity issue, use the right furyctl bootstrap provisioner.

In addition to that, some cloud providers require special networking configuration to work properly and to enable some cloud providers integration: internal and external load balancers, autoscaling features, internet connection using NAT…

Available provisioner


Enterprise provisioner. Contact us

This provisioner creates the required network components enabling the deployment of a Fury EKS cluster. It includes the creation and configuration of a VPC (Virtual Private Cloud) and a VPN Server (using openvpn and furyagent).

Click here to continue reading details about this provisioner


Available provisioner


Community provisioner. Free of charge.

EKS provisioner uses one of the SIGHUP cloud installers: EKS cloud installer This enables to manage in a simpler way the deployment and management of an EKS cluster. Forget about running terraform commands. You can do the same with the furyctl binary without worrying about installing any other tool.

AWS Bootstrap

furyctl aws bootstrap provisioner

EKS Cluster

furyctl eks cluster provisioner