GUI alternative to managing Appstream users
| Boto 3 (1.10.46) | AWS SDK for Python |
| Keyring (18.0.0) | Communicating with native OS keychain |
| Pandas (1.0.1) | Data analysis tool |
In order to use the Appstream User Manager, you'll need an Access Key ID and a Secret Access Key. To obtain one, log in to the AWS console and go to "My Security Credentials" under the user account dropdown menu.
Once your Access key has been made, you will be able to view your Secret Access Key. THIS IS THE ONLY TIME YOU WILL BE ABLE TO VIEW IT. Make sure you make a copy of your key somewhere secure, or else you'll have to recreate your access keys.
There are three main windows in the Appstream User Manager: Manage, Add, and Remove
From the Manage tab, you can search for users via first or last name, or email address. When a user is selected, they will appear in the User Info Pane, which will tell you what stacks are associated with said user. You also have the option of resending a welcome email the user hasn't yet registered a password (temp passwords from account creation emails expire after 7 days).
You also have the option of Setting, Adding, or Removing stacks from the user's account. "Setting" the stacks means checked stacks will be added, and unchecked stacks will be removed. "Adding" will just add selected stacks, and "Removing" will just remove selected stacks. You also have the option of sending a notification email.
What you'll see when "Setting" stacks
From the Add tab, users can be added individually or by roster. Adding by roster requires the standard Rutgers REGIS format. The file must also be formatted as .csv
REGIS-formatted rosters saved as .xlsx can be save[d] as .csv in excel and should work fine.
Standard REGIS .csv
Selected stacks will be associated with the added users, whether by roster or individual addition. Please note that usernames are case-sensitive.
From the Remove tab, specific users can be removed using Batch Remove, or the entire user list can be deleted (with exceptions) from Remove All. User accounts cannot be recovered, but their data should remain in their S3 bucket.
- Rate limiting happens a lot. Had to add delays all over the place.
- Add user count