Goal

Migrate all HyperShift AWS integrations from AWS SDK for Go v1 to v2 before the July 31, 2025 EOL deadline to ensure continued security support, vendor maintenance, and long-term reliability for all AWS-based Hosted Control Plane deployments.

Why is this important? (mandatory)

AWS SDK v1 will reach end-of-life on July 31, 2025. After this date, it will no longer receive security patches, bug fixes, or vendor support. HyperShift currently relies heavily on SDK v1, which creates:

• Security risk: Vulnerabilities in the unsupported SDK cannot be patched.

• Compliance risk: Unsupported dependencies fail SOC2, FedRAMP, and ISO audits.

• Supportability issues: AWS will not assist with SDK v1–related problems.

• Technical debt: Delayed migration increases complexity and cost.

Migrating now ensures HyperShift remains secure, compliant, and maintainable, while enabling future AWS feature adoption.

Scenarios

Main Success Scenario

• HyperShift builds and runs using AWS SDK v2 only.

• AWS-based Hosted Control Planes pass all unit and E2E tests with no regressions.

Dependencies (internal and external) (mandatory)

Internal

• HyperShift core code migration (about 40 files)

• Updated unit tests, mocks, and AWS utility packages

• Operator updates (platform, hostedcluster, control-plane, karpenter integration)

External

• CAPA (already on v2)

• Karpenter (already on v2)

• AWS SDK v2 as the new dependency baseline

Contributing Teams (and contacts) (mandatory) 

• Development: HyperShift, ROSA/ARO HCP teams

• Documentation: OpenShift docs

• QE: HyperShift + ROSA HCP QE

• PX: Release notes and upgrade guidance

• Others: Security/compliance, Release Engineering

Acceptance Criteria (optional)

• No remaining AWS SDK v1 imports

• All unit/E2E tests pass on AWS platform

• No performance or functional regressions

• Documentation updated with v2 patterns

• Security scan shows no critical/high issues

Drawbacks or Risk (optional)

none

Done - Checklist (mandatory)

• CI tests updated and passing

• Documentation complete

• QE validation completed

• Technical enablement ready (if needed)

• Security/compliance review complete