How to access EODATA using S3 protocol on CREODIAS
This article covers different methods which you can use to gain access to the EODATA repository on a virtual machine on CREODIAS.
What Are We Going To Cover
Obtaining S3 credentials
Accessing EODATA using s3fs, boto3, s3cmd, goofys and rclone
No. 1 Hosting
You need a CREODIAS hosting account with Horizon interface https://horizon.cloudferro.com.
No. 2 Linux or Windows virtual machine with access to the eodata_ network
You need a Linux or Windows virtual machine on CREODIAS cloud. It should have access to the eodata_ network found in your cloud environment.
If you want to use a Linux image available on CREODIAS cloud by default, the following articles might help:
Windows virtual machines are also available on CREODIAS.
If you, instead, want to use an image created by you, first you need to upload such an image by using the Horizon dashboard:
You can also use the OpenStack CLI client for that:
After that, you can use that image to create a virtual machine.
Step 1: Obtain S3 credentials
Obtain the S3 credentials which will be used for accessing the EODATA repository by following this article:
Step 2: Access the EODATA repository
Below are different methods of obtaining the EODATA repository. You can choose the ones that are most compatible with your needs.
Other methods not mentioned here might also work. However, if you use them, we might not be able to provide you with technical support.
Method 1: s3fs (Linux)
On virtual machines created using Ubuntu or CentOS default images, access to the EODATA repository using s3fs should be successfully configured during first boot if appropriate prerequisites are met.
If you are using a Linux virtual machine created using a custom image, you might be able to use this method as well.
Check How to mount eodata using s3fs in Linux on CREODIAS to learn more.
Method 2: boto3 (Python)
If you want to access the EODATA repository using Python, you can use boto3 for that purpose.
The following articles contain more information:
Method 3: s3cmd (Linux)
s3cmd can be used if you, say, don’t want to mount the EODATA repository as a file system.
Learn more here:
Method 4: goofys (Linux)
Like s3fs, goofys can be used to mount EODATA as a file system. If you prefer goofys, follow this article:
Method 5: rclone (Windows)
On virtual machines running Windows, access to the EODATA repository using Rclone should be automatically configured during first boot if appropriate prerequisites are met.
If this process is not successful, you can also configure it yourself.
Read this article to learn more: