Epic Goal

• Stop using github.com/aws/aws-sdk-go v2 in both image registry and image registry operator
• Migration details: https://aws.github.io/aws-sdk-go-v2/docs/migrating/

Why is this important?

• aws-sdk-go v1 is in maintanence mode and no longer receiving patches. This stops us from for example supporting new AWS regions
• See https://github.com/aws/aws-sdk-go/issues/5270

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. Upstream distribution is currently on v1 and I don't see any solid plans to move to v2 but move to v2 they must or we will still be unable to support newer AWS regions

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>