Who can use LucidLink Connect?
LucidLink Connect is available for purchase as an add-on for customers on the LucidLink Enterprise plan. Please reach out to your Sales representative for more information.
What filespace version supports LucidLink Connect?
Any filespace version 3.6 or above with LucidLink Connect enabled on the workspace level can use LucidLink Connect. Filespaces < v3.6 will need to be upgraded before they can be used with LucidLink Connect. Alternatively, a new filespace can be created for use with LucidLink Connect.
How is LucidLink Connect configured and accessed?
LucidLink Connect must be configured via the LucidLink API, but once linked, external assets can be accessed via any compatible LucidLink client version 3.6 or above.
Can I modify external entries?
No, external entries are read-only. They can be overwritten or "saved-as" once opened, but they cannot be modified in place. Entries overwritten in this manner become normal LucidLink assets stored in LucidLink-proprietary layout.
See the section on filesystem operations in the LucidLink Connect Overview article for more information.
Is LucidLink Connect protected by LucidLink's Zero-Knowledge Guarantee?
No, LucidLink Connect is not covered by LucidLink's Zero-Knowledge architecture. LucidLink’s zero-knowledge guarantee continues to apply to all non-external data stored within the filespace even when LucidLink Connect is enabled. Assets that are externally linked via LucidLink Connect are handled differently because they remain stored in customer-controlled external environments. More information is available in the LucidLink Connect Overview article.
What happens if I delete an S3 object that's linked from the bucket?
The external entry will remain in your filespace, but attempting to read the file will result in an error. You should delete the external entry when you delete the corresponding S3 object.
What happens if I modify an S3 object that's linked on the bucket side?
The external entry will remain in your filespace if modified, but attempting to read the file will result in an error. You will need to delete and relink the object.
Do external files count against my storage quota?
External entries linked with LucidLink Connect are billed in accordance with your negotiated LucidLink Connect rate, but do not count towards your LucidLink-backed storage quotas. LucidLink Connect entries are represented in frontend storage metrics (the size of the filesystem as it appears on your desktop / through the application).
Can multiple external entries point to the same S3 object?
Yes, you can create multiple external entries pointing to the same object at different filespace paths. Note that you will be charged additional storage costs for each additional link.
Are external files backed up in Lucid snapshots?
External file metadata (the link) is included in snapshots, but the actual S3 object data is not. Configuration of customer-provided S3 buckets and protection of the data inside them falls outside of LucidLink’s responsibility. Additionally, snapshots are a point-in-time representation of metadata, meaning that as URLs expire and are refreshed, they are not updated in the snapshot and access to that asset through the snapshot will fail. External entries are identifiable by the external entry icon.
What's the difference between external files and regular Lucid files?
| Feature | Regular Lucid Files | External Files |
|---|---|---|
| Layout | Chunked, client-side encrypted LucidLink layout | Native, whole-object format |
| Write Access | Full read/write | Read-only |
| Zero-knowledge | Zero-knowledge protected | Non zero-knowledge |
| Snapshots | Snapshot support | Customer responsible for data backup |
| Interoperability | Data cannot be placed directly in the bucket or accessed directly from the bucket, all data access must flow from LucidLink client | Can be accessed and used by third-party applications directly from the bucket |