Skip to content

Cloudflare Workers VPC can now trust a private CA and use mTLS

VPC Services can present a client certificate and trust a private certificate authority, so Workers no longer have to disable TLS verification to reach internally secured databases.

Source: Cloudflare

Cloudflare Workers VPC Services can now authenticate connections with a private certificate authority and present a client certificate for mutual TLS. Until this release, VPC Services only trusted publicly trusted CAs and Cloudflare’s own Origin CA, so reaching a private service meant dropping to verify_ca or disabled verification instead.

You upload the certificates with Wrangler, then reference them when creating or updating a VPC Service:

npx wrangler cert upload certificate-authority --ca-cert ./ca.pem --name private-ca
npx wrangler cert upload mtls-certificate --cert ./client.pem --key ./client-key.pem --name private-client

A custom CA, a client certificate, or both can be attached to a service, and an explicit --cert-verification-mode (such as verify_full) is required whenever either is set. The change ships in Wrangler 4.164.0, the Cloudflare API and Terraform provider 5.29.0.

Why it matters: if you connect to a privately hosted Postgres or MySQL instance, say on Amazon RDS, that’s secured with an internal CA or requires client certificates, you can now verify that connection properly from a Worker instead of weakening TLS to get it working. That also extends to Hyperdrive, which sits on top of Workers VPC for database access.

Share

Related reading

More from The Wire

All briefs