-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
3
-
False
-
-
False
-
-
-
Sprint 245 - Pipeline&Delivery
-
0
-
0.000
We've got into the AWS account. Now, we need to redeploy the servers to make sure the delivery and pipeline team can work smoothly with all the permissions they need via tofu.
Acceptance Criteria
- Understand how to grant admin access to others members.
- Schedule with the ART team a window to redeploy the aarch64 builders and add them in the pipelines
- Redeploy the aarch64 builders in AWS via tofu. See docs: https://github.com/coreos/fedora-coreos-pipeline/tree/main/multi-arch-builders/provisioning/aarch64
- Make sure splunk if working ok
- Redeploy both prod and dev builders
Info:
Here is the ticket that created the aws account https://redhat.service-now.com/help?id=rh_ticket&table=sc_req_item&sys_id=b1ee1073db657950bd297e83e296191c
When I requested the access, I understood the account admin access would be control via this rover group: https://rover.redhat.com/groups/group/rhcos-cloud-admins However, people in this rover group still can't access it.