Module compute

Modules

• address
  Represents an Address resource.
• attached_disk
  Persistent disks can be attached to a compute instance using the attached_disk section within the compute instance configuration. However there may be situations where managing the attached disks via the compute instance config isn’t preferable or possible, such as attaching dynamic numbers of disks using the count variable.
• autoscaler
  Represents an Autoscaler resource.
• backend_bucket
  Backend buckets allow you to use Google Cloud Storage buckets with HTTP(S) load balancing.
• backend_bucket_iam_binding
  Import
• backend_bucket_iam_member
  Import
• backend_bucket_iam_policy
  Import
• backend_bucket_signed_url_key
  A key for signing Cloud CDN signed URLs for BackendBuckets.
• backend_service
  A Backend Service defines a group of virtual machines that will serve traffic for load balancing. This resource is a global backend service, appropriate for external load balancing or self-managed internal load balancing. For managed internal load balancing, use a regional backend service instead.
• backend_service_iam_binding
  Import
• backend_service_iam_member
  Import
• backend_service_iam_policy
  Import
• backend_service_signed_url_key
  A key for signing Cloud CDN signed URLs for Backend Services.
• ca_external_account_key
  A representation of an ExternalAccountKey used for external account binding within ACME.
• disk
  Persistent disks are durable storage devices that function similarly to the physical disks in a desktop or a server. Compute Engine manages the hardware behind these devices to ensure data redundancy and optimize performance for you. Persistent disks are available as either standard hard disk drives (HDD) or solid-state drives (SSD).
• disk_async_replication
  Starts and stops asynchronous persistent disk replication. For more information see the official documentation and the API.
• disk_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
• disk_iam_member
  Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
• disk_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
• disk_resource_policy_attachment
  Adds existing resource policies to a disk. You can only add one policy which will be applied to this disk for scheduling snapshot creation.
• external_vpn_gateway
  Represents a VPN gateway managed outside of GCP.
• firewall
  Each network has its own firewall controlling access to and from the instances.
• firewall_policy
  Hierarchical firewall policy rules let you create and enforce a consistent firewall policy across your organization. Rules can explicitly allow or deny connections or delegate evaluation to lower level policies. Policies can be created within organizations or folders.
• firewall_policy_association
  Allows associating hierarchical firewall policies with the target where they are applied. This allows creating policies and rules in a different location than they are applied.
• firewall_policy_rule
  Represents a rule that describes one or more match conditions along with the action to be taken when traffic matches this condition (allow or deny).
• firewall_policy_with_rules
  Example Usage
• forwarding_rule
  A ForwardingRule resource. A ForwardingRule resource specifies which pool of target virtual machines to forward a packet to if it matches the given [IPAddress, IPProtocol, portRange] tuple.
• global_address
  Represents a Global Address resource. Global addresses are used for HTTP(S) load balancing.
• global_forwarding_rule
  Represents a GlobalForwardingRule resource. Global forwarding rules are used to forward traffic to the correct load balancer for HTTP load balancing. Global forwarding rules can only be used for HTTP load balancing.
• global_network_endpoint
  A Global Network endpoint represents a IP address and port combination that exists outside of GCP. NOTE: Global network endpoints cannot be created outside of a global network endpoint group.
• global_network_endpoint_group
  A global network endpoint group contains endpoints that reside outside of Google Cloud. Currently a global network endpoint group can only support a single endpoint.
• ha_vpn_gateway
  Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you. This type of VPN Gateway allows for the creation of VPN solutions with higher availability than classic Target VPN Gateways.
• health_check
  Health Checks determine whether instances are responsive and able to do work. They are an important part of a comprehensive load balancing configuration, as they enable monitoring instances behind load balancers.
• http_health_check
  An HttpHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTP.
• https_health_check
  An HttpsHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTPS.
• image
  Represents an Image resource.
• image_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
• image_iam_member
  Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
• image_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
• instance
  Manages a VM instance resource within GCE. For more information see the official documentation and API.
• instance_from_machine_image
  Manages a VM instance resource within GCE. For more information see the official documentation and API.
• instance_from_template
  Manages a VM instance resource within GCE. For more information see the official documentation and API.
• instance_group
  Creates a group of dissimilar Compute Engine virtual machine instances. For more information, see the official documentation and API
• instance_group_manager
  The Google Compute Engine Instance Group Manager API creates and manages pools of homogeneous Compute Engine virtual machine instances from a common instance template. For more information, see the official documentation and API
• instance_group_membership
  Represents the Instance membership to the Instance Group.
• instance_group_named_port
  Mange the named ports setting for a managed instance group without managing the group as whole. This resource is primarily intended for use with GKE-generated groups that shouldn’t otherwise be managed by other tools.
• instance_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
• instance_iam_member
  Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
• instance_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
• instance_settings
  Represents an Instance Settings resource. Instance settings are centralized configuration parameters that allow users to configure the default values for specific VM parameters that are normally set using GCE instance API methods.
• instance_template

  Note: Global instance templates can be used in any region. To lower the impact of outages outside your region and gain data residency within your region, use google_compute_region_instance_template.

• interconnect
  Represents an Interconnect resource. The Interconnect resource is a dedicated connection between Google’s network and your on-premises network.
• interconnect_attachment
  Represents an InterconnectAttachment (VLAN attachment) resource. For more information, see Creating VLAN Attachments.
• machine_image
  Represents a Machine Image resource. Machine images store all the configuration, metadata, permissions, and data from one or more disks required to create a Virtual machine (VM) instance.
• machine_image_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine MachineImage. Each of these resources serves a different use case:
• machine_image_iam_member
  Three different resources help you manage your IAM policy for Compute Engine MachineImage. Each of these resources serves a different use case:
• machine_image_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine MachineImage. Each of these resources serves a different use case:
• managed_ssl_certificate
  An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google.
• manged_ssl_certificate
  An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google.
• network
  Manages a VPC network or legacy network resource on GCP.
• network_attachment
  A network attachment is a resource that lets a producer Virtual Private Cloud (VPC) network initiate connections to a consumer VPC network through a Private Service Connect interface.
• network_edge_security_service
  Example Usage
• network_endpoint
  A Network endpoint represents a IP address and port combination that is part of a specific network endpoint group (NEG). NEGs are zonal collections of these endpoints for GCP resources within a single subnet. NOTE: Network endpoints cannot be created outside of a network endpoint group.
• network_endpoint_group
  Network endpoint groups (NEGs) are zonal resources that represent collections of IP address and port combinations for GCP resources within a single subnet. Each IP address and port combination is called a network endpoint.
• network_endpoint_list
  A set of network endpoints belonging to a network endpoint group (NEG). A single network endpoint represents a IP address and port combination that is part of a specific network endpoint group (NEG). NEGs are zonal collections of these endpoints for GCP resources within a single subnet. NOTE: Network endpoints cannot be created outside of a network endpoint group.
• network_firewall_policy
  The Compute NetworkFirewallPolicy resource
• network_firewall_policy_association
  The Compute NetworkFirewallPolicyAssociation resource
• network_firewall_policy_rule
  Represents a rule that describes one or more match conditions along with the action to be taken when traffic matches this condition (allow or deny).
• network_firewall_policy_with_rules
  Example Usage
• network_peering
  Manages a network peering within GCE. For more information see the official documentation and API.
• network_peering_routes_config
  Manage a network peering’s route settings without managing the peering as a whole. This resource is primarily intended for use with GCP-generated peerings that shouldn’t otherwise be managed by other tools. Deleting this resource is a no-op and the peering will not be modified.
• node_group
  Represents a NodeGroup resource to manage a group of sole-tenant nodes.
• node_template
  Represents a NodeTemplate resource. Node templates specify properties for creating sole-tenant nodes, such as node type, vCPU and memory requirements, node affinity labels, and region.
• organization_security_policy
  Organization security policies are used to control incoming/outgoing traffic.
• organization_security_policy_association
  An association for the OrganizationSecurityPolicy.
• organization_security_policy_rule
  A rule for the OrganizationSecurityPolicy.
• packet_mirroring
  Packet Mirroring mirrors traffic to and from particular VM instances. You can use the collected traffic to help you detect security threats and monitor application performance.
• per_instance_config
  A config defined for a single managed instance that belongs to an instance group manager. It preserves the instance name across instance group manager operations and can define stateful disks or metadata that are unique to the instance.
• project_cloud_armor_tier
  Sets the Cloud Armor tier of the project.
• project_default_network_tier
  Configures the Google Compute Engine Default Network Tier for a project.
• project_metadata
  Authoritatively manages metadata common to all instances for a project in GCE. For more information see the official documentation and API.
• project_metadata_item
  Manages a single key/value pair on metadata common to all instances for a project in GCE. Using gcp.compute.ProjectMetadataItem lets you manage a single key/value setting in the provider rather than the entire project metadata map.
• public_advertised_prefix
  Represents a PublicAdvertisedPrefix for use with bring your own IP addresses (BYOIP).
• public_delegated_prefix
  Represents a PublicDelegatedPrefix for use with bring your own IP addresses (BYOIP).
• region_autoscaler
  Represents an Autoscaler resource.
• region_backend_service
  A Region Backend Service defines a regionally-scoped group of virtual machines that will serve traffic for load balancing.
• region_backend_service_iam_binding
  Import
• region_backend_service_iam_member
  Import
• region_backend_service_iam_policy
  Import
• region_commitment
  Represents a regional Commitment resource.
• region_disk
  Persistent disks are durable storage devices that function similarly to the physical disks in a desktop or a server. Compute Engine manages the hardware behind these devices to ensure data redundancy and optimize performance for you. Persistent disks are available as either standard hard disk drives (HDD) or solid-state drives (SSD).
• region_disk_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine RegionDisk. Each of these resources serves a different use case:
• region_disk_iam_member
  Three different resources help you manage your IAM policy for Compute Engine RegionDisk. Each of these resources serves a different use case:
• region_disk_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine RegionDisk. Each of these resources serves a different use case:
• region_disk_resource_policy_attachment
  Adds existing resource policies to a disk. You can only add one policy which will be applied to this disk for scheduling snapshot creation.
• region_health_check
  Health Checks determine whether instances are responsive and able to do work. They are an important part of a comprehensive load balancing configuration, as they enable monitoring instances behind load balancers.
• region_instance_group_manager
  The Google Compute Engine Regional Instance Group Manager API creates and manages pools of homogeneous Compute Engine virtual machine instances from a common instance template.
• region_instance_template
  Import
• region_network_endpoint
  A Region network endpoint represents a IP address/FQDN and port combination that is part of a specific network endpoint group (NEG).
• region_network_endpoint_group
  A regional NEG that can support Serverless Products, proxying traffic to external backends and providing traffic to the PSC port mapping endpoints.
• region_network_firewall_policy
  The Compute NetworkFirewallPolicy resource
• region_network_firewall_policy_association
  The Compute NetworkFirewallPolicyAssociation resource
• region_network_firewall_policy_rule
  Represents a rule that describes one or more match conditions along with the action to be taken when traffic matches this condition (allow or deny).
• region_network_firewall_policy_with_rules
  Example Usage
• region_per_instance_config
  A config defined for a single managed instance that belongs to an instance group manager. It preserves the instance name across instance group manager operations and can define stateful disks or metadata that are unique to the instance. This resource works with regional instance group managers.
• region_resize_request
  Example Usage
• region_security_policy
  Example Usage
• region_security_policy_rule
  Example Usage
• region_ssl_certificate
  A RegionSslCertificate resource, used for HTTPS load balancing. This resource provides a mechanism to upload an SSL key and certificate to the load balancer to serve secure connections from the user.
• region_ssl_policy
  Represents a Regional SSL policy. SSL policies give you the ability to control the features of SSL that your SSL proxy or HTTPS load balancer negotiates.
• region_target_http_proxy
  Represents a RegionTargetHttpProxy resource, which is used by one or more forwarding rules to route incoming HTTP requests to a URL map.
• region_target_https_proxy
  Represents a RegionTargetHttpsProxy resource, which is used by one or more forwarding rules to route incoming HTTPS requests to a URL map.
