Google Access Context Manager (VPC Service Controls) Access Level

This page shows how to write Terraform for Access Context Manager (VPC Service Controls) Access Level and write them securely.

google_access_context_manager_access_level (Terraform)

The Access Level in Access Context Manager (VPC Service Controls) can be configured in Terraform with the resource name google_access_context_manager_access_level. The following sections describe 1 example of how to use the resource and its parameters.

Example Usage from GitHub
resource "google_access_context_manager_access_level" "this" {
  description = var.description
  name        =
  parent      = var.parent
  title       = var.title

Review your Terraform file for Google best practices

Shisho Cloud, our free checker to make sure your Terraform configuration follows best practices, is available (beta).


Description of the AccessLevel and its use. Does not affect behavior.

  • id optional computed - string
  • name required - string

Resource name for the Access Level. The shortname component must begin with a letter and only include alphanumeric and ''. Format: accessPolicies/[policy_id]/accessLevels/[short_name]

The AccessPolicy this AccessLevel lives in. Format: accessPolicies/[policy_id]

Human readable title. Must be unique within the Policy.

  • basic list block

    How the conditions list should be combined to determine if a request is granted this AccessLevel. If AND is used, each Condition in conditions must be satisfied for the AccessLevel to be applied. If OR is used, at least one Condition in conditions must be satisfied for the AccessLevel to be applied. Default value: "AND" Possible values: ["AND", "OR"]

    • conditions list block

      A list of CIDR block IP subnetwork specification. May be IPv4 or IPv6. Note that for a CIDR IP address block, the specified IP address portion must be properly truncated (i.e. all the host bits must be zero) or the input is considered malformed. For example, "" is accepted but "" is not. Similarly, for IPv6, "2001:db8::/32" is accepted whereas "2001:db8::1/32" is not. The originating IP of a request must be in one of the listed subnets in order for this Condition to be true. If empty, all IP addresses are allowed.

      An allowed list of members (users, service accounts). Using groups is not supported yet. The signed-in user originating the request must be a part of one of the provided members. If not specified, a request may come from any user (logged in/not logged in, not present in any groups, etc.). Formats: 'user:[emailid]', 'serviceAccount:[emailid]'

      Whether to negate the Condition. If true, the Condition becomes a NAND over its non-empty fields, each field must be false for the Condition overall to be satisfied. Defaults to false.

      The request must originate from one of the provided countries/regions. Format: A valid ISO 3166-1 alpha-2 code.

      A list of other access levels defined in the same Policy, referenced by resource name. Referencing an AccessLevel which does not exist is an error. All access levels listed must be granted for the Condition to be true. Format: accessPolicies/[policy_id]/accessLevels/[short_name]

      • device_policy list block

        A list of allowed device management levels. An empty list allows all management levels. Possible values: ["MANAGEMENT_UNSPECIFIED", "NONE", "BASIC", "COMPLETE"]

        A list of allowed encryptions statuses. An empty list allows all statuses. Possible values: ["ENCRYPTION_UNSPECIFIED", "ENCRYPTION_UNSUPPORTED", "UNENCRYPTED", "ENCRYPTED"]

        Whether the device needs to be approved by the customer admin.

        Whether the device needs to be corp owned.

        Whether or not screenlock is required for the DevicePolicy to be true. Defaults to false.

        • os_constraints list block

          The minimum allowed OS version. If not set, any version of this OS satisfies the constraint. Format: "major.minor.patch" such as "10.5.301", "9.2.1".

          The operating system type of the device. Possible values: ["OS_UNSPECIFIED", "DESKTOP_MAC", "DESKTOP_WINDOWS", "DESKTOP_LINUX", "DESKTOP_CHROME_OS"]

  • custom list block
    • expr list block

      Description of the expression

      Textual representation of an expression in Common Expression Language syntax.

      String indicating the location of the expression for error reporting, e.g. a file name and a position in the file

      Title for the expression, i.e. a short string describing its purpose.

  • timeouts single block

Explanation in Terraform Registry

An AccessLevel is a label that can be applied to requests to GCP services, along with a list of requirements necessary for the label to be applied. To get more information about AccessLevel, see:

  • API documentation
  • How-to Guides
    • Access Policy Quickstart

      Warning: If you are using User ADCs (Application Default Credentials) with this resource, you must specify a billing_project and set user_project_override to true in the provider configuration. Otherwise the ACM API will return a 403 error. Your account must have the permission on the billing_project you defined.

Frequently asked questions

What is Google Access Context Manager (VPC Service Controls) Access Level?

Google Access Context Manager (VPC Service Controls) Access Level is a resource for Access Context Manager (VPC Service Controls) of Google Cloud Platform. Settings can be wrote in Terraform.

Where can I find the example code for the Google Access Context Manager (VPC Service Controls) Access Level?

For Terraform, the niveklabs/google source code example is useful. See the Terraform Example section for further details.


Automate config file reviews on your commits

Fix issues in your infrastructure as code with auto-generated patches.