Share this page

# Cloud accounts

This section describes how to manage your cloud accounts in LoadRunner Enterprise. You can use a cloud account with a supported cloud provider.

Note: When upgrading from an earlier version of LoadRunner Enterprise, you need to delete your migrated cloud accounts and recreate them in the current version.

In this topic:

## Cloud accounts overview

After establishing a cloud provider account, you must also establish a cloud account in LoadRunner Enterprise. When defining a cloud account in LoadRunner Enterprise, you enter your cloud provider credentials and associate projects to the account. For details, see Add a cloud account.

Tip: See the LoadRunner Enterprise video gallery for a video on how to run tests on load generators that are dynamically provisioned on AWS.

Back to top

## Prerequisites

Note the following guidelines before adding a cloud account to LoadRunner Enterprise:

- Cloud provider account. To add a cloud account to LoadRunner Enterprise, you must have an existing cloud account with a supported cloud provider. LoadRunner Enterprise currently supports Amazon Web Services (AWS EC2) and Microsoft Azure Cloud accounts.

- Account information. After you have your cloud account ready, you need to record the following information from your cloud account:

  AWS EC2

  UI Element | Description
  --- | ---
  Account Access Key | Allows LoadRunner Enterprise to connect to your cloud account.
  Account Secret Key | Serves as the password for the access key used to connect to your cloud account.
  Account Number | The AWS EC2 account number. This number is used to access custom images from the cloud account. Adding an incorrect account number results in the inability to access custom images related to this account.

  Note for AWS EC2 accounts and AWS GovCloud (US) Regions:

  - AWS Account Credentials that require Multi-Factor Authentication (MFA) are not supported.

  - The user linked to the cloud account should have full EC2 access (`AmazonEC2FullAccess`) or have permissions for all the following AWS actions: AssociateAddress, CreateTags, DescribeAddresses, DescribeImages, DescribeInstances, DescribeInstanceStatus, DescribeInstanceTypeOfferings, DescribeKeyPairs, DescribeRegions, DescribeSecurityGroups, DescribeSubnets, DisassociateAddress, GetPasswordData, RunInstances, TerminateInstances

  Microsoft Azure Cloud

  UI Element | Description | Comments
  --- | --- | ---
  Tenant ID | The ID of the Azure Active Directory in which you created the application. | This is available in the Azure account.
  Subscription ID | A GUID that uniquely identifies your subscription to use Azure services.
  Client ID | The application Client ID identifier that is generated from the Azure Active Directory portal. | Requires the creation of an application, and the role for your application must be Contributor or Owner. For more details on application and service principal objects in Azure Active Directory, see the Microsoft documentation.
  Client Secret | The secret key that is used when communicating with Azure Active Directory.

  Note: The LoadRunner Enterprise Backend Service account profile must be configured to use a proxy.

  1. Log on to the LoadRunner Enterprise machine with a LoadRunner Enterprise Backend Service account and configure it with the corporate proxy in order for it to have Internet access to the cloud.

  2. Restart the LoadRunner Enterprise Backend Service.

  3. Restart IIS.

Back to top

## Add a cloud account

This task describes how to add a cloud account to LoadRunner Enterprise.

1. Make sure you follow the prerequisites for adding a cloud account.

   For details, see Prerequisites.

2. Add the cloud account to LoadRunner Enterprise

   1. In LoadRunner Enterprise Administration, select Configuration > Cloud.

   2. In the Accounts tab, click Add Cloud Account , and enter a name and description (optional) for the cloud account.

   3. Select the provider of the cloud account by clicking LG provisioning on AWS or LG provisioning on Microsoft Azure Cloud.

3. Enter your cloud account information:

   - For AWS EC2, enter the account access key, secret key, account number, and select the account category (Standard Cloud or Government Cloud US).
   - For Microsoft Azure Cloud, enter the Client ID, Tenant ID, Client Secret, Subscription ID, and select the account category (Global Cloud or Government Cloud US).

4. Click Save to add the cloud account to LoadRunner Enterprise. The cloud account is added to the grid.

   Note: The account creation process may take several minutes to complete.

   You can now create templates and provision hosts from this cloud account.

   You can see details of the cloud account, including projects that have been assigned to the account and the number of currently provisioned hosts from this account in the Main Details tab.

5. Assign projects to your cloud account

   For details, see Link projects to your cloud account.

6. View cloud account events

   For details, see View cloud account event logs.

Back to top

## Link projects to your cloud account

Every project that needs to provision hosts from a cloud account created in LoadRunner Enterprise must be linked to that account.

To link projects to a cloud account created in LoadRunner Enterprise:

1. In LoadRunner Enterprise Administration, select Configuration > Cloud.

2. In the Accounts grid, select the cloud account you want to link.

3. In the Main Details tab, click Assign Projects , and select the projects you want to link to the cloud account from the grid.

4. Click Assign. This links the selected projects to the cloud account.

All linked projects may now provision cloud hosts from the selected cloud account.

Back to top

## View cloud account event logs

To display the events that occurred in creating the cloud account:

1. In LoadRunner Enterprise Administration, select Configuration > Cloud.

2. In the Accounts grid, select the cloud account you want to view.

3. Select the Event Logs tab to see the events that occurred and the severity of each event.

   Event Type | An indication of the event's severity. From most to least severe: error, warning, or info.
   Created on Date | The date and time the event was logged.
   Project name | The project in which the event occurred.
   Action | The category of action where the event occurred. For example, Create Server.
   Name | The name of the process.
   Description | A description of the event.
   Owner | The user, or automated system process responsible for the event.

Back to top

## Cloud network settings

If you need to configure cloud network settings for communicating from LoadRunner Enterprise to your cloud provider and for communicating with your cloud-based load generators, click Cloud Network Settings, and follow the instructions in Configure cloud network settings.

Back to top

## Export cloud account details to Excel

This task describes how to export information displayed in the cloud account grid to an Excel file.

1. In LoadRunner Enterprise Administration, select Configuration > Cloud.

2. Select the Accounts tab, and then click Export to Excel file . Data from the grid is saved to an Excel file and downloaded to the Downloads folder of the client user.

Back to top

## Delete a cloud account

This task describes how to delete a cloud account.

1. In LoadRunner Enterprise Administration, select Configuration > Cloud.

2. Select a cloud account in the grid, and click Delete . The cloud account and all host templates using the cloud account are deleted.

Note: You cannot delete a cloud account if there are cloud hosts that are currently provisioned by that account.

Back to top

See also:

- Host templates
- Create custom image for cloud hosts

https://admhelp.microfocus.com LoadRunner Enterprise 8942
Tips to improve your search results... LoadRunner Enterprise Help Center LoadRunner Enterprise Help LR Enterprise Help 2023-2023 R1 All View Local Help Center View Online Help Center back Go back in browser history forward Go forward in browser history Remove search highlights next topic Go to next topic previous topic Go to previous topic Print the current topic Version: