Skip to content

Latest commit

 

History

History
148 lines (135 loc) · 4.39 KB

vpc-vsi-permissions.md

File metadata and controls

148 lines (135 loc) · 4.39 KB
Raw
copyright lastupdated keywords subcollection
years
2018, 2019
2019-05-17
resource, access, role, action, permission, assign, administrator, operator, editor, viewer, user, managing
vpc-on-classic

{:shortdesc: .shortdesc} {:codeblock: .codeblock} {:screen: .screen} {:new_window: target="_blank"} {:pre: .pre} {:tip: .tip} {:note: .note} {:important: .important} {:table: .aria-labeledby="caption"}

Planning {{site.data.keyword.vsi_is_short}} Permissions

{: #planning-virtual-servers-for-vpc-permissions}

When you're planning to provision {{site.data.keyword.vsi_is_full}}, you must understand the virtual server access available based on your user role. {:shortdesc}

Review the following table to learn more about user roles and the specific level of access each role encompasses.

  • As an administrator you can define roles and take any available actions on {{site.data.keyword.vsi_is_short}}.
  • As an editor you can modify the state and create or delete subresources.
  • As an operator you can take actions that don't change the state of resources.
  • As a viewer you can take actions that don't change the state of the resources.
Table 1. User permissions
Virtual Server for VPC role Description Actions
Admin All actions including the ability to manage
access control.		 Access control:
  • Add and remove users
  • Assign roles for each user

Virtual Servers:

  • Create virtual servers
  • Delete virtual servers
  • View and list virtual servers
  • Update virtual servers
Editor Actions that can modify the state, as well
as, create and delete sub-resources.		 Virtual Servers:
  • Create virtual servers
  • Delete virtual servers
  • View and list virtual servers
  • Update virtual servers
Operator Actions that do not change state Virtual Servers:
  • View and list virtual servers
Viewer Actions that do not change state Virtual Servers:
  • View and list virtual servers

When you create an instance, you must also have Operator access for the VPC and Security Group resources, if those resources are specified. Subnet and Floating IP resources inherit permissions from the associated VPC.
{: tip}

Next steps

{: #next-manage-vpc-resource-permissions}

For more information on how to change a user's permissions, see Managing user permissions for VPC resources.