Regions

Overview

Akka projects are deployed to specific regions, which are tied to the backend infrastructure Akka uses to support projects. Regions:

Are linked to a particular cloud provider (e.g., GCP, AWS)
Exist in specific geographic locations (e.g., Europe, North America)
May have unique performance characteristics
Can provide varying levels of isolation (e.g., dedicated plans offer isolated regions)

For Organizations

When an organization is created, it is assigned access to one or more regions. A region must be specified when creating a new project within the organization.

For example, if the organization myorg has access to the region `aws-us-east-`2, you would create a project in that region using the following command:

akka project new myproject --organization myorg --region aws-us-east-2

Finding Available Regions

If you are unsure which regions your organization has access to, there are two options:

Error Prompt: If you omit the --region flag when creating a new project, Akka will inform you of the available regions in the error message. For instance:
```
$ akka project new myproject --organization myorg

--region is a required flag. The following regions are available: [aws-us-east-2]
```

List Regions Command: You can list the regions directly using the following command:

akka regions list --organization myorg

Example output:

NAME            ORGANIZATION
aws-us-east-2   db805ff5-4fbd-4442-ab56-6e6a9a3c200a

Requesting new regions

By default organizations are limited to which regions they can use, particularly for trial organizations. If you would like access to other regions, you can use the ? in the upper right of the Akka Console to request additional regions via the Contact support menu item.

Single-tenant regions

Dedicated, BYOC and BYOK8s regions work like any other region and are exclusive to your workloads. They are not available to trial users. See Choose how you run Akka for what each option is and how to start, or contact Akka to set one up.