How to configure the endpoint of AWS S3 storage that Camunda uses?
I’m using Minio and need to connect to it, these are all of the configurations in the docs I can’t find the endpoint variable.
AWS_ACCESS_KEY_ID=AWSACCESSKEYID
AWS_REGION=eu-north-1
AWS_SECRET_ACCESS_KEY=AWSSECRETACCESSKEYGOESHERE
DOCUMENT_STORE_AWS_BUCKET=test-bucket
DOCUMENT_STORE_AWS_BUCKET_PATH=test/path
DOCUMENT_STORE_AWS_BUCKET_TTL=5
DOCUMENT_STORE_AWS_CLASS=io.camunda.document.store.aws.AwsDocumentStoreProvider
DOCUMENT_DEFAULT_STORE_ID=aws
Hi @msebaei - are you configuring IDP? The endpoint is derived from the region, I believe, so I don’t think you need to manually specify it. Have you included those variables (with your values) and it’s not working? If it’s not working, what errors are you getting?
1 Like
Hi, and welcome to the forum!
Since the configurations all refer to AWS, I’m going to assume that Camunda (or the developer that built this component) made some assumptions… specifically that you were using a AWS S3 system, rather than a generic S3-protocol system. While Minio uses the S3 protocol, it’s not AWS.
As such, I’m going to guess that the short answer (at least for now) is “you can’t”
2 Likes
Ah, yes, I missed the reference to MinIO. Thanks @GotnOGuts!
@msebaei - the reply above is correct. At this time, document handling requires use of Amazon S3 or GCP storage buckets (or in-memory or local file system). The next release will include more flexibility, such as supporting Azure storage. I do not know specifically if S3 compatible solutions like MinIO are on the roadmap, but I have shared this message with the product team.
You can also follow our public roadmap here: https://roadmap.camunda.com
1 Like
Thank you so much for your support on this topic.
@nathan.loding @GotnOGuts
The endpoint is derived from the region, and Camunda is currently not supporting Minio.
They are supporting only