Research Academy
My account Customers About Blog Careers Legal Contact Resellers

Burp Suite User Forum

Create new post

Load balancer not automatically created after stack completion

Abbas | Last updated: Jan 26, 2021 01:35PM UTC

Running into issues when deploying Burp Enterprise into AWS, used this article as a guide: https://portswigger.net/burp/documentation/enterprise/getting-started/cloud/deploy-aws and used the following cloud formation templates: https://bsee-cloud-trial.s3-eu-west-1.amazonaws.com/2020.12-5930/burp-suite-enterprise-edition.yaml https://bsee-cloud-trial.s3-eu-west-1.amazonaws.com/2020.12-5930/iam-for-burp-suite-enterprise-edition.yaml On the final step of the guide, it mentions a load balancer will be automatically created once the stack has completed, but it does not. Therefore unable able to retrieve the DNS name to launch the application. The access key generated was initiated from the same user performing the deployment. Seems this is a common problem, what is the solution please?

Liam, PortSwigger Agent | Last updated: Jan 27, 2021 10:58AM UTC

The load balancer should be created by the Kubernetes Ingress Controller so requires the application to be started before it appears. It is possible that something has gone wrong during the deployment, most likely connecting to the database. Would it be possible to provide us with the Cloud Watch logs?

Richard | Last updated: Feb 18, 2021 12:26PM UTC

I have the same issue. I am using free trial AWS 1/ If I go to Elastic Kubernetes Service (Amazon EKS) I see cluster below so I assume that Kubernetes Ingress Controller application is started. Cluster : burpsuiteenterprisemain-Deployment-P1MOWVY8BAOS-bootstrap-cluster Cluster ARN arn:aws:ecs:eu-west-2:068617432556:cluster/burpsuiteenterprisemain-Deployment-P1MOWVY8BAOS-bootstrap-cluster Status ACTIVE Registered container instances 0 Pending tasks count 0 Fargate, 0 EC2 Running tasks count 0 Fargate, 0 EC2 Active service count 0 Fargate, 0 EC2 Draining service count 0 Fargate, 0 EC2 2/ Checked Cloud Watch logs nothing here 3/ I see we have option to create load balancer should I try this 4/ how d o I check connection to data base from deployment

Richard | Last updated: Feb 19, 2021 11:38AM UTC

I tried the deployment without selecting an external database so we should use the default database prior to using external database and I had the same issue. So I’m not sure this is a database problem

Liam, PortSwigger Agent | Last updated: Feb 19, 2021 11:52AM UTC

Did you see anything in your Cloudwatch logs during the second deployment? We have had a similar issue when the templates have been run by a low priv account. The current templates should be run by a user with admin privileges. The deployment needs to be done by the same user who created the cluster. Can you ensure this is the case? We’re fixing this now so we’ll use the permissions created in the IAM roles to run the deployment.

You must be an existing, logged-in customer to reply to a thread. Please email us for additional support.