S3 Object Storage

In this section, you manage your S3 objects (Buckets, Files) including project and panel user permissions and S3 EC2 Credentials (Access Key and Secret).

S3 Element Overview

The following image illustrates the elements you can manage in the Cloud Services Portal under S3 Object Storage. The structure relates to a project. You can create and manage multiple projects as needed.

To use S3, you need at least:

a project
a user with S3 Panel permissions
EC2 Credentials (API & Secret Key)
a bucket

Element	Description
(A) Project	Permissions, buckets, and EC2 credentials are always associated with a project.
(B) Client Admin	The Client Admin is a user with extended rights who manages projects and users and regulates their permissions.
(C) Client User	The Client User sees the projects and buckets for which they have been granted permissions.
(D) Project EC2 Credentials	Access to buckets within a project is authorized using so-called EC2 Credentials¹.
(E) Bucket	A bucket² is like a container for the objects (files) to be stored in Object Storage.
(F) Objects	In the S3 Object Storage Panel, individual files can be easily uploaded or downloaded³.
(G) Bucket2	You can create multiple buckets for better organization of objects.

Legend S3 Administration Overview

Manage S3 Dashboard Permissions

For a user to access the S3 dashboard, the necessary permissions must first be granted.

Navigate to S3 Object Storage on the left, then select Manage permissions.

Note

User permission to the S3 Panel is independent of permissions to a project or bucket. If you do not see this menu item, please contact your Enterprise Partner Support.

Then click the Manage permissions button to the right of the respective user.

Now set the desired permissions for this user according to their task and then click update.

S3 Dashboard Overview

The following image illustrates the structure of the elements you can manage in the Cloud Services Portal under S3 Dashboard.

Element	Description
Project Level (1)	Isolated group of Project Permissions (4), Buckets (2), and EC2 Credentials (3).
Bucket Level (2)	List of buckets for this project
EC2 Credentials (3)	Management of EC2 Credentials belonging to this project.
Users (4)	Management of user permissions for this project.

Once you click on a project (1) and then a bucket (2), if present, the bucket objects and other features (3) such as MPUs (Multi Part Uploads) will be displayed.

Note

MPU - After you initiate a multipart upload (MPU) and upload one or more parts, they are listed in the MPU tab. You must either complete or abort the multipart upload to stop being charged for the storage space consumed by the uploaded parts. Only after you have either completed or aborted a multipart upload does S3 release the part storage and stop billing you for it.

Element	Description
Project (1)	Selected Project with Bucket (2) and Object List
Feature TAB's (3)	Objects TAB with the objects and MPU TAB with the list of incomplete Multipart Uploads
Object Details (4)	Clicking on the Properties column (4) of an object displays further details about the object
Buttons (5)	Using the "Upload file" and "Create Folder" buttons (5), further objects can be created in this bucket.

Create Project

To manage your buckets, users, and EC2 credentials, you first create a project. A project can contain multiple buckets, users, and EC2 credentials.

Note

Your Enterprise Partner may have already created a project for you, and you can proceed directly to creating credentials.

Within the scope of fair use, you can create multiple projects depending on your order.

Navigate to S3 Object Storage on the left, then select S3 dashboard.

Now please click the Create Project button.
Enter a project name and description.
For Quota Profile, please select object-storage⁴.
Then click the Create button.

The project has been created and is displayed.
Now grant user permissions for this project.

Note

A message will appear indicating that you must create a credential for this project before you can create a bucket.

Manage Project User

If you are authorized to create and manage projects yourself, you can create additional users and grant them permissions for projects. This permission is not required for accessing a bucket.

To create a user or grant an existing user permissions for one or more projects, please proceed as follows.

Navigate to S3 Object Storage on the left, then select S3 dashboard.
First, click on the project (1) for which you want to grant user permissions.
Next, please click on the Users TAB (2) on the right.
Now, click Edit roles (3) on the right side of the row for the corresponding user.

Now select the role "s3" and finalize your input by clicking the update button.
You can directly create a new user using the Create User button.

Create EC2 Credentials

Before you can create buckets, you must have created at least one EC2 credential in your project.

Navigate to S3 Object Storage on the left, then select S3 dashboard.
First, click on the project (1) for which you want to create EC2 Credentials.
Next, click the Create Credentials button (2) in the "Credentials" TAB on the right.

The generated EC2 Credentials will be displayed.
Enter a description for the use of these credentials.
If you are authorized⁵, you can also create user-bound EC2 Credentials using the flag is user credentials.
Complete the process by clicking create.

The EC2 Credentials have been created for this project and are displayed in the list.

A) Access and Secret Key - Click the eye symbol to display them.
B) Source - Indicates whether it is a user-bound⁶ or project-bound EC2 Credential.
C) Selected - Shows which EC2 Credential is used to query S3 objects in the Cloud Services Portal. You can set this using the Action button F) Select Credentials.
D) Selected - Description of the EC2 Credential.
E) Copy_to_clipboard - Clicking this column copies the API and Secret Key to the clipboard.
F) Actions - see C). Clicking the arrow reveals the option to delete the EC2 Credential.
Now create your bucket.

Create Bucket

