{"token_count": 5115} # Database Access with Cloud Spanner Teleport can provide secure access to Cloud Spanner via the [Teleport Database Service](https://goteleport.com/docs/enroll-resources/database-access.md). This allows for fine-grained access control through [Teleport's RBAC](https://goteleport.com/docs/enroll-resources/database-access/rbac.md). In this guide, you will: 1. Configure your Cloud Spanner database with a service account. 2. Add the database to your Teleport cluster. 3. Connect to the database via Teleport. ## How it works The Teleport Database Service uses IAM authentication to communicate with Spanner. When a user connects to the database via Teleport, the Teleport Database Service obtains Google Cloud credentials and authenticates to Google Cloud as an IAM principal with permissions to access the database. **Self-Hosted** ![Self-Hosted Teleport Architecture for Cloud Spanner Access](https://website.goteleport.com/_uploads/spanner_selfhosted_bf0e74fb75.png) **Cloud-Hosted** ![Cloud-Hosted Teleport Architecture for Cloud Spanner Access](https://website.goteleport.com/_uploads/spanner_cloud_a781090c6a.png) ## Prerequisites - A running Teleport cluster accessible at a hostname with a valid TLS certificate. If you want to get started with Teleport, [sign up](https://goteleport.com/signup) for a free trial or [set up a demo environment](https://goteleport.com/docs/get-started/deploy-community.md). - The `tctl` and `tsh` clients. Installing `tctl` and `tsh` clients 1. Determine the version of your Teleport cluster. The `tctl` and `tsh` clients must be at most one major version behind your Teleport cluster version. Send a GET request to the Proxy Service at `/v1/webapi/find` and use a JSON query tool to obtain your cluster version. Replace teleport.example.com:443 with the web address of your Teleport Proxy Service: **Mac/Linux** ``` $ TELEPORT_DOMAIN=teleport.example.com:443 $ TELEPORT_VERSION="$(curl -s https://$TELEPORT_DOMAIN/v1/webapi/find | jq -r '.server_version')" ``` **Windows - Powershell** ``` $ $TELEPORT_DOMAIN = "teleport.example.com:443" $ $TELEPORT_VERSION = (Invoke-RestMethod -Uri "https://${TELEPORT_DOMAIN}/v1/webapi/find").server_version ``` 2. Follow the instructions for your platform to install `tctl` and `tsh` clients: **Mac** Download the signed macOS .pkg installer for Teleport, which includes the `tctl` and `tsh` clients: ``` $ curl -O https://cdn.teleport.dev/teleport-${TELEPORT_VERSION?}.pkg ``` In Finder double-click the `pkg` file to begin installation. --- DANGER Using Homebrew to install Teleport is not supported. The Teleport package in Homebrew is not maintained by Teleport and we can't guarantee its reliability or security. --- **Windows - Powershell** ``` $ curl.exe -O https://cdn.teleport.dev/teleport-v$TELEPORT_VERSION-windows-amd64-bin.zip Unzip the archive and move the `tctl` and `tsh` clients to your %PATH% NOTE: Do not place the `tctl` and `tsh` clients in the System32 directory, as this can cause issues when using WinSCP. Use %SystemRoot% (C:\Windows) or %USERPROFILE% (C:\Users\) instead. ``` **Linux** All of the Teleport binaries in Linux installations include the `tctl` and `tsh` clients. For more options (including RPM/DEB packages and downloads for i386/ARM/ARM64) see our [installation page](https://goteleport.com/docs/installation/single-machine.md). ``` $ curl -O https://cdn.teleport.dev/teleport-v${TELEPORT_VERSION?}-linux-amd64-bin.tar.gz $ tar -xzf teleport-v${TELEPORT_VERSION?}-linux-amd64-bin.tar.gz $ cd teleport $ sudo ./install Teleport binaries have been copied to /usr/local/bin ``` Connecting with TLS routing disabled This guide's commands assume your Teleport cluster uses TLS routing (`proxy_listener_mode: multiplex`), where the `tctl` and `tsh` clients reach every Teleport service through the Proxy Service's web address on port `443`. If you're not sure whether this applies to your cluster, check with whoever manages it. If your cluster uses separate listener ports instead, adjust ports as follows: - **`tsh` commands** (e.g., `tsh login --proxy=...`): continue using the Proxy Service web address on port `3080` (or `443` if behind a load balancer). Do not change these to port `3025`. - **Direct `tctl` or Auth Service API commands**: use port `3025` for the Auth Service gRPC listener: ``` $ tctl status --auth-server=teleport.example.com:3025 ``` * A Google Cloud account * A Cloud Spanner instance and database * A host to run the Teleport Database Service (for example, a Compute Engine instance) with outbound HTTPS access to `spanner.googleapis.com:443` * Check that you can connect to your Teleport cluster and verify that you can run `tctl` and `tsh` commands using your current credentials. 1. Assign teleport.example.com to the domain name of the Teleport Proxy Service in your cluster and email\@example.com to your Teleport username. 2. Authenticate to your Teleport cluster. This depends on whether your shell is interactive or not. **In an interactive shell:** Run the following command. By default, this triggers a multi-factor authentication prompt: ``` $ tsh login --proxy=teleport.example.com --user=email@example.com $ tctl status Cluster teleport.example.com Version 18.10.0 CA pin sha256:abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678 ``` **On non-interactive environments:** If you are running `tsh` and `tctl` as an AI agent, in a CI/CD environment, or similar, make sure the `TELEPORT_IDENTITY_FILE` environment variable is assigned to a valid file path with credentials for your cluster. `tsh` and `tctl` read the file path from the environment variable and do not require a separate authentication step. If there is no identity file available, we recommend that you [set up Machine ID](https://goteleport.com/docs/machine-workload-identity/getting-started.md) to provision one automatically. When executing `tctl` commands with an identity file, you must pass the `--auth-server` flag to provide the Teleport Auth Service address, which is not included in the identity file. If you provide the Proxy Service address, `tctl` connects to the Proxy Service, which forwards traffic to and from the Teleport Auth Service. Update 443 to `3025` if you are contacting the Auth Service directly with `tctl`: ``` $ tctl status --auth-server=teleport.example.com:443 ``` For `tsh` commands that read an identity file, you must pass the `--proxy` flag, which points `tsh` to the address of the Teleport Proxy Service: ``` $ tsh status --proxy=teleport.example.com ``` Ensure client commands can access your identity file. Replace path/to/identity/file with the path to your identity file: ``` $ export TELEPORT_IDENTITY_FILE="${TELEPORT_IDENTITY_FILE:-path/to/identity/file}" ``` Add the `--auth-server` or `--proxy` flags to all subsequent `tctl` and `tsh` commands. If you can connect to the cluster and run the `tctl status` command, you can use your current credentials to run subsequent `tctl` commands from your workstation. If you host your own Teleport cluster, you can also run `tctl` commands on the computer that hosts the Teleport Auth Service for full permissions. ## Step 1/6. Create service accounts Teleport requires two types of Google Cloud service accounts: - **Database Service**: a single service account used by the Teleport Database Service to access Google Cloud and impersonate database user service accounts - **Database user**: one or more service accounts impersonated per connection to represent database users For example, in the following steps, we create `teleport-db-service` (Database Service service account) and `spanner-user` (a Database user service account). ### Create the Database Service account This account is used by the Teleport Database Service to access Google Cloud and impersonate the database user account. **Google Cloud console** 1. Navigate to **IAM & Admin** → **Service Accounts**. 2. Click **Create Service Account**. 3. Set the name to `teleport-db-service`. 4. Skip optional steps and click **Done**. You will grant permissions later. **gcloud CLI** ``` $ gcloud iam service-accounts create teleport-db-service --display-name="Teleport Database Service" ``` ### Create the database user account This account represents a database user. Teleport users specify this name when connecting. **Google Cloud console** 1. Navigate to **IAM & Admin** → **Service Accounts**. 2. Click **Create Service Account**. 3. Set the name to `spanner-user`. 4. Skip optional steps and click **Done**. You will grant permissions later. = **gcloud CLI** ``` $ gcloud iam service-accounts create spanner-user --display-name="Spanner User" ``` ## Step 2/6. Grant permissions Grant the database user account access to Spanner, then allow the Database Service account to impersonate the database user account. ### Grant Spanner access **Google Cloud console** 1. Navigate to **Spanner** → **Instances** 2. Select your instance 3. Click **Permissions** → **Add Principal** 4. Enter the `spanner-user` service account 5. Assign **Cloud Spanner Database User** 6. Click **Save** **gcloud CLI** ``` $ gcloud spanner instances add-iam-policy-binding instance-id \ --member="serviceAccount:spanner-user@project-id.iam.gserviceaccount.com" \ --role="roles/spanner.databaseUser" ``` --- CUSTOM SPANNER ROLE The **Cloud Spanner Database User** role is predefined. You can create custom IAM roles to further restrict access if needed. --- ### Allow service account impersonation Grant the Database Service account permission to impersonate the database user account. **Google Cloud console** 1. Navigate to **IAM & Admin** → **Service Accounts** 2. Select `spanner-user` 3. Open the **Permissions** tab 4. Click **Grant Access** 5. Add the `teleport-db-service` account 6. Assign **Service Account Token Creator** 7. Click **Save** **gcloud CLI** ``` $ gcloud iam service-accounts add-iam-policy-binding \ spanner-user@project-id.iam.gserviceaccount.com \ --member="serviceAccount:teleport-db-service@project-id.iam.gserviceaccount.com" \ --role="roles/iam.serviceAccountTokenCreator" ``` --- **CHECKPOINT: Verify GCP permissions** Before proceeding, verify: Confirm that the Database Service account can impersonate the database user account. If the check fails, troubleshoot: Run: ``` $ gcloud iam service-accounts get-iam-policy \ spanner-user@project-id.iam.gserviceaccount.com ``` The output should include a binding that pairs `teleport-db-service` with `roles/iam.serviceAccountTokenCreator`: ``` bindings: - members: - serviceAccount:teleport-db-service@.iam.gserviceaccount.com role: roles/iam.serviceAccountTokenCreator ``` --- ## Step 3/6. Install and configure the Teleport Database Service To install Teleport binaries on your Linux server, the recommended installation method is the cluster install script. It will select the correct version, edition, and installation mode for your cluster. 1. Remove any existing Teleport binaries on your system: ``` $ sudo rm -f /usr/local/bin/{tsh,teleport,tctl,tbot,fdpass-teleport,teleport-update} ``` 2. Assign teleport.example.com:443 to your Teleport cluster hostname and port, but not the scheme (https\://). 3. Run your cluster's install script: ``` $ curl "https://teleport.example.com:443/scripts/install.sh" | sudo bash ``` The Database Service requires a valid join token to join your Teleport cluster. Run the following `tctl` command and save the token output in `/tmp/token` on the server that will run the Database Service: ``` $ tctl tokens add --type=db --format=text abcd123-insecure-do-not-use-this ``` Provide the following information and then generate a configuration file for the Teleport Database Service: - example.teleport.sh:443 The host **and port** of your Teleport Proxy Service or cloud-hosted Teleport Enterprise site. - project-id The GCP project ID. You can normally see it in the organization view at the top of the GCP dashboard. - instance-id The name of your Cloud Spanner instance. ``` $ sudo teleport db configure create \ -o file \ --name=spanner-example \ --protocol=spanner \ --labels=env=dev \ --token=/tmp/token \ --uri=spanner.googleapis.com:443 \ --proxy=example.teleport.sh:443 \ --gcp-project-id=project-id \ --gcp-instance-id=instance-id ``` ## Step 4/6. Configure GCP credentials The Teleport Database Service must have credentials for the "teleport-db-service" GCP service account. If the Teleport Database Service is hosted on a GCE instance, you can [change the attached service account](https://cloud.google.com/compute/docs/instances/change-service-account). For non-GCE deployments of Teleport, we recommend using [workload identity](https://cloud.google.com/iam/docs/workload-identity-federation). Using service account keys (insecure) Alternatively, go to that service account's Keys tab and create a new key: ![Service Account Keys](/docs/assets/images/service-account-keys@2x-0a3270370e86e9a93ce51fb7b6174d2d.png) Make sure to choose JSON format: ![Service Account New Key](/docs/assets/images/service-account-new-key@2x-ebf26eda3b9625e0571a1b53378fe640.png) Save the file. Set the `GOOGLE_APPLICATION_CREDENTIALS` environment variable to point to the JSON credentials file you downloaded earlier. For example, if you use `systemd` to start `teleport`, then you should edit the service's `EnvironmentFile` to include the env var: ``` $ echo 'GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json' | sudo tee -a /etc/default/teleport ``` --- WARNING A service account key can be a security risk - we only describe using a key in this guide for simplicity. We do not recommend using service account keys in production. See [authentication](https://cloud.google.com/docs/authentication#service-accounts) in the Google Cloud documentation for more information about service account authentication methods. --- ## Step 5/6. Start the Teleport Database Service Start the Teleport Database Service. The instructions depend on how you installed the Teleport Database Service and whether your system supports systemd: **Package Manager** Configure the Teleport Database Service to start automatically when the host boots up by creating a systemd service for it. On the host where you will run the Teleport Database Service, enable and start Teleport: ``` $ sudo systemctl enable teleport $ sudo systemctl start teleport ``` You can check the status of the Teleport Database Service with `systemctl status teleport` and view its logs with `journalctl -fu teleport`. **TAR Archive** Configure the Teleport Database Service to start automatically when the host boots up by creating a systemd service for it. On the host where you will run the Teleport Database Service, create a systemd service configuration for Teleport, enable the Teleport service, and start Teleport: ``` $ sudo teleport install systemd -o /etc/systemd/system/teleport.service $ sudo systemctl enable teleport $ sudo systemctl start teleport ``` You can check the status of the Teleport Database Service with `systemctl status teleport` and view its logs with `journalctl -fu teleport`. **No systemd** On the host where you will run the Teleport Database Service, start Teleport: ``` $ sudo teleport start --config=/etc/teleport.yaml ``` Teleport runs in the foreground and outputs logs for the services it is running. --- **CHECKPOINT: Verify database availability** Before proceeding, verify: Confirm that the Spanner database appears in Teleport. If the check fails, troubleshoot: Replace example.teleport.sh and example-user with the proxy and username in question. ``` $ tsh login --proxy=example.teleport.sh --user=example-user $ tsh db ls ``` You should see: ``` Name Description Allowed Users Labels Connect --------------- ----------------- ------------- ------- ------- spanner-example GCP Cloud Spanner [*] env=dev ``` If the database does not appear, verify your Teleport role permissions. See the [RBAC](https://goteleport.com/docs/enroll-resources/database-access/rbac.md) guide. --- ## Step 6/6. Connect using the service account In this step, you will create a Teleport user with access to the Spanner database, connect using the database user service account, and optionally remove stored credentials when you are done. --- TIP To modify an existing user to provide access to the Database Service, see [Database Access Controls](https://goteleport.com/docs/enroll-resources/database-access/rbac.md) --- **Teleport Community Edition** Create a local Teleport user with the built-in `access` role: ``` $ tctl users add \ --roles=access \ --db-users="*" \ --db-names="*" \ alice ``` **Teleport Enterprise/Enterprise Cloud** Create a local Teleport user with the built-in `access` and `requester` roles: ``` $ tctl users add \ --roles=access,requester \ --db-users="*" \ --db-names="*" \ alice ``` | Flag | Description | | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------- | | `--roles` | List of roles to assign to the user. The builtin `access` role allows them to connect to any database server registered with Teleport. | | `--db-users` | List of database usernames the user will be allowed to use when connecting to the databases. A wildcard allows any user. | | `--db-names` | List of logical databases (aka schemas) the user will be allowed to connect to within a database server. A wildcard allows any database. | --- WARNING Database names are only enforced for PostgreSQL, MongoDB, and Cloud Spanner databases. --- For more detailed information about database access controls and how to restrict access see [RBAC](https://goteleport.com/docs/enroll-resources/database-access/rbac.md) documentation. Log in to your Teleport cluster as the new user that you just created: ``` $ tsh login --proxy=example.teleport.sh --user=example-user ``` Connect using the service account name (without the domain suffix): (Note: `--db-name` here refers to the specific database ID within your Spanner instance.) ``` $ tsh db connect --db-user=spanner-user --db-name=database-name spanner-example ``` You should now have an authenticated connection using the impersonated service account. To remove credentials: ``` $ tsh db logout spanner-example ``` To remove all database credentials: ``` $ tsh db logout ``` ## Troubleshooting ### Could not find default credentials This error can come from either your client application or Teleport. For a client application, ensure that you disable GCP credential loading. Your client should not attempt to load credentials because GCP credentials will be provided by the Teleport Database Service. If you see the credentials error message in the Teleport Database Service logs (at DEBUG log level), then the Teleport Database Service does not have GCP credentials configured correctly. If you are using a service account key, then ensure that the environment variable `GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json` is set and restart your Teleport Database Service to ensure that the env var is available to `teleport`. For example, if your Teleport Database Service runs as a `systemd` service: ``` $ echo 'GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json' | sudo tee -a /etc/default/teleport $ sudo systemctl restart teleport ``` See [authentication](https://cloud.google.com/docs/authentication#service-accounts) in the Google Cloud documentation for more information about service account authentication methods. ## Next steps - Learn how to [restrict access](https://goteleport.com/docs/enroll-resources/database-access/rbac.md) to certain users and databases. * View the [High Availability (HA)](https://goteleport.com/docs/installation/agents/high-availability.md) guide. - Take a look at the YAML configuration [reference](https://goteleport.com/docs/enroll-resources/database-access/reference/configuration.md). * See the full CLI [reference](https://goteleport.com/docs/enroll-resources/database-access/reference/cli.md). - Learn how to [connect with a GUI client](https://goteleport.com/docs/connect-your-client/third-party/gui-clients.md#cloud-spanner-datagrip). - Learn more about [service account authentication](https://cloud.google.com/docs/authentication#service-accounts).