Ambassador Edge Stack Licenses

Ambassador Edge Stack requires a valid Enterprise license or Community license to start up. The Community license allows you to use Ambassador Edge Stack for free with certain restrictions and the Enterprise license lifts these restrictions for further use of premium features.

For more details on the different licenses, please visit the editions page.

Enterprise License

To obtain an Enterprise license, you can reach out to our sales team for more information.

If you have any questions regarding your Enterprise license, or require an air gapped license, please to reach out to sales.

Applying a License

The process for applying a license is the same, regardless of which plan you choose:

• Enterprise License: If you have already purchased an Enterprise plan, you can follow the steps below to connect your clusters to Ambassador Cloud. Your Enterprise license will automatically apply to all clusters that you connect. If you believe you have an Enterprise license, but this is not reflected in Ambassador Cloud after connecting your clusters, please reach out to support.

• Lite License: If you wish to utilize a trial Lite license for your Edge Stack clusters, you can follow the steps below to connect your clusters to Ambassador Cloud, and the Lite license will be automatically applied.

1. Installing the cloud connect token

   You can follow the instructions on the quickstart guide to get signed into Ambassador Cloud and obtain a cloud connect token for your installation of Ambassador Edge Stack if you don't already have one. This will let Ambassador Edge Stack request and renew your license from Ambassador Cloud.

   The Cloud Connect Token is a Secret that you will install in your Kubernetes cluster and looks like this:

2. Install the Cloud Connect Token

   If you are using Helm to manage your $aesProductName$ installation, then you can refer to the quickstart guide to install $aesProductName$ and create your Cloud Connect Token, or the upgrade guide to update an existing installation of $aesProductName$ and create your Cloud Connect Token with Helm.

   
   You can also create the Cloud Connect Token manually using Kubectl If you want to. For new installations you can use:

   For existing installations you must check the value of an environment variable from your Deployment that determines the name of the Secret to look for the Cloud Connect token in. First set the name and namespace of your $aesProductName$ Deployment below, then run the following command to create your Cloud Connect token.