I agree. Mounting the bucket on a Lightsail or EC2 instance using s3fs-fuse
or yas3fs, and running FITS there is a (moderately) easy and cheap solution.
On Fri, Jan 7, 2022 at 1:20 PM Steinberg, Benjamin <
[log in to unmask]> wrote:
> You could try s3fs: https://github.com/s3fs-fuse/s3fs-fuse
> If the archive is very large, you might not want to pay for egress, so you
> could consider running FITS on an EC2 instance.
> On 1/7/22, 12:50 PM, "Code for Libraries on behalf of Chris Mayo" <
> [log in to unmask] on behalf of [log in to unmask]> wrote:
> Hi all,
> I've recently become caretaker for a large audio archive, both
> physical and
> digital. I'm planning a large-scale digitization project for the
> that haven't been digitized yet, but the digital collection consists of
> both born-digital material and files that have been digitized from the
> physical collection at various points over the last 25 years.
> I've been requested to re-digitize files that don't meet modern
> so I need to run FITS over the entire digital archive. The hang-up is
> the archive lives in an Amazon S3 bucket which is the backend of the
> we use to serve files to clients. I can't figure out how to point FITS
> the bucket, since it's not mounted to my local system, and I can't
> the path properly. Has anyone else tried this?
The Cherry Hill Company