Technical
Lynx Storage - ir.attachment Routing
Keep attachments in object storage, not on the server disk
lynx_storage_attachment
· v19.0.1.4.0
Storage Attachments routes Lynx attachments to an S3-compatible object storage backend configured in Lynx Storage. You choose the policy: object storage first, local first, or only files above a size threshold. Documents the platform needs to run, such as invoice PDFs, signed originals and compiled assets, always stay on the local filestore.
A migration wizard moves existing attachments from the local filestore to object storage (or back), with a dry run first. Requires Lynx Storage.
Why teams pick it
What Lynx Storage - ir.attachment Routing does for you
Routing policy
Object first, local first or a size threshold, set per company.
Migration wizard
Move existing files from disk to object storage in batches, with a dry run preview.
Critical files stay local
Invoices, signed documents, logos and asset bundles never leave the local filestore.
Safe fallback
If object storage is full or unreachable, the file is saved locally and storage managers are notified.
Routing log
Every placement decision is logged with its reason, and orphaned objects are cleaned up hourly.
Try Lynx Storage - ir.attachment Routing on your team.
Free trial, no credit card. Talk to sales when you're ready.