CloudCIX Object Storage is S3-compatible, allowing you to use standard AWS S3 tools and SDKs to manage your data.
Currently this is our S3-compatible endpoint information:
Endpoint URL: https://s3-boole.cloudcix.com
Region: boole-zonegroup
Before you begin, contact CloudCIX support to obtain:
Access Key and Secret Key
Storage quota allocation
Contact CloudCIX support with:
Desired storage capacity (e.g., 100GB, 1TB)
You’ll receive:
Access Key
Secret Key
# Ubuntu/Debian
sudo apt install s3cmd
# CentOS/RHEL
sudo yum install s3cmd
# Mac
brew install s3cmd
s3cmd --configure
Enter when prompted:
Access Key: [your-access-key]
Secret Key: [your-secret-key]
Default Region: boole-zonegroup
S3 Endpoint: s3-boole.cloudcix.com
DNS-style bucket+hostname: [press Enter to skip]
Encryption password: [press Enter to skip]
Use HTTPS protocol: Yes
HTTP Proxy server name: [press Enter to skip]
# List buckets
s3cmd ls
# Create bucket
s3cmd mb s3://my-bucket
# Upload file
s3cmd put file.txt s3://my-bucket/
# Download file
s3cmd get s3://my-bucket/file.txt
# Delete file
s3cmd del s3://my-bucket/file.txt
By default, newly created buckets in CloudCIX Object Storage (or any S3-compatible system) are private, meaning only the bucket owner can access them.
This tutorial shows how to make a bucket publicly readable using a bucket policy.
s3cmd mb s3://my-bucket
Note
This creates a new bucket named my-bucket.
Create a file named policy.json with the following content:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "PublicRead",
"Effect": "Allow",
"Principal": "*",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::my-bucket/*"
}
]
}
Attach the policy to your bucket:
s3cmd setpolicy policy.json s3://my-bucket
s3cmd put text.txt s3://my-bucket
Any objects uploaded now inherit the bucket policy.
They will be publicly accessible.
Objects can now be accessed using a standard S3 URL:
https://<endpoint>/<tenant>:my-bucket/text.txt
For example:
https://s3-boole.cloudcix.com/tenant-a:my-bucket/text.txt
Check that the policy is applied:
s3cmd info s3://my-bucket
You should see a Policy section showing the JSON you applied.
If you want to make the bucket private again:
s3cmd delpolicy s3://my-bucket
Note
This removes the public access policy, restoring full privacy.
Note
Cyberduck can be used to manage files and folders in your Ceph S3-compatible storage, but it cannot configure bucket policies. Bucket policies must be applied using CLI tools like s3cmd.
Download from: https://cyberduck.io/download/
Open Cyberduck
Click Open Connection
Select Amazon S3 from dropdown
Enter:
Server: s3-boole.cloudcix.com
Access Key ID: <your access key>
Secret Access Key: <your secret access key>
Click Connect
Create folders (buckets)
Drag and drop files to upload
Double-click files to download
Right-click for more options (delete, rename, share)
Contact CloudCIX support for:
Storage quota increases
Access credential resets
Technical assistance
Endpoint: https://s3-boole.cloudcix.com
Protocol: HTTPS (port 443)
API Compatibility: AWS S3