Container data inside FileMaker grows your database file, slows down loads, and forces volume expansions. The S3 SideCar lets you offload that data to Amazon S3 - with file uploading, listing, direct web-viewer uploads, MD5 verification, and a simple API your FileMaker scripts can call.
Amazon S3 (Simple Storage Service) is AWS’s object storage service: massively scalable, with 99.999999999% durability and high availability at competitive pricing. The Soliant.cloud S3 SideCar is a highly available microservice built on a well-supported SDK that gives your FileMaker application secure, programmatic access to S3 - without you needing to maintain AWS integration code.
An object is binary data plus a key (effectively a filename and location). Objects live in buckets that support default encryption, versioning, lifecycle policies, and fine-grained access controls. The SideCar handles the boilerplate so your FileMaker scripts treat S3 like a simple, reliable file store.
Six capabilities, all callable from FileMaker scripts via a simple API.
Move container data from your FileMaker database to Amazon S3 directly. Database file size shrinks, performance improves, and your container data is now in the same storage AWS uses for petabyte-scale workloads.
The SideCar exposes object listing and bucket queries via a simple API, so your FileMaker scripts can browse, paginate, and search S3 contents without managing the underlying SDK.
Users upload files straight into S3 from a FileMaker web viewer - bypassing local storage and dramatically reducing the database server’s I/O load on large file uploads.
Every transfer is verified with MD5 hashing so you have cryptographic confirmation that what you uploaded matches what landed in S3. No silent corruption.
Reference files by their S3 URL instead of pulling container data through your database. Lower latency, lower database load, faster perceived performance.
The SideCar is built on a well-supported AWS SDK so authentication, retries, and AWS service updates are handled correctly without you maintaining integration code.
Moving container data to S3 changes the cost and performance profile of your FileMaker solution.
For initial migrations of very large data sets, AWS Snow Cone devices are supported - physical transfer hardware shipped from AWS for moving terabytes of data into S3 without saturating your internet connection. We can include a sample FileMaker file demonstrating the SideCar integration.
Every Soliant.cloud instance includes SnapBack. As your solution matures, add SideCar microservices designed specifically for FileMaker on AWS.
Built-in backups stored off-instance in Amazon S3 - 15-minute RPO, ransomware-isolated, included with every package.
Learn more →Spin WebDirect servers up and down with user demand. Cut multi-machine deployment costs by up to 80%.
Learn more →A fully functional copy of your FileMaker Server in the cloud - launch from the client portal in minutes.
Learn more →Schedule when your FileMaker instances run. Power down dev or after-hours environments; resume on schedule.
Learn more →Encrypted, walled-off snapshots to independent object storage - for compliance and risk-mitigation requirements.
Learn more →Fault-tolerant queueing for webhooks from Stripe, QuickBooks Online, Shopify, and any JSON-sending service.
Learn more →Real-time synchronous webhook proxy - for when the calling service needs immediate confirmation.
Learn more →If your FileMaker database is bloated with container data, the S3 SideCar is the fix. Let’s look at your storage profile and put together a plan.
Get a Quote