Related Links
- S3 Developer Guide
- Endpoints and Access Keys
- Third-Party Tools
- Veeam®
- Veeam® 12 Direct-to-Cloud
- MSP360
- MSP360 Cloudberry
- MSP360 CloudBerry Explorer
- MSP360 Managed Backup Service
- Ahsay
- Acronis Cyber Protect Cloud
- Anchorpoint
- AirLiveDrive
- Archiware P5
- Arcserve
- Arcserve ImageManager
- Arq Backup
- BackupAssist
- Bunny.net
- ChronoSync
- Cloudmounter
- Cloudflare
- Comet
- Couchbase
- cPanel Backup
- CrossFTP
- CuttingRoom
- CubeBackup
- Cyberduck
- Dell
- Dropshare
- Duplicacy
- Duplicati
- EditShare
- ExpanDrive
- Fastly CDN
- Files.com
- Filezilla Pro
- Flexify.IO
- GoodSync
- Hammerspace
- Hedge OffShoot
- Hitachi Content Platform
- iconik
- Iperius Backup
- iRODS
- Jet Backup5
- LucidLink
- Milestone XProtect
- Mountain Duck
- MultCloud
- /n software S3 Drive
- NAKIVO Backup and Replication
- Nextcloud
- NirvaShare
- NovaBACKUP
- odrive
- Photos+ Cloud Library
- PureStorage
- qBackup
- QNAP
- Quest Rapid Recovery
- Rclone
- Restic
- Retrospect
- S3 Browser
- S3cmd
- S3Drive
- s5cmd
- S3FS
- SFTPCloud
- SimpleBackups
- Snowflake
- SyncBackPro
- Syncovery
- Synology Hyper Backup
- Synology Cloud Sync
- Transmit
- TrueNAS® CORE
- UpdraftPlus Backup
- Vantage Gateway
- Veeam® Backup for Microsoft 365
- Vembu BDR Suite
- Veritas Backup Exec
- WinSCP
- Windows Network Drive
- CNAME Record Guide
- S3 API Documentation
How do I use S3FS with IDrive® e2?
Follow the command syntax illustration below to use S3FS (Fuse over Amazon) with IDrive® e2.
Set up Access Key
To configure S3FS, you must create S3 Access Keys from the IDrive® e2 account. Replace the AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY with your IDrive® e2 Access Key ID and Secret Access Key values in the following syntax.
$ vi /etc/passwd-s3fs AWS_ACCESS_KEY_ID:AWS_SECRET_ACCESS_KEY
Ensure that the file has proper permission
$ chmod 600 /etc/passwd-s3fs
Mount S3 Bucket
Execute the below command to mount S3FS:
$ s3fs mybucket /path/to/mountpoint -o passwd_file=/etc/passwd-s3fs -o url=https://l4g4.ch11.idrivee2-2.com
On successful execution the mount point should work.
$ cd /tmp/idrivee2/
$ ls
BEOST_SInf BEOST_SInf-Bak BEOST_SMap keys.rtf
$ cp example.deb /tmp/idrivee2/
$ ls
BEOST_SInf BEOST_SInf-Bak BEOST_SMap
example.deb keys.rtf