How to access EODATA and Object Storage using s3cmd on Linux on CODE-DE-Lab
EODATA and private Object Storage use separate credentials and endpoints. Keep their s3cmd settings in separate files.
Prerequisites
No. 1 s3cmd
Install s3cmd on the Linux machine from which you will access the storage.
No. 2 Credentials
Obtain your personal EODATA keys and EC2 credentials for private Object Storage.
Configure EODATA
Follow the s3cmd EODATA configuration and save it as ~/.s3cfg-eodata. It uses HTTPS, eodata.code-de.org, and the signing region s3.fra1-3.cloudferro.com.
Test access to the EODATA bucket:
s3cmd -c ~/.s3cfg-eodata ls s3://eodata/
Configure private Object Storage
Run the configurator with a separate file:
s3cmd -c ~/.s3cfg-private --configure
Enter your private Object Storage EC2 keys. Use the following connection settings:
Default Region: RegionOne
S3 Endpoint: s3.fra1-3.cloudferro.com
DNS-style bucket+hostname:port template for accessing a bucket: s3.fra1-3.cloudferro.com
Use HTTPS protocol: Yes
Save the settings and list your private buckets:
s3cmd -c ~/.s3cfg-private ls
Still need help?
If this article does not answer all of your questions, the support team will help you.