Skip to main content

Keep Resources and Model Traffic in One Region

Each Verdictan resource, such as an agent or a gateway, belongs to one region. Two different settings decide where your data goes. This article explains both settings and how to examine them. Select a Region gives the full procedure.

Know the two settings​

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

When traffic must stay in one location, examine both settings.

Examine the management region​

Sign in. Then run these commands:

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.

An agent that you create in eu-west does not show when you query us-east. The Console has no region selector. Sign in to the EU Console or the US Console of your organization.

A new profile default does not move resources. It also does not change where a running gateway sends traffic.

Examine the traffic location​

Verdictan gives each published agent a hostname. Copy it from the agent page. Do not make it from the agent name or the 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 hostname sets the location of the managed endpoint. The provider targets in your configuration set which upstream providers the gateway can call. 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.

Next steps​