Topics Map > Computing Infrastructure > Amazon Web Services

Amazon Web Services, Granting access to the AWS Console

How to use Authman to manage access to an AWS account.

AWS Access Management

AWS accounts managed by UIUC uses Authorization Manager, also known as AuthMan, for user access management. 
The AWS account can be found in AuthMan at the path "Urbana:app:AWS:<AWS_Account_Name>".

Standard Roles

The following roles are created by default for your AWS account.
  • Admins: Granted full control over all resources.
  • PowerUsers: Granted access to all AWS services and resources, excluding user and role management.
  • BusinessOffice: Permitted to access billing and cost management functionalities, which includes viewing account usage and viewing and modifying budgets notifications.
  • ReadOnly: Allowed to view all resources and settings but cannot make changes.
  • Prisma: Grants access to the Prisma Cloud Security system. Does not grant access to the AWS account. Cloud Security, Prisma, What is Prisma Cloud?
See the KB article Authorization Manager, Manage Memberships for step-by-step instructions on adding or removing members.

Creating Custom Roles

If the standard roles do not meet your requirements, you have the option to create custom roles that align with your specific need.
To create a custom role:
  1. Go to the AuthMan application:
  2. Select the folder with your AWS account name. It can be found at  "Urbana:app:AWS:<AWS_Account_Name>"
  3. Click the "Functions" button in the upper right corner and select "Create new group" from the dropdown menu.
  4. Enter a Group name and Description. Click Save.
  5. Log into your AWS account with the Admins role:
  6. Search for and go to the IAM service.
  7. Go to the Roles section and click on "Create role".
  8. In "Trusted entity type", select "SAML 2.0 federation"
  9. In the "SAML 2.0-based provider" drop down, select "".
  10. Select "Allow programmatic and AWS Management Console access" and click Next.
  11. Add the necessary policies to fit your specific need.
  12. Name this role the same as the newly created group in Authman.
  13. Save.

Active Directory

Instructions below are for legacy AWS accounts. If you do not see the AuthMan groups listed above, please contact to be migrated to AuthMan.
Shibboleth is configured to search for AD groups named according to the following format:
  1. AccountID: 12-digit AWS account number, provided when the account is provisioned.
  2. RoleName: Arbitrary name for the AWS IAM role that group members will be able to use.
An example: AWS-123456789012-Researchers
Some groups like to name roles based on logical affiliation with the project (Researchers, ITSupport, Admins), while others prefer to grant access according to organizational units (NetworkEngineering, HelpDesk, ApplicationSupport). Either method is acceptable.
AD groups should be Security Groups with a Global context. At present, it's not possible to nest groups, so your AD group must be populated with people.
Once your group is in place, you can create the corresponding AWS role:

Amazon Web Services

Note: When your account is initially provisioned, this step will be handled by our AWS account management team.
  1. From the AWS Console, navigate to IAM, then select Roles from the left-column menu.
  2. Click the Create Role button at the top of the page.
  3. Select Saml 2.0 federation as the type of trusted entity.
  4. Select as the SAML provider.
  5. Select Allow programmatic and AWS Management Console access and click the blue Next: Permissions button.
  6. Find and attach one or more policies, appropriate to the function of the role. By default, roles have no access, so you must grant appropriate access. Click Next: Review.
  7. Enter the role name which matches the RoleName portion of your AD group name (including capitalization), click Create role.
Once AD and AWS are both configured, users should be able to login to the role via

KeywordsAWS Shibboleth Authman   Doc ID71883
OwnerAmazon C.GroupUniversity of Illinois Technology Services
Created2017-03-20 14:33:19Updated2023-11-08 09:24:15
SitesUniversity of Illinois Technology Services
Feedback  0   0