Configuration files for s3cmd command on 3Engines Cloud🔗¶

s3cmd can access remote data using the S3 protocol. This includes EODATA repository and object storage on the 3Engines Cloud cloud.

To connect to S3 storage, s3cmd uses several parameters, such as an access key, secret key, S3 endpoint, and others. During configuration, you can enter this data interactively, and the command saves it into a configuration file. This file can then be passed to s3cmd when issuing commands using the connection described within.

If you want to use multiple connections from a single virtual machine (such as connecting both to the EODATA repository and to object storage on 3Engines Cloud cloud), you can create and store multiple configuration files — one per connection.

This article provides examples of how to create and save these configuration files under various circumstances and describes some potential problems you may encounter.

The examples are not intended to be executed sequentially as part of a workflow; instead, they illustrate different use cases of s3cmd operations.

What We Are Going To Cover