Add IAM conditions

This page applies to Apigee and Apigee hybrid.

Identity and Access Management (IAM) Conditions lets you to define and enforce conditional access control for Google Cloud resources, including API hub resources. For more information about IAM Conditions, see Overview of IAM Conditions.

In API hub, you can enforce conditional access based on the following IAM resource condition attributes:

resource.service condition attribute: Use to configure conditional access based on the Google Cloud service being used. For example, you can set a condition limiting a user's access to resources that use the apihub.googleapis.com. For a list of supported values, see Resource service values.
resource.type condition attribute: Use to configure conditional access based on the type of resource being accessed. For example, you can set a condition limiting a user's access to apihub.googleapis.com/Api. For a list of supported values, see Resource type values.
resource.name condition attribute: Use to configure conditional access based on all or part of the name of a resource. For a list of supported API hub name formats, see Resource name format.
Resource tags: Use to configure conditional access based on the tags attached to a resource. For example, you can set a condition that grants a role only for resources that have the tag env: prod attached.

Add IAM condition

To add an IAM condition to a existing principal (user, group, or service account), perform the following steps:

In the Google Cloud console, go to the IAM page.

Go to IAM
Select your project, folder, or organization.
From the list of principals, find the principal for which you want to add the IAM condition, and click (Edit principal).
The Edit access pane appears.
Find the role to which you want to add the IAM condition and click + Add IAM Condition.
In the Add condition pane, provide the following information:
1. Title: Enter a name for the condition that you're adding to the role.
2. Description: (Optional) Enter a description for the condition.
3. You can add a condition using either the Condition builder or the Condition editor.
  The Condition builder provides an interactive interface to select your desired condition type, operator, and other applicable details about the expression. The Condition editor provides a text-based interface to manually enter a condition expression using CEL syntax.
  
  For detailed instructions about how to use the Condition builder or the Condition editor, see Configure resource-based access.
4. Click Save to apply the condition.
Click Save again from the Edit access pane to update the principal.

Examples of using IAM conditions for API hub

Example 1: Access control for all API resources starting with a prefix or based on a Tag.

The following condition expression defines access control as follows:

Access to API resources starting with prefix. This includes access to all API resources (API versions, deployments, specifications, operations, and definitions) under that prefix.
Access to API resources that have a specific tag applied, regardless of their name.
Default role-based non-conditional access to other API hub resources.

  (
    resource.name.startsWith("projects/PROJECT_ID/locations/LOCATION/apis/API_ID_PREFIX") ||
    resource.matchTagId("tagKeys/TAG_KEY", "tagValues/TAG_VALUE") ||
    (
      resource.type != "apihub.googleapis.com/Api" &&
      resource.type != "apihub.googleapis.com/Version" &&
      resource.type != "apihub.googleapis.com/Spec" &&
      resource.type != "apihub.googleapis.com/ApiOperation" &&
      resource.type != "apihub.googleapis.com/Definition"
    )
  )

Replace the following:

PROJECT_ID: The ID of your Google Cloud project.
LOCATION: The API hub location.
API_ID_PREFIX: The prefix for the API resource name.
TAG_KEY: The key of the tag to use for conditional access.
TAG_VALUE: The value of the tag to use for conditional access.

Example 2: Access control for multiple APIs with IAM conditions based on resource type.