Research Academy
My account Customers About Blog Careers Legal Contact Resellers
The Burp Suite User Forum was discontinued on the 1st November 2024.

Burp Suite User Forum

For support requests, go to the Support Center. To discuss with other Burp users, head to our Discord page.

SUPPORT CENTER DISCORD

No Load Balancer Created by AWS cloud Formation Teamplate

Sunil | Last updated: Jul 29, 2020 06:37PM UTC

Hi Team, I have followed the AWS deploy documentation(https://portswigger.net/burp/documentation/enterprise/getting-started/cloud/deploy-aws ) and it has successfully created all the CFT stack. As mentioned in steps in documentation, there should be ELB created but It is not creating any ELB as there is no mention of ELB in template. Please have a look at it. Thanks.

Ben, PortSwigger Agent | Last updated: Jul 30, 2020 09:37AM UTC

Hi, A load balancer should have been created under EC2 -> Load Balancers. Are you able to send an email to support@portswigger.net with screenshots of that screen both with and without filtering the stack name that you setup?

Qamber | Last updated: Oct 30, 2020 05:27PM UTC

Hi, I am also having this exact same. There is no load balancer being created, nor should there be according to the cloud formation template provided. Yet the instructions then refer to a load balancer that should have been created. It does not make sense. Exactly where in the template does it reference a load balancer?

Ben, PortSwigger Agent | Last updated: Nov 02, 2020 12:47PM UTC

Hi, We have separated out the creation of the various, infrastructure components into different .yaml files now. The Burp-suite-enterprise-edition.yaml > infrastructure.yaml > ec2-subnet.yaml configuration file should deal with the creation of the load balancer.

Encora | Last updated: Dec 01, 2020 11:23AM UTC

Hey, Facing the same issue. And also checked the ec2-subnet.yaml file which does not have any configuration related to Loadbalancer.

Ben, PortSwigger Agent | Last updated: Dec 02, 2020 09:17AM UTC

Hi, What does the ec2-subnet.yaml file that you are trying to use look like? There should be an entry for alb-ingress located within it. Can you confirm?

Encora | Last updated: Dec 02, 2020 11:15AM UTC

Content of ec2-subnet.yaml as follows, Parameters: CidrBlock: Type: String Description: The CIDR block used by the subnet AllowedPattern: ^([0-9]{1,3}\.){3}[0-9]{1,3}(\/([0-9]|[1-2][0-9]|3[0-2]))?$ ConstraintDescription: Please enter a valid CIDR IP range VpcId: Type: String Description: The ID of the VPC AvailabilityZone: Type: String Description: The availability zone of the subnet MapPublicIpOnLaunch: Type: String AllowedValues: [true, false] Default: false Description: Whether or not to map public IP addresses to instances in the subnet by default RouteTableId: Type: String Description: The ID of the Route Table that the Subnet should use EksClusterName: Type: String Description: The (optional) name of the EKS cluster that the subnet will host nodes for Default: "" Resources: Subnet: Type: AWS::EC2::Subnet Properties: AvailabilityZone: !Ref AvailabilityZone CidrBlock: !Ref CidrBlock MapPublicIpOnLaunch: !Ref MapPublicIpOnLaunch Tags: - Key: Name Value: !Sub ${AWS::StackName} - Key: !Sub kubernetes.io/cluster/${EksClusterName} Value: shared - Key: kubernetes.io/role/internal-elb Value: 1 - Key: kubernetes.io/role/alb-ingress Value: 1 VpcId: !Ref VpcId RouteTableAssociation: Type: AWS::EC2::SubnetRouteTableAssociation Properties: RouteTableId: !Ref RouteTableId SubnetId: !Ref Subnet Outputs: Id: Description: The ID of the subnet. Value: !Ref Subnet And It's taking it from the s3 template path mentioned in the infrastructure template

Ben, PortSwigger Agent | Last updated: Dec 03, 2020 11:27AM UTC

Hi, Is the access key that you are asked to generate in step 3 of the deployment guide (https://portswigger.net/burp/documentation/enterprise/getting-started/cloud/deploy-aws) being generated for the user that is also performing the deployment? At the moment, whoever creates the cluster needs to be the same user as the one running the deployment. We are in the process of changing this to remove the need to enter the access and secret keys at all.

Encora | Last updated: Dec 03, 2020 11:36AM UTC

Yes it's the same user only.

Michelle, PortSwigger Agent | Last updated: Dec 04, 2020 01:01PM UTC

Hi Thanks for confirming that, to help us investigate this further could you send us the following, please? You can email them to support@portswigger.net so you can share any logs with us directly. - Exact steps you took to get the deployment to the stage it is now - The CloudFormation template you used - Any relevant logs from CloudWatch

Encora | Last updated: Dec 07, 2020 07:28AM UTC

Hi Michelle, Provided all the details to the mentioned email.

Michelle, PortSwigger Agent | Last updated: Dec 07, 2020 11:04AM UTC

Thanks! We've received your email, we'll take a look and be in touch

Johan | Last updated: Dec 15, 2020 07:52AM UTC

Hi. I tried to deploy this stack yesterday, also ended up without a load balancer. Are there any updated cloudformation files yet? Best regards, Johan Andersson

Michelle, PortSwigger Agent | Last updated: Dec 15, 2020 03:21PM UTC

The links for the latest CloudFormation templates for 2020.11 can be found in the release notes here: https://portswigger.net/burp/releases If you're still having issues with the latest templates could you send us a copy of the CloudWatch logs relating to the deployment, please? If you can email them to support@portswigger.net we can take a closer look at what's happening.

Anna | Last updated: Jan 06, 2021 02:46AM UTC

Hi, I am also having this issue using the 2020.12 release. I deployed using the AWS CloudFormation templates and it seems like it was successful, but no load balancer. Any help would be appreciated. Thanks!

Michelle, PortSwigger Agent | Last updated: Jan 06, 2021 09:09AM UTC

It's possible that the ALB has not been created because the application has failed to start for some reason. Does connectivity to the database from your VPC look good? Which database are you using for your setup? There are also some deployment logs that can be found in Cloud Watch under a log-group named ${StackName}-ecs-deployment-logs, we'd be happy to take a closer look at these with you if you're happy to email them over to support@portswigger.net.

Thien | Last updated: Jun 07, 2021 10:14PM UTC

Hi, I am also running into this issue. I deployed the main stack using an user with admin access, but still saw no alb. I sent an email to support. Can you please take a look? The log message I got from the cloudwatch log group /aws/ecs/containerinsights/burp-enterprise-main-ecs-cluster/deployment is: Set up kubectl for AWS 2021-06-07T13:23:24.171-07:00 Added new context arn:aws:eks:us-east-1:1234567:cluster/burp-enterprise-main-eks-cluster to /root/.kube/config 2021-06-07T13:23:24.299-07:00 Running pre deployment 2021-06-07T13:23:37.399-07:00 error: You must be logged in to the server (Unauthorized)

Michelle, PortSwigger Agent | Last updated: Jun 08, 2021 07:45AM UTC

Hi We've received your mail so we'll take a look through it and be in touch soon via email.

Tulasinadh | Last updated: Aug 18, 2021 04:12AM UTC

I have been facing the same issue with 2021.6 version, is there any other version I can try to avoid this issue?

Michelle, PortSwigger Agent | Last updated: Aug 18, 2021 09:44AM UTC