- Create a Filespace
- Choose LucidLink Custom Filespace
- Define Filespace name
- Select "Other Cloud"
- Specify a HTTP or HTTPS endpoint URL (including PORT if required)
- Optional: specify Region if required
- Optional: specify Bucket name if required
- Review and confirm, finally Create Filespace
Ensure you have specified Configure advanced settings to provide a Bucket name if you've align your credentials policy against a particular object storage resource.
At this point that the Filespace is being set up - this will take a minute, please be patient. Next you will proceed to initialization of your file space with your object storage credentials. Please follow the instructions from our Initialize your Filespace FAQ
If there is a problem accepting your initialization parameters, and you have double checked to ensure everything supplied is accurate. Please do not close the LucidLink OS client, leave it where it is and consult below to proceed with a manual command-line initialization.
We are happy to assist at LucidLink Support however we encourage you to attempt a manual initialization.
If the standard initialization method did not complete successfully, a manual initialization via the command line might be required. Please do not delete your Filespace.
We can inject some parameters which might have been missed, and required, in the initial Create Filespace Step 1 such as HTTPS vs HTTP, Endpoint:Port, Region or Bucket name - if any of this information was incorrect or accidentally not supplied, don't despair!
Ensure that the LucidLink OS client is open and is prompting to "connect" or at your initialize error as it were in Step 2. Please leave this window open because in the background the LucidLink OS client daemon/service is successfully running.
If you are running an OS client without GUI (Linux) you can launch a LucidLink OS client daemon from your command line with "lucid daemon". Please ensure lucid daemon remains running in the background.
Open command line, terminal, depending on what OS client you are using and enter the following command, making sure to supply the full Filespace and domain, shared secret, endpoint:port, credentials and bucket name if required, followed by a provider "text" as a simple 1 word vendor identity ie. Minio
lucid init-s3 --fs <filespace.domain> --password <rootpassword> --endpoint <ipadddress/url:port> --access-key <access-key> --secret-key <secret-key> --https --region <region> --bucket-name <bucket> --Provider <vendor>
You should receive "Daemon init request sent." for a successful initialization.
Should your initial attempt not complete successfully, additional information for guidance might be provided in the error output, please update your combination of parameters and try again.
You can try multiple times, with parameters such as --http instead of --https for example, and in certain circumstances, parameters such as region are case sensitive. Until your initialization is successful your Filespace will be waiting patiently in the portal for this step to complete.
Should you want to see the full list of initialization parameters to troubleshoot please consult our command-line help with "lucid help init-s3" and of course reach out via our LucidLink Support should there be challenges.
Consult our Command-line Filespace initialization FAQ for guidance.
lucid init-s3 --fs myexample.filespace --password 12345 --endpoint myobjectstorageendpointandport:80 --access-key 6fa50f2185a0a0c094a3e --secret-key yAKs9SxkGsaHLS+rOef8D8UdGvELKYrBL/AfwLki/ --http --provider Minio
Note: If you did close the OS client in Step 2 receive "Connection refused" please ensure to open the OS client or launch a command line/terminal daemon with "lucid daemon". Also note the endpoint URL does not require http:// or https:// like it did through the portal as we supply this manually through our command line options of --https or --http