Next, on your Cloud Server, enter the following command to generate the global credential file. Be sure to replace ACCESS_KEY<\/span> and SECRET_KEY<\/span> with the actual keys for your Object Storage:<\/p>\n\n\n\n

echo \"ACCESS_KEY<\/span>:SECRET_KEY<\/span>\" | sudo tee \/etc\/passwd-s3fs\n<\/pre>\n\n\n\n
Then use chmod<\/tt> to set the necessary permissions to secure the file. 600 ensures that only the root will be able to read and write to the file. If this step is skipped, you will be unable to mount the Object Storage bucket:<\/p>\n\n\n\n
sudo chmod 600 \/etc\/passwd-s3fs\n<\/pre>\n\n\n\n
With the global credential file in place, the next step is to choose a mount point. This is the directory on your server where the Object Storage bucket will be mounted. It can be any empty directory on your server, but for the purpose of this guide, we will be creating a new directory specifically for this.<\/p>\n\n\n\n
sudo mkdir \/mnt\/my-object-storage<\/pre>\n\n\n\n
Any files will then be made available under the directory \/mnt\/my-object-storage\/<\/tt>.<\/p>\n\n\n\n
Mounting your Object Storage bucket<\/h2>\n\n\n\n
We\u2019re now ready to mount the bucket using the format below. Please note that this is not the actual command that you need to execute on your server. You must first replace the parts highlighted in red<\/span> with your Object Storage details:<\/p>\n\n\n\n
sudo s3fs {bucketname}<\/span> {\/mountpoint\/dir\/}<\/span> -o passwd_file=\/etc\/passwd-s3fs -o allow_other -o url=https:\/\/{private-network-endpoint}<\/span>\n<\/pre>\n\n\n\n
{bucketname}<\/span><\/strong> is the name of the bucket that you wish to mount.<\/p>\n\n\n\n
{\/mountpoint\/dir\/}<\/span><\/strong> is the empty directory on your server where you plan to mount the bucket (it must already exist).<\/p>\n\n\n\n
\/etc\/passwd-s3fs<\/strong> is the location of the global credential file that you created earlier. If you created it elsewhere you will need to specify the file location here.<\/p>\n\n\n\n
-o allow_other<\/strong> allows non-root users to access the mount. Otherwise, only the root user will have access to the mounted bucket.<\/p>\n\n\n\n
-o url<\/strong> specifies the private network endpoint for the Object Storage. This can be found by clicking the S3 API access<\/em> link. Don\u2019t forget to prefix the private network endpoint with https:\/\/<\/strong><\/p>\n\n\n\n
<\/figure>\n\n\n\n
The private network endpoint allows access to Object Storage via the utility network. This avoids the use of your transfer quota for internal queries since all utility network traffic is free of charge. However, note that Cloud Servers can only access the internal Object Storage endpoints located within the same data centre.<\/p>\n\n\n\n
Using all of the information above, the actual command to mount an Object Storage bucket would look something like this:<\/p>\n\n\n\n
sudo s3fs my-bucket \/mnt\/my-object-storage -o passwd_file=\/etc\/passwd-s3fs -o allow_other -o url=https:\/\/my-object-storage-internal.sg-sin1.upcloudobjects.com\n<\/pre>\n\n\n\n
You can now navigate to the mount directory and create a dummy text file to confirm that the mount was successful.<\/p>\n\n\n\n
touch \/mnt\/my-object-storage\/testing.txt\n<\/pre>\n\n\n\n
If all went well, you should be able to see the dummy text file in your UpCloud Control Panel under the mounted Object Storage bucked.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
Likewise, any files uploaded to the bucket via the Object Storage page in the control panel will appear in the mount point inside your server.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
If you then check the directory on your Cloud Server, you should see both files as they appear in your Object Storage.<\/p>\n\n\n\n
<\/figure>\n\n\n\n
Mounting your Object Storage bucket automatically on boot<\/h2>\n\n\n\n
To detach the Object Storage from your Cloud Server, unmount the bucket by using the umount command like below:<\/p>\n\n\n\n
umount \/mnt\/my-object-storage\n<\/pre>\n\n\n\n
You can confirm that the bucket has been unmounted by navigating back to the mount directory and verifying that it is now empty.<\/p>\n\n\n\n
Unmounting also happens every time the server is restarted. After every reboot, you will need to mount the bucket again before being able to access it via the mount point.<\/p>\n\n\n\n
However, it is possible to configure your server to mount the bucket automatically at boot. You can do so by adding the s3fs mount command to your \/etc\/fstab<\/tt> file. For the command used earlier, the line in fstab would look like this:<\/p>\n\n\n\n
s3fs#my-bucket \/mnt\/my-object-storage fuse _netdev,allow_other,passwd_file=\/etc\/passwd-s3fs,url=https:\/\/my-object-storage-internal.sg-sin1.upcloudobjects.com\/ 0 0\n<\/pre>\n\n\n\n
If you then reboot the server to test, you should see the Object Storage get mounted automatically.<\/p>\n","protected":false},"featured_media":16932,"comment_status":"open","ping_status":"closed","template":"","community-category":[113,127,128],"class_list":["post-24918","tutorial","type-tutorial","status-publish","has-post-thumbnail","hentry","community-category-integrations","community-category-managed-services","community-category-object-storage"],"acf":[],"_links":{"self":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial\/24918","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/tutorial"}],"about":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/types\/tutorial"}],"replies":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/comments?post=24918"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media\/16932"}],"wp:attachment":[{"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/media?parent=24918"}],"wp:term":[{"taxonomy":"community-category","embeddable":true,"href":"https:\/\/studiogo.tech\/upcloudold\/wp-json\/wp\/v2\/community-category?post=24918"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}