You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
its a 2i2c hub's user environment and its 2i2c hub's associated cloud bucket
In this case, writing data should work straight away as credentials should be setup and available for the user as long as the user environment image has relevant cloud CLI tools installed like aws, gcloud, or az.
I know that the pangeo/pangeo-notebook is an image that includes the aws CLI of relevance for the showcase hub with an AWS bucket.
its their environment / laptop and its 2i2c hub's associated cloud bucket
In this case, they need to acquire and configure credentials manually first. They could either get temporary credentials by extracting such from a 2i2c user environment, or use dedicated credentials in the cloud project setup for them personally.
I think our working with object storage docs should explicitly distinguish the following scenarios:
its a 2i2c hub's user environment and its 2i2c hub's associated cloud bucket
In this case, writing data should work straight away as credentials should be setup and available for the user as long as the user environment image has relevant cloud CLI tools installed like
aws
,gcloud
, oraz
.I know that the
pangeo/pangeo-notebook
is an image that includes theaws
CLI of relevance for the showcase hub with an AWS bucket.its their environment / laptop and its 2i2c hub's associated cloud bucket
In this case, they need to acquire and configure credentials manually first. They could either get temporary credentials by extracting such from a 2i2c user environment, or use dedicated credentials in the cloud project setup for them personally.
Extracting temporary credentials is discussed in Access to buckets on AWS and GCP from local computers features#22 and isn't an established and user friendly procedure yet.
its their environment / laptop and its their cloud bucket
I don't think its in scope for 2i2c to help with this or write docs focused on this situation.
The text was updated successfully, but these errors were encountered: