Skip to content

Consul backinator doesn't work with k8s service account with s3 permissions #48

@cherishedbrain

Description

@cherishedbrain

Hi Team,

I have tried running consul-backinator to take the backup on S3 via k8s service account having enough IAM roles to perform consul backup directly to S3 bucket but it doesn't work.

S3 Policy has below:
"s3:GetObject",
"s3:DeleteObjectVersion",
"s3:AbortMultipartUpload",
"s3:DeleteObject",
"s3:PutObject"

However when i run it to take backup locally it works and just to check if there is any issue with the role i tried installing aws cli and did successful upload via aws-cli.

On another note acl backup always fail complaining
[Error] Failed to backup ACL tokens: Unexpected response code: 403 (Permission denied)

It would be best if you can even mention what kind of S3 permissions and consul policies are required to take the acl backup.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions