This page shows you the mapping of s3cmd commands to their gdcloud CLI equivalent. See the following table:
| s3cmd command | gdcloud command |
| s3cmd put LOCAL_PATH s3://REMOTE_PATH | gdcloud storage cp LOCAL_PATH s3://REMOTE_PATH |
| s3cmd cp s3://REMOTE_SOURCE_PATH s3://REMOTE_MOVE_DESTINATION_PATH | gdcloud storage cp s3://REMOTE_SOURCE_PATH s3://REMOTE_MOVE_DESTINATION_PATH |
| s3cmd mv s3://REMOTE_SOURCE_PATH s3://REMOTE_MOVE_DESTINATION_PATH | gdcloud storage mv s3://REMOTE_SOURCE_PATH s3://REMOTE_MOVE_DESTINATION_PATH |
| s3cmd put FILE [FILE...] s3://BUCKET[/PREFIX] | gdcloud storage cp FILE [FILE...] s3://BUCKET[/PREFIX] |
| s3cmd get s3://BUCKET/OBJECT LOCAL_FILE_TO_SAVE | gdcloud storage cp s3://BUCKET/OBJECT LOCAL_FILE_TO_SAVE |
| s3cmd ls s3://FULLY_QUALIFIED_BUCKET_NAME | gdcloud storage ls s3://FULLY_QUALIFIED_BUCKET_NAME |
| s3cmd ls s3://FULLY_QUALIFIED_BUCKET_NAME/<Prefix>/ | s3cmd ls s3://FULLY_QUALIFIED_BUCKET_NAME/<Prefix>/ |
| s3cmd put FILE [FILE...] s3://BUCKET[/PREFIX] | s3cmd cp FILE [FILE...] s3://BUCKET[/PREFIX] |
| s3cmd modify s3://BUCKET1/OBJECT | Note that the following command is not supported at this time: gdcloud storage objects update s3://BUCKET1/OBJECT --custom-metadata=Key1=Value1 |
| s3cmd mv s3://BUCKET1/OBJECT1 s3://BUCKET2[/OBJECT2] |
gdcloud storage mv s3://BUCKET1/OBJECT1 s3://BUCKET2[/OBJECT2].
Note that the following flags are not supported at this time: --disable-multipart --multipart-chunk-size-mb=SIZE |
| s3cmd del s3://BUCKET/OBJECT | gdcloud storage rm s3://BUCKET/OBJECT |