●Change8

Migrating to Consul Connect v1.22.5

Version v1.22.5 introduces 2 breaking changes. This guide details how to update your code.

Released: 2/27/2026

2
Breaking Changes
2
Migration Steps
4
Affected Symbols

⚠️ Check Your Code

If you use any of these symbols, you need to read this guide:

consul loginVault CA providerEnvoy TLS listener configurationwatch cache fetch mechanism

Breaking Changes

●Issue #1

Connect component migrated from aws-sdk-go (v1) to aws-sdk-go-v2. Users relying on v1 specific behaviors or APIs in custom integrations might need to update their code.

●Issue #2

HTTP server timeouts are now configured by default to prevent Slowloris attacks on agent HTTP and pprof endpoints. If existing applications relied on very long or infinite timeouts, they might now experience connection closures.

Migration Steps

  1. 1
    If you are using AWS SDK integrations within Consul, review changes related to the migration from aws-sdk-go (v1) to aws-sdk-go-v2.
  2. 2
    If your application relies on extremely long or unconstrained HTTP timeouts for agent HTTP or pprof endpoints, review the new default HTTP server timeout configurations and adjust if necessary.

Release Summary

This release focuses heavily on security improvements, including patching Vault CA provider vulnerabilities, configuring HTTP server timeouts, and upgrading the base Go version. It also includes dependency updates for AWS SDKs and fixes for Envoy certificate handling.

Need More Details?

View the full release notes and all changes for Consul Connect v1.22.5.

View Full Changelog