We’ve all experienced it before – an inadvertent change that caused a cascading failure. It could be the change of a file’s headers that caused a script to fail. Or the removal of a node from a load balancer that is causing high response times. Or even the new guy who cuts his teeth by deleting a production server accidentally.
While there will always be a human element (until SkyNet comes online, that is), restricting human access is one way to make these kinds of failures less frequent.
Over the next few months, we will be rolling out Role-Based Access Controls (RBAC). This gives you the ability to:
- Create up to 100 additional users for your account, each with their own password, secret question and answer and API key.
- Grant a variety of roles to the users allowing full access, read-only access or product-specific access.
The first roll-out includes the following products:
- Next generation Cloud Servers
- First generation Cloud Servers
- Cloud Files
- Cloud Load Balancers
- Cloud Databases
We are continuing to work on fine-grained access control (restricting access to specific servers, files, databases, etc.) and two-factor authentication (requiring more than just a password to access your account).
RBAC will be available via the Next Generation Cloud Control Panel (https://mycloud.rackspace.com) and Cloud Identity API (http://docs.rackspace.com/auth/api/v2.0/auth-client-devguide/content/API_Operations.html).
For more information on how RBAC roles are configured, please see http://www.rackspace.com/knowledge_center/article/overview-role-based-access-control-rbac.