HEX
Server: Apache/2.4.65 (Ubuntu)
System: Linux ielts-store-v2 6.8.0-1036-gcp #38~22.04.1-Ubuntu SMP Thu Aug 14 01:19:18 UTC 2025 x86_64
User: root (0)
PHP: 7.2.34-54+ubuntu20.04.1+deb.sury.org+1
Disabled: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,
Upload Files
File: //snap/google-cloud-cli/396/help/man/man1/gcloud_alpha_compute_interconnects_groups_create.1
.TH "GCLOUD_ALPHA_COMPUTE_INTERCONNECTS_GROUPS_CREATE" 1



.SH "NAME"
.HP
gcloud alpha compute interconnects groups create \- create a Compute Engine interconnect group



.SH "SYNOPSIS"
.HP
\f5gcloud alpha compute interconnects groups create\fR \fINAME\fR \fB\-\-intended\-topology\-capability\fR=\fIINTENDED_TOPOLOGY_CAPABILITY\fR [\fB\-\-description\fR=\fIDESCRIPTION\fR] [\fB\-\-interconnects\fR=[\fIINTERCONNECT\fR,...]] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR \fBgcloud alpha compute interconnects groups create\fR is used to
create interconnect groups. An interconnect group connects a set of redundant
interconnects between Google and the customer.

For an example, refer to the \fBEXAMPLES\fR section below.



.SH "EXAMPLES"

To create an interconnect group capable of PRODUCTION_CRITICAL, run:

.RS 2m
$ gcloud alpha compute interconnects groups create \e
    example\-interconnect\-group \e
    \-\-intended\-topology\-capability=PRODUCTION_CRITICAL \e
    \-\-description="Example interconnect group"
.RE

It is easy to add members to an existing interconnect group after creation using
the \fBadd\-members\fR command.

To create an interconnect group capable of PRODUCTION_NON_CRITICAL, with two
members at creation time, run:

.RS 2m
$ gcloud alpha compute interconnects groups create \e
    example\-interconnect\-group \e
    \-\-intended\-topology\-capability=PRODUCTION_NON_CRITICAL \e
    \-\-interconnects=interconnect\-1,interconnect\-2
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fINAME\fR

Name of the interconnect group to create.


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-intended\-topology\-capability\fR=\fIINTENDED_TOPOLOGY_CAPABILITY\fR

The reliability the user intends this group to be capable of, in terms of the
Interconnect product SLAs.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-description\fR=\fIDESCRIPTION\fR

An optional, textual description for the interconnect group.

.TP 2m
\fB\-\-interconnects\fR=[\fIINTERCONNECT\fR,...]

Member interconnects to add to the interconnect group initially.


.RE
.sp

.SH "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 \fB$ gcloud help\fR for details.



.SH "NOTES"

This command is currently in alpha and might change without notice. If this
command fails with API permission errors despite specifying the correct project,
you might be trying to access an API with an invitation\-only early access
allowlist. These variants are also available:

.RS 2m
$ gcloud compute interconnects groups create
.RE

.RS 2m
$ gcloud beta compute interconnects groups create
.RE