> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/sonarqube-cloud/getting-started/getting-started-in-us-region.md).

# Getting started in the US server region

*This feature requires the SonarQube Cloud Enterprise license.*

The SonarQube Cloud US instance is now available at [sonarqube.us](http://sonarqube.us). We refer to the existing instance ([sonarcloud.io](https://sonarcloud.io/login)), which hosts data in the EU server region, as the SonarQube Cloud EU instance.

When users sign up for the SonarQube Cloud US instance, their account is created in the US server region. For more information, see [Signing in to SonarQube Cloud](/sonarqube-cloud/managing-your-account/signing-in.md).

{% hint style="info" %}
Access to [sonarqube.us](http://sonarqube.us) is provided upon request for Enterprise customers. When you request an enterprise setup within the US region, Sonar authorizes your users to access the US instance. As an end user, if you think you should have access, contact your SonarQube Cloud administrator.
{% endhint %}

## Limitations

You currently cannot share or move data between the SonarQube Cloud EU and US instances.

The Slack integration is currently not supported in the SonarQube Cloud US instance.

## Prerequisites

To be able to analyze your projects in the US server region, you must use at least the following scanner version:

* SonarScanner for Maven: 5.1
* SonarScanner for Gradle: 6.1
* SonarScanner for .NET: 10.2
* SonarScanner for NPM: 4.3
* SonarScanner CLI: 7.1
* SonarScanner CLI Docker image: 11.3
* SonarQube Scan GitHub Action: 5.1.0
* SonarCloud Scan Bitbucket Pipe: 4.1
* Azure DevOps extension for SonarQube Cloud: 3.2

If you use CircleCI with our Orb in the US region, use at least Orb version 3.0.

## Configuring your scanner for the US server region

If you use the Azure DevOps Extension, you select the US server region when adding the SonarQube service connection to Azure Pipelines. For more information, see [Configuring project for Azure Pipelines](/sonarqube-cloud/analyzing-source-code/ci-based-analysis/azure-pipelines/setting-up-project-integration.md#adding-sonarqube-service-connection).

For all other scanners, the `sonar.region` analysis parameter determines if a project is hosted in the US region. This parameter defaults to the EU server region. For more information about this parameter, see [Parameters not settable in the UI](/sonarqube-cloud/analyzing-source-code/analysis-parameters/parameters-not-settable-in-ui.md#server-connection). For general guidelines to set your analysis parameters, see [Configuration overview](/sonarqube-cloud/analyzing-source-code/analysis-parameters/configuration-overview.md).

## Connecting SonarQube for IDE to the US instance

[SonarQube for IDE](https://www.sonarsource.com/products/sonarqube/ide/) is a free IDE extension that integrates with SonarQube Cloud using connected mode.

To connect your IDE to the SonarQube Cloud's US instance, see:

* VS Code: [Connected mode setup](/sonarqube-for-vs-code/connect-your-ide/setup.md)
* Intellij: [Connected mode setup](/sonarqube-for-intellij/connect-your-ide/setup.md)
* Visual Studio: [Connected mode setup](/sonarqube-for-visual-studio/connect-your-ide/setup.md)
* Eclipse: [Connected mode setup](/sonarqube-for-eclipse/connect-your-ide/setup.md)

## Connecting your MCP server to your instance

You can connect your local MCP server to the SonarQube Cloud’s US instance. See [https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/setup/environment-considerations#connecting-to-sonarqube-cloud-in-the-us-region](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/setup/environment-considerations#connecting-to-sonarqube-cloud-in-the-us-region "mention").

### Connecting to the SonarQube Cloud-hosted MCP server

When connecting to a SonarQube Cloud organization in the US region, replace the `"url"` configuration variable with `https://api.sonarqube.us/mcp`. See the [https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/setup/sonarqube-cloud-hosted](https://docs.sonarsource.com/sonarqube-developer-tools/sonarqube-mcp-server/setup/sonarqube-cloud-hosted "mention") page for full details.

## Using the US instance's Web API

See [Web API](/sonarqube-cloud/appendices/web-api.md).

## Networking requirements

See [Networking requirements](/sonarqube-cloud/appendices/networking-requirements.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sonarsource.com/sonarqube-cloud/getting-started/getting-started-in-us-region.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
