Migrating from a legacy cloud deployment
Last updated: September 9, 2022
Read time: 2 Minutes
Previously, Burp Suite Enterprise Edition was delivered for the cloud as a full infrastructure stack for AWS EKS and Azure AKS. These deployments are referred to as "legacy cloud deployments" in this documentation. From the 2022.3 release of Burp Suite Enterprise Edition, the application is provided as a Helm chart, which you can deploy on any Kubernetes cluster that meets a simple set of prerequisites.
To safely migrate a legacy cloud deployment of Burp Suite Enterprise Edition to a Kubernetes deployment:
Step 1: Set up a suitable Kubernetes cluster.
Step 2: Install the application.
Step 3: Configuring Transport Layer Security.
Step 5: Configure the database.
Step 6: Activate your license.
Step 7: Check the new deployment.
Initially, we only support Kubernetes migration from a cloud deployment built using our legacy templates.
Using a Helm chart offers several benefits over the older deployment methods:
- It makes it much easier for users who already have a suitable Kubernetes cluster to deploy Burp Suite Enterprise Edition into their existing infrastructure.
- It gives you the option to have your scanning infrastructure scale automatically, potentially helping you to make cost savings.
- It streamlines the install process, which is now simply a case of downloading a Helm chart and running an
- It makes it easier for you to customize configuration in your Kubernetes cluster without affecting Burp Suite Enterprise Edition's running.
- It enables us to introduce new features without having to factor in the underlying compute platform.
Although legacy cloud deployments will continue to work for the immediate future, we strongly recommend that you migrate to the new infrastructure when possible. Future versions of Burp Suite Enterprise Edition will not support legacy cloud deployments.
First step - Set up a Kubernetes cluster
Was this article helpful?
An error occurred, please try again.