Account Identifiers

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

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

Note

You can use either format. However, to use the first format, an ORGADMIN role must be created in one of your accounts. If the role does not exist, contact 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 and other clients (connectors, drivers, etc.) for connecting to Snowflake.

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

  • Security features for protecting 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:

account_identifier.snowflakecomputing.com

For more information about using account identifiers in URLs and Snowflake clients, see Using Account Identifiers for Connecting to Your Accounts.

Format 1 (Preferred): Account Name in Your Organization

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.

Account names must be unique within your organization, and can be changed, which allows more flexibility and leads to shorter and more intuitive account names. You specify an account name when you create a new account (see Creating an Account). To change a name for an existing account, contact Snowflake Support.

While an account name uniquely identifies an account within your organization, it is not a unique identifier of an account across Snowflake organizations.

Account names with underscores also have a dashed version of the URL for features that do not accept URLs with underscores, such as Okta SSO/SCIM.

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)

Where:

  • organization_name is the name of your Snowflake organization.

  • account_name is the unique name of your account within your organization.

For more details, see Organization and Account Names (In this topic).

Organization and Account Names

Organization Name

The organization name is a name chosen by you at the time when your first Snowflake account is provisioned for your organization. The name must be unique across all other organizations in Snowflake. It can include uppercase letters and numbers, but not underscores or other delimiters.

You cannot change your organization name yourself. To change your organization name, contact Snowflake Support.

As a best practice, review and change your organization name, if needed, before using the name in any account identifiers. Renaming the organization name in the future will result in changing all the URLs for your Snowflake accounts to match the new name.

To view the name of your organization, see Viewing the Name of Your Organization.

Account Name

Each account name must be unique within your organization. You specify an account name when you create the account (see Creating an Account).

While an account name uniquely identifies an account within your organization, it is not a unique identifier of an account across Snowflake organizations. To uniquely identify an account in Snowflake, you must prepend your organization name to the account name. For example:

organization_name-account_name

Consistent with SQL standards for identifiers, account names can include underscores as separators between words (e.g. MARKETING_TEST_ACCOUNT).

URLs that include underscores can sometimes cause issues for certain features, such as Okta SSO/SCIM. For this reason, Snowflake also supports a version of the account name that substitutes the hyphen character (-) in place of the underscore character. For example both of the following URLs are supported:

URL with underscores: https://acme-marketing_test_account.snowflakecomputing.com

URL with dashes: https://acme-marketing-test-account.snowflakecomputing.com

Existing Accounts

If you have any accounts that existed before the Organizations feature was enabled, the Format 2 (Legacy): Account Locator in a Region is used as the account name.

In addition, if you have existing accounts with the same name in different regions, the cloud and region names are appended to the account name in the new URL format.

For example, if your organization name is ACME, and there are two accounts named TEST, one in the AWS us-east-2 region and the other in the Azure west-us-2 region, the new URLs will use the following structure:

  • First account:

    Original URL

    https://test.us-east-2.aws.snowflakecomputing.com

    New URL

    https://acme-test_aws_us_east_2.snowflakecomputing.com

  • Second account:

    Original URL

    https://test.west-us-2.azure.snowflakecomputing.com

    New URL

    https://acme-test_azure_west_us_2.snowflakecomputing.com

These account names can be changed as long as the new names are unique. For instructions on how to change an account name, see Changing Account Name.

Format 2 (Legacy): 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.

Note

Account locators continue to be supported for identifying accounts in Snowflake, but this is no longer the preferred method. The preferred method for identifying accounts is now the account name within your organization (as described earlier in this topic).

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 account. Depending on the region and cloud platform for the account, additional segments may be required, in the form of:

account_locator.cloud_region_id or

account_locator.cloud_region_id.cloud

Where:

  • cloud_region_id is the identifier for the cloud region (dictated by the cloud platform).

  • cloud is the 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 xy12345.snowflakecomputing.com.

  • If the account is located in the AWS US East (Ohio) region, additional segments are required and the URL would be xy12345.us-east-2.aws.snowflakecomputing.com.

For a complete list of regions and locator formats, see Non-VPS Account Locator Formats by Cloud Platform and Region (in this topic).

Note

If your Snowflake Edition is VPS, the account locator uses a different format. See Finding the Account Locator for a VPS Account (in this topic).

Finding the Region and Locator for an 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.

Finding the Account Locator for a VPS Account

If your Snowflake Edition is VPS, the account locator uses different naming conventions than the accounts for other Snowflake Editions. This results in a different structure for the hostnames and URLs used to access VPS accounts.

For details, please contact Snowflake Support or your Snowflake representative.

As an alternative, you can use the preferred format of organization_name-account_name as your account identifier. This format works for accounts that use the VPS edition. For details, see Format 1 (Preferred): Account Name in Your Organization (in this topic).

Non-VPS Account Locator Formats by Cloud Platform and Region

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

If your account locator is xy12345:

Cloud Platform / Region

Account Locator

Notes

Amazon Web Services (AWS)

US West (Oregon)

xy12345

No additional segments required.

US Gov West 1

xy12345.us-gov-west-1.aws

US East (Ohio)

xy12345.us-east-2.aws

US East (N. Virginia)

xy12345.us-east-1

Cloud region ID is the only additional segment required.

US East (Commercial Gov - N. Virginia)

xy12345.us-east-1-gov.aws

Canada (Central)

xy12345.ca-central-1.aws

EU (Ireland)

xy12345.eu-west-1

Cloud region ID is the only additional segment required.

Europe (London)

xy12345.eu-west-2.aws

EU (Frankfurt)

xy12345.eu-central-1

Cloud region ID is the only additional segment required.

Asia Pacific (Tokyo)

xy12345.ap-northeast-1.aws

Asia Pacific (Seoul)

xy12345.ap-northeast-2.aws

Asia Pacific (Mumbai)

xy12345.ap-south-1.aws

Asia Pacific (Singapore)

xy12345.ap-southeast-1

Cloud region ID is the only additional segment required.

Asia Pacific (Sydney)

xy12345.ap-southeast-2

Cloud region ID is the only additional segment required.

Google Cloud Platform (GCP)

US Central1 (Iowa)

xy12345.us-central1.gcp

Europe West2 (London)

xy12345.europe-west2.gcp

Europe West4 (Netherlands)

xy12345.europe-west4.gcp

Microsoft Azure

The Azure account locators were implemented with hyphens for consistency with AWS and GCP.

West US 2 (Washington)

xy12345.west-us-2.azure

Central US (Iowa)

xy12345.central-us.azure

South Central US (Texas)

xy12345.south-central-us.azure

East US 2 (Virginia)

xy12345.east-us-2.azure

US Gov Virginia

xy12345.us-gov-virginia.azure

Canada Central (Toronto)

xy12345.canada-central.azure

North Europe (Ireland)

xy12345.north-europe.azure

West Europe (Netherlands)

xy12345.west-europe.azure

Switzerland North (Zurich)

xy12345.switzerland-north.azure

UAE North (Dubai)

xy12345.uae-north.azure

Japan East (Tokyo)

xy12345.japan-east.azure

Southeast Asia (Singapore)

xy12345.southeast-asia.azure

Australia East (New South Wales)

xy12345.australia-east.azure

Account Identifiers for Private Connectivity

If Private Connectivity to the Snowflake Service is enabled for your account and you wish to use the feature to connect to Snowflake, run the SYSTEM$GET_PRIVATELINK_CONFIG function to determine the private connectivity URL to use. You can use either the account name or account locator in the URL to connect to the Snowflake web interface.

Note

Currently, when using Format 1 (Preferred): Account Name in Your Organization, the private connectivity URL to the Snowflake service is not supported for SnowSQL and other Snowflake clients.

As a workaround when using SnowSQL or other Snowflake clients with private connectivity to the Snowflake service, use the URL format shown in Format 2 (Legacy): Account Locator in a Region.

For more details, see Using Account Identifiers for Connecting to Your Accounts.

Account Identifiers for Replication and Failover

If the Organization feature is enabled for your account, see Format 1 (Preferred): Account Name in Your Organization.

Replication and failover related SQL commands require using the Snowflake Region ID as part of the account identifier:

snowflake_region_id.account_locator

Where:

For more details and a complete list, see Region IDs (in this topic).

In addition, for replication and failover across different region groups, you will also need to specify the region group in the account identifier:

region_group.snowflake_region_id.name

The value for region_group can be found in the output of SHOW REPLICATION ACCOUNTS.

For more details, see Region Groups (in this topic).

Snowflake Region IDs and Region Groups

A Snowflake Region is a distinct region (deployed within an AWS, Azure, or GCP cloud region) that is isolated from other Snowflake Regions. A Snowflake Region can be either multi-tenant (containing accounts for multiple organizations) or single-tenant (aka Virtual Private Snowflake for a single organization).

Each Snowflake Region has an unique identifier and belongs to a region group, which enables global features such as data sharing and replication.

Region IDs

Because each cloud platform utilizes different conventions and formats for naming their regions, Snowflake assigns a canonical ID to each Snowflake Region that uniquely identifies it across all the cloud platforms and their regions.

If the Organizations feature is enabled, specifying the Snowflake Region ID as part of an account identifier is required when you create a new account, as well as when you configure replication and failover.

The following table displays the complete list of Snowflake Region IDs:

Cloud Region

Cloud Region ID

Snowflake Region ID

Notes

Amazon Web Services (AWS)

US West (Oregon)

us-west-2

aws_us_west_2

US Gov West 1

us-gov-west-1

aws_us_gov_west_1

Available only for accounts on Business Critical (or higher); located in AWS GovCloud (US).

US East (Ohio)

us-east-2

aws_us_east_2

US East (N. Virginia)

us-east-1

aws_us_east_1

US East (Commercial Gov - N. Virginia)

us-east-1

aws_us_east_1_gov

Available only for accounts on Business Critical (or higher); located in US East 1, not AWS GovCloud (US).

Canada (Central)

ca-central-1

aws_ca_central_1

EU (Ireland)

eu-west-1

aws_eu_west_1

Europe (London)

eu-west-2

aws_eu_west_2

EU (Frankfurt)

eu-central-1

aws_eu_central_1

EU (Stockholm)

eu-north-1

aws_eu_north_1

Asia Pacific (Tokyo)

ap-northeast-1

aws_ap_northeast_1

Asia Pacific (Seoul)

ap-northeast-2

aws_ap_northeast_2

Asia Pacific (Mumbai)

ap-south-1

aws_ap_south_1

Asia Pacific (Singapore)

ap-southeast-1

aws_ap_southeast_1

Asia Pacific (Sydney)

ap-southeast-2

aws_ap_southeast_2

Google Cloud Platform (GCP)

US Central1 (Iowa)

us-central1

gcp_us_central1

Europe West2 (London)

europe-west2

gcp_europe_west2

Europe West4 (Netherlands)

europe-west4

gcp_europe_west4

Microsoft Azure

West US 2 (Washington)

westus2

azure_westus2

Central US (Iowa)

centralus

azure_centralus

South Central US (Texas)

southcentralus

azure_southcentralus

East US 2 (Virginia)

eastus2

azure_eastus2

US Gov Virginia

usgovvirginia

azure_usgovvirginia

Available only for accounts on Business Critical (or higher); located in Microsoft Azure Government.

Canada Central (Toronto)

canadacentral

azure_canadacentral

North Europe (Ireland)

northeurope

azure_northeurope

West Europe (Netherlands)

westeurope

azure_westeurope

Switzerland North (Zurich)

switzerlandnorth

azure_switzerlandnorth

UAE North (Dubai)

uaenorth

azure_uaenorth

Japan East (Tokyo)

japaneast

azure_japaneast

Southeast Asia (Singapore)

southeastasia

azure_southeastasia

Australia East (New South Wales)

australiaeast

azure_australiaeast

Region Groups

A region group is a group of Snowflake Regions that offer similar security controls, isolation, and compliance. The region group to which a Snowflake Region belongs differs depending on the region:

  • All Snowflake multi-tenant commercial regions (across all the supported cloud platforms) are in the same shared/general PUBLIC group.

  • Each Snowflake multi-tenant government region is in a separate group specific to the region.

  • Each single-tenant Virtual Private Snowflake (VPS) is in a separate region group specific to the VPS. If your organization has more than one VPS, you can have one VPS per region group or multiple VPSs can share the same region group.

If the Organizations feature is enabled, specifying the region group as part of an account identifier is required when you want to create accounts in different region groups, or when you want to replicate and failover to/from accounts in different region groups.