Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

remote backup s3 with sse-kms-key-id #619

Closed
jazz0013 opened this issue Mar 17, 2023 · 3 comments
Closed

remote backup s3 with sse-kms-key-id #619

jazz0013 opened this issue Mar 17, 2023 · 3 comments
Assignees
@Slach
Milestone
2.2.1

Comments

@jazz0013
Copy link

is it possible to explicitly specify sse-kms-key-id for backup on s3?
@Slach Slach self-assigned this Mar 17, 2023
@Slach Slach added this to the 2.3.0 milestone Mar 17, 2023
@Slach
Copy link
Collaborator

Slach commented Mar 17, 2023

Unfortunately, not. ;(
Currently
it couldn't be defined inside clickhouse-backup (only S3_SSE environment and s3->sse config could be setup, it define only SSE algorithm like AES256, aws:kms etc)

I will add it on 2.3.0 release

@jazz0013
Copy link
Author

@Slach Thank you.

@jazz0013 jazz0013 reopened this Mar 17, 2023
@Slach
Copy link
Collaborator

Slach commented Mar 17, 2023

@jazz0013 could you try docker image altinity/clickhouse-backup:master

@Slach Slach closed this as completed in 551a1e3 Mar 28, 2023
o-mdr pushed a commit to o-mdr/clickhouse-backup that referenced this issue Mar 28, 2023
@Slach
add additional server-side encryption parameters to s3 config section, …
b137d79 
…fix Altinity#619
@Slach Slach modified the milestones: 2.3.0, 2.2.1 Mar 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Slach Slach

Labels
None yet
Projects
None yet
Milestone
2.2.1
Development

No branches or pull requests
2 participants
@Slach @jazz0013