Skip to content

Frequently Asked Question about Cloud Storage

Estimated time to read: 7 minutes

Discover how to effectively use and manage storage resources in Cyso Cloud. This section covers the different storage types available through our OpenStack-based platform, from block storage volumes to object storage solutions. Whether you're new to cloud storage concepts, need help managing your volumes and snapshots, or want to understand the benefits of object storage for your specific use case, these frequently asked questions will guide you through the essentials of Cyso Cloud storage services. Learn about storage types, volume management, troubleshooting common issues, and best practices for different storage scenarios.

How does storage work in OpenStack and Cyso Cloud?

Read all about it at our OpenStack storage types page.

I am unable to delete a volume. Why is that?

You can only delete a volume if it's no longer in use and no snapshots of it exist. In order to check if this is the case follow these steps:

  1. Log in to the Dashboard.
  2. Click on the Storage tab and select Volume Store.
  3. Go to the Volume Snapshots tab and delete any snapshots of the volume first.
  4. Then go to the Volumes tab and check whether to see if it's in use.
  5. If so, click on the drop-down menu to the right of the 'edit volume' button and click on Manage Attachments.
  6. Click on detach volume.
  7. If this is done the volume is no longer in use, and you should be able to delete the volume.
  8. Click on the drop-down menu again and select Delete Volume.

What is Object storage, and why should I use it?

With object storage, users access binary objects through a URL or REST API. It’s great for archiving or managing large datasets. In addition, as an alternative to storing the images on a file system, OpenStack can store your virtual machine images inside an object storage system, as well as back-ups and large media files.

What pricing model do you use?

We use a flexible pay-per-hour pricing model with no startup costs. This means you only pay for the resources you actively use, ensuring cost efficiency and scalability. Whether you’re running virtual machines, containers, databases, or storage, you are billed only for the time they are running—down to the hour.

With no upfront investment, our pricing structure is designed to eliminate unnecessary costs, making it ideal for businesses of all sizes. You can easily scale resources up or down based on demand, avoiding over-provisioning and ensuring you never pay for more than you need. This pay-as-you-go approach provides maximum flexibility while keeping cloud expenses under control.

Where is my Object Storage data stored?

Object Storage data is stored securely on our own managed hardware. To ensure maximum reliability, your data is automatically written to three different disks, preventing data loss in case of hardware failure.
You have full control over on which Region your data is stored. Currently, you can choose between our data centers in Europe: Amsterdam (Netherlands) and Frankfurt (Germany).

Do you offer S3-compatible object storage?

Yes, our Object Storage is fully compatible with S3, meaning you can use standard S3 tools, SDKs and applications to work with it. This ensures easy migration, integration and management using familiar workflows.

How do I use object storage on my instances?

You can use Object Storage on your instances by connecting via an S3-compatible client or command-line tools such as AWS CLI, Rclone, or MinIO Client (mc). Simply configure your access credentials, define the endpoint, and start uploading or retrieving data. Many applications also support direct integration with Object Storage for seamless data management.

How does object storage differ from block storage?

Object Storage and Block Storage serve different purposes:

  • Object Storage stores data as objects with metadata and is designed for scalability, making it ideal for backups, media files and big data. It can be accessed via APIs such as S3.
  • Block storage divides data into fixed-size blocks and is optimised for high-performance workloads such as databases and virtual machines. It is mounted by an operating system as a local disk.

Object Storage is best for scalability and cost-effective long-term storage, while Block Storage is suitable for low-latency, high-performance applications.

How much data can I store with Cyso Cloud Object Storage?

With Cyso Cloud Object Storage, there is no predefined storage limit: you can store as much data as you need. Our storage is designed to scale seamlessly, allowing you to handle terabytes or even petabytes of data without performance degradation.

Your total storage capacity depends on your plan, budget and usage needs. If you expect large-scale storage requirements, feel free to contact our team for customised solutions and pricing options.

What is an S3 client?

