Skip to content

Issue with object storage when sse-s3 is not supported. Can we make this optional (is sse-c an option?)Β #1071

Open

Description

@chris-milsted

The two encryption options (AES or aws:kms) call sse-s3. This is not supported on linode object at the moment, so I would like to be able to specify encryption: "" in the wal archive. When I try this I get

$ k create -f barmanObjectStore.yaml The ObjectStore "paris-object" is invalid: spec.configuration.wal.encryption: Unsupported value: "": supported values: "AES256", "aws:kms"

Can we make this optional or allow a key to be specified so that we can use sse-c instead?

Activity

  1. martinmarques commented on Mar 6, 2025

    @martinmarques
    Contributor

    @chris-milsted please check this reply from @alwinzwets
    #957 (comment)

  2. chris-milsted commented on Mar 6, 2025

    @chris-milsted
    Author

    That reply almost works.... as I mentioned I did try to pass in encryption: "" but it fails as below:

    $ k create -f barmanObjectStore.yaml The ObjectStore "paris-object" is invalid: spec.configuration.wal.encryption: Unsupported value: "": supported values: "AES256", "aws:kms"

    Is this a cloud native pg issue or a barman issue on this validation?

  3. martinmarques commented on Dec 29, 2025

    @martinmarques
    Contributor

    I was going over some old issues and found #973, which seems related to this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions