Import to Wasabi S3

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 Wasabi 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 Key ID and Secret Access Key are required to authenticate requests to your cloud resources. To generate the HMAC keys, follow the steps below after creating your bucket:

1. Using Wasabi’s console, create a policy.
2. Copy the provided JSON script below to paste into your policy document:



		{
			“Version”: “2012-10-17”,
			“Statement”: [
				{
					“Effect”: “Allow”,
					“Action”: “s3:*”,
					“Resource”: [
						“arn:aws:s3:::{yourbucketname}”,
						“arn:aws:s3:::{yourbucketname}/*”
					]
					“Condition”:{}
				}
			]
		}       

3. Replace {yourbucketname} with your actual S3 bucket name. Click Create Policy.
4. Create a user with programmatic access and attach the policy you created to this user. To learn more, see Creating a User Account and Access Key.
5. Record the Access Key ID and Secret Access Key that are generated in a safe place.

Recommendations

Seagate strongly recommends the following best practices:

• Create a bucket dedicated to your import plan.
• Block all public access for your bucket.
• Disable or delete the HMAC key after the import plan has ended.

Configure your import plan

Add your cloud destination credentials and bucket information to configure your cloud import plan. 

• All devices within a subscription must be imported to the same destination and region.
• You will be required to enter and validate your bucket credentials.

1. On your Home page, select a Lyve Mobile service subscription that includes a Cloud Import plan.

Alternatively, select the More icon in the 'Actions' column, and then select View Subscription.

2. Select the link at the top of the page:

3. Confirm the Cloud Destination and Region. Select Next.
4. Add the Access Key ID and Secret Access Key for your cloud destination. Specify an existing bucket for the subscription. Select Validate Credentials.

5. (Optional) Under 'Customized Path', provide the name of an existing folder or provide a folder name for Seagate to use to create a new folder for import. If you don’t provide a folder name, Seagate will create a folder based on the device serial number and date.

6. To enable the checkbox, select the IP Address Access Guide link.
7. Select the checkbox, and then select Submit.

Inviting another user to configure an import plan

If a different member of your Org needs to configure the import plan for a Lyve Mobile subscription, you can invite them to do so in Lyve Management Portal.

• The person must be a member of the Org containing the Lyve Mobile subscription to which you want to add the import plan. See Manage Org members in the Lyve Management Portal User Manual.
• The member must be given the Manage Import Plans permission. See Manage subscription members in the Lyve Management Portal User Manual.

Naming guidelines

Bucket naming guidelines:

• The name must be unique across all existing bucket names in Wasabi.
• A bucket name must:
• Be a valid DNS-compliant name
• Begin with a lowercase letter or number, and
• Consist of 3 to 63 lowercase letters, numbers, periods, and/or dashes.
• The name cannot contain underscores, end with a dash, have consecutive periods, or use dashes adjacent to periods.
• The name cannot be formatted as an IP address (for example, 123.45.678.90).

Characters to avoid:

• % (percent)
  < (less than symbol)
  > (greater than symbol)
  \ (backslash)
  # (pound sign)
  ? (question mark)
• Certain file names may have non-ASCII characters that are 4 byte UTF8 characters (such as emojis). Wasabi does not support these characters and will return a 400 error message to an application that tries to write a file with 4 byte UTF characters in the file name. We recommend renaming the affected files, if possible.

Troubleshooting

See the following knowledge base articles:

• FAQs
• Troubleshooting