mysql-operator S3 backup 403 response issues

[kabudu]

Is this a BUG REPORT or FEATURE REQUEST?

BUG REPORT

This is more of a question than a bug report, but I couldn't work out where else to ask it, and there was no other suitable option.

Versions

MySQL Operator Version: 0.3.0

Environment:

• Kubernetes version (use kubectl version): v1.10.0
• Cloud provider or hardware configuration: Hetzner Cloud
• OS (e.g. from /etc/os-release): Ubuntu 16.04.4 LTS
• Kernel (e.g. uname -a): Linux 4.4.0-130-generic
• Others:

What happened?

The mysql-operator was unable to upload the backup due to a 403 response from Amazon S3

What you expected to happen?

The backup to be uploaded successfully.

How to reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

I tested my AWS credentials in isolation with the AWS cli and I was able to upload a file to my bucket in S3. Are there:

a) Any details somewhere that describe exactly how the operator performs the upload to S3 and if there are a defined set of permissions that the bucket needs to have from the context of the operator? b) A way of extracting more detailed error information from the mysqlbackup resource