Recommended:   Affiliate NetID Access

By default all UW AWS accounts will be accessed using NetID authentication.   This extends the security provided by NetID authentication & Multi-factor Authentication to UW AWS accounts. (AWS - Sign In to the AWS Management Console )

AWS authorization groups are managed using the campus Manifest service.   

• The recommended way to provide access to non-UW collaborators is to invite them to create a NetID:    Manifest - Using a Manifest Group to Invite People to Create Identities (NetIDs) 
• For longer term relationships you can request an NetID for an affiliate population - see  Getting NetIDs for Affiliate Populations  for information on eligibility and considerations.

Your collaborator can then be added to an existing Manifest group, or you can create a custom Role & Manifest group:

• [Link for document 65493 is unavailable at this time] 

Affiliate NetID Access quick reference

While individual schools, colleges, and departments have their own HR policies and processes, some cloud account holders have successfully used the process below to create NetIDs for external consultants who needed access to UW-Madison cloud accounts:

1. [Local HR in UW-Madison] Adding or Maintaining a Person of Interest (POI) in HRS: https://kb.uwss.wisconsin.edu/15636
2. [Consultant] - NetID - Activating Your Account: https://kb.wisc.edu/iam/1140
3. [Consultant] - NetID - Activating Missing Services (O365) https://kb.wisc.edu/iam/page.php?id=4479
4. [AWS account owner] AWS - Granting Users Access to the AWS Management Console using NetID Authentication: https://kb.wisc.edu/public-cloud/65493
5. [Consultant] AWS - Sign-In to the AWS Management Console: https://kb.wisc.edu/public-cloud/65490

AWS IAM User Access

***Note!  If your AWS account is provisioned since July 2022, you will need to work with the Public Cloud Team to create/manage IAM/service account users.

** If you are creating an AWS IAM user for CLI access please consider using AWS Cloud Shell as an alternative. **

NetID login is handled using an identity provider and does not create a native IAM user account within Amazon.   IAM users are most frequently used as service accounts to run processes.   If it is necessary to create an IAM user, please review Security best practices in IAM, in particular using the principle of least privilege. 

This account should be secured with Multi-Factor Authentication (MFA) to comply with UW System authentication standards.

See  AWS - Sign In to the AWS Management Console for information on how to log in with an IAM user