Skip to main content

Security & Data

Select a region

Each Verdictan resource, such as an agent or a gateway, belongs to one region. The Console and the API of that region manage it. An agent that you create in eu-west does not show when you query us-east.

Two settings are separate:

  • The management region decides where Verdictan stores and manages your resources. Your CLI profile and Console URL select it.
  • The traffic location decides where model requests go. Your agent hostname and your provider targets decide it.

Examine your CLI setup​

Sign in first. Then run:

verdictan regions current
verdictan regions list --enabled

regions current shows the resolved region, the profile, the API address, and the setting that supplied the region. regions list --enabled shows the regions that you can use.

The profile and the API address must match the organization that you work with. If regions current reports no region configured, set a default for the profile.

Set a default for a profile​

verdictan configure set region eu-west --profile default
verdictan regions current --profile default

Use an enabled region from regions list. The CLI saves it as profiles.<profile>.default_region in ~/.verdictan/config.yaml. verdictan regions use <region> does the same thing, and regions switch is an alias for use.

A new default does not move resources, and it does not change where a running gateway sends traffic.

Override one command​

An API command that has a --region option uses it for that call only:

verdictan events tail --region eu-west --since 10m --json

API commands select the region in this order:

  1. The --region option of the command
  2. The default region of the profile
  3. The legacy top-level default_region value in the config file

The top-level verdictan --region option works differently. It sets VERDICTAN_REGION for the process, which the local gateway and regions current read. API commands do not use it as a fallback.

The API address has its own order: --api-url, then VERDICTAN_API_URL, then api_url in the config file, then https://api.verdictan.com. The API overview lists the regional addresses.

Use the Console​

Sign in to the Console of your organization's region: the EU Console or the US Console. The Console has no region selector. A CLI profile change does not make a resource from a different region show in the Console.

Control where model traffic goes​

Verdictan gives each published agent a hostname. Copy it from the agent page. Do not build it from the agent or organization name.

HostnameTraffic stays in
*.ai.eu.verdictan.comThe EU
*.ai.us.verdictan.comThe US
*.ai.global.verdictan.comAn eligible published region, subject to organization and region rules

The first label of the hostname is a 12-character publication key that the API assigns.

The hostname sets the location of the managed endpoint. The provider targets in your configuration set which upstream providers the gateway can call. When traffic must stay in one location, examine both. If the necessary region is not available, Verdictan does not send the traffic to a different region.

verdictan.com, eu.verdictan.com, and us.verdictan.com are websites. They do not accept model requests.

Troubleshooting​

ProblemWhat to check
An agent or another resource is missing.Compare the CLI region and API address with the region of the resource. Also examine the selected organization and your permissions.
Traffic goes to an unexpected location.Examine the hostname family of the agent and the location of each provider target. A profile default does not change them.
A provider target is not available.Examine its region and the routing rules in policy-config.yaml.
no region configuredSet a default for the active profile.
invalid region slugUse an enabled value from regions list, such as eu-west, us-east, or global.

Next steps​