My team and I are using a self-hosted version of unstructured and we would like to secure our service, similar to how the hosted version uses API keys to prevent unauthorized access.
I was thinking it might be possible to pass in a single optional API key as an ENV variable to the Docker service such that any requests without the unstructured-api-key header are rejected. This way, we could reasonably ensure that our self-hosted version of unstructured is only invokable from our application.
My team and I are using a self-hosted version of unstructured and we would like to secure our service, similar to how the hosted version uses API keys to prevent unauthorized access.
I was thinking it might be possible to pass in a single optional API key as an
ENVvariable to the Docker service such that any requests without theunstructured-api-keyheader are rejected. This way, we could reasonably ensure that our self-hosted version of unstructured is only invokable from our application.Thanks for building such a great tool!