Hi,
I have a software product in my architecture that uses an S3 compatible service to store objects. The product is called form.io.
The system is deployed on-premises and we are using min.io as object repository. However AWS S3 and any other S3 compatible service is fully supported.
In this architecture, the purpose of the object store is to keep documents, which eventually also need to be stored in the Content Server. However, the software product (form.io) cannot be changed to interface with the Content Server REST API and can only talk with S3 APIs.So eventually, we end up with duplicated content because the original documents need to stay in min.io and a copy needs to go to the Content Server.
A wild idea floated into the architect's brain, which was to implement an S3 compatible API for the Content Server. That way we could hook up form.io directly to the Content Server and store the files in there from the start.
Has anyone come across a similar need? Any solutions for this?
Any thoughts on how hard it would be to map the concepts from the S3 API to Content Server (e.g. bucket, object)?
And if you think it's the silliest idea ever, feel free to say it 
Thanks,
João