-
Epic
-
Resolution: Unresolved
-
Major
-
None
-
None
-
BYO encrypted AMIs on AWS
-
Product / Portfolio Work
-
-
0% To Do, 33% In Progress, 67% Done
-
False
-
-
False
-
Not Selected
-
None
-
None
Epic Goal
- Document how to use BYO encrypted RHCOS AMIs when deploying OCP on AWS
- QE to create a profile to validate the flow with encrypted AMIs across releases
Why is this important?
- For users who want to use encrypted AMIs when deploying OCP on AWS to have a supported documented path they can follow
- Ensure there are no regressions when using encrypted AMIs across releases
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
Previous Work (Optional):
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>
- is related to
-
OCPBUGS-60837 kms:ReEncrypt* permission is missing if using BYO encrypted AMI with BYO KMS key
-
- POST
-
-
OCPBUGS-56225 Edge node with custom KMS key may not be created in particular edge zones due to kms:ReEncrypt* permission is missing in Machine API.
-
- Closed
-
- links to