Uploaded image for project: 'OpenShift Windows Containers'
  1. OpenShift Windows Containers
  2. WINC-1436

Migrate to aws-sdk-go to v2

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • WMCO 10.21.0
    • None
    • wmco
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • None
    • None
    • None

      User or Developer story

      As a developer, I want to migrate from AWS SDK for Go v1 to v2 so that project remains secure, supported, and compatible with future AWS services before the official end-of-support date.

      Description

      AWS SDK for Go v1 will reach end-of-support on July 31, 2025. After this date, no new features, security updates, or bug fixes will be provided for v1. AWS strongly recommends migrating to AWS SDK for Go v2, which offers improved performance, modularity, and ongoing support. This story covers the initial audit and planning phase, following AWS’s recommended migration process and timeline.

      Required

      • Audit the main project source code (excluding vendor and indirect dependencies) for any direct imports or usage of `github.com/aws/aws-sdk-go`.
      • Document all AWS services and APIs currently used via SDK v1.
      • Identify any transitive dependencies that may require updates.
      • Review the official AWS migration guide and end-of-support announcement for best practices and required steps.
      • Create a migration plan outlining:
      • Mapping of v1 APIs to v2 equivalents
      • Identification of breaking changes (e.g., API signatures, error handling, configuration)
      • Steps for updating dependencies and refactoring code
      • Testing and validation strategy

      Nice to have

      • Provide a list of files and functions that will be impacted by the migration.
      • Suggest incremental migration steps if full migration is not feasible in one sprint.
      • Reference documentation or guides for AWS SDK Go v2 migration.
      • Estimate effort and timeline for full migration.
      • Identify opportunities to improve code quality or performance during migration.

      Engineering Details

      Acceptance Criteria

      • All direct imports and usage of `github.com/aws/aws-sdk-go` in the main project code are identified
        -  Migration mapping of v1 APIs to v2 equivalents and a list of impacted files/functions.
      • No new deprecation warnings for AWS SDK v1 in the main project code after audit (excluding vendor/transitive dependencies).

              Unassigned Unassigned
              jvaldes@redhat.com Jose Valdes
              None
              None
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: