Learn how to create your first instance in a Local Zone.
Introduction
Local Zones are an extension of Regions that bring OVHcloud services closer to specific locations, offering reduced latency and improved performance for applications. Local Zones are strategically placed in proximity to areas with high user demand. Their goals are to:
- minimize the time it takes to transfer data between the user and the cloud,
- make services faster and more responsive, and
- meet Data residency requirements.
Find more information on our dedicated Local Zone Compute page.
Available Features
| Public Cloud Services | Feature | Availability | Limitations |
|---|---|---|---|
| Compute | Instances | Yes | The suspend (shelve) action is not supported in Local Zones. |
| Rescue mode | Yes | ||
| GPU | No | ||
| Instance backup | Yes | ||
| Distant backup | No | ||
| Backup Workflow management | Yes | ||
| Linux images | Yes | ||
| Windows images | No | ||
| Upload your own image | Yes | Image size is limited to 25 GB maximum. | |
| Network | Private Network with vRack | No | Local Zones are not compatible with vRack. Private networks are limited to the same Local Zone only. DHCP is supported on Local Private Networks. |
| Load Balancer | No | ||
| Floating IP | No | ||
| Public IPv4/IPv6 support | Yes | ||
| Additional IP | No | ||
| Gateway | No | ||
| Edge Firewall | No | ||
| Anti-DDoS | Yes | ||
| Storage | Object Storage | Yes |
User policies not supported. All access keys within a project can access all buckets across all Local Zones. Only the Standard storage class supported. S3™* features not supported: S3 tags, Legal Hold, SSE-OMK, S3 replication, server access logging. |
| Block Storage | Yes | No encryption support. Classic volumes cannot be multi-attached. Classic volumes are limited to 250 IOPS and a maximum size of 4 TB. | |
| Other services | Managed Kubernetes Service | No | |
| Managed Private Registry | No | ||
| Databases and Analytics | No | ||
| AI & Machine Learning | No |
Capabilities and limitations
Support for unavailable features, like Volume Snapshots or Object Storage, will be released in the next few months. Our goal is to support the entire feature set that is currently supported in global regions.
Requirements
- Access to the OVHcloud Control Panel
- A Public Cloud project
Instructions
Create an instance
From the OVHcloud Control Panel, select your Public Cloud project and click Instances in the left-hand menu under Compute.
Click + Create an instance.
Select a model
Choose an instance model that has the Local Zone label and click Next.
Location
(Optional) Select a deployment zone: You can choose to only filter for 1-AZ regions or Local Zone locations.
If you select a Local Zone that has not been activated on your account, clicking Next will activate it for you.
Select an image
Select an image, add an SSH key, and click Next.
Configure your instance
Configure your network
NOTE: If you want to connect to the Public network, you need to check ☑ the box.
If you want to connect to a Private network (click here)
Select Local Private Network compatible with Local Zone and then Create a local private network.
Give your private network a name.
WARNING: If you choose to disable DHCP, you MUST ALSO untick the box for "Declare the first address of a CIDR given as the default gateway (DHCP option 3)." Otherwise, instances created with this private network attached will not be accessible on their public IP.
Click Next to proceed.
Select a billing period
An Hourly billing period will automatically be selected. Click Create an instance to complete your order.
Go further
For more information and tutorials, please see our other Public Cloud support guides or explore the guides for other OVHcloud products and services.
*S3 is a trademark filed by Amazon Technologies, Inc. OVHcloud's service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.