Esse conteúdo foi útil?
Como poderíamos tornar este artigo mais útil?
This guide explains how to configure third-party clients including AWS CLI, Cyberduck, Mountain Duck, or S3 Browser to manage data in Lyve Cloud. Lyve Cloud is an S3-compatible storage service for data-intensive applications such as data backup and analytic workloads, that leverage multi-petabyte data lakes. You can also use any other compatible third-party client to copy and move files, manage files and folders, and synchronize folders between Lyve Cloud and your local storage, once you've established a connection.
This document and its subtopics provide instructions about how to:
Use Cyberduck to connect with Lyve Cloud and transfer your data. For more information, review the Cyberduck Tutorial and Cyberduck Quick Reference Guide.
To enable and register the S3 (HTTPS) profile:
Alternatively, to register the S3 (HTTPS) profile:
Bookmarks store the details of the connection to easily re-connect to the server.
To connect Cyberduck to Lyve Cloud:
Field Name | Description |
---|---|
Nickname | Enter a name for the bookmark. |
URL | Displays the URL once you enter the server and access key in the following format:http:// <Access Key ID><Server> |
Server | Enter Lyve Cloud S3 endpoint. For more information see S3 API endpoints. Lyve Cloud supports only region-specific S3 endpoints. To access buckets created in different regions in the S3 client, add an endpoint connection for each of the regions. Tip—Copy the URL without https:// |
Port | Enter 443 as the port number to access the server. |
Access Key ID | Enter your access key, a private key for authentication to connect a bucket created in Lyve Cloud. The access key is displayed when you create a new service account in Lyve Cloud. A service account contains bucket credentials for Lyve Cloud to access a bucket. For more information, see Creating service accounts. |
Secret Access Key | Enter your secret key, a private key password for authentication to connect a bucket created in Lyve Cloud. The secret key displays when you create a new service account in Lyve Cloud. For more information, see Creating service accounts. |
Seagate on Vimeo: Lyve Cloud - How to connect Cyberduck to Lyve Cloud
Perform various actions once a connection is established between Cyberduck and Lyve Cloud. For more information, see Cyberduck Help.
To upload data to a bucket:
To download data to local storage:
To delete data from the bucket:
To create a new folder:
To delete a folder:
To disconnect Cyberduck from Lyve Cloud:
Use S3 Browser to connect with Lyve Cloud and manage your data transfer. For more information on S3 Browser see, S3 Browser Help.
To connect S3 Browser to Lyve Cloud:
Field Name | Description |
---|---|
Account name | Enter an account name. |
Account type | Enter the account type. Select S3 Compatible Storage from the list. |
REST Endpoint | Enter Lyve Cloud S3 endpoint. For more information see S3 API endpoints. Currently, Lyve Cloud supports only region-specific S3 endpoints. To access buckets created in different regions in the S3 client, add an endpoint connection for each of the regions. |
Access Key | Enter your access key.The access key displays when you create a new service account in Lyve Cloud. A service account contains the bucket credentials for the Lyve Cloud bucket.For more information, see Creating service accounts. |
Secret Key | Enter your secret key.The secret key displays when you create a new service account in Lyve Cloud.For more information, see Creating service accounts. |
Use secure transfer (SSL/TLS) | Select this option to ensure all communication with the storage passes through encrypted SSL/TLS. |
Advanced S3 Compatible storage settings | Select the signature version and addressing model in the advanced settings. For more information, see Advanced S3 compatible storage settings below. |
Field Name | Description |
---|---|
Signature Version | Select Signature V4.For more information, see S3 Browser's help documentation. |
Addressing Model | Path Style is selected by default and is the recommended setting.For more information, see S3 Browser's help documentation. |
Seagate on Vimeo: Lyve Cloud - How to use S3 Browser with Lyve Cloud
Perform various actions once the connection between S3 Browser and Lyve Cloud is established. For more information, see S3 Browser's help documentation.
To upload data to a bucket:
To download data to your local machine:
The Tasks tab displays the upload or download progress.
To delete data from a bucket:
To create a new folder:
To delete a folder:
To disconnect S3 browser:
Use Mountain Duck to mount your Lyve Cloud storage as a disk in the Windows File Explorer or Mac OS Finder, and manage your files through a familiar interface. For more information on Mountain Duck see, Mountain Duck Help.
To connect Mountain Duck to Lyve Cloud:
Field Name | Description |
---|---|
Nickname | Enter a unique name. This will be the name of your connection bookmark. |
Server | Enter the endpoint based on the region. To select endpoint see, the section called “S3 API endpoints”.Currently, Lyve Cloud supports only region-specific S3 endpoints. To access buckets created in different regions in the S3 client, add an endpoint connection for each of the regions. |
Port | This should populate as 443. If not, enter that port number. |
Access Key ID | Enter your access key ID. For more information, see the section called “Creating service accounts”. |
Secret Access Key | Enter your secret key.For more information, see the section called “Creating service accounts”. |
Drive Letter(Windows only) | Enter a drive letter so that Mountain Duck always uses that same letter for the mounted drive. |
When connected, the drive and folder contents display their sync status. Look for a circle in the lower-left corner of the folder or file icon. Once mounted, all the files are stored on your local drive.
icon | Meaning |
---|---|
In Progress. Synchronization is in progress for this item. | |
In sync. This item is selected to be synced, and the content will always be available offline. | |
Sync error. This item cannot be synchronized. | |
Up to date. This item is synced and up to date. | |
Ignored. The file is available in its temporary location and never synced to cloud or remote storage. | |
Paused. The sync on that item is paused. | |
Online only. This item is available in the cloud but can be opened and edited when you have an active connection to the server. |
To learn more about various Mountain Duck options and sync modes, see Mountain Duck’s Help documentation.
Seagate on Vimeo: Lyve Cloud - How to mount Lyve Cloud as a local drive on Windows with Mountain Duck
Once your Lyve Cloud storage is mounted as a drive, managing your files works much the same as working in any other network drive. Many of these operations may only be performed once a given bucket has synced with the local drive. Learn more about Mountain Duck’s user interface documentation.
To copy data:
You can also drag and drop the data from one folder to another. If the bucket's or your service account’s permissions do not allow you to write to that bucket, an error message appears.
To delete bucket data:
To create a folder in a bucket:
The new folder immediately begins syncing with its Lyve Cloud destination.
To disconnect Mountain Duck from Lyve Cloud:
A notification pop-up appears when the connection is broken.
Windows | Mac |
---|---|
Use rclone to connect with Lyve Cloud and manage your files from the command line, or mount the cloud storage as a drive.
You will need the access key and secret key for each account you’ll be using to connect with Rclone. For more information, see Creating service accounts.
To configure a remote connection with Rclone:
n
for a new remote.No remotes found - make a new one n) New remote s) Set configuration password q) Quit config n/s/q> n
name> <Name>
Type the storage to configure. Choose a number from below, or type in your own value 1 /Fichier \(fichier) 2 /Akamai NetStorage \(netstorage) 3 / Alias for an existing remote \ (alias) 4 / Amazon Drive \ (amazon cloud drive) 5 / Amazon S3 Compliant Storage Providers including AWS, Alibaba, Ceph, Digital Ocean, Dreamhost, IBM COS, Lyve Cloud, Minio, RackCorp, SeaweedFS, and Tencent COS \ (s3) 6 / Backblaze B2 \ (b2) [snip] 46 / seafilehttp Connection \ (seafile) Storage> 5
Choose the S3 provider. Choose a number from below, or type in your own value Press Enter for the default ("") 1 / Amazon Web Services (AWS) S3 \ (AWS) 2 / Alibaba Cloud Object Storage System (OSS) formerly Aliyun \ (Alibaba) 3 / Ceph Object Storage \ (Ceph) 4 / Digital Ocean Spaces \ (DigitalOcean) 5 / Dreamhost DreamObjects \ (Dreamhost) 6 / IBM COS S3 \ (IBMCOS) 7 / Seagate Lyve Cloud \ (LyveCloud) 8 / Minio Object Storage \ (Minio) 9 / Netease Object Storage (NOS) \ (Netease) 10 / RackCorp Object Storage \ (RackCorp) 11 / Scaleway Object Storage \ (Scaleway) 12 / SeaweedFS S3 \ (SeaweedFS) 13 / StackPath Object Storage \ (StackPath) 14 / Storj (S3 Compatible Gateway) \ (Storj) 15 / Tencent Cloud Object Storage (COS) \ (TencentCOS) 16 / Wasabi Object Storage \ (Wasabi) 17 / Any other S3 compatible provider \ (Other) Provider>7
Get AWS credentials from the runtime (environment variables or EC2/ECS meta data if no env vars). Only applies if access_key_id and secret_access_key is blank.Enter a boolean value (true or false). Please Enter for the default ("false").Choose a number from below, or type in your own value 1 / Enter AWS credentials in the next step \ "false" 2 / Get AWS credentials from the environment (env vars or IAM) \ "true" env_auth>false
AWS Access Key ID. Leave blank for anonymous access or runtime credentials. Enter a string value. Press Enter for the default ("") access_key_id> <access key> AWS Secret Access Key (password) Leave blank for anonymous access or runtime credentials. Enter a string value. Press Enter for the default ("") secret_access_key> <secret key>
Region to connect to. Leave blank if you are using an S3 clone and you don't have a region. Enter a string value. Press Enter for the default ("") Choose a number from below, or type in your own value 1 / Use this if unsure. | Will use v4 signatures and an empty region. \ () 2 / Use this only if v4 signatures don't work. | E.g. pre Jewel/v10 CEPH. \ "other-v2-signature" region> <>
Endpoint for S3 API. Required when using an S3 clone. Choose a number from below, or type in your own value. Press Enter to leave empty. 1 / Seagate Lyve Cloud US East 1 (Virginia) \ (s3.us-east-1.lyvecloud.seagate.com) 2 / Seagate Lyve Cloud US West 1 (California) \ (s3.us-west-1.lyvecloud.seagate.com) 3 / Seagate Lyve Cloud AP Southeast 1 (Singapore) \ (s3.ap-southeast-1.lyvecloud.seagate.com) endpoint> 1
Location constraint - must be set to match the Region. Leave blank if not sure. Used when creating buckets only. Enter a string value. Press Enter for the default ("")location constraint>
Canned ACL used when creating and or storing or copying objects. This ACL is used for creating objects and if bucket_acl isn't set, for creating buckets too. Note that this ACL is applied when server-side copying objects as S3 It doesn't copy the ACL from the source but rather writes a fresh one. Enter a string value. Press Enter for the default ("") Choose a number from below, or type in your own value 1 / Owner gets FULL_CONTROL. | No one else has access rights (default). \(private) 2 / Owner gets FULL_CONTROL. | The ALLUsers group gets READ access. \(public-read) 3 /Owner gets FULL_CONTROL. | The ALLUsers group gets READ and WRITE access. [snip] acl>1
Edit advanced config? (y/n) y) Yes n) No (default) y/n>n
NAME] type = s3 Provider = LyveCloud env_auth = false access_key_id = xxx secret_access_key = yyy region = us-west-1 endpoint = s3.us-east-1.lyvecloud.seagate.com acl = private
y) Yes this is OK (default) e) Edit this remote d) Delete this remote y/e/d>y
Current remotes: Name Type ==== ==== ashrcl s3 e) Edit existing remote n) New remote d) Delete remote r) Rename remote c) Copy remote s) Set configuration password q) Quit config e/n/d/r/c/s/q>q
Seagate on Vimeo:Lyve Cloud - How to configure Rclone
Prior to mounting Lyve Cloud as a drive, connect and test the connection by viewing the contents of one or more buckets using the rclone ls command.
To mount Lyve Cloud as a drive, use this command where:
rclone mount remote:path/to/files /path/to/local/mount
For more information, see Rclone’s mount command documentation.
Here are several of the more commonly-needed commands for viewing and managing your data from the command line. See the Rclone docs, including information on global flags, for additional information.
There are three list commands with easily readable output available: ls, lsd, and lsl.
rclone ls remote:path [flags]
rclone lsd remote:path [flags]
Or
rclone lsd remote: [flags]
rclone lsl remote:path [flags]
Seagate on Vimeo: Lyve Cloud - How to use Rclone list commands
rclone copy C:/path/to/filename remote:path [flags] rclone copy filename remote:path
Seagate on Vimeo: Lyve Cloud - How to use Rclone Copy-to and Copy-sync Commands.
This is the same as copying, but the source path is something in the remote or in a bucket, while the destination path is on your local storage.
rclone copy remote:path C:/path/to/filename [flags]
rclone delete remote:path [flags]
rclone --min-size 100MB delete remote:path
To delete only a specific file:
rclone deletefile remote:path [flags]
Learn more about rclone delete and deletefile.
To create a new folder:
rclone mkdir blue
Create folders in other paths, or with other permissions, by setting the proper flags. Learn more about mkdir.
rclone rmdir blue
rclone rmdirs blue
The folders must be empty for rmdir
or rmdirs
to work.
Learn more about rmdir
and rmdirs
.
[REMOTE NAME]type = s3provider = Otherenv_auth = falseaccess_key_id = XXXXXXXXXXsecret_access_key = YYYYYYYYYYYYYYYYYYYYYYYYYYYendpoint = https://s3.us-east-1.lyvecloud.seagate.comacl = privateregion = us-east-1
$ rclone copy SOURCE REMOTE:[SOURCE BUCKET] <TARGET REMOTE>[TARGET BUCKET>/<PREFIX>]
$ rclone copy SRT:[ SB ] TRT:[TB]
$ rclone copy SRT:[ SB ]/mypath1 TRT:[TB]/mypath1
To delete a remote from Lyve Cloud, delete the remote’s name using this command, changing REMOTE_NAME to the name of the remote to disconnect:
rclone config delete REMOTE_NAME [flags]
Learn more about config delete
.
To migrate data:
rclone sync <source remote name>:path <target remote name>:path
--progress
Displays the real-time transfer progress.--interactive
: Enables interactive mode and displays interactive for every action taken.For more information on RClone, see https://rclone.org/s3/.
Seagate on Vimeo: Lyve Cloud - Use Rclone Delete and Purge commands.