Quick Start – Cloud4You OCS¶

This guide shows step by step how to start using Cloud4You OCS (Object Cloud Storage).

If you only want to upload a few files, the easiest option is to use OCS Browser.

If you want to connect an application, server, script, or perform operations from the terminal, use AWS CLI or another client compatible with the S3 API.

What do you need?¶

To connect to Cloud4You OCS, you need:

Parameter	Value
Endpoint	`https://s3.cloud4you.pl`
Region	`eu-pl-1`
Access Key ID	the access key you received
Secret Access Key	the secret key you received

We recommend using the main endpoint https://s3.cloud4you.pl.

You receive the Access Key ID and Secret Access Key when the service credentials are created.

Do not share your Secret Access Key with other people.

Do not include access keys in screenshots, support tickets, or public configuration files.

Easiest option – OCS Browser¶

If you want to browse buckets and files from a web browser, you do not need to install anything.

Open OCS Browser

Enter:

Access Key ID
Secret Access Key

Then click:

Connect

The endpoint and region are configured automatically.

After logging in, you will see the buckets that the key can access.

What is a bucket?¶

A bucket is the main container for data.

The simplest way to think about it is as a top-level directory.

Example:

firma-backup

Inside it, objects may be presented in the panel as files and folders:

firma-backup
├── dokumenty
│   ├── umowa.pdf
│   └── faktura.pdf
└── backup
    └── serwer01.tar.gz

In OCS, files are technically called objects.

Installing AWS CLI¶

AWS CLI is a command-line client that supports the S3 API.

You can also use it with Cloud4You OCS.

If AWS CLI is already installed, go directly to Configuring AWS CLI.

Windows¶

Open PowerShell.

Run:

irm https://awscli.amazonaws.com/v2/install.ps1 | iex

When the installation finishes, close and reopen PowerShell.

Check the installation:

aws --version

You should receive output similar to:

aws-cli/2.x.x ...

If the aws command is not immediately available, close the terminal and open it again.

Linux – Ubuntu / Debian¶

First install the required tools:

sudo apt update
sudo apt install -y curl unzip

Then download AWS CLI:

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"

Extract it:

unzip awscliv2.zip

Install it:

sudo ./aws/install

Check:

aws --version

After a successful installation, you can remove the installation files:

rm -rf aws awscliv2.zip

Linux – Rocky Linux / AlmaLinux / RHEL¶

Install the required tools:

sudo dnf install -y curl unzip

Download AWS CLI:

curl "https://awscli.amazonaws.com/awscli-exe-linux-x86_64.zip" -o "awscliv2.zip"

Extract it:

unzip awscliv2.zip

Install it:

sudo ./aws/install

Check:

aws --version

After a successful installation:

rm -rf aws awscliv2.zip

Linux ARM64¶

If you use Linux on ARM64 architecture, for example on some ARM servers, use the aarch64 package instead of x86_64:

curl "https://awscli.amazonaws.com/awscli-exe-linux-aarch64.zip" -o "awscliv2.zip"
unzip awscliv2.zip
sudo ./aws/install

Then run:

aws --version

macOS¶

Open Terminal and run:

curl -fsSL https://awscli.amazonaws.com/v2/install.sh | bash

After installation, close and reopen Terminal.

Check:

aws --version

If you want to install AWS CLI for all system users:

curl -fsSL https://awscli.amazonaws.com/v2/install.sh | sudo bash -s -- --system

Configuring AWS CLI¶

We recommend creating a separate profile named:

cloud4you

This prevents the Cloud4You configuration from overwriting an existing AWS configuration.

Run:

aws configure --profile cloud4you

The program will ask for four values:

AWS Access Key ID [None]:
AWS Secret Access Key [None]:
Default region name [None]:
Default output format [None]:

Enter:

AWS Access Key ID:        YOUR_ACCESS_KEY
AWS Secret Access Key:    YOUR_SECRET_KEY
Default region name:      eu-pl-1
Default output format:    json

