# Persistent volume on S3 based storage

**URL:** <https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585>\
**Category:** SUSE Rancher Prime\
**Created:** [October 18, 2019, 8:39am UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585 "2019-10-18T08:39:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![tjans](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@tjans](https://forums.suse.com/u/tjans)\
**Post date:** [October 18, 2019, 8:39am UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/1 "2019-10-18T08:39:04Z")

</div>

Currently trying to run a small cluster on scaleway instances. Got the cluster up and running but want to add some persistent storage. Scaleway offers object storage based on the S3 api. I tied to attach it as a storage class but cant figure out how to do this.

Can anyone help me to use this as a persistent volume within rancher?

---

<div class="post-metadata">

**Author:** ![chris.ingenhaag](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chris.ingenhaag/32/5703_2.png) [@chris.ingenhaag](https://forums.suse.com/u/chris.ingenhaag)\
**Post date:** [October 19, 2019, 10:40am UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/2 "2019-10-19T10:40:46Z")

</div>

Welcome @tjans,  
am I right you want to use S3 as volume provisioner for a filesystem? Afaik this is not possible. S3 is an object storage. But you need a block storage for provide a filesystem. Maybe there are solutions out there that make this working, who knows?

Want kind of application do you want to deploy? Maybe community can help then.

best

---

<div class="post-metadata">

**Author:** ![tjans](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@tjans](https://forums.suse.com/u/tjans)\
**Post date:** [October 21, 2019, 9:07am UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/3 "2019-10-21T09:07:21Z")

</div>

@chris.ingenhaag thank you for your response.  
Wanted to use the S3 to make persistend volumes to use on my pods. I want to deploy a small MariaDB/MySQL database to use for some personal projects so very little traffic and i’m looking for a cheap way to persist the data.

---

<div class="post-metadata">

**Author:** ![chris.ingenhaag](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/chris.ingenhaag/32/5703_2.png) [@chris.ingenhaag](https://forums.suse.com/u/chris.ingenhaag)\
**Post date:** [October 21, 2019, 8:53pm UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/4 "2019-10-21T20:53:09Z")

</div>

Ok, I think this is not possible afaik.

You may look if scaleway offers some block storage for this.

regards,  
christian

---

<div class="post-metadata">

**Author:** ![vincent](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/vincent/32/7156_2.png) [@vincent](https://forums.suse.com/u/vincent)\
**Post date:** [October 21, 2019, 9:33pm UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/5 "2019-10-21T21:33:12Z")

</div>

It is “possible” with things like [https://github.com/s3fs-fuse/s3fs-fuse](https://github.com/s3fs-fuse/s3fs-fuse) but a bad idea in general… And a fantastically bad idea for a database in particular. The only way to update a file in S3 is to upload an entire new copy, and the whole database (or table with innodb\_file\_per\_table). So you’d be rewriting the entire table/DB every time it changes.

As @chris.ingenhaag has said, you really need block storage for arbitrary volumes. Object storage is primarily for (relatively) high latency write-once/read-many high level API access to whole files. It’s not random-writable primary storage.

---

<div class="post-metadata">

**Author:** ![tjans](https://avatars.discourse-cdn.com/v4/letter/t/ce73a5/32.png) [@tjans](https://forums.suse.com/u/tjans)\
**Post date:** [October 23, 2019, 7:56am UTC](https://forums.suse.com/t/persistent-volume-on-s3-based-storage/15585/6 "2019-10-23T07:56:11Z")

</div>

i knew that it would have bad performance but didn’t know that it had to rewrite the entire table/DB on every change. I’ll try to find something else for my persistent storage.
