Uploaded image for project: 'Red Hat Workload Availability'
  1. Red Hat Workload Availability
  2. RHWA-312

Medik8 AWS Account Separation From Special Project Account

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • rhwa
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Moderate

      For enhanced management and resource isolation, the Medik8 AWS account will be migrated from the shared "Special Project" account into its own dedicated AWS account. This will ensure that Medik8's resources are completely separate from other teams.

      This epic aims to improve cloud operations by separating team resources within AWS, leading to greater stability and financial clarity. The key objectives are:

      • Prevent resource conflicts to increase operational stability.
      • Enable accurate cost allocation and clear visibility into each team's usage.
      • Empower teams with ownership of their spending, fostering accountability and making it easier to identify cost-saving opportunities.

      Please refer to the attached Confluence guide for instructions on configuring "OpenShift CI Cluster profile" .
      You can find details about AWS account limits at the following link - https://spaces.redhat.com/pages/viewpage.action?pageId=436142709&spaceKey=dragonfly&title=AWS%2Blimits 

      Acceptance Criteria:

      • The new account is configured with the company's standard security baselines.
      • A test CI/CD pipeline is executed to confirm that resources can be deployed and managed in the new account without errors.

              Unassigned Unassigned
              rh-ee-slevi Shai Shimon Levi
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: