AWS Administration Roles - Improvement/fixes

**Describe the Issue**
Need to fix administration roles function in AWS, to one that allows the minimum set of administrative permissions and which are focused on rapid need in platform administration task areas

**Additional Context**
After the KeyCloak login page the console environment log in options and offered permissions groupings are problematic, as they currently require higher than best practice access to conduct simple administration tasks (Security Hub, quota administration, budget management, cost investigations, etc.)

**Acceptance Criteria**
- Platform administration team frame out what should the Cloud Login\Realm page result (post-login) look like ideally, with administration tasks as the focus (This list of access areas we get should be 'task orientated')
- Re-grouping\combining of administration AWS Roles, according to key platform administration task and decision areas
- Review of recommended dashboarding\admin build+scheduling areas of AWS post ProServe work if possible, and incorporate
- Consider having ProServe do code for final re-vamp of admin roles, according to our needs\input, best practice and recommended administration processes\dashboard types

.
.
.
.
.
.
.
.
.
.
.

**Extra Template Info**

***Definition of Ready***
These set of conditions will need to be met in order to bring a ticket into the sprint and start work. Protects the team from unclear requirements.
Issues (Task/Story/Spike) aligned to an EPIC and linked appropriately.
Assigned to the appropriate CPF MEMBER (and is not left blank in ZenHub) at the start of sprint (1st day of the sprint)
Acceptance has been defined for the issue and has been reviewed with CPF team and approved by the necessary approver.
Has been sized and estimated by the delivery team.
Detailed breakdown of the steps required to complete the story in the additional context
Any additional specifications have been documented, reviewed with CPF and approved by the necessary approver.

***Acceptance Criteria***
A set of pre-defined requirement that need to be met in order to mark the user story as “done”.
It should be testable with no room for interpretation
It should be either “pass” or “fail”
It should be clear enough for business stake holders to understand
As part of the user story, it should be written from the user perspective
A well written acceptance criteria is great for
- managing expectations
- defining scope
- reducing ambiguity
- establishing testing criteria for QA
Given (Pre-condition)
When (Action)
Then (Outcome)

***Definition of Done***
These set of conditions are met for work to be considered as complete on an issue.
All acceptance criteria(s) have been validated.
All the necessary documentation for the issue has been uploaded to Teams.
Functionality has been tested when applicable.
Functionality has been demonstrated to the relevant stakeholders (where applicable).
Story has been scheduled for a Sprint Demo/community update and impacted teams invited to the Demo.
Stories accepted by PO and documented for potential sharing with impacted users.
- Documented = Captured in Community Update (CU) deck
- Release notes = aspirational goal of providing a bulleted list of features and changes that our users can touch. Was going to store them in our Cloud Pathfinder repo. Can also display to users in the CU