Differences

This shows you the differences between the selected revisions of the page.

2018-02-20 2019-06-13
do not repeat S3 acronym (martin) when keys do not have permissions to list buckets (martin)
Line 21: Line 21:
The //[[task_create_directory|Create directory]]// command in the root folder in fact creates a new bucket. The //[[task_create_directory|Create directory]]// command in the root folder in fact creates a new bucket.
-You will not see buckets that were shared with you by another AWS user, in the root listing. To access such buckets, you have to specify ''/bucketname'' as an initial //[[ui_login_directories|Remote directory]]//, when setting up your %%S3%% session.+You will not see buckets that were shared with you by another AWS user, in the root listing. To access such buckets, you have to specify ''/bucketname'' as an initial //[[ui_login_directories|Remote directory]]//, when setting up your %%S3%% session. Similarly, when your access key does not have permissions to list buckets, you will need to specify the path to the desired bucket the same way. In [[scripting]], you do that by appending the path to the bucket to a [[session_url|session URL]]: ''s3://accesskey:secretkey@s3.amazonaws.com/bucket/''.
===== Further reading ===== ===== Further reading =====
  * Guide to [[guide_upload|uploading files to server]];   * Guide to [[guide_upload|uploading files to server]];
  * Guide to [[guide_automation|automating operations]] (including upload).   * Guide to [[guide_automation|automating operations]] (including upload).

Last modified: by martin