Design and Implement a User On-Boarding and User Access Management Process for Unity

[ramesh-maddegoda]

Checked for duplicates

• Ex. Yes - I've already checked

Alternatives considered

• Ex. Yes - and alternatives don't suffice (for example using Cognito native users with email approvals or manual checks)

Related problems

At the moment, we on-board users to Unity Cognito user pools based on requests recived through emails or messages. This approach may be sufficient for now to continue the development work. However, according to the NASA policies, we must make sure that a given user has gone through relevant background checks and necessary approvals before adding a user and/or before associating Cognito user groups (Authorization).

In many other applications, user and user permissions approvals are managed through NAMS requests. Also, many other applications are integrated with the Launchpad that can enforce a user to use a smart card for login.

Describe the feature request

It is required to design and implement a user boarding and user access management process for unity with the following features.

Must Have

• The user on-boarding requests should go through an approval process, preferably utilizing the NAMS request process
• Adding Cognito users to Unity Cognito User Pools and associating suer groups to to Cognito users should be based on above approvals

Should Have

• Integrate LaunchPad with Cognito if it is technically feasible

[ramesh-maddegoda]

These workflows will be created for Cognito User Pools in Unity Dev, Unity Test and Unity Prod.

User Management Workflows

1. Create a Cognito user
2. Update a Cognito user
3. Delete a Cognito user

User Group Management Workflows

1. Create a Cognito user group
2. Update a Cognito user group
3. Delete a Cognito user group
4. Associate an IAM role with a Cognito user group

User Access Management Workflows

1. Associate a Cognito user group with a Cognito user
2. Remove a Cognito user from a Cognito user group