Skip to main content

GCP Big Table Admin App Profile

An App Profile in Google Cloud Bigtable defines how an application connects to, routes traffic within and interacts with a Bigtable instance. It specifies whether traffic should use multi-cluster routing (for higher availability) or single-cluster routing (for lower latency), and can set additional request-level parameters such as transactional consistency options. Correctly configuring an App Profile is essential for ensuring that reads and writes are directed to the intended clusters and that fail-over behaviour matches the application’s tolerance for latency and consistency.
For more detail, see the official documentation: https://cloud.google.com/bigtable/docs/reference/admin/rest/v2/projects.instances.appProfiles#AppProfile

Terrafrom Mappings:

  • google_bigtable_app_profile.id

Supported Methods​

  • GET: Get a gcp-big-table-admin-app-profile by its "instances|appProfiles"
  • LIST
  • SEARCH: Search for BigTable App Profiles in an instance. Use the format "instance" or "projects/[project_id]/instances/[instance_name]/appProfiles/[app_profile_id]" which is supported for terraform mappings.

gcp-big-table-admin-instance​

A Bigtable App Profile is always created within a specific Bigtable instance. Overmind links the profile back to its parent gcp-big-table-admin-instance so that blast-radius analysis can show which applications might be affected by changes to, or deletion of, the instance.

gcp-big-table-admin-cluster​

If an App Profile uses single-cluster routing, it explicitly targets one particular Bigtable cluster. Overmind therefore links the App Profile to the corresponding gcp-big-table-admin-cluster to surface potential risks where routing changes or cluster outages could impact the application.