⬆️ For table of contents, click the above icon

Tailscale discovery

Runs on AWS Lambda as an readonly API that returns only hostnames and IP addresses for the devices.

Why?

Currently Tailscale's API token gives ultimate root access to your network, even allows configuring subnet routers to your devices so it would allow an attacker gaining access to the API key to expose any internal networks the Tailscale devices are connected to.

I just want to do device discovery with an readonly auth token that exposes a subset of device data. This way if the token gets exposed it is not a big deal.

Usage

• Create API key in Tailscale and set it as ENV var TAILSCALE_API_KEY
• Set your tailnet ID as TAILSCALE_TAILNET

Serve this Lambda function from Lambda. It is assumed that you have a reverse proxy in front of it that implements your authorization (even though this is not very sensitive data).

Keeping the Tailscale API key updated in Lambda

There is a CLI command which updates the API key (stored as Lambda ENV variable).

This will soon be hooked up to Cloudwatch scheduled events so it does it automatically. TODO tasks:

• Automatically request new API key from Tailscale control panel (before the old has expired)

It is a good idea to use this IAM policy for your CLI session (or Lambda handler) to limit the AWS access keys' power to only update config of this specific function. Here's the inline policy:

{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "lambda:UpdateFunctionConfiguration",
            "Resource": "arn:aws:lambda:*:*:function:WebTailscaleDiscovery"
        }
    ]
}