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/current/help/man/man1/gcloud_alpha_alloydb_users_create.1
.TH "GCLOUD_ALPHA_ALLOYDB_USERS_CREATE" 1



.SH "NAME"
.HP
gcloud alpha alloydb users create \- creates a user in a given cluster



.SH "SYNOPSIS"
.HP
\f5gcloud alpha alloydb users create\fR \fIUSERNAME\fR \fB\-\-cluster\fR=\fICLUSTER\fR \fB\-\-region\fR=\fIREGION\fR [\fB\-\-db\-roles\fR=[\fIROLE\fR,...]] [\fB\-\-keep\-extra\-roles\fR=\fIKEEP_EXTRA_ROLES\fR] [\fB\-\-password\fR=\fIPASSWORD\fR] [\fB\-\-superuser\fR=\fISUPERUSER\fR] [\fB\-\-type\fR=\fITYPE\fR;\ default=\f5"BUILT_IN"\fR] [\fIGCLOUD_WIDE_FLAG\ ...\fR]



.SH "DESCRIPTION"

\fB(ALPHA)\fR Creates a user in a given cluster with specified username,
cluster, region, type, and password.



.SH "EXAMPLES"

To create a new user, run:

.RS 2m
$ gcloud alpha alloydb users create my\-username \e
    \-\-cluster=my\-cluster \-\-region=us\-central1 \-\-password=postgres
.RE



.SH "POSITIONAL ARGUMENTS"

.RS 2m
.TP 2m
\fIUSERNAME\fR

AlloyDB username


.RE
.sp

.SH "REQUIRED FLAGS"

.RS 2m
.TP 2m
\fB\-\-cluster\fR=\fICLUSTER\fR

AlloyDB cluster ID

.TP 2m
\fB\-\-region\fR=\fIREGION\fR

Regional location (e.g. \f5asia\-east1\fR, \f5us\-east1\fR). See the full list
of regions at https://cloud.google.com/sql/docs/instance\-locations.


.RE
.sp

.SH "OPTIONAL FLAGS"

.RS 2m
.TP 2m
\fB\-\-db\-roles\fR=[\fIROLE\fR,...]

Comma separated list of database roles this new user will be granted upon
creation.

.TP 2m
\fB\-\-keep\-extra\-roles\fR=\fIKEEP_EXTRA_ROLES\fR

If the user already exists and has extra roles, keep them.

.TP 2m
\fB\-\-password\fR=\fIPASSWORD\fR

Password for this database user.

.TP 2m
\fB\-\-superuser\fR=\fISUPERUSER\fR

If true, new user will have AlloyDB superuser privileges. Default value is
false.

.TP 2m
\fB\-\-type\fR=\fITYPE\fR; default=\f5"BUILT_IN"\fR

Type corresponds to the user type. \fITYPE\fR must be one of:

.RS 2m
.TP 2m
\fBBUILT_IN\fR
This database user can authenticate via password\-based authentication
.TP 2m
\fBIAM_BASED\fR
This database user can authenticate via IAM\-based authentication
.RE
.sp



.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 alloydb users create
.RE

.RS 2m
$ gcloud beta alloydb users create
.RE