AWS CloudFormation template changesIf you are looking to deploy Burp Suite Enterprise Edition within your AWS cloud infrastructure, we have created a number of improvements to the existing process. These are designed to provide simplification, as well as additional options for configuration to meet your specific deployment requirements:
- AWS infrastructure is now created via a series of nested CloudFormation templates, making it easier to instantiate a subset of the infrastructure while using existing resources for the remainder.
- You are no longer required to provide an AWS access key ID and secret key in the AWS CloudFormation template. Instead you can use Role Based Access Control (RBAC) to control permissions.
- You can now add an optional PostgreSQL database to the AWS CloudFormation template to set it up at the same time.
- Credentials provided in the AWS CloudFormation template are now obfuscated in nested templates.
- Application logging is now enabled at the beginning of the deployment phase on AWS. This means that database migration errors are now captured in CloudWatch for improved monitoring and support.
Azure Resource Manager improvementsAzure Resource Manager (ARM) templates are the Microsoft Azure version of AWS CloudFormation templates. They enable you to quickly spin up infrastructure with set configurations. In this way, you can more efficiently set up the infrastructure to deploy Burp Suite Enterprise Edition using an ARM template.
While a template has previously been available for those on Azure cloud, we now provide nested templates to facilitate separate deployment of infrastructure and application. This is helpful if you want to instantiate a subset of the infrastructure while using existing resources for the remainder.