Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: S3 storage bucket support #91

Open
tibers opened this issue Sep 15, 2021 · 3 comments
Open

Feature Request: S3 storage bucket support #91

tibers opened this issue Sep 15, 2021 · 3 comments

Comments

@tibers
Copy link

tibers commented Sep 15, 2021

Right now it looks like Wyng only supports SSH as a remote destination option but this would be an awesome thing to have in our cloud-toolkit.

Use cases:

  • Backup local machines to S3 to save money on backup costs
  • Backup local machines to S3 to rehydrate them as VMs in the cloud
  • Snapshots are time consuming and don't have differential support
@tasket
Copy link
Owner

tasket commented Sep 21, 2021

This would be a duplicate or a branch of issue #21 (not sure which one yet).

I'll mention that https://github.com/s3fs-fuse/s3fs-fuse looks like it would work with Wyng immediately. Otherwise, you are correct about SSH being the only internal option for now.

How to implement internally is a little uncertain. Common practice seems to be to import 'boto3' library, but it would be interesting to do it with FUSE instead (then all the I/O routines stay the same). :-)

@tlaurion
Copy link
Contributor

Yesssss

@tlaurion
Copy link
Contributor

tlaurion commented Jan 28, 2022

Duplicate of #21 but really needed in personal non performant PoC over rsync.net because lack of python and basic Linux tools required.

S3 seems to be able to be setuped both as RO and RW and if that is possible, then restoring through tiny core overlay, or crafted detached signed iso over Heads would make it work without the need of packaging fuse, lvm-tools sshfs and other heavy requirements

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants