Using IAM Identity Policies to Grant Access to DNS

Prerequisites

Before granting permissions, learn about system-defined permissions in Identity Policy-based Authorization. To grant permissions for other services, learn about all system-defined policies/roles supported by IAM.

Process Flow

Figure 1 Process of granting DNS 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 DNSReadOnlyAccessPolicy 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 > Domain Name Service > Private Zones. Then click Create Private Zone. If a message appears, indicating that you have insufficient permissions to perform the operation, the DNSReadOnlyAccessPolicy policy is in effect
   • Choose any other service from Service List. If a message appears, indicating that you have insufficient permissions to access the service, the DNSReadOnlyAccessPolicy policy is in effect.

Example Custom Identity Policies

You can create custom identity policies to supplement system-defined identity policies. For details about actions supported in custom identity policies, see "Identity Policy-Based Authorization" in the Domain Name Service API Reference.

To create a custom identity 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 identity policy, use the Resource element to specify the resources the policy applies to and use the Condition element (service-specific condition keys) to control when the policy is in effect. For details about the supported resource types and condition keys, see "Identity Policy-based Authorization" in the Domain Name Service API Reference. The following are examples of custom identity policies.

• Example 1: Grant the permissions to create and delete zones.

  {
      "Version": "5.0",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "dns:zone:create",
                  "dns:zone:delete"
              ]
          }
      ]
  }

• Example 2: Create a custom identity policy that contains multiple actions.

  A custom identity policy can contain the actions of one or multiple services. The following is an example policy containing multiple actions:

  {
      "Version": "5.0",
      "Statement": [
          {
              "Effect": "Allow",
              "Action": [
                  "dns:zone:create",
                  "dns:recordset:create"
              ]
          },
          {
              "Effect": "Deny",
              "Action": [
                  "dns:zone:delete",
                  "dns:recordset:delete"
              ]
          },
          {
              "Effect": "Allow",
              "Action": [
                  "vpc:vpcs:get",
                  "vpc:vpcs:list"
              ]
          }
      ]
  }