Import to Wasabi

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 and Secret Key that are generated in a safe place.

Recommendations

Seagate strongly recommends the following best practices:

• Create a bucket dedicated to your Lyve Import project.
• 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:

• 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