Swap AWS s3 v1 -> v2 SDK API
General
Escalation
General
Escalation
Description
Environment
None
Activity
Show:
Jakub Vecera January 30, 2025 at 1:52 PM
found out that SSE-C encryption doesn't work with native AWS bucket.
We had to take this ticket back to in progress to update these changes. And after I will focus on the GCP.
Details
Details
Assignee
Jakub VeceraReporter
Boris IlijicNeeds QA
Yes
Needs Doc
No
Story Points
21
Sprint
Fix versions
Priority
Medium
Smart Checklist
Open Smart Checklist
Smart Checklist
Open Smart Checklist
Created January 9, 2025 at 5:54 PM
Updated March 7, 2025 at 1:33 PM
Problem description
In current version PBM uses github.com/aws/aws-sdk-go (v1) dependency for accessing S3 service. That SDK library (v1) will be EOL soon, so it’s necessary to migrate to new version of the library (v2).
Solution proposition
Swap github.com/aws/aws-sdk-go (v1) SDK library with https://pkg.go.dev/github.com/aws/aws-sdk-go-v2 SDK library.
Acceptance Criteria
All S3 storage operations remain the same from the PBM perspective.
QA and Documentation
It is necessary to test access to S3 storage during backup/restore/status features using different storage configurations.
Documentation is not necessary because it’ll not be provided and additional feature/improvements.