Tech previews

• 1: Elastx Cloud Console
• 1.1: Introduction
• 1.2: Access and permissions
• 1.3: Announcements
• 1.4: Features
• 1.5: Onboarding
• 2: The Vault
• 2.1: Knowledge base
• 2.1.1: FAQ
• 2.2: Backup solutions

1 - Elastx Cloud Console

1.1 - Introduction

The Elastx Cloud Console (ECC) or just “Cloud Console” is our new web interface to manage your services on the Elastx Cloud Platform (ECP).

The address is https://console.elastx.cloud - to login and access your organization you need a user account in the IdP, contact our support.

Right now features are limited, a selection of what is currently available:

• Invite and manage users for your organization
• Create and manage access to DBaaS projects
• Create and manage access to Openstack projects

1.2 - Access and permissions

The Cloud Console features a rudimentary permissions system based on hardcoded groups, usually a “Admins” and a “Members” group where the “Admins” group can be considered “RW” (read and write) and the “Members” group can be considered read only.

Organization

Organization admins can manage permissions through the “Organization” page in the sidebar. Minimum permissions in an organization is represented by the “Members” group. They can view everything for the organization in Cloud Console.

Admins can edit everything owned by the organization in the Cloud Console and make other users Admins in the organization.

DBaaS

For each DBaaS project, there is a “Admins” and a “Members” group. Their privileges in DBaaS are the same, ie. complete.

In the Cloud Console organization Admins can:

• Create projects
• Add/remove users for each project

OpenStack

For OpenStack projects, organization Admins can:

• Create projects
• Add/remove users for each project
• Manage users’ Openstack project roles for each project

1.3 - Announcements

Release in tech preview

2026-04-20 - Today marks the availability of Cloud Console in tech preview.

1.4 - Features

Features

Overview of features in Cloud Console:

• Organization, invite and manage your users
• DBaaS, create and manage projects for DBaaS
• OpenStack
  • Create and manage projects
  • Manage user access with OpenStack project roles for your users
• The Vault, manage access for your users

1.5 - Onboarding

To get access to your organization in Cloud Console you need to be added by an admin in the organization or by our support.

The Cloud Console is located at https://console.elastx.cloud

Reviewing existing resources

If you have been an Elastx customer since before the Cloud Console was introduced, begin by reviewing DBaaS and Openstack projects in the Cloud Console, ie. make sure your current projects are listed.

If something is missing or incorrect, please contact our support.

Adding users

If you are a member of the “Admins” group for your organization, you can add/invite other users.

To view members of the “Admins” and “Members” group, click “Organization” in the sidebar.

To add new members to your organization, click “Users” in the sidebar and the “Add user” button on the new page.

New users will automatically be added to your organization’s “Members” group. To make a user admin:

1. Click “Organization” in the sidebar
2. Below the “Admins” header, click the “Add member” button
3. Select the user(s), click the “Save” button

Setting up projects

Create the DBaaS/Openstack projects you need.

For DBaaS, the difference between “Admins” and “Members” for a project is just that “Admins” for a project can add/remove other users’ access in the Cloud Console. They both have full permissions in CCX to manage datastores.

Openstack project names needs to be globally unique, ie. not already in use by another customer. If you try to create a project with an existing name you will get an error that says the project already exists.

For Openstack you can manage access with the native Openstack project roles. When viewing a Openstack project in Cloud Console, use the edit button next to a members name to edit their roles. Or press the “Add member” button to add a new member from the organization to the project.

2 - The Vault

NOTE: The Vault is in development

Getting Started with Elastx The Vault

Welcome to Elastx The Vault — a secure, S3-compatible object storage service, now available for testing. Built with compliance, security, and flexibility at its core, The Vault is ideal for secondary storage and long-term data retention.

Overview of The Vault

The Vault combines scalable object storage with enterprise-grade security:

• S3-Compatible Object Storage – Easily integrate with existing tools and workflows
• Geographically and Physically Isolated – Hosted in an isolated, dedicated and physically protected region within the Elastx Cloud Platform
• Encryption at Rest – Your data is always secured with encryption
• Immutable Storage – Safeguard against deletion or tampering including Ransomware
• Integrated with Elastx IDP – Centralized identity and access management with MFA
• Purpose-Built for Secondary Storage – Designed for archiving, backups, and compliance-driven storage

Getting Access to The Vault

Before using Elastx The Vault, your organization must designate at least one Customer Admin User.

1. Request an Admin Account
   An authorized manager can use Elastx Support Page or email support@elastx.se to request access for your first admin user.

2. Activate Your User
   Once provisioned follow the instructions to activate your Elastx Identity Provider (IDP) account and setup MFA.

Accessing The Console

Use the Elastx The Vault Console to manage your The Vault configuration (only Customer Admin Users): Elastx The Vault Console

From the console you can setup and manage:

• Buckets and objects for the whole organization
• Your access keys and their policies for users and applications to access The Vault securely
• Immutable settings etc

