Cloudflare’s Workers VPC service now accepts a custom certificate authority (CA) and a client certificate for mutual TLS (mTLS). The change lets you keep full certificate verification while reaching private endpoints, including PostgreSQL databases accessed through Hyperdrive.
What changed in Workers VPC TLS handling
Previously, VPC services only trusted publicly trusted CAs and Cloudflare Origin CA. Connecting to a service that used a private CA required setting verify_ca or disabling verification, and services that demanded a client certificate were unreachable. The new release lets you upload your own CA bundle and a client certificate, then reference them in the TLS configuration of a VPC service. The feature is available through Wrangler 4.164.0+, the Cloudflare API, or Terraform provider 5.29.0+.
Why the change matters to engineers
AI, cloud, and platform engineers often need to call internal databases, APIs, or other services that are secured with self‑signed or privately‑issued certificates. The ability to present a client certificate also satisfies services that enforce mTLS for inbound connections. By keeping verification strict, you avoid the security trade‑offs of turning verification off, and you can integrate Workers VPC with existing PKI investments without code changes.
How to configure custom CA and client certificates
Upload the artifacts with Wrangler, then attach them when creating the VPC service. A minimal workflow looks like this:
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
npx wrangler vpc service create private-db \
--type tcp \
--tcp-port 5432 \
--app-protocol postgresql \
--hostname db.internal.example \
--tunnel-id <TUNNEL_ID> \
--certificate-authority <CA_CERTIFICATE_ID> \
--client-certificate <CLIENT_CERTIFICATE_ID> \
--cert-verification-mode verify_full
The same identifiers can be supplied via the API or Terraform resources. The verify_full mode enforces full chain validation against the uploaded CA.
Architectural and operational considerations
- Certificate lifecycle: Uploaded CA and client certificates become part of the VPC service definition. Rotating them requires a new upload and an update to the service configuration, which may cause brief connection interruptions.
- Scope of enforcement: The custom CA and client certificate settings apply to both HTTPS traffic from
httpservices and TLS traffic fromtcpservices, covering use cases such as Hyperdrive connections to private RDS instances that rely on the RDS CA bundle. - Verification mode: Choosing
verify_fullretains strict validation. If a service cannot present a full chain, you would need to adjust the mode, but that re‑introduces the security trade‑off the feature is meant to avoid. - Tooling compatibility: Ensure your automation pipelines use Wrangler 4.164.0+ or the corresponding Terraform provider version to avoid version mismatches.
Related CloudNinjas coverage: hands-on guides.
What This Means For Practitioners
With native custom CA and mTLS support, you can now integrate Workers VPC into existing private PKI ecosystems without compromising verification. Plan for certificate rotation, update your IaC scripts to include the new upload steps, and verify that your services are configured to use verify_full. Doing so preserves end‑to‑end security while extending Workers VPC to private databases and APIs that were previously inaccessible.

