Terms and Concepts
Get familiar with a few key terms and concepts that will enable you to quickly get up and running with Ionburst Cloud.
The backend storage systems used by Ionburst Cloud to store data fragments.
The logical construct that defines how data is stored, and against which API credentials are created.
Where do I store my data?
In standard Cloud storage platforms, data is stored within what’s often called a bucket (AWS S3, GCS) or container (Azure Blob). Within Ionburst Cloud, this is known as a party.
What are parties?
As a private-by-design service, Ionburst Cloud parties have some key differences that distinguish them from a standard Cloud storage bucket or container.
- Ionburst Cloud parties have no concept of public access. Data stored within Ionburst Cloud cannot be made public, either deliberately or accidentally.
- API credentials used to authenticate against the Ionburst Cloud API are generated for and can only be used with a single party. They cannot be shared between parties.
- Data stored by a party cannot be shared with another party.
What are classifications?
Classifications are an additional piece of metadata that can be attached to an upload (PUT) request, to select the policies used to secure and store the file or object. If no classification is specified, Ionburst Cloud will select a default.
Classifications can be attached to a request either as a string, or by ID.
It’s important to note that uploading a file or object with the same classification multiple times provides unique protection at the object level. No two objects are ever secured in the same way.