Managing e24files using the console

What is S3cmd for AWS S3?

Managing e24files using the console is very simple. This is mainly thanks to tools that have been created for AWS S3, such as S3cmd. The tool allows for quick operations without the need for programming or S3 API knowledge. It is an invaluable solution for, for example, sending locally created backups to the cloud using scripts. It also gives the possibility of freely manipulating data saved in e24cloud from any of your own scripts and programs. To start playing with this application, we first download the program. If you are using the Debian/Ubuntu distribution, it is worth installing the package:

wget https://s3tools.org/repo/deb-all/stable/s3cmd_1.0.0-4_all.deb
dpkg -i s3cmd_1.0.0-4_all.deb 

Configuring the S3cmd program

Now we proceed to configure the s3cmd program:

e24@178.216.200.XXX:~# s3cmd –configure
Enter new values or accept defaults in brackets with Enter.
Refer to user manual for detailed description of all options.Access key and Secret key are your identifiers for Amazon S3
Access Key []: 51b0651b0-4962-46fe-4962-a4cff90ff909
Secret Key []: fa44fc55-721c-4a6b-99e5-1345df3a6932
Encryption password is used to protect your files from reading by unauthorized persons while in transfer to S3
Encryption password: (puste)
Path to GPG program [/usr/bin/gpg]:
When using secure HTTPS protocol all communication with Amazon S3 servers is protected from 3rd party eavesdropping. This method is slower than plain HTTP and can’t be used if you’re behind a proxy
Use HTTPS protocol [No]:
On some networks all internet access must go through a HTTP proxy.
Try setting it here if you can't conect to S3 directly
HTTP Proxy server name:New settings:
Access Key: 51b0651b0-4962-46fe-4962-a4cff90ff909
Secret Key: fa44fc55-721c-4a6b-99e5-1345df3a6932
Encryption password:
Path to GPG program: /usr/bin/gpg
Use HTTPS protocol: False
HTTP Proxy server name:
HTTP Proxy server port: 0
Test access with supplied credentials? [Y/n] n
Save settings? [y/N] y
Configuration saved to '/e24/.s3cfg'

To complete the configuration in the /e24/.s3.cfg file, we change the lines:

host_base = e24files.com
host_bucket = %(bucket)s.e24files.com

From now on, we can try to operate with e24files containers and objects using s3cmd.

Example S3cmd commands

Creating a bucket (container) - s3cmd mb

s3cmd mb s3://blog
Bucket 's3://blog/' created

Deleting a bucket (container) - s3cmd rb

s3cmd rb s3://blog
Bucket 's3://blog/' removed

Listing buckets - s3cmd ls

s3cmd ls
2013-04-05 19:28 s3://wp_db_backup
2013-04-05 20:36 s3://work_stuff

Putting files - s3cmd put

s3cmd put s3cmd_1.0.0-4_all.deb s3://wp_db_backup
s3cmd_1.0.0-4_all.deb -> s3://wp_db_backup/s3cmd_1.0.0-4_all.deb [1 of 1]
60288 of 60288 100% in 0s 279.05 kB/s done

Downloading a file - s3cmd get

s3cmd get s3://wp_db_backup/s3cmd_1.0.0-4_all.deb s3cmd_1.0.0-4_all.deb2
s3://wp_db_backup/s3cmd_1.0.0-4_all.deb -> s3cmd_1.0.0-4_all.deb2 [1 of 1]
60288 of 60288 100% in 0s 414.99 kB/s done 

Deleting a file - s3cmd del

s3cmd del s3://wp_db_backup/s3cmd_1.0.0-4_all.deb
File s3://wp_db_backup/s3cmd_1.0.0-4_all.deb deleted

Counting occupied space (in bytes) - s3cmd du

s3cmd du
0 s3://wp_db_backup/
2680 s3://work_stuff/
——–
2680 Total

Updated on 23 May 2024