Yes, I agree, that’s an interesting idea.  We use S3 for backup of our image data, but the files aren’t accessible by regular workstations unless you have some special software or a special storage gateway in the middle. S3 files don’t use the same sort of filesystem (CIFS) that TMS wants to work with.  Without something “special” going on, you can’t treat S3 as a typical external fileserver on a Windows computer.

And as always, I’m curious about who (if anyone) is using Amazon AWS servers for any portion of their TMS system…

-Steve


Steve Rothman, Systems Administrator
Peabody Museum of Archaeology and Ethnology  -  mobile: 617-517-4855 or x5-9968



Thanks for posting this, Peter! I'd be curious to hear from anyone using this on how it's going. Storage space has become a big issue for us.


Fatima Mahdi
Collections Information Specialist/TMS

Virginia Museum of Fine Arts




On Wed, Nov 7, 2018 at 4:42 PM Dueker, Peter <[log in to unmask]<mailto:[log in to unmask]>> wrote:
Hello TMS users,

We are looking at using an Amazon S3 bucket for some of our TMS media records – these are PDFs of agreements that are not managed in our DAM (which manages access for collection images).  We are trying to figure out the best way to set appropriate permissions at the S3 level – we want all TMS users to be able to access the PDF’s.

I'm still new to the S3 permission structure and haven’t yet figured out the optimal way to configure security for TMS access.

Are any of you using S3 to store assets for TMS? Suggestions / thoughts on the best approach esp. re: permissions would be appreciated!

Peter Dueker
National Gallery of Art, Washington



To unsubscribe, send an email to [log in to unmask] with the following commands in the body of the email:

     signoff TMSUSERS

     //  eoj


You will receive a confirmation that your subscription has been removed.