Run outside Germany
Place instances, volumes, networks and elastic IPs in Helsinki (region fi1) once your organization allows EU locations outside Germany.
Last updated 18 November 2026View as Markdown
Everything is in Germany (de1) unless your organization decides otherwise. Region fi1 (zone
fi1a, Helsinki, Finland, in the EU) is offered only after an administrator turns on Allow EU
locations outside Germany under Settings, Data location. Turning it on needs
iam:UpdateOrganization.
Prerequisites
- The organization setting is on. Without it, a create in
fi1is refused with403"Region fi1 (Helsinki, Finland) is outside Germany: an administrator has to allow EU locations outside Germany first (Settings → Data location)" before anything is ordered. An unknown region is refused with400"Unknown region …"; nothing falls back to another region. - The permission for the create itself, for example
ec2:RunInstances. - In the console, also
ec2:DescribeInstancesto open Instances (without it the page says "Access denied").
Create in fi1
In the examples, replace 114690387 with the id of an OS image from the catalog.
- Open Compute, then Instances, and choose Create instance (other create forms have the same Region field).
- For Region, choose
fi1. It carries the badge outside Germany · Finland, as does every resource in it. - Fill in the rest of the form, then choose Create instance.
dcloud ec2 instances run --region-id fi1 --server-type performance-2 --image-id 114690387Commands without a region field take --region fi1.
POST /ec2/api/instances
{ "serverType": "performance-2", "imageId": 114690387, "regionId": "fi1" }Requests without a region field take the X-EWS-Region: fi1 header.
Result
- A resource and what it attaches to stay in one region: a volume attaches to an instance of its region, a network and its subnets are in one region.
- Turning the setting off moves nothing. Resources already in Helsinki stay usable; nothing new is placed there.
Related
Did this page help you?
Related