Account Identifiers

An account identifier uniquely identifies a Snowflake account within your business entity, as well as throughout the global network of Snowflake supported cloud platforms and cloud regions.

Snowflake supports two different options for identifying a Snowflake account. You can identify an account using either its name in your organization or its Snowflake-assigned locator in the cloud region where the account is located.


Either option can be used. However, to use the first option, organizations must be enabled in your account(s). Organizations are currently in preview and must be requested to be enabled through Snowflake Support.

In this Topic:

Where are Account Identifiers Used?

Account identifiers are required in Snowflake wherever you need to specify the account you are using, including:

  • URLs for accessing any of the Snowflake web interfaces.

  • SnowSQL, drivers, connectors, and other clients for connecting to Snowflake.

  • 3rd-party applications and services that comprise the Snowflake ecosystem.

  • Features for securing Snowflake internal operations and communication/interaction with external systems.

  • Global features such as Secure Data Sharing and Database Replication and Failover/Failback.

For example, the URL for an account uses the following format:

Option 1: Account Name in Your Organization — Preview

An organization is a first-class Snowflake object that links the accounts owned by your business entity. Organizations enable organization administrators (i.e. users with the ORGADMIN role) to view, create, and manage all of your accounts across different cloud platforms and regions.

Using an Account Name as an Identifier

The account identifier for an account in your organization takes one of the following forms, depending on where and how the identifier is used:

  • organization_name-account_name (for most URLs and other general purpose usage)

  • organization_name_account_name (for scenarios/features where hyphens are not supported in URLs)

  • organization_name.account_name (for SQL commands and operations)



Name of your Snowflake organization. Currently, organization names are assigned by Snowflake, but you can request the name to be changed.


Unique name of your account within your organization:

  • If you are an organization administrator and create an account within your organization, you can specify the name of the account at creation.

  • If an account is created for your organization, either through self-service or a Snowflake representative, the account name is provided by Snowflake, but you can request the name to be changed.

For example, if your organization name is abccorp and account name is usprod1, either of the following formats would work for the account URL: or (if hyphens aren’t supported)

For more details about organizations and account identifiers, see Understanding Organization and Account Names.

Finding Your Organization and Account Name

To determine your organization and account name, contact your Snowflake administrator.

Option 2: Account Locator in a Region

An account locator is an identifier assigned by Snowflake when the account is created:

  • If the account is created by a Snowflake representative, you may be able to request a specific value for the locator, such as a company name, acronym, or other recognizable string.

  • If the account is created through self-service or an automated/background process, the locator is a random string of unique characters and numbers (e.g. xy12345).

The locator for an account cannot be changed once the account is created.

Using an Account Locator as an Identifier

Each Snowflake account is hosted on a cloud platform in a geographical region. The region determines where the data in the account is stored and where the compute resources used by the account are provisioned.

When using an account locator to identify an account, the locator by itself is not always sufficient to identify the location of the account. Depending on the region and cloud platform for the account, additional segments may be required, in the form of:

account_locator.region_id or



Identifier for the cloud region (dictated by the cloud platform).


Identifier for the cloud platform (aws, azure, or gcp).

For example, if your account locator is xy12345:

  • If the account is located in the AWS US West (Oregon) region, no additional segments are required and the URL would be

  • If the account is located in the AWS US East (Ohio) region, additional segments are required and the URL would be

For a complete list of region and locator formats, see Locator Formats by Cloud Platform and Region (in this topic).

Finding the Region and Locator for Your Account

If you can connect to your Snowflake account, you can query the following context functions to identify the region and account locator for the Snowflake account you are connected to:

If you are unable to connect to Snowflake, contact the Snowflake administrator for your account to retrieve this information.

Locator Formats by Cloud Platform and Region

The following table lists the account locator formats across all the supported regions, including whether the account locator for a given region requires additional segments.

If your account locator is xy12345:

Cloud Platform / . Region

Account Locator . (with additional segments if required)

Amazon Web Services (AWS)

US West (Oregon)


US East (Ohio)

US East (N. Virginia)

US East (Commercial Gov - N. Virginia)

Canada (Central)

EU (Ireland)

Europe (London)

EU (Frankfurt)

Asia Pacific (Tokyo)

Asia Pacific (Mumbai)

Asia Pacific (Singapore)


Asia Pacific (Sydney)


Google Cloud Platform (GCP)

US Central1 (Iowa)

Europe West2 (London)


Europe West4 (Netherlands)


Microsoft Azure

West US 2 (Washington)

East US 2 (Virginia)

US Gov Virginia

Canada Central (Toronto)

West Europe (Netherlands)

Switzerland North (Zurich)

Southeast Asia (Singapore)

Australia East (New South Wales)


If either of the following conditions is true, your account locator is different than the structure described in the above examples: