S3 File System (s3fs) is a utility that allows remote object storage containers, or buckets, to be exported as a local file system. This means that Hostwinds’ Object Storage can be mounted to a VPS, and the user can have access to scalable, static storage locally. Object storage can be used for storing backups, for file-sharing, or other unstructured data.
The guide below will explain the steps required to mount Hostwinds’ Object Storage to a CentOS 7 server.
Step 1: Install s3fs-fuse:
Access your VPS via SSH as the root user, or a user with
sudo access. Next install s3fs-fuse with the following:
yum install gcc libstdc++-devel gcc-c++ fuse fuse-devel curl-devel libxml2-devel mailcap git automake make yum install openssl-devel git clone https://github.com/s3fs-fuse/s3fs-fuse cd s3fs-fuse/ ./autogen.sh export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig ./configure --prefix=/usr --with-openssl make sudo make install
Step 2: Retrieve the Hostwinds Object API Info:
After completing the installation, you can retrieve your Object Storage API information from Hostwinds’ Cloud Control portal. Navigate from the client area to the Cloud Portal.
Next, select Storage > Object Storage, as seen below.
Select Create Container. Name the container and select your preference of Hostwinds data center locations.
Next, select Object API Info. You will need your Access Key, Secret Key, and API Endpoint for the selected location. Store this information temporarily for the following steps, or leave this page open while proceeding.
Step 3: Create Credentials File:
Using a text editor, create your credentials file:
Then enter your Hostwinds API credentials in the first line of the new file, in the format:
Next, change the permissions of this file:
chmod 600 /etc/passwd-s3fs
Step 4: Create Mountpoint and Cache:
Now you can create your mount point, and the cache for the container. Use a mount point similar to below, it does not need to be called my-container:
mkdir /tmp/cache /mnt/my-container
Change the permissions:
chmod 777 /tmp/cache /mnt/my-container
Step 5: Make New Entry in fstab:
Finally, you will need to add a line to
fstab has 6 columns. Be careful to add the following to your new line, separated by spaces:
You will need your own
Lastly, mount the container using:
Reboot, and verify that the container stays mounted on boot by running:
The output should be similar to:
Now you have access to far more storage at $0.03/GB/month!
To mount additional containers from the same data center location:
- Perform Steps 4 and 5 again using a different container name and mountpoint.
To mount additional containers from a different data center location:
- Perform Steps 2-5 again using a new Access Key, Secret Key, API Endpoint, container name, mountpoint, and credentials file.