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
Is your feature request related to a problem? Please describe.
With the automated script we can customize the S3 bucket name that will be created/used during the deployment.
This is not possible at the moment with the terraform deployment option
Describe the solution you'd like
I am requesting the port of this feature to the terraform deployment option.
There could be a variable that we can set to customize the S3 bucket name.
Nice to have that can be added later :
Ideally, the bucket creation should be skipped if the bucket already exists (this way we can re-install using a previously created bucket from a previous install).
Additional context
Current result :
The text was updated successfully, but these errors were encountered:
@surajkota Extra motivation : Having a known name allows to fine-tune the S3 policy to authorize just this specific bucket instead of using a policy with a wildcard that allows access to all S3 resources *.
Is your feature request related to a problem? Please describe.
With the automated script we can customize the S3 bucket name that will be created/used during the deployment.
This is not possible at the moment with the terraform deployment option
Describe the solution you'd like
I am requesting the port of this feature to the terraform deployment option.
There could be a variable that we can set to customize the S3 bucket name.
Nice to have that can be added later :
Ideally, the bucket creation should be skipped if the bucket already exists (this way we can re-install using a previously created bucket from a previous install).
Additional context
Current result :
The text was updated successfully, but these errors were encountered: