Skip to content

Commit 1b6ec1c

Browse files
committed
chore: update service account impersonation section's notes
1 parent 1d15710 commit 1b6ec1c

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -350,15 +350,15 @@ This allows the Proxy to act as a different service account, which can be useful
350350
for granting access to resources that are not accessible to the default IAM principal.
351351

352352
To use service account impersonation, you must have the
353-
`iam.serviceAccounts.getAccessToken` permission on the IAM principal. You can grant this permission by assigning the
353+
`iam.serviceAccounts.getAccessToken` permission on the IAM principal impersonating another service account. You can grant this permission by assigning the
354354
`roles/iam.serviceAccountTokenCreator` role to the IAM principal.
355355

356356
To impersonate a service account, use the `--impersonate-service-account` flag:
357357

358358
> [!NOTE]:
359359
>
360-
> The service account must have `Cloud SQL Instance User`, `Service Usage Consumer` and `Cloud SQL Client permissions`.
361-
> The `roles/iam.serviceAccountTokenCreator` role is not required on the impersonated service account but on the IAM principal impersonating the service account.
360+
> The impersonated service account must have the `Service Usage Consumer` and `Cloud SQL Client` permissions. Additionally, to use IAM Authenticated users, add the `Cloud SQL Instance User` permission.
361+
362362

363363
```shell
364364
# Starts a listener on localhost:5432 and impersonates the service account

0 commit comments

Comments
 (0)