For an overview of the Filespace initialization process and demonstration of Wasabi and LucidLink working together click here.
In order to begin you will require your credentials from your Wasabi account. These come in the form of Access and Secret Access Keys.
To obtain your Wasabi keys please login to your account. Select "Users", and select an existing user and expand the "User Access Keys" sidebar entry and select "Create New Access Key".
Alternatively, you can create a new user specific to your LucidLink workloads or separate users and credentials for each of your Filespaces:
1. Select "Create User" and tick "Programmatic (create API key).
2. Assign AmazonS3FullAccess policy to your user or create and provide your own custom policy.
AmazonS3Full Access—Gives full access to all S3 resources, but no IAM access.
Your custom policy could limit access to a specific bucket to further restrict credential access across S3 compatible resources - see below an example restrictive user policy.
3. Confirm everything is correct and "Create User".
4. You'll be presented with your Access Key and need to select "show" to expose your Secret Key.
Note your secret access key will only be available to you once, please make store these in a secure location or download the credentials.csv
Once you have your Access and Secret Access Key you can create your LucidLink Filespace, selecting "Your Storage" and please select "Wasabi Cloud" as your Filespace object storage vendor.
Choose your Wasabi region. Selecting a region closest to your client devices offers the best performance. Keep in mind that your storage provider pricing may vary by region.
If preferred your can provide your own bucket name (optional), although we will create a bucket based on your Filespace name and GUID. Please review and confirm to create your Filespace.
You will note your Filespace is being prepared. This will take, up to, a couple of minutes to complete.
Once your freshly created Filespace is ready for initialization. Please follow the steps within the portal to install your LucidLink OS client and provide your Access and Secret Access Key to successfully initialize your Filespace.
To initialize your Filespace you will be prompted for a root password. This password is associated with you root user account, and used to AES-256 encrypt your filespace to prevent unauthorized access to your data. Should you have any trouble initializing your filespace, please do not hesitate to reach out to LucidLink Support.
An example custom policy to assign a user which only has access to the minimum S3 APIs required for a Filespace and applied to a specific bucket-name:
{
"Version": "2012-10-17",
"Statement": [
{
"Effect": "Allow",
"Action": [
"s3:PutObject",
"s3:GetObject",
"s3:ListBucket",
"s3:DeleteObject"
],
"Resource": [
"arn:aws:s3:::<bucket-name>/*",
"arn:aws:s3:::<bucket-name>"
]
}
]
}
The policy allows a specific User to access only a specific pre-allocated bucket, this bucket must exist and can be specified during Filespace creation by selecting "Configure advanced settings" and providing the exact "Bucket name".
"Configure advanced settings" in conjunction with policy to specify the exact bucket-name when you create your Filespace.
If you wish to specify additional options you can initialize manually with our command line, please review "lucid help init-s3" for further details such as data layout block size. Review our guide on command-line Filespace initialization for more information.
Example initialization string:
lucid init-s3 --fs <filespace.domain> --password <rootpassword> --endpoint s3.us-west-1.wasabisys.com --region us-west-1 --access-key <accesskey> --secret-key <secretkey> --block-size 256 --https --provider Wasabi
Consult Wasabi - Service URLs for information on Wasabi regions.
Note: Wasabi recommends storing around 100 million objects per-bucket. Learn more about choosing a filespace block size for more information on how this may affect your filespace size.
Please note that Wasabi charges an early deletion fee for data stored less than 90 days. This can affect short term archive data stored on object storage. If you are planning to store data where the typical retention period is less than 90 days, you will incur additional charges. For example, if you delete your data on day 14, Wasabi will charge you for the amount of active storage days the object existed (14), as well as a pro-rated charge for the remaining days (76).
When using LucidLink your data is split into chunks that represent the filespace block size. In a backup scenario, with synthetic, forever-incremental operations, chunks are deleted upon merge in existing files every time a new restore point is created. The data deleted on a given day is equivalent to the size of the oldest incremental, or the effective daily change rate (1-10% of the total dataset). This means you need to be careful with data the retention model chosen, as you may be charged for daily changes and there may not be cost gains from having a retention period shorter than 90 days.
Note: In some cases you may find it is possible to contact Wasabi support to reduce early deletion charges. For more on this see Wasabi - Pricing.