ENTERPRISE

Check the new deployment

• Last updated: July 3, 2023

• Read time: 2 Minutes

Once you have installed and activated your new Burp Suite Enterprise Edition deployment, log in to the system and confirm that everything is working.

Because Burp Suite Enterprise Edition's data is held in the database rather than the app itself, the vast majority of your data should already be available. However, you may need to perform some additional steps to complete the migration.

As a minimum, you should:

• Check that all of your site, scan, and team data is present on the relevant tabs.
• Run at least one test scan to confirm that scans are completing successfully.
• Check whether your custom settings are displayed on the settings menu.

• Test any integrations you had set up on your old deployment, as these may need to be set up again depending on the configuration of your old deployment:

  • Integrating with CI/CD platforms.
  • Integrating with issue tracking platforms.
  • Integrating with other tools.
• Re-upload any scan extensions you intend to use from your new deployment. While extension configuration is carried across as part of the migration, the extension files themselves are not. For information on uploading scan extensions, see the Extensions in Burp Suite Enterprise Edition page.

If you cannot see some of your existing data or you encounter problems running scans on the new deployment, contact our Support team.

Decommission your old deployment

Now that you have deployed the Kubernetes version of Burp Suite Enterprise Edition and confirmed that your data has been migrated across, you are ready to decommission your old deployment.

How you should decommission largely depends on the underlying setup of your old deployment and any customization you may be running:

• For a standard AWS deployment you should be able to decommission by deleting the stack from the AWS console.
• For Azure, you can usually remove Burp Suite Enterprise Edition by deleting the entire resource group. If you encounter errors, you can try deleting individual items first and then deleting the resource group itself.

Next steps with Kubernetes

• For a guide to configuring and using auto-scaling scanning on a Kubernetes installation, see Managing auto-scaling scan resources.
• For a guide to updating Kubernetes deployments of Burp Suite Enterprise Edition, see Updating Burp Suite Enterprise Edition on Kubernetes.