Some API calls or Taurus YAML configurations require referencing the specific Location Name of a region.
Note: For the purpose of this article, "location" and "region" are synonymous.)
For example, if your test is configured to run on an AWS engine in the US East (Virginia) region, you may need to know that the Location Name would be us-east-1.
Note that each provider (AWS, Google, Azure) has a different name format for their regions. Consider the following examples:
US East (Virginia) = us-east-1
US East (Virginia, Google) = us-east4-a
Azure East US 2 (Virginia) = azure-east-us-2
To find a location name, try one of the following options:
You can cross-reference the lists with our list of locations you can generate load from.
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:
Note: For more information about the bzt -locations command, see Configuring Cloud Locations (gettaurus.org) in the Taurus documentation.
If you are using an On-Premise Location (OPL) instead of a public cloud location, you will need to find the Harbor ID of your OPL, which doubles as the Location Name. It will use the following format:
To find your Harbor ID, refer to Where can I find the Harbor ID and Ship ID?