// AI Platform Drift

Workers VPC adds custom CA and mTLS client certificate support

Cloudflare developer changelog · published 2026-11-18 07:32 UTC
WORTH KNOWING VERIFY_ONLY SECURITYAPI
WHAT CHANGEDCloudflare Workers VPC Services now accept custom certificate authority (CA) certificates and client certificates for mutual TLS. Previously, Workers VPC trusted only publicly trusted CAs and Cloudflare Origin CA, requiring verify_ca or disabled modes to connect to private CAs, and could not reach origins requiring client certificates. Configuration requires Wrangler 4.164.0 or later, or Terraform provider 5.29.0 or later.
WHY IT MATTERSExisting Workers VPC connections to private CAs that use weakened verification modes (verify_ca or disabled) can now use full certificate verification. Services requiring mTLS, including PostgreSQL databases with Amazon RDS CA bundles, become reachable where they were not before.
WHAT TO DOIf you connect Workers VPC to private certificate authorities or databases requiring client certificates, upload your CA and client certificates with wrangler cert upload, reference them in VPC Service TLS settings, and set cert-verification-mode to verify_full to replace weakened verification.
Model-reported confidence 85% (not measured accuracy) Primary source ↗ written by anthropic/claude-sonnet-4.5
Show the reasoning — raw diff, triage verdict, confidence
RAW DIFF
+## Hyperdrive, Workers VPC - Custom CA and client certificates (mTLS) for Workers VPC
+https://developers.cloudflare.com/changelog/post/2026-11-18-custom-ca-mtls/
+Wed, 18 Nov 2026 00:00:00 GMT
+
+VPC Services can now verify private services that use certificates from your own certificate authority (CA), and authenticate to services that require mutual TLS (mTLS). Previously, Workers VPC only trusted publicly trusted CAs and Cloudflare Origin CA, so connecting to a private CA meant weakening verification with verify_ca or disabled, and origins that required client certificates were unreachable.
+Upload your CA certificate and client certificate, then reference them from the TLS settings of 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
+
+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
+You can use a custom CA, a client certificate, or both. The settings apply to HTTPS connections from http services and to TLS connections from tcp services, including PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle.
+You can configure custom CA and client certificates with Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later.
+For details, refer to Custom CA and client certificates.
HOW IT WAS JUDGED
Triage signals below are model-reported assertions, preserved verbatim; they are not independent arithmetic verification.
triage verdictMATERIAL at 0.92, needed 0.5
triage reasoningNew mTLS and custom CA support removes prior workaround requirement and enables previously unreachable integrations.
signalsnew feature capability added · security/authentication enhancement · breaking change removal: previously required weakened verification (verify_ca or disabled) for private CAs, now supported natively · integration change: mTLS support for VPC Services · tool version requirement: Wrangler 4.164.0+, Terraform provider 5.29.0+ · future date: 18 Nov 2026
suppression—
triage modelanthropic/claude-haiku-4.5 ($0.00000)
writer modelanthropic/claude-sonnet-4.5 ($0.00000)