Cloud Import Service User Manual & Reference Guide
Cloud Import Service 

Was this content helpful?

Import to OVHcloud


Before you can configure and submit your import plan, make sure to complete the following steps so that Lyve Import Service can securely access your specified OVHcloud container to import your data:

OVHcloud subscription—Set up an OVHcloud account.

OVH Public Cloud project—Set up a OVHcloud Public Cloud project. To learn more, see Creating your first OVHcloud Public Cloud project.

OVHcloud container—Set up a dedicated object container for your import. To learn more, see Object Storage - Creating a bucket.

OVHcloud Public Cloud instance—Set up an instance. To learn more, see Creating an instance.

IP address access—If configured by your organization, list Seagate’s IP address(es) as an allowed source. See IP Address Access.

Seagate authorizations—Seagate requires permissions to read, write, and list to your container to perform the import. Hash-based message authentication code (HMAC) keys using an access ID and secret are required to authenticate requests to your cloud resources. To generate the HMAC keys, select an existing user or create a new user to link to your container. Set Read and write access to your container for this user. Once the user has been created and added to your container, you will see the credentials.

To learn more, see Object Storage - Identity and access management.


Seagate strongly recommends the following best practices:

  • Create a container dedicated to your Lyve Import project.
  • Block all public access for your container.
  • Disable or delete the HMAC key after the cloud import project has ended.
 Important note on file sizes—In general, Seagate does not recommend importing individual files larger than 5TB. Please refer to your cloud provider’s file size limitations and best practices.

Configure your import plan

Enter credentials

  1. In Lyve Management Portal, click Import Plans in the navigation bar, and then click Configure Plan.

  2. Enter your Access Key and Secret Access Key. (If you need to update the import destination first, click on the Import Destinations step and edit.)

  3.  Characters you enter in these fields are always masked.

  4. Enter your container name. The name is case-sensitive and must match exactly.
  5. (Optional) Enter a name for your folder.

  6.  Each storage device in your project will have a designated folder in your container. The device’s serial number will be automatically appended to the folder name at the time of import.

    • Provide a name for Seagate to use to create the folder(s) in your container on your behalf. (Recommended)
    • If you leave this field blank, Seagate will create a folder(s) for your files and will use the device’s serial number as its name.
    • Alternatively, if you have an existing folder within your container that you would like to import your files to, provide the name of this folder.
    • Important—Make sure that your container policy does not block folder creation. If you are providing a name for a new folder to be created, ensure that the name follows the Naming Guidelines.
  7. Click Validate Credentials.

  8.  If the validation fails, check that the access, secret access key, and container name entered are accurate, and then revalidate.
  9. Check the box to confirm that you have read and understand the details in IP Address Access.
  10. Click Next.

Review and submit your import plan

  1. Review your import destination and credential details.
  2. Check the box to confirm that you’ve read and understand the information in this reference guide.
  3. Click Submit Plan.

Inviting another user to configure an import plan

If a different member of your organization needs to configure the import plan for a project, you can invite them to do so in Lyve Management Portal. See Invite Another User to Configure an Import Plan.

Naming guidelines

Container naming guidelines:

  • Must be between 3 and 63 characters long.
  • Must begin and end with lower case alphanumeric characters (a to z and 0 to 9).
  • Must be unique within the same OVHcloud region.
  • May contain the following punctuation marks: . and - .
  • Must not contain multiple punctuation marks in a row ( .. or -. or .- or -- ).
  • Must not look like an IP address (for example,

Best practices

See the following knowledge base article:


See the following knowledge base articles: