Introduction
Load tests can be performed using Amazon Virtual Private Cloud (VPC). A logically isolated portion of the AWS cloud is made available by the Amazon Virtual Private Cloud (Amazon VPC), allowing you to launch AWS resources in a virtual network that you specify. Your virtual networking environment is completely in your control, and this includes choosing your IP address range, setting up subnets, configuring route tables, and setting up network gateways. The network setup for your Amazon Virtual Private Cloud can be simply customized. You could, for instance, choose a private-facing subnet for your backend systems like databases or application servers and a public-facing subnet for web servers that may access the internet.
The prerequisites for starting the LoadUI agent in your Amazon VPC subnet are a VPC with an automatically assigned public subnet and public IPs and on the port, the agent will use, access to the subnet instances. The agents typically use port 1991.
Creating VPC
Step 1: Select VPC after logging into the Amazon Web Services Console.

Step 2: Click Start VPC Wizard on the VPC Dashboard page.

Step 3: Check that the VPC with a Single Public Subnet checkbox is selected, then click it.

Step 4: Define your VPC and subnet names and configure IP ranges. Simply provide the VPC name and Subnet name and leave the other fields' default values if you're unsure what to do.
A VPC with a subnet that can be utilised for load tests will be created by Amazon.
Verifying your VPC
Step 1: Go to the Subnets page first. The Auto-assign Public IP setting should be set to Yes. If not, go to Subnet Actions > Modify Auto-Assign Public IP and turn on automatic IP assignment.

Step 2: Change to Internet Gateways and confirm that your VPC is connected to a gateway.

Step 3: Go to the Route Tables page and check to see if your VPC is mentioned there. Switch to the Routes tab after selecting it.

Running Load Tests in a VPC
Running load tests on Amazon EC2 is comparable to running them on a VPC. The main distinction is that you choose the network and subnet you constructed rather than the EC2 Classic network.
