I was among the thousands of attendees of yesterday's Amazon AWS Summit in New York. One of the key services announced was Zocalo, a file storage and sharing service for the enterprise.
One aspect of the Zocalo service that wasn't clear is whether it will have an API. Part of the system I am currently working on provides a workflow for analysts to work with small sets of files. An API for Zocalo would allow automated process and analysts to jointly curate the files.
Other AWS services have great API's: I've especially enjoyed working with the Java libraries for AWS services. Amazon usually takes API development very seriously and produces solid interfaces. Interoperating Zocalo with other AWS services would be the killer feature for my current use case, and an API with good libraries would facilitate this.
Here are some ideas for what could be done combining Zocalo and other AWS services:
One aspect of the Zocalo service that wasn't clear is whether it will have an API. Part of the system I am currently working on provides a workflow for analysts to work with small sets of files. An API for Zocalo would allow automated process and analysts to jointly curate the files.
Other AWS services have great API's: I've especially enjoyed working with the Java libraries for AWS services. Amazon usually takes API development very seriously and produces solid interfaces. Interoperating Zocalo with other AWS services would be the killer feature for my current use case, and an API with good libraries would facilitate this.
Here are some ideas for what could be done combining Zocalo and other AWS services:
- Analyze file access and update logs using EMR or Kinesis. This could reveal suspicious access patterns associated with loss of IP, or it could be used to run a cluster analysis of users to identify ad-hoc groups that are collaborating on content.
- Build content-based workflows. Workflows that depend on file data could be built on top of Zocalo. This allows easy ad-hoc access to the data, while also enabling systems where the data is modified by automated processes or external systems. For example, new versions could automatically trigger review from a quality assurance group.
- Find trending topics in documents. If new versions could be fed into Amazon Kinesis, it would be possible for the system to identify trending keywords or phrases in real time. Data could be fed into Redshift and shown to editors or management.
- Manage users and security automatically. For example, when a new user is provisioned in ActiveDirectory then the onboarding system could trigger the user to be added to Zocalo and could grant appropriate access rights.
I'm sure there are many other interesting things that can be done through an API integration, maybe even capabilities provided by outside vendors that expands the partner network concept. Zocalo is an exiting offering as-is, but with an API the possibilities are multiplied.
Hi Greg,
ReplyDeleteI had some questions regarding Amazon Zocalo. It would be very helpful if you share your thoughts on the same.
1. Can I restrict Users from uploading files of a particular name or extension? (Ex. I want users not to upload *.exe files)
2. Can I keep files in Amazon Zocalo for eternity? If not how long?
3. Is White labelling enabled for Amazon Zocalo?
4. Is there any guarantee which Amazon Zocalo provides for stored documents by various users?
Thanks
Suvojyoty
Thanks for your comment. I haven't spent much time looking into Zocalo since this post. After looking at the pricing and capabilities, my team decided to stick with S3 storage for our data processing system. We certainly wouldn't have been typical Zocalo users had we switched over.
DeleteFor answers to your specific questions, I strongly suggest you ask them on the Zocalo AWS forum:
https://forums.aws.amazon.com/forum.jspa?forumID=172
Thanks for the prompt reply Greg.
Delete