RosettaCloud™ Storage
Object, file, block and snapshots
One dataset.
Everyone who needs it.
Storage is where collaboration actually happens. Give a colleague the original rather than a copy and there is one dataset to secure, one to pay for and one that is current, reachable from whichever account or cloud the work runs in.
Four kinds of storage,
managed the same way
Created, listed, encrypted, attached and shared through the same operations on every cloud you connect.
Object storage
Buckets with the access rights you set, optionally serving a static site or fronted by a CDN, and shareable down to a folder path.
File storage
Shared file systems across availability zones, with mount targets managed for you and encryption with your own key.
Block storage
Volumes with the type, size, throughput and IOPS you choose, attached to a machine and encrypted at rest.
Snapshots
Point-in-time copies that can be shared, published, or restored into a new volume.
Reachable from where
the work happens
The usual answer to a colleague needing your data is to send them a copy, which creates a second thing to secure, pay for and keep current. Sharing the original avoids all three.
Across accounts and clouds
A machine in one account reaches a bucket in another, or on another cloud, with the credentials handled by the platform.
A folder, not the whole bucket
Share a single path with the rights you choose, so exposing one dataset does not mean exposing the rest.
Ends when the share ends
Access is issued on share and withdrawn on unshare. There is no key left behind and nothing to remember to revoke.
Storage is the cost
that outlives its owner
A machine that is switched off is obviously free. The volume it was using is not, and neither are the snapshots taken of it. Unattached volumes and orphaned snapshots are among the twenty eight kinds of waste detected across the estate, reported before anything is touched.
What counts as waste →Common questions
Can a machine in one account reach storage in another?
Yes, and across clouds too. Sharing storage issues the credentials that make the access work and revokes them when you stop sharing, so nobody exchanges keys and no administrator writes a policy in the middle.
Is storage encrypted with our own keys?
Yes. File storage, block storage and snapshots can each be encrypted with an encryption key you manage. The key is yours and lives in your own account.
Can I share part of a bucket rather than all of it?
Yes. A share can be scoped to a single folder path with the rights you choose, so exposing one dataset to a collaborator does not expose everything else that happens to live in the same bucket.
What happens to storage nobody is using?
Unattached volumes and orphaned snapshots are among the twenty eight kinds of waste that get detected, which matters because storage is the classic cost that survives the thing that created it. Findings are reported first, and cleaned up when you say so.