Writing /var/www/docs.clearos.com/data/cache/5/5f1b051ad2d7cf9e5cb00520489be959.metadata failed

RBAC for Multi-Cloud (EC2, ARM, GCE)

Use Case: Multi-cloud self-service provisioning for developers across AWS, Azure Resource Manager, and GCE.

Who can use this feature? Businesses that build software and use more than one public and/or private clouds. An administrator can use ClearGLASS to create accounts for developers and manage their usage to control costs and enable self-service.


These instructions assume:

  • You have a ClearGLASS account
  • Clouds have been added to ClearGLASS
  • A Team has been created

The Policy Engine is how permissions are set for a Team. The policy below shows that this Team can Create Resources on AWS EC2 N. Virginia, Azure Resource Manager, and GCE, but all other actions are denied. The policy is simple: Read a Cloud and Create Resources.


More advanced policies can be created. For example, you can grant or deny permission to all ClearGLASS features.


You can also give users Read only access or allow them to Edit Tags or Read Logs.


Use the multi-cloud provisioning policy at the beginning of this article to get going, the setup process should only take a few minutes. Next, you can invite members to join your team. Each Member will get their own ClearGLASS account, user name, and password. When they log in to their account, they will only be able to perform actions based on the Team Policy you have created.

content/en_us/cg_how-to-setup-rbac-for-multi-cloud-environment.txt · Last modified: 2018/03/08 19:14 by cjones