Using IAM Identity Policies to Grant Access to VPC

Prerequisites

Before granting permissions, learn about system-defined permissions in identity policy-based authorization for VPC.

To grant permissions for other services, learn about all system-defined permissions supported by IAM.

Process Flow

Figure 1 Process for granting VPC permissions using identity policy-based authorization

1. On the IAM console, create an IAM user or create a user group.

2. Attach a system-defined identity policy to the user or user group.

   Assign the permissions defined in the system-defined identity policy VPCReadOnlyPolicy to the user or group, or attach the system-defined identity policy to it.

3. Log in as the IAM user and verify permissions.

   In the authorized region, perform the following operations:

   • Choose Service List > Virtual Private Cloud. Then click Create VPC on the VPC console. If a message appears indicating that you have insufficient permissions to perform the operation, the VPCReadOnlyPolicy policy is in effect.
   • Choose another service from Service List. If a message appears indicating that you have insufficient permissions to access the service, the VPCReadOnlyPolicy policy is in effect.

Example Custom Policies

You can create custom identity policies to supplement the system-defined identity policies of VPC.

To create a custom policy, choose either visual editor or JSON.

• Visual editor: Select cloud services, actions, resources, and request conditions. This does not require knowledge of policy syntax.
• JSON: Create a JSON policy or edit an existing one.

For details, see Creating a Custom Identity Policy and Attaching It to a Principal.

When creating a custom policy, use the Resource element to specify the resources the policy applies to and use the Condition element (condition keys) to control when the policy is in effect.

The following lists examples of custom identity policies.

• Example 1: Grant permission to create and delete VPCs.

  { 
      "Version": "5.0", 
      "Statement": [ 
          { 
              "Effect": "Allow", 
              "Action": [ 
                  "vpc:vpcs:create", 
                  "vpc:vpcs:delete" 
              ] 
          } 
      ] 
  }

• Example 2: Create a custom policy containing multiple actions.
  A custom policy can contain the actions of one or multiple services. Example policy containing multiple actions:

  { 
      "Version": "5.0", 
      "Statement": [ 
          { 
              "Effect": "Allow", 
              "Action": [ 
                  "vpc:vpcs:create", 
                  "vpc:vpcs:delete" 
              ] 
          }, 
          { 
              "Effect": "Allow", 
              "Action": [ 
                  "evs:volumes:create", 
                  "evs:volumes:list" 
              ] 
          }, 
          { 
              "Effect": "Allow", 
              "Action": [ 
                  "ecs:cloudServers:createServers", 
                  "ecs:cloudServers:listServersDetails" 
              ] 
          } 
      ] 
  }