Cloudflare Workers VPC adds custom CA and mutual TLS for private services
Workers and Hyperdrive can now verify origins signed by a private certificate authority and present client certificates, instead of weakening TLS verification. Workers VPC remains in beta.
Cloudflare announced today, in its developer changelog, that Workers VPC can now trust a private certificate authority and present a client certificate when it connects to services in a private network. The change also applies to Hyperdrive, Cloudflare's database connection service, when it reaches a PostgreSQL database through Workers VPC. Both sources for this article are Cloudflare's own: the changelog entry dated November 18, 2026 and the Workers VPC documentation.
Workers VPC lets code running on Cloudflare Workers reach resources in a private network, such as an internal API or a database, through Cloudflare Tunnel. Each resource is registered as a VPC Service of type http or tcp.
What was missing until now
According to the changelog, Workers VPC previously trusted only publicly trusted certificate authorities and Cloudflare Origin CA. Connecting to a service whose certificate came from a private CA meant weakening verification with the verify_ca or disabled modes, and origins that required client certificates could not be reached at all.
What changes for people who build with it
- A VPC Service can reference a custom CA (certificate_authority) to verify the origin, a client certificate (client_certificate) to authenticate to it with mutual TLS, or both.
- The settings apply to HTTPS connections from http services and to TLS connections from tcp services. Cloudflare names PostgreSQL databases used with Hyperdrive, such as Amazon RDS instances that use the RDS CA bundle, as a case this covers.
- Certificates are uploaded with npx wrangler cert upload certificate-authority and npx wrangler cert upload mtls-certificate, then referenced when creating or updating the VPC Service.
- Configuration requires Wrangler 4.164.0 or later, the Cloudflare API, or Terraform provider 5.29.0 or later.
For teams that keep a database or internal service behind a private PKI, this removes the trade-off between connecting from Workers and keeping full certificate verification. An application or AI agent running on Workers that needs to query a private PostgreSQL database through Hyperdrive can now do so with verify_full, the default mode, instead of skipping hostname or chain checks.
Rules to know before switching
The documentation sets several conditions. cert_verification_mode must be set explicitly whenever a custom CA or client certificate is configured. A custom CA cannot be combined with the disabled mode; it works with verify_full or verify_ca. A client certificate can be used with any verification mode.
Updating a VPC Service replaces its complete configuration, including TLS settings. Cloudflare warns that certificate references and the verification mode left out of an update are cleared, and that an update without TLS settings returns the service to the default verification. To rotate a certificate, the documentation says to upload the new one and update the service to point at its ID; changes can take a few seconds to apply. Removing a reference or deleting the service does not delete the uploaded certificate. If a certificate does not match the origin, the connection fails instead of falling back to weaker verification, and fetch() throws an exception that includes the reason, such as CERTIFICATE_VERIFY_FAILED.
What is not known
Workers VPC is still in beta. The documentation says features and APIs may change before general availability, and that during the beta Workers VPC is free on all Workers plans. Cloudflare has not published a general availability date or the pricing that will apply after the beta. There was no independent coverage of this change at the time of writing; everything here is Cloudflare's own description.
为什么重要
- Apps and AI agents running on Workers that query private databases or internal APIs no longer have to choose between reaching a privately signed origin and full certificate verification.
- Origins that require client certificates, which Workers VPC could not reach before, can now be connected to Workers and Hyperdrive.
- An update to a VPC Service replaces its whole TLS configuration, so teams automating certificate rotation need to send every setting each time.
要点
- Workers VPC now supports a custom CA, a client certificate for mTLS, or both, on each VPC Service.
- It covers HTTPS from http services and TLS from tcp services, including PostgreSQL with Hyperdrive, such as Amazon RDS.
- Requires Wrangler 4.164.0 or later, the API, or Terraform provider 5.29.0 or later; Workers VPC is in beta and free on all Workers plans during the beta.
来源
- Cloudflare一手来源Custom CA and client certificates (mTLS) for Workers VPCdevelopers.cloudflare.com
- Cloudflare一手来源VPC Services: Custom CA and client certificates (Workers VPC documentation)developers.cloudflare.com
- workers
- mtls
- tls
- hyperdrive
- private-networks
- Cloudflare