What is a volume?
Cloud storage providers come with their own interfaces, features and terminology. At a certain level, though, they all view resources as data objects organized in repositories. Authentication and operations are commonly defined on those objects and repositories, and while each cloud provider might call these things different names and apply different parameters to them, their basic behavior is the same.
CAVATICA mediates access to these repositories using volumes. A volume is associated with a particular cloud storage repository that you have enabled Seven Bridges to read from (and, optionally, to write to).
Currently, volumes may be created using three types of cloud storage repository:
- Amazon Web Services' (AWS) S3 buckets
- Google Cloud Storage (GCS) buckets
- Other types of cloud storage, through an S3-compatible API (read-only). This cloud storage type requires an additional API layer that the storage employs, which must use the same "language" as the AWS S3 API.
A volume enables you to treat the cloud repository associated with it as external storage for CAVATICA.
What information should I provide?
To create a volume on CAVATICA, you should provide the following information:
A volume name consists of 3-32 letters of the English alphabet, numbers, and underscores (_). Each of your volumes must have a unique name.
The access mode of a volume is either read-only (
RO) or read-write (
Each volume will have its access mode set by default to read-only. Volumes from cloud providers other than AWS S3 and Google Cloud Storage can be connected in read-only mode.
Read-only volumes can only be used to make files available to CAVATICA for reading; for example, by importing files into projects. Read-write volumes' contents can be modified by operations performed with the Volumes API. Note that regardless of access mode, the owner of the volume is still the only CAVATICA account that can issue operations on that volume. However, it is a good practice to avoid configuring your input buckets as read-write, as a safeguard against honest mistakes.
Cloud service configuration
To access the cloud storage provider on your behalf, CAVATICA needs to know the type of storage provider it should talk to, and be configured to interface with it.
As each cloud storage provider supports slightly different features and authorization schemas, the configuration will be different for each storage type. Depending on your selected storage provider and your intended use of the volume, there might be additional properties you may want to set to further modify the way CAVATICA accesses it.
For more details on each supported storage type and its corresponding configuration, see the following pages:
- Amazon Web Services' Simple Storage Service (AWS S3) Volumes
- Google Cloud Storage (GCS) Volumes
- Attach a volume from other cloud providers through an S3-compatible endpoint
A prefix is a string that can be set on a volume to refer to a specific location on a single bucket. This feature can be used to replicate the folder or grouping structure inside a bucket in your cloud storage account. As such, a prefix is useful if you have grouped files devoted to distinct projects within a single bucket.
For example, on Amazon S3, folders can also be assigned specific access permissions in the bucket policy itself, or an IAM user can be configured to have read-only or read-write access per each folder. When you assign your volume a prefix as well as a bucket, you limit the volume's operations within the specified folder on the bucket.
For example, if you set the
prefix for a volume to
"a10", and import a file with
location set to
"test.fastq" from the volume to CAVATICA, then the object that will be referred to by the newly-created alias will be
What can I do with a volume?
Once a volume has been configured, you can make its data objects available for computation on CAVATICA, and, conversely, and copy files to the volume from CAVATICA.
These operations can be carried out through the visual interface or using the Volumes API. All API calls are listed in the Volumes section of the API documentation.
Operations on volumes
Updated less than a minute ago