Example:

AWS Access Key ID [None]: YOUR_ACCESS_KEY
AWS Secret Access Key [None]: YOUR_SECRET_KEY
Default region name [None]: eu-pl-1
Default output format [None]: json

Do not copy your real Secret Access Key into documentation or a technical support ticket.

The Cloud4You endpoint is not entered in the aws configure wizard.

Pass it in commands as:

--endpoint-url https://s3.cloud4you.pl

Testing the connection¶

After configuration, run:

aws s3 ls \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

If everything works, you will see a list of available buckets.

Example:

2026-08-28 10:15:00 backup-firma
2026-08-28 10:20:00 dokumenty

If the account does not have any buckets yet, the list may be empty.

Creating a bucket with AWS CLI¶

Example:

aws s3 mb s3://backup-firma-01 \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl \
  --region eu-pl-1

After creating it, check the list:

aws s3 ls \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Listing bucket contents¶

To list files:

aws s3 ls s3://backup-firma-01/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

To also display the contents of prefixes presented as subfolders:

aws s3 ls s3://backup-firma-01/ \
  --recursive \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Uploading one file¶

Assume you have a file:

test.txt

To upload it to the bucket:

aws s3 cp test.txt s3://backup-firma-01/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Check:

aws s3 ls s3://backup-firma-01/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Uploading a file to a folder¶

Example:

aws s3 cp faktura.pdf s3://backup-firma-01/dokumenty/faktura.pdf \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

After the command completes, the object will be visible as:

dokumenty/faktura.pdf

Uploading an entire directory¶

If you have a local directory:

dokumenty/

and want to upload all of its contents:

aws s3 cp ./dokumenty/ s3://backup-firma-01/dokumenty/ \
  --recursive \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Synchronizing a directory¶

For regular data transfers, the following command is more convenient:

aws s3 sync ./dokumenty/ s3://backup-firma-01/dokumenty/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

AWS CLI compares the local content with the bucket and uploads the required files.

The sync command without additional options does not automatically delete files that exist only at the destination.

Downloading a file¶

To download a file:

aws s3 cp s3://backup-firma-01/dokumenty/faktura.pdf ./faktura.pdf \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

The file will be saved in the current directory.

Downloading an entire directory¶

aws s3 cp s3://backup-firma-01/dokumenty/ ./dokumenty/ \
  --recursive \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Deleting a single file¶

To delete an object:

aws s3 rm s3://backup-firma-01/test.txt \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Before running the command, make sure you are pointing to the correct file.

Deleting multiple files¶

You can remove the entire contents under a selected path:

aws s3 rm s3://backup-firma-01/stare-dane/ \
  --recursive \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Warning: --recursive means the operation applies to all content under the selected path. Check the command before pressing Enter.

Deleting a bucket¶

The bucket must be empty.

To delete an empty bucket:

aws s3 rb s3://backup-firma-01 \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

If the bucket still contains objects, the operation will fail.

Generating a temporary link to a file¶

You can generate a temporary link that allows someone to download a specific file without giving them the Access Key and Secret Access Key.

Example of a link valid for 1 hour:

aws s3 presign s3://backup-firma-01/dokumenty/faktura.pdf \
  --expires-in 3600 \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl \
  --region eu-pl-1

The command returns a URL.

You can send it to the recipient.

After the validity period expires, the link will stop working.

Anyone who has an active link can access the specified object until the link expires.

Where does AWS CLI store the keys?¶

After using:

aws configure --profile cloud4you

AWS CLI stores the configuration locally on the user's computer.

Linux and macOS:

~/.aws/credentials
~/.aws/config

Windows:

%USERPROFILE%\.aws\credentials
%USERPROFILE%\.aws\config

Example credentials file:

[cloud4you]
aws_access_key_id = YOUR_ACCESS_KEY
aws_secret_access_key = YOUR_SECRET_KEY

This file contains access credentials.

Do not send it to other people and do not commit it to a public Git repository.

Checking the configuration¶