Note: Access keys are bound to the customer admin who creates them. It’s important to note that in an organization with multiple customer admins, these admins cannot view each other’s keys.

Creating Access Keys and access the API

To enable other users, applications, services to access the The Vault api.

1. Log in to the console as an admin
2. Create Access Keys for your organization’s users or services
3. Store the secret key securely — it is only shown once
4. Access the api via: https://vault.elastx.cloud

Start using MinIO - i.e. create a new bucket with Minio Client

Note! Your buckets always need to be named with your organisations unique prefixed uid. I.e. <uid.bucketname> which is provided by Elastx Support to your Authorized manager

   mc alias set <alias> https://vault.elastx.cloud <accesskey> <secret>
   mc mb <alias>/<uuid>.<bucketname>

Additional User Roles

You may also request WriteOnly and ReadOnly users/accounts via support@elastx.se. These users are pre-assigned with limited policies suitable for:

• WriteOnly – I.e. to upload data into The Vault
• ReadOnly – I.e when the need is only to read from storage

Technical details

The S3 API is rate-limited with max 128 active sessions and 1k requests per second per source IP. This limit is quite low on purpose as the main usage of the system should be to stream large backup/archive objects and not to store millions of small objets. Hitting the limit will trigger a HTTP 429 response which most S3 clients can handle gracefully with exponential backoff.

Learn More

For more complete documentation including how to manage immutability, refer to official documentation, i.e.:

• MinIO Docs on Github
• MinIO S3 Compatible API Documentation

2.1 - Knowledge base

2.1.1 - FAQ

I can’t get the “Object Locking” functionality to work. What is wrong?

Unfortunately there is a bug in the GUI and this functionality can only be accessed via the API.

2.2 - Backup solutions

Introduction

This page describes solutions för running backups against The Vault object storage.

The goal is to create an efficient backup solution especially when you have many small files that you need to backup. This will reduce the number of objects stored and the number of requests needed against The Vault to a minimum.

Juicefs

This solution is a High-Performance, Cloud-Native, Distributed File System. In this case we will primarily use it to reduce the number of requests against The Vault. This is a good solution if you want to backup a large number of small files. Juicefs handles all metadata in a database so all requests during a sync are handled against the database instead of requests in The Vault.

Setup

Install the juicefs binary in a Linux instance.

curl -sSL https://d.juicefs.com/install | sh -

Install sqllite

apt-get install sqlite3

Setup the drive using The Vault and SQLite

juicefs format --storage minio --bucket https://vault.elastx.cloud/<bucket> --access-key <access> --secret-key <secret> "sqlite3://thevaultfs.db" thevaultfs

Mount drive

mkdir /thevaultfs
juicefs mount sqlite3://thevaultfs.db /thevaultfs -d

Now you can sync data using rclone or other tools and to compare content between the primary and The Vault through juicefs does not require any requests on The Vault.

Setup using Swift as storage

Setup the drive using swift s3 (ec2 credentials) and SQLite

juicefs format --storage swift --bucket https://<container>.swift.elastx.cloud --access-key <access> --secret-key <secret> sqlite3://swiftfs.db swiftfs

Mount drive

mkdir /swiftfs
juicefs mount sqlite3://swiftfs.db /swiftfs -d

Veeam

Install a Veeam backup server to take backups of object storage or other resources and store those backups in The Vault.

Create a Bucket in The Vualt with immutable support.

mc mb --with-lock thevault/<bucket-name>

Setup

This is an instruction on how to install the Veeam Software Appliance in Openstack IaaS. Download the VeeamSoftwareAppliance iso file from Veeam. Create an account if you don’t have one and start a trial if you want to test.

Create an openstack image from the iso file using the openstack cli.

openstack image create  --container-format bare --disk-format iso --property hw_firmware_type=uefi --file VeeamSoftwareAppliance_13.0.1.1071_20251217.iso VeeamSoftwareAppliance_13.0.1.1071_20251217-iso

Create a volume from the iso file and place the volume in the availability zone where you want to run the Veeam server.

openstack volume create --image VeeamSoftwareAppliance_13.0.1.1071_20251217-iso --availability-zone <az> --type v2-1k --size 15 veeam-iso

Create a boot volume, a data volume and then create an instance that attaches the boot volume, the data volume and the volume with the Veeam iso image. All must be located in the same availability zone. Both the boot and data volume needs to be at least 240 GB in size.

On the boot volume set the following property to make the instance use uefi.

openstack volume set --image-property hw_firmware_type=uefi <veeam-iso-volume-id>

Create the backup server instance.

openstack server create --flavor <flavor-id> --availability-zone <az> --volume <boot-volume-id> --block-device uuid=<data-volume-id>,source_type=volume,destination_type=volume --block-device uuid=<veeam-iso-volume-id>,source_type=volume,destination_type=volume,boot_index=1,device_type=cdrom,disk_bus=sata --nic net-id=<network-id> veeam-server

Follow the instructions and install the Veeam Server Appliance.