This page describes how to add a user or service account that uses IAM database authentication to a database and how to manage those user and service accounts. For more information about the IAM integration, see IAM authentication.
Before you begin
- Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
-
Make sure that billing is enabled for your Google Cloud project.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
In the Google Cloud console, on the project selector page, select or create a Google Cloud project.
-
Make sure that billing is enabled for your Google Cloud project.
- Install the Google Cloud CLI.
-
To initialize the gcloud CLI, run the following command:
gcloud init
-
Enable the Cloud Key Management Service API.
- Make sure you have the Cloud SQL Admin role on your user account.
- Enable IAM database authentication on your Cloud SQL instance.
- Make sure to grant IAM access to users that need it for each project that contains databases that users need to access. See Granting, changing, and revoking access to resources.
- Make sure you have added a service account for each service that requires access to databases in the project.
Add an IAM user or service account to the database
You must create a new database user for each IAM user you want to
have access to the database instance. The database username must be the
IAM user's email address, for example, test-user@example.com.
When using REST commands, the username must use quotes because it contains
special characters (@ and .).
Service accounts use the format service-account-name@project-id.iam.gserviceaccount.com.
To add an IAM user or service account, you add a new database user and select IAM as the authentication method:
Console
-
In the Google Cloud console, go to the Cloud SQL Instances page.
- To open the Overview page of an instance, click the instance name.
- Select Users from the SQL navigation menu.
- Click Add user account. The Add a user account to instance instance_name tab opens.
- Click the Cloud IAM radio button.
- Add the email address for the user or service account you want to add in the Principal field.
- Click Add. The user is now in the user list.
If the user isn't assigned to the Cloud SQL Instance User role, then a
icon
appears to the left of the username.To give the user login privileges, click the icon, and then select Add IAM role. The icon no longer appears. The user is now a member of the role.
gcloud
Create a user account
Use the email, such as test-user@example.com, to identify the user.
Replace the following:
- USERNAME: The email address for the user.
- INSTANCE_NAME: The name of the instance you want to authorize the user to access.
gcloud sql users create USERNAME \ --instance=INSTANCE_NAME \ --type=cloud_iam_user
Create a service account
Replace the following:
- SERVICE_ACCT: The email address of the service account.
- INSTANCE_NAME: The name of the instance you want to authorize the service account to access.
gcloud sql users create SERVICE_ACCT \ --instance=INSTANCE_NAME \ --type=cloud_iam_service_account
REST v1
Create a user account
Before using any of the request data, make the following replacements:
- project-id: Your project ID
- instance-id: The instance ID for the instance you are adding the user to
- username: The email address for the user
- operation-id: The ID for the operation
HTTP method and URL:
POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/users
Request JSON body:
{
"name": "username",
"type": "CLOUD_IAM_USER"
}
To send your request, expand one of these options:
You should receive a JSON response similar to the following:
{
"kind": "sql#operation",
"targetLink": "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id",
"status": "DONE",
"user": "user@example.com",
"insertTime": "2020-02-07T22:44:16.656Z",
"startTime": "2020-02-07T22:44:16.686Z",
"endTime": "2020-02-07T22:44:20.437Z",
"operationType": "CREATE_USER",
"name": "operation-id",
"targetId": "instance-id",
"selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",
"targetProject": "project-id"
}
Create a service account
Before using any of the request data, make the following replacements:
- service-acct: Your service account email
- project-id: Your project ID
- instance-id: The instance ID for the instance you are adding the service account to
- operation-id: The ID for the operation
HTTP method and URL:
POST https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id/users
Request JSON body:
{
"name": "service-acct",
"type": "CLOUD_IAM_SERVICE_ACCOUNT"
}
To send your request, expand one of these options:
You should receive a JSON response similar to the following:
{
"kind": "sql#operation",
"targetLink": "https://sqladmin.googleapis.com/v1/projects/project-id/instances/instance-id",
"status": "DONE",
"user": "user@example.com",
"insertTime": "2020-11-20T04:08:00.211Z",
"startTime": "2020-11-20T04:08:00.240Z",
"endTime": "2020-11-20T04:08:02.003Z",
"operationType": "CREATE_USER",
"name": "operation-id",
"targetId": "instance-id",
"selfLink": "https://sqladmin.googleapis.com/v1/projects/project-id/operations/operation-id",
"targetProject": "project-id"
}
REST v1beta4
Create a user account
Before using any of the request data, make the following replacements:
- project-id: Your project ID
- instance-id: The instance ID for the instance you are adding the user to
- username: The email address for the user
- operation-id: The ID for the operation
HTTP method and URL:
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users
Request JSON body:
{
"name": "username",
"type": "CLOUD_IAM_USER"
}
To send your request, expand one of these options:
You should receive a JSON response similar to the following:
{
"kind": "sql#operation",
"targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id",
"status": "DONE",
"user": "user@example.com",
"insertTime": "2020-02-07T22:44:16.656Z",
"startTime": "2020-02-07T22:44:16.686Z",
"endTime": "2020-02-07T22:44:20.437Z",
"operationType": "CREATE_USER",
"name": "operation-id",
"targetId": "instance-id",
"selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",
"targetProject": "project-id"
}
Create a service account
Before using any of the request data, make the following replacements:
- service-acct: Your service account email
- project-id: Your project ID
- instance-id: The instance ID for the instance you are adding the service account to
- operation-id: The ID for the operation
HTTP method and URL:
POST https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users
Request JSON body:
{
"name": "service-acct",
"type": "CLOUD_IAM_SERVICE_ACCOUNT"
}
To send your request, expand one of these options:
You should receive a JSON response similar to the following:
{
"kind": "sql#operation",
"targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id",
"status": "DONE",
"user": "user@example.com",
"insertTime": "2020-11-20T04:08:00.211Z",
"startTime": "2020-11-20T04:08:00.240Z",
"endTime": "2020-11-20T04:08:02.003Z",
"operationType": "CREATE_USER",
"name": "operation-id",
"targetId": "instance-id",
"selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",
"targetProject": "project-id"
}
Grant database privileges to the IAM user
When an IAM user is added to a database instance, that new user is granted no privileges on any databases, by default.When a user or service account connects to a database, they can run queries against any database objects whose access has been granted to PUBLIC.
If they need additional access, more privileges can be granted using the GRANT statement. See the GRANT reference page for a complete list of privileges you can grant to users and service accounts. Run GRANT from the command line.
Replace the following:
- USERNAME: The email address for the user. You must use quotes
around the email because it contains special characters (
@and.) - TABLE_NAME: The name of the table that you want to give the user access to.
grant select on TABLE_NAME to "USERNAME";
Remove an IAM user or service account from the database
To remove a user or service account from the database, you delete the account from the instance:
Console
-
In the Google Cloud console, go to the Cloud SQL Instances page.
- To open the Overview page of an instance, click the instance name.
- Select Users from the SQL navigation menu.
- Click for the user you want to remove.
- Select Remove. This revokes access to this instance only.
gcloud
Revoke a user
Use the email, such as test-user@example.com, to identify the user.
Replace the following:
- USERNAME: The email address without the @domain name.
- INSTANCE_NAME: The name of the instance you want to remove the user from.
gcloud sql users delete USERNAME \ --instance=INSTANCE_NAME
Delete the service account
Replace the following:
- SERVICE_ACCT: The email address of the service account.
- INSTANCE_NAME: The name of the instance you want to remove the user from.
gcloud sql users delete SERVICE_ACCT \ --instance=INSTANCE_NAME
REST v1beta4
The request below uses the users:delete method to delete the specified user account.
Before using any of the request data, make the following replacements:
- project-id: Your project ID
- instance-id: The desired instance ID
- username: The email address for the user or service account
HTTP method and URL:
DELETE https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id/users?host=&name=username
To send your request, expand one of these options:
You should receive a JSON response similar to the following:
{
"kind": "sql#operation",
"targetLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/instances/instance-id",
"status": "DONE",
"user": "user@example.com",
"insertTime": "2020-02-07T22:38:41.217Z",
"startTime": "2020-02-07T22:38:41.217Z",
"endTime": "2020-02-07T22:38:44.801Z",
"operationType": "DELETE_USER",
"name": "operation-id",
"targetId": "instance-id",
"selfLink": "https://sqladmin.googleapis.com/sql/v1beta4/projects/project-id/operations/operation-id",
"targetProject": "project-id"
}
View login information in audit logs
You can enable audit logs to capture IAM logins to the database. When there are login issues, you can use the audit logs to diagnose the problem.
Once configured, you can view Data Access audit logs of successful logins using the Logs Explorer.
For example, a log might have information similar to the following:
{
insertId: "..."
logName: "projects/.../logs/cloudaudit.googleapis.com%2Fdata_access"
protoPayload: {
@type: "type.googleapis.com/google.cloud.audit.AuditLog"
authenticationInfo: {
principalEmail: "..."
}
authorizationInfo: [
0: {
granted: true
permission: "cloudsql.instances.login"
resource: "instances/..."
resourceAttributes: {
}
}
]
methodName: "cloudsql.instances.login"
request: {
@type: "type.googleapis.com/google.cloud.sql.authorization.v1.InstancesLoginRequest"
clientIpAddress: "..."
database: "..."
databaseSessionId: ...
instance: "projects/.../locations/us-central1/instances/..."
user: "..."
}
requestMetadata: {
callerIp: "..."
destinationAttributes: {
}
requestAttributes: {
auth: {
}
time: "..."
}
}
resourceName: "instances/..."
serviceName: "cloudsql.googleapis.com"
status: {
}
}
receiveTimestamp: "..."
resource: {
labels: {
database_id: "...:..."
project_id: "..."
region: "us-central"
}
type: "cloudsql_database"
}
severity: "INFO"
timestamp: "..."
}
Troubleshoot a login failure
When an attempt to log in fails, PostgreSQL returns a minimal error message for security reasons. For example:
PGPASSWORD=not-a-password psql --host=... --username=... --dbname=...
psql: error: could not connect to server: FATAL: Cloud SQL IAM user authentication failed for user "..."
FATAL: pg_hba.conf rejects connection for host "...", user "...", database "...", SSL off
You can review the PostgreSQL error logs for more details about the error. For more information, see Viewing Logs.
For example, for the previous error, the following log entry explains the action you can take to resolve the problem.
F ... [152172]: [1-1] db=...,user=... FATAL: Cloud SQL IAM user authentication failed for user "..."
I ... [152172]: [2-1] db=...,user=... DETAIL: Request is missing required authentication credential. Expected OAuth 2 access token, log in cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Check the error message you receive. If the message does not indicate that you
used "Cloud SQL IAM user authentication" or
"Cloud SQL IAM service account authentication," verify that
the database user type used to log in is either CLOUD_IAM_USER or
CLOUD_IAM_SERVICE_ACCOUNT.
You can use the Google Cloud console or the gcloud sql
users list command to check this.
For an IAM user, verify that the database username is the
IAM user's email.
If you used IAM database authentication, check the details of the error message. You can find the
error message in the database error log. If it indicates the access token (OAuth
2.0) you sent as a password was invalid, you can use the
gcloud auth application-default print-access-token
gcloud command to find details of the token, as follows:
curl -H "Content-Type: application/x-www-form-urlencoded" \ -d "access_token=$(gcloud auth application-default print-access-token)" \ https://www.googleapis.com/oauth2/v1/tokeninfo
Verify that the token is for the intended IAM user or service account and has not expired.
If the details indicate a lack of permission, then verify the IAM
user or service account is granted the cloudsql.instances.login permission using
the predefined Cloud SQL Instance User role or custom role in the
IAM policy of the instance's project. Use the IAM
Policy Troubleshooter for additional help.
If a login fails due to IAM database authentication unavailability, the user can log in using the default PostgreSQL user and password. This method of logging in still gives the user access to the entire database. Verify that the connection is a secured connection.
What's next
- Learn more about IAM database authentication.
- Learn how to log in to a Cloud SQL database.
- Learn how to configure instances for IAM database authentication.