You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we need to specify S3_URL in the configurations in multiple services (api, conversion, mosaic, etc.). And on the
Frontend we allow users to create workspaces (which is equivalent to 1 bucket).
The problem is that since the S3 providers (Amazon, Digital Ocean, etc.) requires a bucket to be created first to be able to use it. That means the S3_URL must be dynamically created/configured during the workspace creation time instead of hard coding ones.
Even though we can find providers that offer providing 1 S3_URL and then creating buckets under the hood, I have not found out such providers.
Therefore, I suggest to change the S3_URL from statically defined to dynamic creation. Meaning that with the creation of the workspace, the bucket will also be created automatically. Afterwards, the S3_URL will be stored in the database together with the workspace information. Then when we select a workspace to work with, we use this S3_URL which we get from the database instead.
This will require some changes in the frontend as well. An additional dropdown box that allow users to select regions where the bucket will be created (and thus the S3_REGION static configuration will also be removed from the .env). For now we restrict only EU region and US region as we will target the markets in these regions.
Description of the use case
No response
Explanation of the benefits
No response
Possible Implementation (if applicable)
No response
Any additional information, context, or logs
No response
The text was updated successfully, but these errors were encountered:
Detailed description of the feature
Currently we need to specify
S3_URL
in the configurations in multiple services (api, conversion, mosaic, etc.). And on theFrontend we allow users to create workspaces (which is equivalent to 1 bucket).
The problem is that since the S3 providers (Amazon, Digital Ocean, etc.) requires a bucket to be created first to be able to use it. That means the
S3_URL
must be dynamically created/configured during the workspace creation time instead of hard coding ones.Even though we can find providers that offer providing 1
S3_URL
and then creating buckets under the hood, I have not found out such providers.Therefore, I suggest to change the
S3_URL
from statically defined to dynamic creation. Meaning that with the creation of the workspace, the bucket will also be created automatically. Afterwards, theS3_URL
will be stored in the database together with the workspace information. Then when we select a workspace to work with, we use thisS3_URL
which we get from the database instead.This will require some changes in the frontend as well. An additional dropdown box that allow users to select regions where the bucket will be created (and thus the
S3_REGION
static configuration will also be removed from the .env). For now we restrict only EU region and US region as we will target the markets in these regions.Description of the use case
No response
Explanation of the benefits
No response
Possible Implementation (if applicable)
No response
Any additional information, context, or logs
No response
The text was updated successfully, but these errors were encountered: