Teleport
Database Access with MySQL on GCP Cloud SQL
- Version 16.x
- Version 15.x
- Version 14.x
- Version 13.x
- Older Versions
Teleport can provide secure access to MySQL on Google Cloud SQL via the Teleport Database Service. This allows for fine-grained access control through Teleport's RBAC.
In this guide, you will:
- Configure an MySQL on Google Cloud SQL with a service account.
- Join the MySQL on Google Cloud SQL database to your Teleport cluster.
- Connect to the MySQL on Google Cloud SQL database via the Teleport Database Service.
Prerequisites
-
A running Teleport cluster. If you want to get started with Teleport, sign up for a free trial or set up a demo environment.
-
The
tctl
admin tool andtsh
client tool version >= 15.2.2.On Teleport Enterprise, you must use the Enterprise version of
tctl
, which you can download from your Teleport account workspace. Otherwise, visit Installation for instructions on downloadingtctl
andtsh
for Teleport Community Edition.
- Google Cloud account
- A host, e.g., a Compute Engine instance, where you will run the Teleport Database Service
- To check that you can connect to your Teleport cluster, sign in with
tsh login
, then verify that you can runtctl
commands using your current credentials.tctl
is supported on macOS and Linux machines. For example:If you can connect to the cluster and run thetsh login --proxy=teleport.example.com --user=[email protected]tctl statusCluster teleport.example.com
Version 15.2.2
CA pin sha256:abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678abdc1245efgh5678
tctl status
command, you can use your current credentials to run subsequenttctl
commands from your workstation. If you host your own Teleport cluster, you can also runtctl
commands on the computer that hosts the Teleport Auth Service for full permissions.
Step 1/7. Enable Cloud SQL IAM authentication
Teleport uses IAM authentication with Cloud SQL MySQL instances.
If you're creating
a new MySQL instance, make sure to add the cloudsql.iam_authentication
database flag under "Customize your instance / Flags" section:
To check whether IAM authentication is enabled for an existing Cloud SQL instance, look for the flag on the Configuration panel on the instance's Overview page:
If it isn't enabled, you can add this flag using the "Edit configuration" dialog at the bottom of the Configuration panel. Changing this setting may require a database instance reboot.
Step 2/7. Create a service account for a database user
Teleport uses service accounts to connect to Cloud SQL databases.
Create a service account
Go to the IAM & Admin Service Accounts page and create a new service account:
Press "Create".
Grant permissions
On the second step grant this service account the "Cloud SQL Instance User" role which will allow it to connect to Cloud SQL instances using IAM token for authentication:
Press "Done".
Configure authentication for your service account
Now go back to the Users page of your Cloud SQL instance and add a new user account. In the sidebar, choose "Cloud IAM" authentication type and add the service account you've just created:
Press "Add". See Creating and managing IAM users in Google Cloud documentation for more info.
Step 3/7. Create a service account for the Teleport Database Service
The final part of GCP configuration is to create a service account for the Teleport Database Service.
Create a service account
If creating a new service account, go to the Service Accounts page and create another service account:
Grant permissions
Assign the Service Account the following IAM roles:
- "Service Account Token Creator" will allow the Database Service to generate IAM authentication tokens when connecting to the database as the service account user we created above.
- Either "Cloud SQL Viewer" or "Cloud SQL Admin":
- "Cloud SQL Viewer" will allow the Database Service to automatically download your Cloud SQL instance's root CA certificate, but does not support client certificate authentication.
- "Cloud SQL Admin" will allow the Database Service to automatically download your Cloud SQL instance's root CA certificate and generate an ephemeral client certificate when the GCP instance is configured to "Allow only SSL connections."
Assign it the "Service Account Token Creator" role:
"Service Account Token Creator", "Cloud SQL Viewer", and "Cloud SQL Admin" IAM roles include more permissions than the Database Service needs. To further restrict the service account, you can create a role that includes only the following permissions:
# Used to generate IAM auth tokens when connecting to a database instance.
iam.serviceAccounts.getAccessToken
# Used to check database user type.
cloudsql.users.get
# Used to auto-download the instance's root CA certificate.
cloudsql.instances.get
(Optional) Allow only SSL connections
If you intend to use "Allow only SSL connections" option on your Cloud SQL database, the service account must include the following permission to be able to generate ephemeral client certificates:
cloudsql.sslCerts.createEphemeral
GCP does not currently support granting this permission to custom roles so you'd need to assign "Cloud SQL Admin" role to the Teleport service account.
Note that "Allow only SSL connections" setting only forces the client to provide a client certificate - all communication between Teleport and the database is still over TLS even with this setting disabled.
In addition, when using Cloud SQL MySQL with "Allow only SSL connections"
enabled, Teleport connects to the database's Cloud SQL Proxy port 3307
instead of the default 3306
as the default Cloud SQL MySQL listener does not
trust generated ephemeral certificates. For this reason, you should make sure
to allow port 3307
when using "Allow only SSL connections" with MySQL.
(Optional) Create a key for the service account
You can directly attach the service account to a VM.
Alternatively, go to that service account's Keys tab and create a new key:
Make sure to choose JSON format:
Save the file. Your Teleport Database Service will need to use it as GCP application credentials file.
Step 4/7. Gather Cloud SQL instance information
To connect a Cloud SQL database to Teleport, you'll need to gather a few pieces of information about the instance.
- GCP Project ID.
You can normally see it in the organization view at the top of the GCP dashboard.
- Cloud SQL instance ID.
The instance ID is the name of your Cloud SQL instance shown at the top of the Overview page:
- Cloud SQL instance endpoint.
You will use the instance's public IP address to connect to it. It can be viewed on the "Connect to this instance" panel on the Overview page:
- (Optional) Cloud SQL instance root certificate.
The instance's root certificate is required so Teleport can validate the certificate presented by the database instance.
The Database Service can automatically download the instance's root certificate
if the service is granted the cloudsql.instances.get
permission.
Alternatively, you can download server-ca.pem
file from the Connections tab
under Security section:
Step 5/7. Create a Teleport user
To modify an existing user to provide access to the Database Service, see Database Access Access Controls
Create a local Teleport user with the built-in access
role:
tctl users add \ --roles=access \ --db-users=\* \ --db-names=\* \ alice
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. |
Database names are only enforced for PostgreSQL and MongoDB databases.
For more detailed information about database access controls and how to restrict access see RBAC documentation.
Step 6/7. Set up the Teleport Database service
The Database Service requires a valid auth token to connect to the cluster. Generate
one by running the following command against your Teleport Auth Service and save
it in /tmp/token
on the node that will run the Database Service:
tctl tokens add --type=db
Install Teleport on the host where you will run the Teleport Database Service:
Install Teleport on your Linux server:
-
Assign edition to one of the following, depending on your Teleport edition:
Edition Value Teleport Enterprise Cloud cloud
Teleport Enterprise (Self-Hosted) enterprise
Teleport Community Edition oss
-
Get the version of Teleport to install. If you have automatic agent updates enabled in your cluster, query the latest Teleport version that is compatible with the updater:
TELEPORT_DOMAIN=example.teleport.comTELEPORT_VERSION="$(curl https://$TELEPORT_DOMAIN/v1/webapi/automaticupgrades/channel/default/version | sed 's/v//')"Otherwise, get the version of your Teleport cluster:
TELEPORT_DOMAIN=example.teleport.comTELEPORT_VERSION="$(curl https://$TELEPORT_DOMAIN/v1/webapi/ping | jq -r '.server_version')" -
Install Teleport on your Linux server:
curl https://goteleport.com/static/install.sh | bash -s ${TELEPORT_VERSION} editionThe installation script detects the package manager on your Linux server and uses it to install Teleport binaries. To customize your installation, learn about the Teleport package repositories in the installation guide.
Below is an example of a Database Service configuration file that proxies
a single Cloud SQL MySQL database. Save this file as /etc/teleport.yaml
:
version: v3
teleport:
data_dir: /var/lib/teleport
nodename: test
# Proxy address to connect to. Note that it has to be the proxy address
# because the Database Service always connects to the cluster over a reverse
# tunnel.
proxy_server: teleport.example.com:443
auth_token: "/tmp/token"
db_service:
enabled: "yes"
# This section contains definitions of all databases proxied by this
# service. Can contain multiple items.
databases:
# Name of the database proxy instance. Used to reference in CLI.
- name: "cloudsql"
# Free-form description of the database proxy instance.
description: "GCP Cloud SQL MySQL"
# Database protocol.
protocol: "mysql"
# Database endpoint. For Cloud SQL use instance's public IP address.
uri: "35.1.2.3:3306"
# (Optional) path to Cloud SQL instance root certificate you downloaded
# manually above.
ca_cert_file: /path/to/cloudsql/instance/root.pem
# GCP-specific configuration when connecting a Cloud SQL instance.
gcp:
# GCP project ID.
project_id: "<project-id>"
# Cloud SQL instance ID.
instance_id: "test"
# Labels to assign to the database, used in RBAC.
static_labels:
env: dev
auth_service:
enabled: "no"
ssh_service:
enabled: "no"
proxy_service:
enabled: "no"
version: v3
teleport:
data_dir: /var/lib/teleport
nodename: test
# Proxy address to connect to. Use your Teleport Cloud tenant address.
proxy_server: mytenant.teleport.sh:443
auth_token: "/tmp/token"
db_service:
enabled: "yes"
# This section contains definitions of all databases proxied by this
# service. Can contain multiple items.
databases:
# Name of the database proxy instance. Used to reference in CLI.
- name: "cloudsql"
# Free-form description of the database proxy instance.
description: "GCP Cloud SQL MySQL"
# Database protocol.
protocol: "mysql"
# Database endpoint. For Cloud SQL use instance's public IP address.
uri: "35.1.2.3:3306"
# (Optional) path to Cloud SQL instance root certificate you downloaded
# manually above.
ca_cert_file: /path/to/cloudsql/instance/root.pem
# GCP-specific configuration when connecting a Cloud SQL instance.
gcp:
# GCP project ID.
project_id: "<project-id>"
# Cloud SQL instance ID.
instance_id: "test"
# Labels to assign to the database, used in RBAC.
static_labels:
env: dev
auth_service:
enabled: "no"
ssh_service:
enabled: "no"
proxy_service:
enabled: "no"
A single Teleport process can run multiple different services, for example multiple Database Service instances as well as other services such the SSH Service or Application Service.
Configure the Teleport Database Service to start automatically when the host boots up by creating a systemd service for it. The instructions depend on how you installed the Teleport Database Service.
On the host where you will run the Teleport Database Service, enable and start Teleport:
sudo systemctl enable teleportsudo systemctl start teleport
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.servicesudo systemctl enable teleportsudo 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
.
GCP credentials
The Teleport Database Service must have credentials for the
teleport-db-service
GCP service account we created in step 3.
If the Teleport Database Service is hosted on a VM, you can change the attached service account.
Alternatively, set the GOOGLE_APPLICATION_CREDENTIALS
environment variable to
point to the JSON credentials file you downloaded earlier. If you are using
systemd
to start teleport
, then you should edit the service's
EnvironmentFile
to include the following env var:
echo 'GOOGLE_APPLICATION_CREDENTIALS=/path/to/credentials.json' | sudo tee -a /etc/default/teleport
Step 7/7. Connect
Once the Database Service has joined the cluster, log in to see the available databases:
tsh login --proxy=teleport.example.com --user=alicetsh db lsName Description Labels
-------- ------------------- --------
cloudsql GCP Cloud SQL MySQL env=dev
tsh login --proxy=mytenant.teleport.sh --user=alicetsh db lsName Description Labels
-------- ------------------- --------
cloudsql GCP Cloud SQL MySQL env=dev
Note that you will only be able to see databases your role has access to. See our RBAC guide for more details.
To retrieve credentials for a database and connect to it:
tsh db connect --db-user=teleport --db-name=mysql cloudsql
When connecting to the database, use either the database user name or the service account's Email ID. Both the user name and the service account's Email ID are shown on the Users page of your Cloud SQL instance.
To log out of the database and remove credentials:
Remove credentials for a particular database instance.
tsh db logout cloudsqlRemove credentials for all database instances.
tsh db logout
Troubleshooting
Error when connecting to a replica instance
You may encounter the following error when connecting to a replica instance:
tsh db connect --db-user root -n test cloudsql-replicaERROR 1105 (HY000): Could not update Cloud SQL user "<username>" password:
The requested operation is not valid for a replica instance.
...
Connecting as built-in database users with passwords are not supported for Cloud SQL replica instances. Please follow this guide to use IAM authentication instead.
Next steps
- Learn how to restrict access to certain users and databases.
- View the High Availability (HA) guide.
- Take a look at the YAML configuration reference.
- See the full CLI reference.
- Learn more about authenticating as a service account in Google Cloud.