To display configured profiles:

aws configure list-profiles

You should see, among others:

cloud4you

To inspect the profile configuration:

aws configure list --profile cloud4you

The Secret Access Key will be masked.

Most common errors¶

`InvalidAccessKeyId`¶

This most commonly means that the Access Key ID is incorrect.

Check the configuration:

aws configure --profile cloud4you

`SignatureDoesNotMatch`¶

The most common causes are:

an incorrect Secret Access Key,
an incorrect region,
incorrect system time on the computer or server.

For Cloud4You OCS, use the region:

eu-pl-1

`AccessDenied`¶

The connection works, but the key does not have permission to perform the requested operation.

For example, an account may have permission to read objects but not create new buckets.

AWS CLI cannot connect to the endpoint¶

Check that you are using:

https://s3.cloud4you.pl

Test:

aws s3 ls \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

If the problem persists, check the Internet connection, DNS, and any local firewall or proxy.

Bucket already exists¶

Choose a different name.

Example:

backup-firma-01

instead of:

backup

Quick AWS CLI reference¶

List buckets¶

aws s3 ls \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Create a bucket¶

aws s3 mb s3://BUCKET-NAME \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl \
  --region eu-pl-1

List files¶

aws s3 ls s3://BUCKET-NAME/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Upload¶

aws s3 cp file.txt s3://BUCKET-NAME/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Download¶

aws s3 cp s3://BUCKET-NAME/file.txt ./file.txt \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Synchronize a directory¶

aws s3 sync ./data/ s3://BUCKET-NAME/data/ \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

Delete a file¶

aws s3 rm s3://BUCKET-NAME/file.txt \
  --profile cloud4you \
  --endpoint-url https://s3.cloud4you.pl

What should I choose?¶

If you only want to manage files manually:

OCS Browser – web panel

https://ocs.cloud4you.pl

If you are configuring a server, script, or automation:

AWS CLI / S3 API

If you are configuring an S3-compatible application, you usually only need:

Endpoint:          https://s3.cloud4you.pl
Region:            eu-pl-1
Access Key ID:     YOUR_ACCESS_KEY
Secret Access Key: YOUR_SECRET_KEY

Security¶

Finally, a few simple rules:

Treat the Secret Access Key like a password.
Do not send access keys in technical support tickets.
Do not include keys in screenshots.
Do not store keys in a public Git repository.
Before deleting objects, check the bucket name and path.
For commands containing --recursive, double-check exactly what they apply to.
For standard connections, use the main endpoint https://s3.cloud4you.pl.

Help¶

Documentation:

https://docs.cloud4you.pl

Support portal:

https://support.cloud4you.pl

Quick Start – Cloud4You OCS¶

What do you need?¶

Easiest option – OCS Browser¶

What is a bucket?¶

Installing AWS CLI¶

Windows¶

Linux – Ubuntu / Debian¶

Linux – Rocky Linux / AlmaLinux / RHEL¶

Linux ARM64¶

macOS¶

Configuring AWS CLI¶

Testing the connection¶

Creating a bucket with AWS CLI¶

Listing bucket contents¶

Uploading one file¶

Uploading a file to a folder¶

Uploading an entire directory¶

Synchronizing a directory¶

Downloading a file¶

Downloading an entire directory¶

Deleting a single file¶

Deleting multiple files¶

Deleting a bucket¶

Generating a temporary link to a file¶

Where does AWS CLI store the keys?¶

Checking the configuration¶

Most common errors¶

InvalidAccessKeyId¶

SignatureDoesNotMatch¶

AccessDenied¶

AWS CLI cannot connect to the endpoint¶

Bucket already exists¶

Quick AWS CLI reference¶

List buckets¶

Create a bucket¶

List files¶

Upload¶

Download¶

Synchronize a directory¶

Delete a file¶

What should I choose?¶

Security¶

Help¶

`InvalidAccessKeyId`¶

`SignatureDoesNotMatch`¶

`AccessDenied`¶