Import to IBM Cloud

Prerequisites

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 IBM Cloud bucket to import your data:

Seagate authorizations

Seagate requires permissions to read, write, and list to your bucket 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, follow the steps below after creating your bucket:

1. In your Object Storage instance, click the Service credentials tab.
2. Click the New Credential button.





3. Name the credential and make the following selections:
   • Role = None
   • Service ID = Auto Generated
   • Include HMAC Credential = On
   
   

   

   Click the Add button. Once added, you can expand the credentials to view the values for the access key ID and secret access key.

Proceed through the steps below to edit the access policy for the service ID:

1. Navigate to the IAM console by clicking Manage > Access (IAM). Click Service IDs in the side panel. Click on the service ID you want to edit.
2. Under Access policies, locate the role with the access policy you want to edit. Click the Actions icon and select Edit.





3. Click on the Resources tab and select Edit. Select Specific resources and add conditions to scope access to specific resources.





4. Click Next to continue to the Roles and actions tab. In the Service access column, assign the Writer role. Click Review.





5. Click Save.

Recommendations

Seagate strongly recommends the following best practices:

• Create a bucket dedicated to your Lyve Import project.
• When creating your bucket, select “Regional” for resiliency.
• Block all public access for your bucket.
• Disable or delete the HMAC key after the cloud import project has ended.

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 ID and Secret Access Key. (If you need to update the import destination first, click on the Import Destinations step and edit.)


 Characters you enter in these fields are always masked.



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


 Each storage device in your project will have a designated folder in your bucket. 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 bucket 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 bucket that you would like to import your files to, provide the name of this folder.
• Important—Make sure that your bucket 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.
5. Click Validate Credentials.


 If the validation fails, check that the access ID, secret, and bucket name entered are accurate, and then revalidate.
6. Check the box to confirm that you have read and understand the details in IP Address Access
7. 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

Bucket naming guidelines:

• Must be unique across the whole IBM Cloud Object Storage system.
• Do not use any personal information (any part of a name, address, financial or security accounts or SSN)
• Must start and end in alphanumeric characters (3 to 63)
• Characters allowed: lowercase, numbers and nonconsecutive dots and hyphens
• Avoid using these characters: / \ “ ? < > 1 . This will not cause issues with IBM Cloud Object Storage but may cause issues with your applications.

Object naming guidelines:

• Object keys can be up to 1024 characters in length, and it’s best to avoid any characters that might be problematic in a web address. For example, ? , = , < , and other special characters might cause unwanted behavior if not URL-encoded.

Troubleshooting

See the following knowledge base articles:

• FAQ
• Support