dabde

Hi, thanks for the comment. Yes S3 would be nice. Think also to implement this is not to hard. It should already possible with a dirty workaround to use S3....

Add this to our internal agenda.

Yes, we don't have implement any AWS support, related we don't use AWS. So only way to work with AWS instances, is create one by hand or any other automation...

For adding AWS support, think the starting point is to extend this case block: https://github.com/kloeckner-i/db-operator/blob/master/controllers/dbinstance_controller.go#L182 then mostly clone this one: https://github.com/kloeckner-i/db-operator/blob/e84d79235d0cdfcdd4e4a2c36199cfc3e06e8c3c/pkg/utils/dbinstance/gsql.go And replace the API communicate to aws one. https://docs.aws.amazon.com/AmazonRDS/latest/APIReference/API_CreateDBInstance.html#API_CreateDBInstance_Examples...

hi, we not managing this files with the db-operator. you have 2 options for the db-operator. 1. using google cloud sql (there you can define the API body to create...

close ticket, related it's out of the scope of the db-operator.

Hi thanks for your issue. Think it's sounds interesting, but also I would try not to have a feature overloaded db-operator with everything possible implemented. My idea for your issue...