A Compute Engine instance template lets you describe a VM instance. You can
then create groups of identical instances based on the template. For more
information, see the following:
This document describes the connections and parameters you can configure when
using App Design Center to create a Compute Engine instance
template. The configuration parameters are based on the instance_template
Terraform module.
The following table includes the components that you can connect to a
Compute Engine instance template, and the resulting updates to your
application and its generated Terraform code.
Connected component |
Application updates |
Background information |
Service Account |
- The Compute Engine instance template uses the connected service account instead of creating a new service account. The connected service account is used for authentication and authorization to other Google Cloud services.
- The service account email and IAM information are added to the Compute Engine instance template.
|
Create a VM that uses a user-managed service account |
AlloyDB for PostgreSQL |
- The Compute Engine instances can connect to the AlloyDB for PostgreSQL instance.
- The AlloyDB for PostgreSQL resource metadata information is added to the instance template.
- The
roles/alloydb.admin role is added to the Compute Engine instance template service account.
|
Connect from Compute Engine |
BigQuery |
- The Compute Engine instances can read and write data to the BigQuery dataset.
- The BigQuery resource metadata is added to the Compute Engine instance template.
- The
roles/bigquery.dataEditor role is added to Compute Engine instance template service account.
|
BigQuery overview |
Bigtable |
- The Compute Engine instances can access the Bigtable instance.
- The Bigtable resource metadata information is added to the instance template.
- The
roles/bigtable.admin role is added to the Compute Engine instance template service account.
|
Bigtable overview |
Cloud SQL (MySQL) |
- The Compute Engine instances can connect and read and write data to the Cloud SQL (MySQL) instance.
- The Cloud SQL connection metadata is added to the Compute Engine instance template.
- The
roles/cloudsql.instanceUser and roles/cloudsql.client roles are added to the Compute Engine instance template service account.
- The Compute Engine service account is added as an IAM user to the Cloud SQL instance.
|
Connect from Compute Engine |
Cloud SQL (PostgreSQL) |
- The Compute Engine instances can connect and read and write data to the Cloud SQL (PostgreSQL) instance.
- The Cloud SQL connection metadata is added to the Compute Engine instance template.
- The
roles/cloudsql.instanceUser and roles/cloudsql.client roles are added to the Compute Engine instance template service account.
- The Compute Engine service account IAM information is added to the Cloud SQL instance.
|
Connect from Compute Engine |
Cloud Storage |
- The Compute Engine instances can control bucket objects, including listing, creating, viewing, and deleting objects.
- The
roles/storage.objectAdmin role is assigned to the Compute Engine instance template service account.
|
Set and manage IAM policies on buckets |
Memorystore |
- The Compute Engine instances can manage and cache data in the Memorystore instance.
- The Pub/Sub topic ID is added to the Compute Engine instance template metadata.
|
Deployment options for Redis on Google Cloud |
Pub/Sub |
- The Compute Engine instances can publish to and receive messages from the Pub/Sub topic.
- The Pub/Sub topic ID is added to the Compute Engine instance template metadata.
|
Subscription overview |
Regional Cloud Load Balancing frontend |
- The Compute Engine instances can redirect traffic to the regional Cloud Load Balancing frontend.
- The Cloud Load Balancing address is added to the Compute Engine instance template.
|
Forwarding rules overview |
Spanner |
- The Compute Engine instances can read and write data in the Spanner instance.
- The
roles/spanner.databaseAdmin role is added to the Compute Engine instance template service account.
- The Compute Engine IAM information is added to the Spanner instance.
|
Using Spanner in a virtual machine instance |
Vertex AI |
- The Compute Engine instances can interact with Vertex AI services.
- The
roles/aiplatform.user role is added to the Compute Engine instance template service account.
|
Vertex AI access control with IAM |
Compute Engine (MIG) |
- The Compute Engine instance template is used to create instances in the managed instance group.
- The instance template self link is added to the Compute Engine MIG.
|
Basic scenarios for creating managed instance groups (MIGs) |
If your template includes a Compute Engine instance template component, you
must configure the following parameters before you deploy.
The following parameters are optional. To display advanced parameters, in the
Configuration area, select Show advanced fields.