Is WorkDocs a good fit for transactional/customer-based organization of documents

Yes James, you can. On this WorkDocs page we have a lot of use cases to help you understand and get ideas for your environment.

https://aws.amazon.com/workdocs/

And, to use APIs to improve your usability, you can integrate WorkDocs with another tools, like Kendra, to maximize capabilities of intelligent search in your company. https://aws.amazon.com/blogs/machine-learning/get-started-with-the-amazon-kendra-amazon-workdocs-connector/

You can edit online, without need a Office editor in PCs or workstations: https://aws.amazon.com/blogs/aws/new-collaborative-editing-for-amazon-workdocs-powered-by-hancom-thinkfree-office-online/

So, many options to help you.

So after experimenting with WorkDocs for a bit, I'm not able to see how it or the integration with Kendra would satisfy some requirements.

We have thousands of transactions in our company every day and each of these generates documents. We would need to be able to search for documents with a variety of parameters:

• Our internal transaction number that we generate
• The customer's reference number that they generate
• Customer name
• Time range
• Etc.

A possible solution would allow us to attach metadata to documents stored in WorkDocs, and then provide a search function by that metadata.

Of course, we could build something like this using S3 for file storage and DynamoDB for metadata storage, but then we would need to build our own search interface and it would be a lot more work than a managed solution.

Please let me know if I'm missing something with AWS's current offering.

Thanks!

James