Uploaded image for project: 'OpenShift Cloud Credential Operator'
  1. OpenShift Cloud Credential Operator
  2. CCO-21

Support AWS Security Token Service


    • Support AWS Security Token Service
    • False
    • False
    • Cluster Operator
    • Done
    • OCPPLAN-5656 - AWS STS - Security Token Service
    • 0% To Do, 0% In Progress, 100% Done
    • Undefined

      Epic Goal

      • Complete the implementation for AWS STS, including support and documentation.

      Why is this important?

      • Many customers want to follow best security practices for handling credentials.
      • This is the way recommended by AWS. 
      • Customer interest: EMEA, AMER

      Acceptance Criteria

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

      Dependencies (internal and external)

      Open questions:

      1. Will this cover existing OCP deployments or only new OCP deployments?
      2. Is there a migration path for existing customers to start using AWS STS?
      3. Are there considerations that apply to Operators so they can work with limited privilege credentials?

      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>

            rhn-engineering-gshereme Greg Sheremeta
            rhn-engineering-gshereme Greg Sheremeta
            Lin Wang Lin Wang
            1 Vote for this issue
            12 Start watching this issue