Get the Location Name

Some API calls or Taurus YAML configurations require referencing the specific Location Name.

For example, to configure your test to run on an AWS engine in the US East (Virginia) location, you need to know that the Location Name is us-east-1.

Note that each provider (AWS, Google, Azure) has a different name format for their locations. Consider the following examples:

AWS

US East (Virginia) = us-east-1

Google Cloud

US East (Virginia, Google) = us-east4-a

Microsoft Azure

Azure East US 2 (Virginia) = azure-east-us-2

To find a location name, try one of the following options:

• Check the Provider
• Check via Taurus
• Private Locations

Check the Provider

• List of AWS regions (locations) names

• List of Google Cloud regions (locations)

• List Microsoft Azure locations

You can cross-reference the lists with our list of locations you can generate load from.

Check via Taurus

If you have Taurus installed locally, a fast and easy method to see all available location names is to run the following from the command line:

bzt -locations

Note: For more information about the bzt -locations command, see Configuring Cloud Locations (gettaurus.org) in the Taurus documentation.

Private Locations

If you are using a Private Location instead of a public cloud location, you will need to find the Harbor ID of your Private Location, which doubles as the Location Name. It will use the following format:

harbor-<Harbor ID>

To find your Harbor ID, refer to Where can I find the Harbor ID and Ship ID?