• region_target_tcp_proxy
  Represents a RegionTargetTcpProxy resource, which is used by one or more forwarding rules to route incoming TCP requests to a regional TCP proxy load balancer.
• region_url_map
  UrlMaps are used to route requests to a backend service based on rules that you define for the host and path of an incoming URL.
• reservation
  Represents a reservation resource. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running.
• resize_request
  Represents a Managed Instance Group Resize Request
• resource_policy
  A policy that can be attached to a resource to specify or schedule actions on that resource.
• route
  Represents a Route resource.
• router
  Represents a Router resource.
• router_interface
  Manages a Cloud Router interface. For more information see the official documentation and API.
• router_nat
  A NAT service created in a router.
• router_nat_address
  A resource used to set the list of IP addresses to be used in a NAT service and manage the draining of destroyed IPs.
• router_peer
  BGP information that must be configured into the routing stack to establish BGP peering. This information must specify the peer ASN and either the interface name, IP address, or peer IP address. Please refer to RFC4273.
• router_route_policy
  Example Usage
• security_policy
  A Security Policy defines an IP blacklist or whitelist that protects load balanced Google Cloud services by denying or permitting traffic from specified IP ranges. For more information see the official documentation and the API.
• security_policy_rule
  A rule for the SecurityPolicy.
• security_scan_config
  A ScanConfig resource contains the configurations to launch a scan.
• service_attachment
  Represents a ServiceAttachment resource.
• shared_vpc_host_project
  Enables the Google Compute Engine Shared VPC feature for a project, assigning it as a Shared VPC host project.
• shared_vpc_service_project
  Enables the Google Compute Engine Shared VPC feature for a project, assigning it as a Shared VPC service project associated with a given host project.
• snapshot
  Represents a Persistent Disk Snapshot resource.
• snapshot_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
• snapshot_iam_member
  Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
• snapshot_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
• ssl_certificate
  An SslCertificate resource, used for HTTPS load balancing. This resource provides a mechanism to upload an SSL key and certificate to the load balancer to serve secure connections from the user.
• ssl_policy
  Represents a SSL policy. SSL policies give you the ability to control the features of SSL that your SSL proxy or HTTPS load balancer negotiates.
• subnetwork
  A VPC network is a virtual version of the traditional physical networks that exist within and between physical data centers. A VPC network provides connectivity for your Compute Engine virtual machine (VM) instances, Container Engine containers, App Engine Flex services, and other network-related resources.
• subnetwork_iam_binding
  Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
• subnetwork_iam_member
  Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
• subnetwork_iam_policy
  Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
• target_grpc_proxy
  Represents a Target gRPC Proxy resource. A target gRPC proxy is a component of load balancers intended for load balancing gRPC traffic. Global forwarding rules reference a target gRPC proxy. The Target gRPC Proxy references a URL map which specifies how traffic routes to gRPC backend services.
• target_http_proxy
  Represents a TargetHttpProxy resource, which is used by one or more global forwarding rule to route incoming HTTP requests to a URL map.
• target_https_proxy
  Represents a TargetHttpsProxy resource, which is used by one or more global forwarding rule to route incoming HTTPS requests to a URL map.
• target_instance
  Represents a TargetInstance resource which defines an endpoint instance that terminates traffic of certain protocols. In particular, they are used in Protocol Forwarding, where forwarding rules can send packets to a non-NAT’ed target instance. Each target instance contains a single virtual machine instance that receives and handles traffic from the corresponding forwarding rules.
• target_pool
  Manages a Target Pool within GCE. This is a collection of instances used as target of a network load balancer (Forwarding Rule). For more information see the official documentation and API.
• target_ssl_proxy
  Represents a TargetSslProxy resource, which is used by one or more global forwarding rule to route incoming SSL requests to a backend service.
• target_tcp_proxy
  Represents a TargetTcpProxy resource, which is used by one or more global forwarding rule to route incoming TCP requests to a Backend service.
• url_map
  UrlMaps are used to route requests to a backend service based on rules that you define for the host and path of an incoming URL.
• vpn_gateway
  Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you.
• vpn_tunnel
  VPN tunnel resource.