gcloud bigtable app-profiles create

NAME
gcloud bigtable app-profiles create - create a new Bigtable app profile
SYNOPSIS
gcloud bigtable app-profiles create(APP_PROFILE :--instance=INSTANCE)([--route-any :--restrict-to=[RESTRICT_TO,…]--row-affinity]    | [--route-to=ROUTE_TO :--transactional-writes])[--description=DESCRIPTION][--force][--data-boost--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER    |--priority=PRIORITY--standard][GCLOUD_WIDE_FLAG]
DESCRIPTION
Create a new Bigtable app profile.
EXAMPLES
To create an app profile with a multi-cluster routing policy, run:
gcloudbigtableapp-profilescreatemy-app-profile-id--instance=my-instance-id--route-any

To create an app profile with a single-cluster routing policy which routes allrequests tomy-cluster-id, run:

gcloudbigtableapp-profilescreatemy-single-cluster-app-profile--instance=my-instance-id--route-to=my-cluster-id

To create an app profile with a friendly description, run:

gcloudbigtableapp-profilescreatemy-app-profile-id--instance=my-instance-id--route-any--description="Routes requests for my use case"

To create an app profile with a request priority of PRIORITY_MEDIUM, run:

gcloudbigtableapp-profilescreatemy-app-profile-id--instance=my-instance-id--route-any--priority=PRIORITY_MEDIUM

To create an app profile with row-affinity routing enabled, run:

gcloudbigtableapp-profilescreatemy-app-profile-id--instance=my-instance-id--route-any--row-affinity

To create an app profile with Data Boost enabled which bills usage to the hostproject, run:

gcloudbigtableapp-profilescreatemy-app-profile-id--instance=my-instance-id--data-boost--data-boost-compute-billing-owner=HOST_PAYS
POSITIONAL ARGUMENTS
App profile resource - The app profile to create. The arguments in this groupcan be used to specify the attributes of this resource. (NOTE) Some attributesare not given arguments in this group but can be set in other ways.

To set theproject attribute:

  • provide the argumentapp_profile on the command line with a fullyspecified name;
  • provide the argument--project on the command line;
  • set the propertycore/project.

This must be specified.

APP_PROFILE
ID of the app profile or fully qualified identifier for the app profile.

To set thename attribute:

  • provide the argumentapp_profile on the command line.

This positional argument must be specified if any of the other arguments in thisgroup are specified.

--instance=INSTANCE
Bigtable instance for the app profile.

To set theinstance attribute:

  • provide the argumentapp_profile on the command line with a fullyspecified name;
  • provide the argument--instance on the command line.
REQUIRED FLAGS
Exactly one of these must be specified:
Multi Cluster Routing Policy
--route-any
Use Multi Cluster Routing policy.

This flag argument must be specified if any of the other arguments in this groupare specified.

--restrict-to=[RESTRICT_TO,…]
Cluster IDs to route to using the Multi Cluster Routing Policy. If unset, allclusters in the instance are eligible.
--row-affinity
Use row-affinity routing for this app profile.
Single Cluster Routing Policy
--route-to=ROUTE_TO
Cluster ID to route to using Single Cluster Routing policy.

This flag argument must be specified if any of the other arguments in this groupare specified.

--transactional-writes
Allow transactional writes with a Single Cluster Routing policy.
OPTIONAL FLAGS
--description=DESCRIPTION
Friendly name of the app profile.
--force
Ignore warnings and force create.
At most one of these can be specified:
Data Boost Read-only Isolation
--data-boost
Use Data Boost serverless compute option, rather than standard provisioned nodecompute. If specified, --data-boost-compute-billing-owner is required.Specifying Data Boost compute on an app profile that uses standard provisionednode compute may cause unexpected behavior for running applications.

This flag argument must be specified if any of the other arguments in this groupare specified.

--data-boost-compute-billing-owner=DATA_BOOST_COMPUTE_BILLING_OWNER
Specify the Data Boost compute billing owner, required if --data-boost ispassed.DATA_BOOST_COMPUTE_BILLING_OWNER must be (onlyone value is supported):
HOST_PAYS
Compute billing should be accounted towards the host Cloud project (containingthe targeted Bigtable instance / table).
This flag argument must be specified if any of the other arguments in this groupare specified.
Standard Isolation
--priority=PRIORITY
Specify the request priority under standard provisioned node computecapabilities. Passing this option implies standard provisioned node compute,e.g. the--standard option. If not specified, the app profile usesstandard provisioned node compute with PRIORITY_HIGH by default. Specifyingrequest priority on an app profile that has Data Boost serverless computeenabled changes the compute option to standard and uses the specified priority,which might cause unexpected behavior for running applications.PRIORITY must be one of:
PRIORITY_HIGH
Requests are treated with high priority.
PRIORITY_LOW
Requests are treated with low priority.
PRIORITY_MEDIUM
Requests are treated with medium priority.
--standard
Use standard provisioned node compute option, rather than Data Boost computeoption. If specified,--priority is required.
GCLOUD WIDE FLAGS
These flags are available to all commands:--access-token-file,--account,--billing-project,--configuration,--flags-file,--flatten,--format,--help,--impersonate-service-account,--log-http,--project,--quiet,--trace-token,--user-output-enabled,--verbosity.

Run$gcloud help for details.

NOTES
These variants are also available:
gcloudalphabigtableapp-profilescreate
gcloudbetabigtableapp-profilescreate

Except as otherwise noted, the content of this page is licensed under theCreative Commons Attribution 4.0 License, and code samples are licensed under theApache 2.0 License. For details, see theGoogle Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2026-02-03 UTC.