Details
-
Feature
-
Must have
-
Services
-
-
-
Intra Program
-
2
-
2
-
0
-
Team_IT, Team_SYSTEM
-
Sprint 5
-
-
-
System Team:
- AWS usernames for the identified Staff
- AWS Permissions for the above roles are set up with a joint workshop
- ST can manage its own AWS resources
- IT has policies for the above accounts and resources on how they are shared and communicated
(these continue to be developed as we mature the service)
System Team: AWS usernames for the identified Staff AWS Permissions for the above roles are set up with a joint workshop ST can manage its own AWS resources IT has policies for the above accounts and resources on how they are shared and communicated (these continue to be developed as we mature the service) - AWS usernames for the identified Staff
-
19.6
-
Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO
-
-
Team_IT Team_SYSTEM
Description
As part of the ST work to continue to provide services hosted on AWS, we need to have access to AWS and manage it.
To achieve this, we need to setup
- AWS Production Accounts for Office Staff
- How the permissions should look like for accounts per procurement.
- Idea: Pick an example and walkthrough it together (i.e. kubernetes cluster)
- Identify how we should work. Policies, guidelines, communication channels, monitoring/logging etc.
- Do it again for new services (or existing ones) alone