Role Based Access Control FAQ

What is Aviatrix Role Based Access Control (RBAC)?

Aviatrix Controller is a multicloud and multitenant Enterprise platform. As such, the Aviatrix Controller manages multiple cloud accounts by requiring access by multiple administrators. RBAC provides access controls to protect the security and integrity of the Controller while providing the ability to delegate and limit specific Aviatrix features to groups defined by the admin of the Controller.

Aviatrix RBAC aims to achieve two objectives:

  • Granular Access Control A Controller administrator in a specific permission group can perform certain tasks for a subset of Aviatrix Access Account. For example, an Administrative user can be limited to perform on his own AWS account VPC attachment function.
  • Self Service A Controller administrator in a specific permission group can onboard its own cloud accounts on the Controller and perform tasks. For example, a Controller administrator can be allowed to onboard his own AWS account on the Controller and create a group of users for different tasks on this access account. Another use case is for developers to have a read_only login permission to troubleshoot network connectivity issues.

How does RBAC work?

RBAC allows you to create a hierarchy of administrators within the Aviatrix Controller. It has the flexibility to permutate based on your requirements.

The best way to explain how RBAC works is through examples. Following are a few deployment examples.

RBAC Deployment Example 1

In this example, the Controller admin creates a user Bob who has full responsibility to access account account-A and account-B. The Controller admin also creates a user Alice who has full responsibility to access account-C and account-D.


Tasks carried out by admin

Step 1 Create an account admin group. Admin Login. Go to Accounts -> Permission Groups -> +Add New. Give the group a name, for example, account-admins.

Step 2 Give this group the privilege to create Access Accounts. Go to Accounts -> Permission Groups. Click the 3 skewer dots, click Manage Permission. Click +Add New. Select Accounts in the list of functions. Click OK to confirm.

Step 3 Create user Bob to the account_admins group. Go to Account Users -> +New User. Fill the name, Bob, and other fields. For the field RBAC Groups, select account-admins created in Step 1.

Tasks carried out by Bob

Step 4 Bob should receive an email to invite him to access the Controller. Bob login. Bob creates a new permission group with full access. Go to Accounts -> Permission Groups -> +Add New. Fill permission group name, for example, group-bob.

Step 5 Bob associates himself with the group-bob. Go to Accounts -> Permission Groups. Select bob-group, click Manage users. Select Bob to associate with the group.

Step 6 Bob grants group-bob functional functional privilege. Go to Accounts -> Permission Groups. Select group-bob. Click Manage permissions. Click ALLWrite to grant group-bob

Step 7 Bob creates a new Access Account account-A. Bob login. Go to Accounts -> Access Accounts -> +Add New. For the field “Attach to RBAC Groups”, select group-bob. This creates an access account that associates a cloud account that Bob manages. For the Account Name field, Bob enters account-A.

Bob can repeat Step 7 to create account-B. Now Bob has full functional access to both account-A and account-B.

Apply Step 3 to Step 7 for Alice to manage account-C and account-D.

Can Bob assign a teammate with subset of functional privileges?

Yes. The deployment is shown in the diagram below.


Bob should perform the following tasks to have it setup.

  1. Bob creates a new permission group, say Site2Cloud-ops.
  2. Bob assigns himself to Site2Cloud-ops group.
  3. Bob clicks “Manage permission” for Site2Cloud-ops group to select Site2Cloud permission for the group.
  4. Bob clicks “Manage access accounts” for Site2Cloud-ops group to select account-A.
  5. Bob creates a new user, say Adam and associate Adam to Site2Cloud-ops group.

After the above tasks, Adam will be able to login and perform Site2Cloud tasks for account-A. But Adam cannot perform Site2Cloud tasks for Alice’s account.

How to add a read_only user?

Read_only user has visibility to all pages on the Controller and can perform troubleshooting tasks. A read_only user cannot make modifications to any functions or accounts.


In this example, Alice creates a read_only user George. Alice performs the following steps.

  1. Alice login.
  2. Go to Accounts -> Account Users -> +Add New.
  3. Add User Name George, User Email, Password. For RBAC Groups, select read_only.

Can there be multiple admin users?

Yes. Only admin can add more admin users. An admin user has the same privilege as the login admin with full access to all pages and accounts.

In this example, admin creates an admin user Jennifer. admin performs the following steps.


1. admin login. # Go to Accounts -> Account Users -> +Add New. #. Add User Name Jennifer, User Email, Password. For RBAC Groups, select admin.

Does RBAC support remote authentications?

RBAC supports remote authentication against LDAP, Duo and other SAML IDPs.

For LDAP and Duo, RBAC supports authentication only; the permissions are still validated locally on the Controller.

For other SAML IDPs, you can configure profile attribute associated with the SAML user for permissions, thus avoiding having to add users on the Controller.

How do I setup SAML login for RBAC?

Aviatrix Controller login supports SAML login.

You have the option of authorizing user by Controller configuration or through SAML IDP Attribute. Go to Settings -> Controller -> SAML Login -> + Add New

If you select “Set Access By” to be ‘SAML IDP attribute’, follow the instructions to setup SAML. In the SAML IDP Attribute Statements, add a new attribute “Profile”. For Value field, add the Name of the Permission Groups you configured on the Controller.

When a user authenticates against SAML IDP, the Controller retrieves the profile attribute and apply permission to the user. There is no need to configure account users on the Controller, but you still need to specify Permission Groups and their associated permissions.

If you select “Set Access By” to be ‘Controller’, you need to select an RBAC Group when creating an IDP endpoint.