An S3 client is a piece of software for a specific operating system (e.g. MacOS, Linux, Windows) that is designed to facilitate the day-to-day use of S3 buckets. There are many S3 clients on the market, which differ in their feature set and also in their performance when creating or deleting.
Examples:

  • AWS CLI – Command-line tool for managing S3 storage.
  • Cyberduck – GUI-based client for S3-compatible storage.
  • Rclone – Command-line tool for syncing and managing cloud storage.
  • MinIO Client (mc) – CLI tool for interacting with S3-compatible storage like MinIO.
  • SDKs (Python Boto3, AWS SDKs, etc.) – Programmatic access for developers.

How do I access my stored objects?

You can access objects using APIs (such as S3-compatible APIs), SDKs, command-line tools, or the Cyso Cloud portal.

Is data encrypted when it is stored in Object and Volume Storage?

Basic Encryption Questions

** Is my data encrypted when stored in your object storage?**
Currently, we do not apply standard encryption to objects stored in our storage systems. The data is not encrypted but is stored in chunks (split files) on our systems. However, all data communication between your systems and our cloud occurs via TLS (Transport Layer Security), ensuring encrypted data transfer during transit.

** Is my data secure even without encryption at rest?**
While your data is securely transferred via TLS encryption, for sensitive information we recommend implementing client-side encryption for maximum security. Our storage systems have robust physical and logical security controls, but encryption at rest provides an additional security layer, especially for sensitive data.

** What encryption options does Cyso offer?**
We currently provide:

Transport encryption: All data transfers between your systems and our cloud are automatically encrypted using TLS.
Client-side encryption support: We fully support you implementing your own encryption before uploading data to our storage.

Client-Side Encryption

** How can I implement client-side encryption with your storage?**
You can implement client-side encryption in several ways:

  1. Using S3/boto tooling: You can provide your own encryption keys when uploading objects:

  2. Use SSE-C (Server-Side Encryption with Customer-Provided Keys) with the AWS SDK/boto3

  3. Apply client-side encryption before sending the data
    2.Using encryption libraries: Implement encryption in your application using standard cryptographic libraries before uploading data

** What are the benefits of client-side encryption?**
Client-side encryption offers several advantages:

  • Complete control over your encryption keys
  • We have no access to your unencrypted data
  • Enhanced security as encryption keys never leave your systems
  • Compliance with regulatory requirements that mandate encryption for sensitive data

Server-Side Encryption

** Why don’t you offer standard server-side encryption?**
With server-side encryption that we would provide, we would also manage the keys. This means:

  • The encryption offers limited additional security because the same party (us) manages both the data and the keys
  • This creates a false sense of security without significantly improving the actual security level

** Can you implement server-side encryption on request?**
While technically possible, we recommend client-side encryption as a best practice instead. This gives you complete control over your encryption keys and provides true data confidentiality. We’d be happy to discuss your specific requirements and recommend appropriate solutions.

Technical Implementation

** Which encryption methods are compatible with your storage?**
Our S3-compatible API supports various encryption methods, including:

  • AES-256 encryption
  • Customer-provided encryption keys (SSE-C)
  • Most standard encryption algorithms implemented client-side

** Do you have examples of implementing encryption with your storage?**
Yes, we can provide code examples for common programming languages and frameworks. Please contact our technical support team for detailed implementation guides specific to your environment.

Compliance and Best Practices

** Does your approach to encryption meet compliance requirements?**
Many compliance frameworks (GDPR, HIPAA, etc.) require appropriate security measures but don’t always specifically mandate server-side encryption. Client-side encryption, when properly implemented, often provides stronger security guarantees and can help meet these requirements. However, we recommend consulting with your compliance officer regarding your specific regulatory needs.

** What is your recommendation for optimal security?**
For optimal security, we recommend:

  • Encrypting your sensitive data before sending it to our storage
  • Implementing your own key management
  • Using the S3-compatible APIs with your own encryption parameters

Can you help implement a client-side encryption solution?
Absolutely! We’re available to provide technical advice and support for implementing client-side encryption solutions. Please contact our technical support team for assistance.

Do you have documentation about the Object Storage?

Here you can find the object storage: documentation.