Package-level declarations
Types
Represents an Address resource. Each virtual machine instance has an ephemeral internal IP address and, optionally, an external IP address. To communicate between instances on the same network, you can use an instance's internal IP address. To communicate with the Internet and instances outside of the same network, you must specify the instance's external IP address. Internal IP addresses are ephemeral and only belong to an instance for the lifetime of the instance; if the instance is deleted and recreated, the instance is assigned a new internal IP address, either by Compute Engine or by you. External IP addresses can be either ephemeral or static. To get more information about Address, see:
Represents an Address resource. Each virtual machine instance has an ephemeral internal IP address and, optionally, an external IP address. To communicate between instances on the same network, you can use an instance's internal IP address. To communicate with the Internet and instances outside of the same network, you must specify the instance's external IP address. Internal IP addresses are ephemeral and only belong to an instance for the lifetime of the instance; if the instance is deleted and recreated, the instance is assigned a new internal IP address, either by Compute Engine or by you. External IP addresses can be either ephemeral or static. To get more information about Address, see:
Builder for AddressArgs.
Builder for Address.
Attached Disk can be imported the following ways
Attached Disk can be imported the following ways
Builder for AttachedDiskArgs.
Builder for AttachedDisk.
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about Autoscaler, see:
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about Autoscaler, see:
Builder for AutoscalarArgs.
Builder for Autoscalar.
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about Autoscaler, see:
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about Autoscaler, see:
Builder for AutoscalerArgs.
Builder for Autoscaler.
Backend buckets allow you to use Google Cloud Storage buckets with HTTP(S) load balancing. An HTTP(S) load balancer can direct traffic to specified URLs to a backend bucket rather than a backend service. It can send requests for static content to a Cloud Storage bucket and requests for dynamic content to a virtual machine instance. To get more information about BackendBucket, see:
Backend buckets allow you to use Google Cloud Storage buckets with HTTP(S) load balancing. An HTTP(S) load balancer can direct traffic to specified URLs to a backend bucket rather than a backend service. It can send requests for static content to a Cloud Storage bucket and requests for dynamic content to a virtual machine instance. To get more information about BackendBucket, see:
Builder for BackendBucketArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendBucketIamBindingArgs.
Builder for BackendBucketIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendBucketIamMemberArgs.
Builder for BackendBucketIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendBuckets/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendbucket IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendBucketIamPolicyArgs.
Builder for BackendBucketIamPolicy.
Builder for BackendBucket.
This resource does not support import.
This resource does not support import.
Builder for BackendBucketSignedUrlKeyArgs.
Builder for BackendBucketSignedUrlKey.
BackendService can be imported using any of these accepted formats
BackendService can be imported using any of these accepted formats
Builder for BackendServiceArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendServiceIamBindingArgs.
Builder for BackendServiceIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendServiceIamMemberArgs.
Builder for BackendServiceIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/backendServices/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine backendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for BackendServiceIamPolicyArgs.
Builder for BackendServiceIamPolicy.
Builder for BackendService.
This resource does not support import.
This resource does not support import.
Builder for BackendServiceSignedUrlKeyArgs.
Builder for BackendServiceSignedUrlKey.
Disk can be imported using any of these accepted formats
Disk can be imported using any of these accepted formats
Builder for DiskArgs.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for DiskIamBindingArgs.
Builder for DiskIamBinding.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for DiskIamMemberArgs.
Builder for DiskIamMember.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for DiskIamPolicyArgs.
Builder for DiskIamPolicy.
Builder for Disk.
DiskResourcePolicyAttachment can be imported using any of these accepted formats
DiskResourcePolicyAttachment can be imported using any of these accepted formats
Builder for DiskResourcePolicyAttachmentArgs.
Builder for DiskResourcePolicyAttachment.
Represents a VPN gateway managed outside of GCP. To get more information about ExternalVpnGateway, see:
Represents a VPN gateway managed outside of GCP. To get more information about ExternalVpnGateway, see:
Builder for ExternalVpnGatewayArgs.
Builder for ExternalVpnGateway.
Each network has its own firewall controlling access to and from the instances. All traffic to instances, even from other instances, is blocked by the firewall unless firewall rules are created to allow it. The default network has automatically created firewall rules that are shown in default firewall rules. No manually created network has automatically created firewall rules except for a default "allow" rule for outgoing traffic and a default "deny" for incoming traffic. For all networks except the default network, you must create any firewall rules you need. To get more information about Firewall, see:
Each network has its own firewall controlling access to and from the instances. All traffic to instances, even from other instances, is blocked by the firewall unless firewall rules are created to allow it. The default network has automatically created firewall rules that are shown in default firewall rules. No manually created network has automatically created firewall rules except for a default "allow" rule for outgoing traffic and a default "deny" for incoming traffic. For all networks except the default network, you must create any firewall rules you need. To get more information about Firewall, see:
Builder for FirewallArgs.
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. This resource should be generally be used with gcp.compute.FirewallPolicyAssociation and gcp.compute.FirewallPolicyRule For more information see the official documentation
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. This resource should be generally be used with gcp.compute.FirewallPolicyAssociation and gcp.compute.FirewallPolicyRule For more information see the official documentation
Builder for FirewallPolicyArgs.
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. For more information on applying hierarchical firewall policies see the official documentation
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. For more information on applying hierarchical firewall policies see the official documentation
Builder for FirewallPolicyAssociationArgs.
Builder for FirewallPolicyAssociation.
Builder for FirewallPolicy.
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. For more information see the official documentation
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. For more information see the official documentation
Builder for FirewallPolicyRuleArgs.
Builder for FirewallPolicyRule.
Builder for Firewall.
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. To get more information about ForwardingRule, see:
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. To get more information about ForwardingRule, see:
Builder for ForwardingRuleArgs.
Builder for ForwardingRule.
Represents a Global Address resource. Global addresses are used for HTTP(S) load balancing. To get more information about GlobalAddress, see:
Represents a Global Address resource. Global addresses are used for HTTP(S) load balancing. To get more information about GlobalAddress, see:
Builder for GlobalAddressArgs.
Builder for GlobalAddress.
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. For more information, see https://cloud.google.com/compute/docs/load-balancing/http/
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. For more information, see https://cloud.google.com/compute/docs/load-balancing/http/
Builder for GlobalForwardingRuleArgs.
Builder for GlobalForwardingRule.
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. To get more information about GlobalNetworkEndpoint, see:
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. To get more information about GlobalNetworkEndpoint, see:
Builder for GlobalNetworkEndpointArgs.
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. Recreating a global network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about GlobalNetworkEndpointGroup, see:
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. Recreating a global network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about GlobalNetworkEndpointGroup, see:
Builder for GlobalNetworkEndpointGroupArgs.
Builder for GlobalNetworkEndpointGroup.
Builder for GlobalNetworkEndpoint.
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. To get more information about HaVpnGateway, see:
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. To get more information about HaVpnGateway, see:
Builder for HaVpnGatewayArgs.
Builder for HaVpnGateway.
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. Health Checks poll instances at a specified interval. Instances that do not respond successfully to some number of probes in a row are marked as unhealthy. No new connections are sent to unhealthy instances, though existing connections will continue. The health check will continue to poll unhealthy instances. If an instance later responds successfully to some number of consecutive probes, it is marked healthy again and can receive new connections. ~>NOTE: Legacy HTTP(S) health checks must be used for target pool-based network load balancers. See the official guide for choosing a type of health check. To get more information about HealthCheck, see:
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. Health Checks poll instances at a specified interval. Instances that do not respond successfully to some number of probes in a row are marked as unhealthy. No new connections are sent to unhealthy instances, though existing connections will continue. The health check will continue to poll unhealthy instances. If an instance later responds successfully to some number of consecutive probes, it is marked healthy again and can receive new connections. ~>NOTE: Legacy HTTP(S) health checks must be used for target pool-based network load balancers. See the official guide for choosing a type of health check. To get more information about HealthCheck, see:
Builder for HealthCheckArgs.
Builder for HealthCheck.
An HttpHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTP.
An HttpHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTP.
Builder for HttpHealthCheckArgs.
Builder for HttpHealthCheck.
An HttpsHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTPS.
An HttpsHealthCheck resource. This resource defines a template for how individual VMs should be checked for health, via HTTPS.
Builder for HttpsHealthCheckArgs.
Builder for HttpsHealthCheck.
Represents an Image resource. Google Compute Engine uses operating system images to create the root persistent disks for your instances. You specify an image when you create an instance. Images contain a boot loader, an operating system, and a root file system. Linux operating system images are also capable of running containers on Compute Engine. Images can be either public or custom. Public images are provided and maintained by Google, open-source communities, and third-party vendors. By default, all projects have access to these images and can use them to create instances. Custom images are available only to your project. You can create a custom image from root persistent disks and other images. Then, use the custom image to create an instance. To get more information about Image, see:
Represents an Image resource. Google Compute Engine uses operating system images to create the root persistent disks for your instances. You specify an image when you create an instance. Images contain a boot loader, an operating system, and a root file system. Linux operating system images are also capable of running containers on Compute Engine. Images can be either public or custom. Public images are provided and maintained by Google, open-source communities, and third-party vendors. By default, all projects have access to these images and can use them to create instances. Custom images are available only to your project. You can create a custom image from root persistent disks and other images. Then, use the custom image to create an instance. To get more information about Image, see:
Builder for ImageArgs.
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Builder for ImageIamBindingArgs.
Builder for ImageIamBinding.
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Builder for ImageIamMemberArgs.
Builder for ImageIamMember.
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Image. Each of these resources serves a different use case:
Builder for ImageIamPolicyArgs.
Builder for ImageIamPolicy.
Builder for Image.
Manages a VM instance resource within GCE. For more information see the official documentation and API.
Manages a VM instance resource within GCE. For more information see the official documentation and API.
Builder for InstanceArgs.
Builder for InstanceFromMachineImageArgs.
Builder for InstanceFromMachineImage.
Manages a VM instance resource within GCE. For more information see the official documentation and API. This resource is specifically to create a compute instance from a given source_instance_template. To create an instance without a template, use the gcp.compute.Instance resource.
Manages a VM instance resource within GCE. For more information see the official documentation and API. This resource is specifically to create a compute instance from a given source_instance_template. To create an instance without a template, use the gcp.compute.Instance resource.
Builder for InstanceFromTemplateArgs.
Builder for InstanceFromTemplate.
Instance group can be imported using the zone and name with an optional project, e.g.
Instance group can be imported using the zone and name with an optional project, e.g.
Builder for InstanceGroupArgs.
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
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
Builder for InstanceGroupManagerArgs.
Builder for InstanceGroupManager.
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. To get more information about InstanceGroupNamedPort, see:
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. To get more information about InstanceGroupNamedPort, see:
Builder for InstanceGroupNamedPortArgs.
Builder for InstanceGroupNamedPort.
Builder for InstanceGroup.
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Builder for InstanceIAMBindingArgs.
Builder for InstanceIAMBinding.
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Builder for InstanceIAMMemberArgs.
Builder for InstanceIAMMember.
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Instance. Each of these resources serves a different use case:
Builder for InstanceIAMPolicyArgs.
Builder for InstanceIAMPolicy.
Builder for Instance.
Instance templates can be imported using any of these accepted formats
Instance templates can be imported using any of these accepted formats
Builder for InstanceTemplateArgs.
Builder for InstanceTemplate.
Represents an InterconnectAttachment (VLAN attachment) resource. For more information, see Creating VLAN Attachments.
Represents an InterconnectAttachment (VLAN attachment) resource. For more information, see Creating VLAN Attachments.
Builder for InterconnectAttachmentArgs.
Builder for InterconnectAttachment.
MachineImage can be imported using any of these accepted formats
MachineImage can be imported using any of these accepted formats
Builder for MachineImageArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for MachineImageIamBindingArgs.
Builder for MachineImageIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for MachineImageIamMemberArgs.
Builder for MachineImageIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/global/machineImages/{{name}} * {{project}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine machineimage IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for MachineImageIamPolicyArgs.
Builder for MachineImageIamPolicy.
Builder for MachineImage.
An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google. For a resource where you provide the key, see the SSL Certificate resource. To get more information about ManagedSslCertificate, see:
An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google. For a resource where you provide the key, see the SSL Certificate resource. To get more information about ManagedSslCertificate, see:
Builder for ManagedSslCertificateArgs.
Builder for ManagedSslCertificate.
An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google. For a resource where you provide the key, see the SSL Certificate resource. To get more information about ManagedSslCertificate, see:
An SslCertificate resource, used for HTTPS load balancing. This resource represents a certificate for which the certificate secrets are created and managed by Google. For a resource where you provide the key, see the SSL Certificate resource. To get more information about ManagedSslCertificate, see:
Builder for MangedSslCertificateArgs.
Builder for MangedSslCertificate.
Manages a VPC network or legacy network resource on GCP. To get more information about Network, see:
Manages a VPC network or legacy network resource on GCP. To get more information about Network, see:
Builder for NetworkArgs.
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. To get more information about NetworkEndpoint, see:
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. To get more information about NetworkEndpoint, see:
Builder for NetworkEndpointArgs.
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 groups can be used as backends in backend services for HTTP(S), TCP proxy, and SSL proxy load balancers. You cannot use NEGs as a backend with internal load balancers. Because NEG backends allow you to specify IP addresses and ports, you can distribute traffic in a granular fashion among applications or containers running within VM instances. Recreating a network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about NetworkEndpointGroup, see:
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 groups can be used as backends in backend services for HTTP(S), TCP proxy, and SSL proxy load balancers. You cannot use NEGs as a backend with internal load balancers. Because NEG backends allow you to specify IP addresses and ports, you can distribute traffic in a granular fashion among applications or containers running within VM instances. Recreating a network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about NetworkEndpointGroup, see:
Builder for NetworkEndpointGroupArgs.
Builder for NetworkEndpointGroup.
Builder for NetworkEndpoint.
The Compute NetworkFirewallPolicy resource
The Compute NetworkFirewallPolicy resource
Builder for NetworkFirewallPolicyArgs.
The Compute NetworkFirewallPolicyAssociation resource
The Compute NetworkFirewallPolicyAssociation resource
Builder for NetworkFirewallPolicy.
The Compute NetworkFirewallPolicyRule resource
The Compute NetworkFirewallPolicyRule resource
Builder for NetworkFirewallPolicyRuleArgs.
Builder for NetworkFirewallPolicyRule.
Manages a network peering within GCE. For more information see the official documentation and API.
Manages a network peering within GCE. For more information see the official documentation and API.
Builder for NetworkPeeringArgs.
Builder for NetworkPeering.
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. To get more information about NetworkPeeringRoutesConfig, see:
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. To get more information about NetworkPeeringRoutesConfig, see:
Builder for NetworkPeeringRoutesConfigArgs.
Builder for NetworkPeeringRoutesConfig.
Builder for Network.
NodeGroup can be imported using any of these accepted formats
NodeGroup can be imported using any of these accepted formats
Builder for NodeGroupArgs.
Builder for NodeGroup.
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. To get more information about NodeTemplate, see:
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. To get more information about NodeTemplate, see:
Builder for NodeTemplateArgs.
Builder for NodeTemplate.
{{% examples %}}
{{% examples %}}
Builder for OrganizationSecurityPolicyArgs.
{{% examples %}}
{{% examples %}}
Builder for OrganizationSecurityPolicy.
{{% examples %}}
{{% examples %}}
Builder for OrganizationSecurityPolicyRuleArgs.
Builder for OrganizationSecurityPolicyRule.
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. To get more information about PacketMirroring, see:
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. To get more information about PacketMirroring, see:
Builder for PacketMirroringArgs.
Builder for PacketMirroring.
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. To get more information about PerInstanceConfig, see:
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. To get more information about PerInstanceConfig, see:
Builder for PerInstanceConfigArgs.
Builder for PerInstanceConfig.
Configures the Google Compute Engine Default Network Tier for a project. For more information, see, the Project API documentation.
Configures the Google Compute Engine Default Network Tier for a project. For more information, see, the Project API documentation.
Builder for ProjectDefaultNetworkTierArgs.
Builder for ProjectDefaultNetworkTier.
Authoritatively manages metadata common to all instances for a project in GCE. For more information see the official documentation and API.
Authoritatively manages metadata common to all instances for a project in GCE. For more information see the official documentation and API.
Builder for ProjectMetadataArgs.
Project metadata items can be imported using the key, e.g.
Project metadata items can be imported using the key, e.g.
Builder for ProjectMetadataItemArgs.
Builder for ProjectMetadataItem.
Builder for ProjectMetadata.
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about RegionAutoscaler, see:
Represents an Autoscaler resource. Autoscalers allow you to automatically scale virtual machine instances in managed instance groups according to an autoscaling policy that you define. To get more information about RegionAutoscaler, see:
Builder for RegionAutoscalerArgs.
Builder for RegionAutoscaler.
RegionBackendService can be imported using any of these accepted formats
RegionBackendService can be imported using any of these accepted formats
Builder for RegionBackendServiceArgs.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for RegionBackendServiceIamBindingArgs.
Builder for RegionBackendServiceIamBinding.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for RegionBackendServiceIamMemberArgs.
Builder for RegionBackendServiceIamMember.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
For all import syntaxes, the "resource in question" can take any of the following forms* projects/{{project}}/regions/{{region}}/backendServices/{{name}} * {{project}}/{{region}}/{{name}} * {{region}}/{{name}} * {{name}} Any variables not passed in the import command will be taken from the provider configuration. Compute Engine regionbackendservice IAM resources can be imported using the resource identifiers, role, and member. IAM member imports use space-delimited identifiersthe resource in question, the role, and the member identity, e.g.
Builder for RegionBackendServiceIamPolicyArgs.
Builder for RegionBackendServiceIamPolicy.
Builder for RegionBackendService.
RegionDisk can be imported using any of these accepted formats
RegionDisk can be imported using any of these accepted formats
Builder for RegionDiskArgs.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for RegionDiskIamBindingArgs.
Builder for RegionDiskIamBinding.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for RegionDiskIamMemberArgs.
Builder for RegionDiskIamMember.
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Disk. Each of these resources serves a different use case:
Builder for RegionDiskIamPolicyArgs.
Builder for RegionDiskIamPolicy.
Builder for RegionDisk.
RegionDiskResourcePolicyAttachment can be imported using any of these accepted formats
RegionDiskResourcePolicyAttachment can be imported using any of these accepted formats
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. Health Checks poll instances at a specified interval. Instances that do not respond successfully to some number of probes in a row are marked as unhealthy. No new connections are sent to unhealthy instances, though existing connections will continue. The health check will continue to poll unhealthy instances. If an instance later responds successfully to some number of consecutive probes, it is marked healthy again and can receive new connections. To get more information about RegionHealthCheck, see:
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. Health Checks poll instances at a specified interval. Instances that do not respond successfully to some number of probes in a row are marked as unhealthy. No new connections are sent to unhealthy instances, though existing connections will continue. The health check will continue to poll unhealthy instances. If an instance later responds successfully to some number of consecutive probes, it is marked healthy again and can receive new connections. To get more information about RegionHealthCheck, see:
Builder for RegionHealthCheckArgs.
Builder for RegionHealthCheck.
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. To get more information about regionInstanceGroupManagers, see:
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. To get more information about regionInstanceGroupManagers, see:
Builder for RegionInstanceGroupManagerArgs.
Builder for RegionInstanceGroupManager.
A regional NEG that can support Serverless Products. Recreating a region network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about RegionNetworkEndpointGroup, see:
A regional NEG that can support Serverless Products. Recreating a region network endpoint group that's in use by another resource will give a resourceInUseByAnotherResource error. Use lifecycle.create_before_destroy to avoid this type of error. To get more information about RegionNetworkEndpointGroup, see:
Builder for RegionNetworkEndpointGroupArgs.
Builder for RegionNetworkEndpointGroup.
The Compute NetworkFirewallPolicy resource
The Compute NetworkFirewallPolicy resource
Builder for RegionNetworkFirewallPolicyArgs.
The Compute NetworkFirewallPolicyAssociation resource
The Compute NetworkFirewallPolicyAssociation resource
Builder for RegionNetworkFirewallPolicy.
The Compute NetworkFirewallPolicyRule resource
The Compute NetworkFirewallPolicyRule resource
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. To get more information about RegionPerInstanceConfig, see:
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. To get more information about RegionPerInstanceConfig, see:
Builder for RegionPerInstanceConfigArgs.
Builder for RegionPerInstanceConfig.
RegionSslCertificate can be imported using any of these accepted formats
RegionSslCertificate can be imported using any of these accepted formats
Builder for RegionSslCertificateArgs.
Builder for RegionSslCertificate.
RegionSslPolicy can be imported using any of these accepted formats
RegionSslPolicy can be imported using any of these accepted formats
Builder for RegionSslPolicyArgs.
Builder for RegionSslPolicy.
Represents a RegionTargetHttpProxy resource, which is used by one or more forwarding rules to route incoming HTTP requests to a URL map. To get more information about RegionTargetHttpProxy, see:
Represents a RegionTargetHttpProxy resource, which is used by one or more forwarding rules to route incoming HTTP requests to a URL map. To get more information about RegionTargetHttpProxy, see:
Builder for RegionTargetHttpProxyArgs.
Builder for RegionTargetHttpProxy.
Represents a RegionTargetHttpsProxy resource, which is used by one or more forwarding rules to route incoming HTTPS requests to a URL map. To get more information about RegionTargetHttpsProxy, see:
Represents a RegionTargetHttpsProxy resource, which is used by one or more forwarding rules to route incoming HTTPS requests to a URL map. To get more information about RegionTargetHttpsProxy, see:
Builder for RegionTargetHttpsProxyArgs.
Builder for RegionTargetHttpsProxy.
RegionTargetTcpProxy can be imported using any of these accepted formats
RegionTargetTcpProxy can be imported using any of these accepted formats
Builder for RegionTargetTcpProxyArgs.
Builder for RegionTargetTcpProxy.
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.
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.
Builder for RegionUrlMapArgs.
Builder for RegionUrlMap.
Represents a reservation resource. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running. Reservations apply only to Compute Engine, Cloud Dataproc, and Google Kubernetes Engine VM usage.Reservations do not apply to f1-micro or g1-small machine types, preemptible VMs, sole tenant nodes, or other services not listed above like Cloud SQL and Dataflow. To get more information about Reservation, see:
Represents a reservation resource. A reservation ensures that capacity is held in a specific zone even if the reserved VMs are not running. Reservations apply only to Compute Engine, Cloud Dataproc, and Google Kubernetes Engine VM usage.Reservations do not apply to f1-micro or g1-small machine types, preemptible VMs, sole tenant nodes, or other services not listed above like Cloud SQL and Dataflow. To get more information about Reservation, see:
Builder for ReservationArgs.
Builder for Reservation.
A policy that can be attached to a resource to specify or schedule actions on that resource.
A policy that can be attached to a resource to specify or schedule actions on that resource.
Builder for ResourcePolicyArgs.
Builder for ResourcePolicy.
Represents a Route resource. A route is a rule that specifies how certain packets should be handled by the virtual network. Routes are associated with virtual machines by tag, and the set of routes for a particular virtual machine is called its routing table. For each packet leaving a virtual machine, the system searches that virtual machine's routing table for a single best matching route. Routes match packets by destination IP address, preferring smaller or more specific ranges over larger ones. If there is a tie, the system selects the route with the smallest priority value. If there is still a tie, it uses the layer three and four packet headers to select just one of the remaining matching routes. The packet is then forwarded as specified by the next_hop field of the winning route -- either to another virtual machine destination, a virtual machine gateway or a Compute Engine-operated gateway. Packets that do not match any route in the sending virtual machine's routing table will be dropped. A Route resource must have exactly one specification of either nextHopGateway, nextHopInstance, nextHopIp, nextHopVpnTunnel, or nextHopIlb. To get more information about Route, see:
Represents a Route resource. A route is a rule that specifies how certain packets should be handled by the virtual network. Routes are associated with virtual machines by tag, and the set of routes for a particular virtual machine is called its routing table. For each packet leaving a virtual machine, the system searches that virtual machine's routing table for a single best matching route. Routes match packets by destination IP address, preferring smaller or more specific ranges over larger ones. If there is a tie, the system selects the route with the smallest priority value. If there is still a tie, it uses the layer three and four packet headers to select just one of the remaining matching routes. The packet is then forwarded as specified by the next_hop field of the winning route -- either to another virtual machine destination, a virtual machine gateway or a Compute Engine-operated gateway. Packets that do not match any route in the sending virtual machine's routing table will be dropped. A Route resource must have exactly one specification of either nextHopGateway, nextHopInstance, nextHopIp, nextHopVpnTunnel, or nextHopIlb. To get more information about Route, see:
Builder for RouteArgs.
Represents a Router resource. To get more information about Router, see:
Represents a Router resource. To get more information about Router, see:
Builder for RouterArgs.
Builder for Route.
Manages a Cloud Router interface. For more information see the official documentation and API.
Manages a Cloud Router interface. For more information see the official documentation and API.
Builder for RouterInterfaceArgs.
Builder for RouterInterface.
A NAT service created in a router. To get more information about RouterNat, see:
A NAT service created in a router. To get more information about RouterNat, see:
Builder for RouterNatArgs.
Builder for RouterNat.
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. To get more information about RouterBgpPeer, see:
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. To get more information about RouterBgpPeer, see:
Builder for RouterPeerArgs.
Builder for RouterPeer.
Builder for Router.
Security policies can be imported using any of the following formats
Security policies can be imported using any of the following formats
Builder for SecurityPolicyArgs.
Builder for SecurityPolicy.
ScanConfig can be imported using any of these accepted formats
ScanConfig can be imported using any of these accepted formats
Builder for SecurityScanConfigArgs.
Builder for SecurityScanConfig.
Represents a ServiceAttachment resource. To get more information about ServiceAttachment, see:
Represents a ServiceAttachment resource. To get more information about ServiceAttachment, see:
Builder for ServiceAttachmentArgs.
Builder for ServiceAttachment.
Enables the Google Compute Engine Shared VPC feature for a project, assigning it as a Shared VPC host project. For more information, see, the Project API documentation, where the Shared VPC feature is referred to by its former name "XPN".
Enables the Google Compute Engine Shared VPC feature for a project, assigning it as a Shared VPC host project. For more information, see, the Project API documentation, where the Shared VPC feature is referred to by its former name "XPN".
Builder for SharedVPCHostProjectArgs.
Builder for SharedVPCHostProject.
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. For more information, see, the Project API documentation, where the Shared VPC feature is referred to by its former name "XPN".
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. For more information, see, the Project API documentation, where the Shared VPC feature is referred to by its former name "XPN".
Builder for SharedVPCServiceProjectArgs.
Builder for SharedVPCServiceProject.
Snapshot can be imported using any of these accepted formats
Snapshot can be imported using any of these accepted formats
Builder for SnapshotArgs.
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Builder for SnapshotIamBindingArgs.
Builder for SnapshotIamBinding.
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Builder for SnapshotIamMemberArgs.
Builder for SnapshotIamMember.
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Snapshot. Each of these resources serves a different use case:
Builder for SnapshotIamPolicyArgs.
Builder for SnapshotIamPolicy.
Builder for Snapshot.
SslCertificate can be imported using any of these accepted formats
SslCertificate can be imported using any of these accepted formats
Builder for SSLCertificateArgs.
Builder for SSLCertificate.
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. To get more information about SslPolicy, see:
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. To get more information about SslPolicy, see:
Builder for SSLPolicyArgs.
Builder for SSLPolicy.
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. Each GCP project contains one or more VPC networks. Each VPC network is a global entity spanning all GCP regions. This global VPC network allows VM instances and other resources to communicate with each other via internal, private IP addresses. Each VPC network is subdivided into subnets, and each subnet is contained within a single region. You can have more than one subnet in a region for a given VPC network. Each subnet has a contiguous private RFC1918 IP space. You create instances, containers, and the like in these subnets. When you create an instance, you must create it in a subnet, and the instance draws its internal IP address from that subnet. Virtual machine (VM) instances in a VPC network can communicate with instances in all other subnets of the same VPC network, regardless of region, using their RFC1918 private IP addresses. You can isolate portions of the network, even entire subnets, using firewall rules. To get more information about Subnetwork, see:
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. Each GCP project contains one or more VPC networks. Each VPC network is a global entity spanning all GCP regions. This global VPC network allows VM instances and other resources to communicate with each other via internal, private IP addresses. Each VPC network is subdivided into subnets, and each subnet is contained within a single region. You can have more than one subnet in a region for a given VPC network. Each subnet has a contiguous private RFC1918 IP space. You create instances, containers, and the like in these subnets. When you create an instance, you must create it in a subnet, and the instance draws its internal IP address from that subnet. Virtual machine (VM) instances in a VPC network can communicate with instances in all other subnets of the same VPC network, regardless of region, using their RFC1918 private IP addresses. You can isolate portions of the network, even entire subnets, using firewall rules. To get more information about Subnetwork, see:
Builder for SubnetworkArgs.
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Builder for SubnetworkIAMBindingArgs.
Builder for SubnetworkIAMBinding.
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Builder for SubnetworkIAMMemberArgs.
Builder for SubnetworkIAMMember.
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Three different resources help you manage your IAM policy for Compute Engine Subnetwork. Each of these resources serves a different use case:
Builder for SubnetworkIAMPolicyArgs.
Builder for SubnetworkIAMPolicy.
Builder for Subnetwork.
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. To get more information about TargetGrpcProxy, see:
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. To get more information about TargetGrpcProxy, see:
Builder for TargetGrpcProxyArgs.
Builder for TargetGrpcProxy.
Represents a TargetHttpProxy resource, which is used by one or more global forwarding rule to route incoming HTTP requests to a URL map. To get more information about TargetHttpProxy, see:
Represents a TargetHttpProxy resource, which is used by one or more global forwarding rule to route incoming HTTP requests to a URL map. To get more information about TargetHttpProxy, see:
Builder for TargetHttpProxyArgs.
Builder for TargetHttpProxy.
Represents a TargetHttpsProxy resource, which is used by one or more global forwarding rule to route incoming HTTPS requests to a URL map. To get more information about TargetHttpsProxy, see:
Represents a TargetHttpsProxy resource, which is used by one or more global forwarding rule to route incoming HTTPS requests to a URL map. To get more information about TargetHttpsProxy, see:
Builder for TargetHttpsProxyArgs.
Builder for TargetHttpsProxy.
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. To get more information about TargetInstance, see:
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. To get more information about TargetInstance, see:
Builder for TargetInstanceArgs.
Builder for TargetInstance.
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
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
Builder for TargetPoolArgs.
Builder for TargetPool.
Represents a TargetSslProxy resource, which is used by one or more global forwarding rule to route incoming SSL requests to a backend service. To get more information about TargetSslProxy, see:
Represents a TargetSslProxy resource, which is used by one or more global forwarding rule to route incoming SSL requests to a backend service. To get more information about TargetSslProxy, see:
Builder for TargetSSLProxyArgs.
Builder for TargetSSLProxy.
Represents a TargetTcpProxy resource, which is used by one or more global forwarding rule to route incoming TCP requests to a Backend service. To get more information about TargetTcpProxy, see:
Represents a TargetTcpProxy resource, which is used by one or more global forwarding rule to route incoming TCP requests to a Backend service. To get more information about TargetTcpProxy, see:
Builder for TargetTCPProxyArgs.
Builder for TargetTCPProxy.
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. To get more information about UrlMap, see:
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. To get more information about UrlMap, see:
Builder for URLMapArgs.
Builder for URLMap.
Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you. To get more information about VpnGateway, see:
Represents a VPN gateway running in GCP. This virtual device is managed by Google, but used only by you. To get more information about VpnGateway, see:
Builder for VPNGatewayArgs.
Builder for VPNGateway.
VpnTunnel can be imported using any of these accepted formats
VpnTunnel can be imported using any of these accepted formats
Builder for VPNTunnelArgs.
Builder for VPNTunnel.