To create a bucket, please proceed as follows.

Navigate to S3 Object Storage on the left, then select S3 dashboard.
First, click on the project (1) in which you want to create a bucket.
Next, please click the Create Bucket button (2) on the right.

Enter a name and click create.

Note

Please note the restrictions on the bucket name.

Bucket Name Restrictions

Generally, bucket names should follow domain name restrictions.

Bucket names can contain lowercase letters, numbers, and hyphens. Each label must begin and end with a lowercase letter or a number.
Bucket names must be unique.
Bucket names cannot be formatted as an IP address.
Bucket names can be between 3 and 63 characters long.
Bucket names cannot contain uppercase letters or underscores.
Bucket names must begin with a lowercase letter or a number.

Upload Files

After creating a bucket, you can now upload or download individual files in the S3 panel.

Navigate to S3 Object Storage on the left, then within the corresponding project(1), select the desired Bucket(2).
Now click the Upload File button (3) on the right.

The S3 Upload Manager will appear in a new browser TAB.
Now open your File Explorer and drag & drop (using the left mouse button) individual files or entire directories into the upload list within the dashed area (1).
Once you have added all objects you want to upload, start the upload process by clicking Start uploading (3).

Alternatively, you can add individual files by clicking Select files (2).
While compiling the upload list, the objects are listed below Total size.
You can delete individual objects or add more (C) in the upload list.
After clicking the Start uploading button (3), an animation (A) Preparing uploads appears until the actual upload begins.
The upload status is displayed on the right in the object list (B).

Note

You can switch browser tabs during the upload process and continue working in the Cloud Services Portal or another application until the upload is complete. If you close the S3 Upload Manager browser tab during an upload process, the upload will be aborted and may potentially be resumed later with Resume Upload.

Resume Upload

If an upload was interrupted, e.g., by accidentally closing the upload browser tab, the upload is incomplete. You now have two options.

A) Abort all uploads

To delete the interrupted upload process and the MPU files, please proceed as follows:

Navigate to S3 Object Storage on the left, then within the corresponding project(1), select the Bucket(2) where the upload process was interrupted.

Now click the Upload File button (3) on the right.
The MPU (Multi Part Upload) files (C) of the aborted upload will now be displayed.

To clean up the MPU files and the upload process, click Abort all uploads (3).
Confirm the prompt with OK.
The MPU files will now be deleted, and you can close the S3 Upload Manager by clicking the Cancel button, or you can create a new Upload List.

Note

Files that were already uploaded completely remain in the bucket and are not deleted!

B) Resume folder uploading

To resume the interrupted upload process, please proceed as follows:

Navigate to S3 Object Storage on the left, then within the corresponding project(1), select the Bucket(2) where the upload process was interrupted.

Now click the Upload File button (3) on the right.
The MPU (Multi Part Upload) files (C) of the aborted upload will now be displayed.

Now click Resume folder uploading (B).
An Explorer window will open, showing the source directory you intended to upload. Select this directory again and confirm the next prompt after the upload with the OK button.
The upload process will now resume, and the remaining objects will be uploaded.
After the upload is complete, you can close the S3 Upload Manager by clicking the Cancel button.

MPU - Multi Part Upload

When uploading objects above a certain size, the files are divided into multi-part upload "packages" or parts (MPU). Each part is a contiguous section of the object's data. The object parts can be uploaded independently and in any order.

If a part transfer fails, only the failed part is retransmitted, without affecting other parts. After all parts of your object are uploaded, S3 assembles these parts to create the object.

Advantages of Multipart Upload (MPU):

Improved throughput - Parallel uploading (up to 100 parts) increases throughput.
Quick recovery from network problems - The smaller part size minimizes the impact of restarting a failed upload due to a network error.
Pausing and resuming object uploads - You can upload object parts over a period of time. However, you must explicitly complete or abort the multipart upload.

Download File

After you have created a bucket and uploaded files, you can now also download individual files in the S3 panel.

Navigate to S3 Object Storage on the left, then within the corresponding project(1), select the desired Bucket(2) where the file is located.
Now click on the name of the desired file in the list; the file will be downloaded automatically.

Note

Depending on your browser settings, the file will be downloaded or displayed, or in the case of an MP4 file, played.

The file will be saved in your Download directory.

Note

Larger data volumes can also be uploaded or downloaded using an external tool (e.g., S3 Explorer or S3cmd).

An EC2 Credential consists of an API and Secret Key and belongs to the project. You can create multiple EC2 Credentials per project. Accessing via EC2 Credentials always makes all buckets in a project visible. It is also possible to use user-bound EC2 Credentials. ↩
Within the scope of fair use, any number of buckets can be created in a project. ↩
Larger data volumes are usually loaded using an external tool (e.g., S3 Explorer or S3 CLI). ↩
Profile object-storage - This special quota profile exclusively contains #Projects Quotas to prevent accidental use of other resources (e.g., CPU, RAM). ↩
To create user-bound EC2 Credentials, you must have successfully logged in to the OpenStack Management Portal beforehand. If this prerequisite is not met, the User Credential option will not appear. ↩
Only the user-bound EC2 Credentials of the logged-in user are displayed! ↩