How to boot on Block Storage volumes with Enterprise Instances

Boot-on-Block - Overview

Scaleway Enterprise Instances are our latest high-end instances based on the AMD EPYC™ 7003 Series Processor. These instances support the boot-on-block feature which allows them to boot from attached Block Storage volumes. Block Storage is fully backed by SSDs and comes with guaranteed IOPS for critical applications. All data on the Block Storage platform is replicated three times to ensure integrity. Your data is highly available and remains accessible even in case of a disk failure.

Enterprise instances come without local storage and you can add one or several Block Storage volumes depending on your requirements. The minimum size of a Block Storage volume is 10GB.

Requirements

You have:

Creating an Enterprise Instance with Boot on Block

1 . Log into your Scaleway console.

2 . Click Instances in the Compute section of the side menu. The instances overview displays.

3 . Click + Create an Instance. The instance creation wizard displays.

4 . Select the Availability Zone for your Enterprise instance. Currently this instance-type is available in the FR-PAR-2 zone, more zones will be available in the near future.

5 . Select an image to deploy the instance from.

Enterprise Instances can boot from different image sources:

  • OS Images: Choose your favourite basic Linux distribution, ready to be configured by you.

The following OS images are compatible with Enterprise Instances:

  • Ubuntu Focal, Bionic, Xenial
  • Debian Buster
  • CentOS 8
  • Fedora 32

  • My images: You can populate your own list of instance templates, created from a backup image of an existing Enterprise Instance. See also: Create your own image

  • Snapshots: You can recover an Enterprise instance from a previously saved block volume containing a compatible boot image. See also: Backup your data with snapshots

Note:

  • Instant Apps are not available for Enterprise Instances
  • Enterprise Instances are not compatible with Bootscripts, except for for rescue mode

6 . Click the Enterprise tab in the instances selection area. Choose the configuration to deploy by clicking on its name.

7 . Configure the Block Storage volumes for your instance. You can attach one or several volumes to your instance, depending on your requirements. The minumum size for a Block Storage volume is 10 GB.

Note:

  • If several Block Storage volumes are connected to an Enterprise Instance, the first volume will contain the OS and is required to boot the instance.
  • Do not detach the first volume from your instance, to avoid any issues.

For more information about Block Storage volumes, refer to our product documentation.

Connecting to Enterprise Instances

Once deployed, you can connect to your Enterprise Instance using your SSH key and your favourite SSH client. For more information, refer to our SSH documentation

Backing-up an Enterprise Instances

You can backup your Enterprise Instances using the snapshot-feature. It allows you to clone instances having exact the same configuration.

Note: Note that snapshots created from a local volume (l_ssd) can not be used to create an Enterprise Instance, as it only supports booting from block volume (b_ssd).

Secure Encrypted Virtualization (SEV)

Enterprise Instances rely on the AMD EPYC™ 7003 series Processor, which provide the SEV feature. AMD SEV helps keep your Instance information confidential, by encrypting the memory of the virtual machine. SEV doesn’t require any changes to you application software, it is enabled in the hypervisor and image of the Enterprise Instance. More details on SEV feature available at the AMD website.

SEV activation on Enterprise Instance can be checked by the following command line on the instance:

# dmesg | grep -i sev

Note:

  • As the encryption is activated at the boot of the Instance, the boot time can take few more seconds on larger Enterprise instances.
  • If the instance is booted into rescue mode SEV is disabled automatically.

Discover the Cloud That Makes Sense